Skip to content
HR community

AI readiness for HR: six questions that turn a pilot into a decision

A practical agenda for HR and business leaders to discuss AI purpose, accountability, employee readiness, feedback and evidence.

THE SHORT ANSWER

HR can assess an AI pilot by asking what work changes, which information may be used, who can reject an output, what support employees need, how problems reach an owner and what evidence will determine the next step. A useful pilot leaves a decision record, including reasons to stop or revise, rather than only a demonstration that the tool works.

Three things to take with you.

  1. Make the intended change to work explicit.
  2. Name the owner of consequential decisions.
  3. Give employees a route to question, report and improve the process.

A public question from the SOA community

SOA’s public invitation for its 15 October 2026 HR Mastermind placed employee readiness, HR ownership and the intersection of people, AI and governance on the agenda. It named Dr Jaclyn Lee, Sam Neo and Andrew Chai as contributors. That invitation establishes the questions the session intended to explore; it does not establish what anyone said in the closed-door discussion or what the group concluded. SOA event invitation

The worksheet below is an editorial extension of that public agenda. Use it before deciding whether a pilot is ready to expand.

Source context: Stories of Asia — public invitation for the 15 October 2026 HR Mastermind

1. What changed in the work?

Name one task, its user and its output. “Help managers communicate” leaves too much open. “Prepare a first draft of a routine team update for the manager to check” makes the boundary easier to inspect. Record the current steps before comparing them with the AI-assisted version. Include preparation, checking and corrections in the time comparison.

2. What information can enter the system?

List approved input types and excluded material. Check the actual account, storage location and access arrangement rather than assuming a familiar product name makes every use appropriate. If the answer depends on security, privacy or employment policy, assign it to the relevant specialist. This worksheet is a discussion aid, not approval to process sensitive information.

IMDA and the AI Verify Foundation’s 2024 generative-AI governance framework includes accountability, data, testing and incident reporting. It is background context, not a substitute for your organisation’s current policies or specialist review.

Source context: IMDA — Model AI Governance Framework for Generative AI, finalised May 2024

3. Who can reject the output?

Name a reviewer with the knowledge, time and authority to send work back. Describe what they must check. For a routine message, that might include factual accuracy, audience, tone and consistency with the approved source. Record how a rejected draft is corrected and who decides when the tool should not be used.

4. What support makes review realistic?

Ask employees to try a representative task and explain where they hesitate. Separate a training need from an access problem, unclear instruction or unreasonable workload. A person who does not trust an output may have found a useful defect. Give them a route to demonstrate it without having to defend their attitude toward AI.

5. What happens when something goes wrong?

Define where to report an incorrect answer, who responds and what requires an immediate pause. Preserve a safe, minimal record of the issue and correction. Do not circulate confidential examples merely to make the learning more vivid.

6. What evidence changes the decision?

Agree the review criteria before celebrating the result. Compare quality, total effort and exceptions alongside adoption. Keep a small decision log:

This is a practical record, not a validated scoring system. A successful demonstration is useful evidence, but it is only one observation.

Review areaRecordDecision it supports
QualityErrors and corrections against a defined standardIs the output fit for its intended use?
EffortPreparation, generation, review and reworkDoes the whole task improve?
PeopleFriction, confidence and support needsWhat must change before wider use?
BoundariesOut-of-scope inputs or attempted usesShould the pilot pause or narrow?

Before the next review

  • Bring one representative example and one failure or unresolved case.
  • Label observations, assumptions and decisions separately.
  • Assign an owner to every missing piece of evidence.
  • Choose explicitly: continue, revise, pause or stop.
COMMON QUESTIONS

A little more clarity.

Should HR own the entire AI programme?

Not by default. HR can lead people-related questions while working with business, technology, security and other relevant owners.

Is this an AI compliance checklist?

No. It is a conversation guide. Use your organisation’s policies and appropriate specialist advice for approval, privacy, security and employment decisions.

Sources & editorial notes

The event agenda is drawn from the public SOA invitation. The expanded worksheet and examples are Stories of Asia editorial recommendations, not reported event findings, speaker quotations or a validated scoring system.

  1. IMDA — Model AI Governance Framework for Generative AI, finalised May 2024 ↗

    Governance background. The six-question discussion guide is SOA editorial guidance.

  2. Stories of Asia — public invitation for the 15 October 2026 HR Mastermind ↗

    Public agenda and named contributors only. This guide does not report private discussion findings.

Published by Stories of Asia. How we work with sources and corrections ↗

YOUR NEXT STEP

Find peers asking better questions.

Continue the discussion in an SOA HR or leadership gathering.

See the event calendar ↗