Within a week of the findings walkthrough, pick a small number of findings, give each one an owner inside your business, and lay them across 90 days in three blocks: decide and write in the first month, run one real cycle in the second, fix and lock in the third. Review progress every week for twenty minutes. That is the whole method. The rest of this article is how to do each part without the plan stalling.
Plans after an audit usually stall for one of two reasons. Either everything in the report is accepted at once and nothing moves, or the work is left with whoever ran the audit and stops when they step away. The plan below avoids both by being small and by belonging to your own team.
Week one: choose what goes in
Start with the gap register and the roadmap from the HR process audit. Do not reopen a debate about every finding. Ask three questions of each one and pick the few that answer best.
- 1
Does it block other fixes?
Some gaps sit upstream of others. If nobody owns the employee master record, fixes to payroll inputs or reports will keep failing. Upstream gaps go first, even when they are not the most visible.
- 2
Is it causing pain this month?
A finding people feel, such as a payroll input that gets rebuilt every cycle, earns goodwill for the whole plan when it is fixed. Include at least one of these.
- 3
Can it be done with the people you have?
If a fix needs a system you have not bought or a person you have not hired, the fix does not belong in these 90 days. Put the decision to buy or hire in the plan instead.
Everything you leave out goes on a deferred list with a review date. Writing it down matters. It tells the team that the other findings were heard and scheduled rather than ignored, and it stops them creeping back into the plan halfway through.
Turn each finding into a change someone can own
A finding describes what is missing. A plan needs what will be done. Rewrite each chosen finding in the form below before any work starts. The example is illustrative, not taken from a client.
FINDING Leave requests from the warehouse team
have no named approver.
CHANGE Each warehouse supervisor approves leave
for their own shift, with the operations
head as deputy.
OWNER Operations head
APPROVER Founder
FINISH End of week 4
DONE WHEN One full month of warehouse leave shows
a named approver on every request.The format is the point: one owner who does the work, one approver who signs it off, a finish date, and a test of done that someone else could check. If you cannot write the done-when line, the change is not clear enough to start.
The owner should be a line manager or the person who runs the process, not the consultant and not the founder by default. Whoever runs the process every month is the person who has to keep it running after day 90.
Days 1 to 30: decide and write
The first block is about decisions, not documents. For each change, settle four answers: who does it, who approves it, by when, and where the record sits. Then write the shortest version of the rule that a manager could follow without asking anyone.
- Draft one page per change, not a policy manual. A long document in month one usually means the decisions have not been made yet.
- Show the draft to the two or three people who will use it, and change it after their questions.
- Tell managers what is changing and from when, before the first cycle runs under the new rule.
Days 31 to 60: run one real cycle
Run the next real occurrence under the new rule: the next month-end, the next few joiners, the next exits. Do not pilot on invented cases. Real cycles expose what drafting misses, such as the deputy who is also on leave or the form nobody can find.
Ask each owner to keep a simple log during the cycle: what happened, what did not follow the rule, and why. The log is the most useful output of the 90 days, because it shows whether the rule was wrong or whether people did not know about it. Those two problems need different fixes.
Days 61 to 90: fix and lock
Change the rule wherever the cycle showed it was wrong. Then lock it: put the final version where people will find it, brief anyone who joined during the cycle, and if you use an HR system, configure it to the rule as it now stands rather than as it was first drafted.
At day 90, check each change against its done-when line. A change is finished when the evidence exists, not when the document is written. Changes that are not finished move into the next 90 days with a one-line note on what got in the way.
The weekly review
Twenty minutes, on the same day each week, with the owners and one person who can make decisions. Ask three questions of each change: what moved, what is stuck, and what decision is needed from this room. Record each decision in one line. A monthly meeting is too far apart for a 90-day plan, because by the time it meets, a stuck change has lost a month.
When something urgent arrives, and something will, the review decides openly whether a change pauses. Pausing is acceptable. Quietly dropping a change because nobody mentioned it is how plans fade.
CHANGE OWNER STATUS STUCK ON
-------------------------------------------------
Leave approver Ops head on track -
Joining pack HR exec stuck IT access list
Payroll cut-off Accounts paused month-end close
DECISIONS THIS WEEK
1. IT head to send the access list by Friday.
2. Cut-off change resumes from the next cycle.When to bring outside help back in
Most of the plan should be run by your own people. Outside help earns its place at three points: when a change needs a design decision the team has not made before, when two owners disagree and need a neutral view, and at day 90 to check what has held. A periodic re-assessment is part of the HR process audit engagement for that reason, and where a change needs a process designed rather than tidied, HR process consulting picks up the work.
