Where You Actually Are, and What to Do First
A readiness assessment and a recommended first move for each profile
The map that belonged to someone else
A CHRO we know spent a quarter copying a peer's plan almost line for line. The peer had stood on a conference stage and walked through the sequence: connect the systems, stand up the first agent, expand from there. It sounded like a finished answer, so she started where the peer had started. Six months later she was stuck, and the reason was simple. The peer's company had spent two years getting its data and its governance in order before that stage. She had not. She had copied the fifth move of a game she had not begun.
Here is the whole chapter in one line. The right first move is not the one that worked for someone else. It is the one that matches where you actually are, not where you would like to be. Most readiness failures are not failures of ambition or budget. They are the result of an honest assessment nobody ran, so the plan starts three steps ahead of the company. Before you copy anyone, score yourself.
Score yourself with a pen
Five dimensions, four levels each. Read every cell as it looks from inside a company, then circle the one that describes yours today, not the one you are working toward.
Do this alone first, then have two colleagues do it without seeing your answers. Where you disagree is more useful than where you agree. A dimension that reads level 3 to you and level 1 to your head of IT is not a level 2. It is a conversation you have not had.
| Dimension | Level 1 | Level 2 | Level 3 | Level 4 |
|---|---|---|---|---|
| Knowledge maturity | The team has read a few articles and sat through one vendor demo. | A working group can say what agentic means and why it is not a chatbot. | Leaders can name which work should stay human and defend the choice. | People argue about design tradeoffs, not about whether any of this is real. |
| Integration readiness | Employee data lives in systems nobody fully controls, and exports happen by ticket. | You have a system of record and know who owns its API, though nobody has called it. | A few systems talk through supported connections you actually trust. | An agent can read context and act across systems without a person copying fields. |
| Governance readiness | Nobody has asked what an agent is allowed to do on its own. | Legal and security have opinions but no written rule for autonomous action. | The human line is drawn: which decisions an agent may take, which it may not. | Governance is a living document that changes when an agent gets something wrong. |
| HR capability | HR runs processes; nobody on the team thinks about how work is designed. | One or two people are curious and read outside the function. | You have someone who can sit with engineering and hold their own. | HR owns process design and treats agent behavior as part of its craft. |
| Executive sponsorship | Your CEO mentioned AI in an all-hands and moved on. | A budget line exists, attached to efficiency, not to redesign. | An executive who controls process, not just tools, is asking you for a plan. | The board expects a company built differently, and HR is named in the answer. |
Do not average the five into one number. An organization that is level 3 on integration and level 1 on governance is not a level 2 company. It is a company about to connect systems it has no rules for, which is a specific and avoidable mistake.
What your shape tells you to do
Find the profile that looks most like your five circled cells. The first move is different for each, and starting on the wrong one is how the borrowed map fails.
Mostly level 1 to 2
Do not buy anything yet. Run a four-week readiness sprint instead: pick one high-stakes moment an employee dreads, map every system and form it touches today, and use it to teach your own leaders what agentic work would actually change. You are buying shared understanding, not software.
Strong on tech, weak on governance
Your connections work and nobody has said what the agent may do with them. Draw the human line before you wire one more system together. Write down, per task, which decisions an agent takes alone and which stop for a person. Governance that arrives after the first bad outcome arrives too late.
Strong on rules and sponsorship, weak on integration
You have the mandate and the guardrails but your systems do not talk. Pick a single pair, your system of record and one system of action, and prove one supported connection end to end. One agent that reads an entitlement and files a request beats a strategy deck about ten.
High everywhere except HR capability
The rarest and most fixable gap. You have money, rules, and systems, but no one in HR who can sit with engineering and design the work. Hire or grow that person now. Without them, the platform gets built to IT's model of the work, and HR spends the next two years asking for changes.
One honest read, all the way through
Take a real shape. A mid-size company scores itself: knowledge maturity level 2, integration readiness level 3, governance readiness level 1, HR capability level 2, executive sponsorship level 3. The instinct in the room is to celebrate the two 3s and start building, because integration and sponsorship are exactly the dimensions a vendor asks about first.
Read the shape instead. The strongest signals point at the build, and the weakest signal, that level 1 on governance, is the one that decides whether the build is safe. This company has the systems to connect and an executive pushing for speed, and no written rule for what an agent may do on its own. That is the tech-strong, governance-weak profile wearing a more flattering outfit. Its first move is not the pilot the sponsor wants.
So the recommended first move is the governance move, not the build move: spend the next month writing the human line for the one process the sponsor wants to pilot, get legal and security to sign it, and only then connect the two systems. The sponsorship does not get wasted. It gets pointed at the work that makes the pilot survivable. That is the whole discipline of this chapter. Let the weakest load-bearing dimension choose your first move, even when louder dimensions are pulling you somewhere else.
The next thirty days, and the ways it slips
- Score the five dimensions yourself, then have your head of IT and one skeptical peer score them without seeing your sheet. Book the meeting to reconcile the gaps before you do anything else.
- Write your shape in one sentence, in the form "strong on X, weak on Y." If you cannot, you have not finished the assessment.
- Match that sentence to a profile and commit to its single first move. Say out loud the move you are choosing not to make yet, and why.
- Put the assessment and the chosen first move in front of the one executive who controls process. You are testing whether your read of the company matches theirs.
- You score the company you want to be. Every dimension mysteriously lands at level 3, and the assessment tells you nothing because it was written to feel good.
- You average the five into a single grade, lose the shape, and pick a generic middle move that fits no real gap.
- You run the assessment, see the honest answer, and start the vendor pilot anyway because the sponsor is impatient and the demo was good.
What all of it was for
Step back from the assessment, the layers, the domains, and the approval memo, and remember what they were in service of. The goal was never a better HR function.
The goal is a company built for a different era: one where agents absorb the friction, people spend their judgment where judgment is actually needed, and the organization gets faster without getting colder. If it works, HR is remembered as the function that made that happen.
Which brings us back to the morning we opened with.
This time, Marcus gets the call at 10:40 and tells his Personal Work Agent he needs to be with his father. The request is handled in one conversation: his time off is filed under the right entitlement, his manager is notified, and the payroll implications are explained back to him in plain language before he thinks to ask. He closes his laptop and spends the afternoon at the hospital instead of fighting forms.