The Internal Owner Every Rollout Needs
The role nobody advertises for and every successful rollout has. What the owner actually decides, how much time it genuinely takes, why it should not be the IT person, and the six decisions to hand them in writing on day one.
Rollouts do not stall on hard problems. They stall on small ambiguous ones that nobody has the authority to settle — whether the storekeeper may write off a broken carton on his own word, whether a delivery that arrives without its order number gets received anyway, which of two nearly-identical item records survives. Each takes thirty seconds to decide and three weeks to escalate.
The owner is the person who decides those in thirty seconds. That is the whole job description, and it is why sponsorship is not a substitute: an MD can approve a budget but will not be available for the forty-first question about item naming.
Who it should be
Usually
the operations or finance manager
They live with the consequences of the answers, they already arbitrate between the store and the office, and they will be personally embarrassed if the figures are wrong. That embarrassment is the mechanism.
Sometimes
a senior storekeeper or head of stores
Works well in stock-heavy businesses where the store is the operation. Needs explicit authority over people senior to them, granted publicly, or every decision gets re-litigated upwards.
Rarely
the MD, and only under about fifteen staff
In a genuinely small business the MD is the operations manager. Above that, they will not be available for the volume of small decisions and the project will queue behind their diary.
Almost never
the IT person
They can make the system work and cannot decide whether a short delivery gets received. Giving them the role converts every business decision into a technical one, and the business then experiences the system as something IT did to them.
The six decisions to hand over in writing
Authority that has not been written down is authority that gets tested at the worst moment. Six statements, on one page, signed by whoever is above them — this takes twenty minutes and prevents most of the escalation.
What the owner decides alone
Decision Why it has to be theirs
Item naming and which duplicate survives Because a committee produces three conventions
Which module goes live next, and when Because the person watching adoption knows when it is boring enough to add another
Approval thresholds, within a stated range Because thresholds get tuned in the first month or never
Whether a specific person gets a specific permission Because the alternative is everyone being made an administrator on a Friday
When the old process stops Because only they can see whether it has actually stopped
What counts as done for each phase Because otherwise the vendor decides, and the vendor's definition is delivery
What is deliberately not on this list: spend. The owner should not be authorising extra modules or paid work — that stays with whoever holds the budget, and separating the two protects the owner from being the person who kept saying yes.
The time, honestly
What the role actually costs, 40-staff business, two modules
The steady-state two hours a month is the part nobody plans for and the part that keeps the system honest — reading the dead-stock report, checking who has accumulated permissions, noticing that the reorder points were set in a different demand environment. It never appears in an implementation plan because it starts after the plan ends.
And the corollary: those days have to come off something else, visibly. An owner given the role and no relief will do their existing job and defer the rollout, which is the correct individual choice and a project-level failure. Announce what they are being taken off, so the organisation can see the trade-off was deliberate.
What the owner is not
Four misreadings of the role
The owner as data entry clerk
The misreading
They end up keying everyone's movements because they are fastest at it.
What it produces
You have digitised the paper book and added a step. The owner's job is to make other people enter their own work, which is a management task, not a keyboard one.
The owner as first-line support
The misreading
Every question routes to them, all day, forever.
What it produces
They become a bottleneck and stop doing the deciding. The fix is training people to teach the next person, so the answer lives near the question.
The owner as the person who signs off the vendor
The misreading
They are asked to confirm delivery of work they did not scope.
What it produces
Conflict of role. The owner should say whether the phase works for the business; whoever holds the budget says whether the vendor gets paid.
The owner as a committee
The misreading
Three names on the plan, "jointly responsible".
What it produces
Nobody. Small ambiguous decisions cannot be made jointly at the speed they arrive — a committee will settle the item-naming convention in a month, by which time three conventions are in the data.
The handover problem
Owners leave. It is the most common way a working implementation degrades a year later: the person who knew why the thresholds were set where they are moves on, nobody inherits the two hours a month, and the system slowly becomes something everyone uses and nobody tends.
The defence is unglamorous and effective. Keep the one page — the six decisions, the roles, the thresholds, the phase definitions — as a live document with a date on it. Have the owner add a line whenever they decide something that took thought. When they leave, that page is the handover, and it takes an afternoon rather than a quarter. Without it, the successor's first instinct is to change things they do not understand, which is how a tuned configuration becomes a default one.
One thing to ask candidates for the role
"When the figures are wrong, will you want to know?" It sounds soft and it is the whole test. Some people find a discrepancy interesting and some find it threatening, and the second kind — however competent — will manage the appearance of the numbers rather than the numbers.
Our take
One person, named publicly, from operations or finance rather than IT, with six decisions handed to them in writing and about twelve to fifteen working days freed up across the rollout — plus two hours a month permanently, which is the part everybody forgets and the part that keeps the configuration honest. Keep their one page alive, because it is also the handover when they leave.
Tell us who will own it before we quote
It is the first question we ask, and if the answer is a committee or the IT manager we would rather discuss that than start. Rollouts with a named owner and freed-up time succeed at a rate that has nothing to do with which software they chose.
See plans & pricingFrequently asked questions
Who should own an ERP implementation internally?
Usually the operations or finance manager — someone who lives with the consequences of the answers and will be personally embarrassed if the figures are wrong. A senior head of stores works in stock-heavy businesses, provided their authority over more senior people is granted publicly. The MD only under about fifteen staff. Almost never the IT person, because they can make the system work but cannot decide whether a short delivery gets received.
How much time does the owner need?
Roughly twelve to fifteen working days across a three-month rollout: two half-days a week early on, one half-day a week during the parallel run, plus the count day. Then about two hours a month permanently — reading the dead-stock report, checking accumulated permissions, revisiting reorder points. That steady-state time is the part no implementation plan contains, because it begins after the plan ends.
Can two people share the role?
Not well. The decisions that stall a rollout are small, ambiguous and arrive constantly, and they cannot be made jointly at that tempo — a pair or a committee will settle the item-naming convention in a month, by which time three conventions are already in the data. Two people can divide by module, with one of them named as the tie-breaker.
What authority does the owner need in writing?
Six things: item naming and duplicate resolution, which module goes live next and when, approval thresholds within a stated range, individual permission grants, when the old process stops, and what counts as done for each phase. Deliberately not spend — extra modules and paid work stay with whoever holds the budget, which protects the owner from being the person who kept saying yes.
What happens when the owner leaves?
This is the most common way a working implementation degrades. The defence is a live one-page document — the six decisions, the roles, the thresholds, the phase definitions — with a line added whenever the owner decides something that took thought. That page makes the handover an afternoon instead of a quarter, and it stops a successor changing a tuned configuration back to defaults because they cannot see why it was tuned.
Should the owner do the data entry?
No, and it is the most common way the role goes wrong. If the owner ends up keying everyone else's movements because they are fastest, you have digitised the paper book and added a step. Their job is to get people entering their own work same-day, which is a management task rather than a keyboard one.
