LO
Business systems owner — tasks, one by one
The unit of analysis is the task, not the job title. Each one below carries its direction, whether the judgement rests on evidence or on platform inference, the reasoning, and what it does not establish.
Every task on this page#
Shaping the process inside the system
Being augmented✓ Evidence-backedTurning how the business actually works into stages, fields, rules and permissions — and deciding what the system will refuse to let someone do.
Building the configuration got much cheaper: describing a workflow in words and getting the objects and automations back is squarely what these tools do. Knowing which of the described steps is the one people actually skip, and why, did not — that is learned by watching the team, not by reading the process document.
Faster configuration means more configuration, not less work. Every rule added is a rule that will later be wrong and have to be found — so the role's hours move from building to untangling, and untangling is invisible on a roadmap.
Keeping the records worth trusting
Automating≈ Platform inferenceDuplicates, half-filled fields, statuses nobody updates, three spellings of the same customer — finding them and deciding which version is the real one.
Matching records that refer to the same real thing is entity resolution, and it is one of the clearest places current models beat rules — they handle the messy cases string matching never could. Deciding which duplicate survives when the two disagree on a number that matters is still a business call.
Cleaner data makes everything downstream more trustworthy, which is the point — and it also removes the only visible artefact of this job. Nobody notices records that were never wrong, so the work reads as an absence, which is a poor position when the budget is set.
Deciding what the system may decide alone
New task✓ Evidence-backedWhich actions the automation takes without a person — assigning an owner, scoring a lead, sending a message, closing a record — and what happens when it is unsure.
When the system only stored what people did, this decision did not exist. Now that it acts, someone has to set the boundary, and the person who understands both the configuration and the business consequence is this one. The duty arrived with the capability and was assigned to nobody.
Setting the boundary is not the same as being allowed to hold it. This role usually has the knowledge and not the authority: when sales wants the automation to send more, the person who can say no is further up, and being overruled repeatedly is how the boundary erodes without any decision ever being recorded.
Making the numbers mean something
Automating≈ Platform inferenceBuilding the reports management steers by, and being the one who knows which of those numbers is solid and which is held together by an assumption.
Writing the query and drafting the commentary are both commodity now, and asking a question in plain language and getting a chart back removes most of the request queue this role used to carry.
Self-service reporting does not remove the person who knows the number is wrong. It multiplies the number of people confidently quoting a figure whose caveat they never saw — so the work shifts from producing reports to correcting them in meetings, which is slower and harder to defend as a headcount.
Getting the team to use it properly
Still human-led≈ Platform inferenceTraining, answering the same question for the fifth time, and finding out that the reason a field is always empty is that filling it costs someone twenty seconds they do not have.
In-product help and assistants answer the how questions well. They cannot answer the why-should-I question, which is the one that actually determines whether the field gets filled — and that answer requires knowing what the person is measured on and being able to change it.
This is the first task cut when the role is under pressure, because it produces nothing shippable. Cutting it does not show up as a problem for two quarters, and then shows up as data nobody trusts — by which time the cause is no longer attributable.