Five operations management services, each with a defined scope.
Natalia Cerednicenco designs the way a chosen flow is routed, ruled, and reviewed. The services below can be commissioned separately after an Operating Brief, or in sequence. Each one states who it is for, what happens, and what you can hold at the end. Fees are quoted in writing. The offer page explains that step.
Operating model and decision rights
This service makes it obvious who may promise a date, spend capacity, change sequence, and accept an exception. It is the right first design when the route is roughly known and the arguments are about authority.
Purpose
Move decisions to the person who has the information, and name the few decisions that stay with a manager. The inbox of the owner stops being the default routing system.
Scope
One operation or one family of orders, the roles that touch it, and the decisions that currently float. Organisation-wide restructuring, employment contracts, and pay design are outside this service.
Process
List the decisions that recur in a normal month, using real jobs rather than a blank chart.
Mark where each decision sits today, and where the information for it actually is.
Draft a decision chart and an escalation path.
Test the draft against recent exceptions and revise the lines that fail.
Deliverables
A decision chart, a short escalation path, a list of decisions returned to the front line, and a list that stays with a named manager. Each line names the role, not a hope that “the team” will decide.
Intended customer
Owner-led companies in which unusual requests still arrive in one person’s messages, and managers who are ready to give a decision away once the rule is written.
How it is commissioned
Usually after an Operating Brief, or when the client can already point at the decisions that collide. The sequence of an engagement is on the engagement page.
Work routes and handoffs
This service gives one family of jobs a visible path and a standard for what “done” means before the job is allowed to move. It is the right service when work dies between desks.
Purpose
Replace the partial story that travels by memory with a handoff the next station can accept or refuse. Refusal is a status, recorded in the open, with an owner.
Scope
One flow from the moment a commitment is accepted to the moment it is closed. Neighbouring flows are noted where they share a constraint. Building a software workflow, and redesigning the product itself, are outside this service.
Process
Walk the flow with the people who touch it, including the stations that are usually skipped in a tidy description.
Write the current route, including the informal queues.
Agree the future stations and the waiting states that are allowed.
Write a handoff standard for each station: what must be true, what information moves, and who receives it.
Deliverables
A route map, a handoff standard per station, and the short list of statuses a job is allowed to be in. The map is short enough to be used in a meeting, not only filed.
Intended customer
Operations where sales, production or delivery, and invoicing each hold a different version of the job. Also project teams whose “almost done” has no definition.
This service ties promises to a constraint the team can see. A schedule that ignores the constraint is a wish list, and the practice treats it as one.
Purpose
Make the scarce resource visible — a crew, a machine, a specialist, a dock, a review slot — and stop the company from promising more of it than the week contains.
Scope
The constraint that governs the chosen flow, the queue in front of it, and the rule for promising dates against it. Full materials planning, warehouse slotting software, and payroll modelling are outside this service.
Process
Find the constraint by looking at where work actually waits, not where the organisation chart suggests it should wait.
Describe capacity in units the team already counts: hours, slots, pallets, visits, cases.
Set a queue limit and the response when the queue is full, including what sales may say.
Trial the rule on live work during the cadence, and adjust the unit if the team will not use it.
Deliverables
A capacity picture for the chosen constraint, a scheduling rule, a visible queue with a limit, and the sentence people use when the queue is full.
Intended customer
Teams that miss dates because every request is accepted, and planners who are asked to “fit it in” after the promise has already been made.
How it is commissioned
Alongside the route, or immediately after it. The promise rule on the decision chart has to match the queue limit or the two papers will contradict each other.
Management cadence
This service installs the meetings and the one-page view that keep the route honest after the design weeks end. A map without a cadence is a souvenir.
Purpose
Give managers a repeating forum where promises, blockers, and exceptions are compared with what moved. The forum is short enough to survive a busy week.
Scope
The meetings required to run one flow, the page or board those meetings use, and the coaching needed until a named manager can run them. Company-wide performance frameworks and bonus schemes are outside this service.
Process
Draft the calendar: who attends, how long, and which decision each meeting is allowed to make.
Design the one-page view from the route, the queue, and the exception log.
Run the meetings with the team until the page matches the floor.
Hand the chair to the named manager and attend as a guest until the close.
Deliverables
A cadence calendar, an agenda for each meeting, the one-page board or sheet, and a short guide so a manager can run the meeting without the practice in the room.
Intended customer
Teams that have already described their process and then returned to the old habits, and owners who want the new rules used when nobody is visiting.
How it is commissioned
As Rhythm Installation, after the route and the rules exist in a form the team accepts. The pattern of a week is described on the engagement page.
Exception control and rework
This service separates normal work from one-off rescues, and reduces the repeat fixes that eat the week. An exception without an owner becomes the way the company actually works.
Purpose
Define what counts as normal, give every exception an owner and an age, and turn repeating exceptions into a change to the route rather than another heroic afternoon.
Scope
The exception types on the chosen flow, the log used to age them, and the rework reasons worth tracking. Quality certifications, laboratory methods, and legal claims handling are outside this service.
Process
Agree a plain definition of an exception, with examples taken from the last month.
Separate rework (the job returns to a station) from a true exception (the route has no station for it).
Install a log: type, owner, age, and the decision to absorb it or change the rule.
Review the log in the cadence until the same cause stops appearing as a surprise.
Deliverables
An exception definition, a log with owner and age, the rework reasons the team will actually mark, and a rule for when an exception becomes a permanent change to the route.
Intended customer
Teams whose week is consumed by side-door requests and repeat fixes, and supervisors who can describe the rescue and cannot describe the normal path.
How it is commissioned
With the route, or as a focused follow-on when the cadence shows that exceptions are the real product. Start with the contact form if you already know this is the pressure.
Choosing where to start
If the operation is hard to describe, start with the Operating Brief. If you can already name the flow and the failure — dates, handoffs, authority, or rework — say so in the enquiry and the quotation will aim at that service. The practice will narrow the scope rather than sell all five at once.