Services

Six kinds of operations support, each with a boundary.

Every service below can be commissioned on its own. An engagement covers the area we agree in writing, not the whole organization by default.

Operating Routines

Make daily, weekly, and monthly work repeatable without adding a heavy system.

What it is

Most operating trouble is not a lack of effort. It is recurring work that lives in memory, inboxes, and half-kept spreadsheets. An operating routine names the task, the person responsible, when it happens, and what “done” looks like.

We write that routine in plain language, small enough that a busy person will actually use it. The aim is a week that still runs when the person who usually remembers it is away.

How it runs

Map the week
Remove noise
Name owners
Trial two cycles
Revise the sheet

We start from the work you already do. We do not import a generic checklist and ask you to match it.

Who it is for

Teams that miss the same recurring tasks, or that depend on one person to remember how the week works.

Scope

Recurring tasks across a day, a week, and a month
A simple register of those tasks
An owner and a backup for each task
The evidence that shows the task was done
A short note on how to run the routine

Deliverables

Routine sheet
Owner and backup list
Cadence calendar
One-page running note

Handoff Design

Stop work stalling in the gap between roles, shifts, or tools.

What it is

Work is often lost not inside a task but between two people. A handoff says what moves, in what form, who receives it, and what happens if it arrives incomplete.

We design that transfer so a person who was not in the original conversation can follow it. The test is practical: a real item from your current work should move without an oral history.

How it runs

Follow one real item
Mark where it waits
Define the transfer
Try it on live work
Write the rule

We use a real request from your current work, not a hypothetical example.

Who it is for

Teams where tasks sit between people, or where “I thought you had it” is a familiar sentence.

Scope

Handoffs between roles or functions
Shift or end-of-day transfers
Requests that arrive by email or message and need an owner
The minimum information a receiver needs
A rule for incomplete work

Deliverables

Handoff rule
Minimum information list
One example of a complete transfer
Exception note for incomplete work

Vendor Coordination

Keep external partners moving without building a new procurement department.

What it is

Vendors wait when nobody owns the next step. Coordination, in this practice, is a record of who you buy from, what you are waiting for, when you chase, and who is allowed to decide.

We set a light cadence your team can keep after the engagement. We do not negotiate contracts and we do not give legal advice. We organize the operating rhythm around suppliers you already use.

How it runs

List active suppliers
Separate open items
Set chase dates
Agree decision rights
Run one monthly pass

The register covers one area of spend or delivery, not every supplier the organization has ever used.

Who it is for

Companies whose supplier follow-up lives in personal inboxes, or who discover late that an order never left.

Scope

A register of active suppliers for one agreed area
The status of open requests
Chase dates and the person who chases
What must be true before an order or a renewal proceeds
A monthly look at what is stuck

Deliverables

Supplier register for the agreed area
Open-item status sheet
Chase cadence
Decision note stating who may approve what

Quality Controls

Catch the mistakes you already recognize, before a customer or a deadline does.

What it is

A useful control is specific. It names the error, the moment it can be seen, the person who looks, and what they do when they find it. A long policy that nobody opens is not a control.

We design a short check for a known failure, then watch whether that check is possible inside the real day. If the day cannot hold it, we make the check smaller rather than adding a reminder.

How it runs

Name the real failures
Find the earliest visible moment
Draft the check
Run it on live work
Keep only what was used

We would rather leave you with one check that happens than a manual of checks that do not.

Who it is for

Operations with repeat errors, complaints, or rework, where the team already knows the usual cause.

Scope

One to three known failure points, not a whole-company quality manual
The moment the check happens
The person who performs it
The record of the check
What happens when the check fails

Deliverables

Check sheet
Failure response note
Record format
A short list of what we deliberately left out

Capacity and Scheduling

Help a team promise only the work the current week can hold.

What it is

Schedules break when every request is treated as urgent and nobody can see the load. This work makes the limits visible: what is already committed, what can still be accepted, and what must be moved.

We do not install a planning product. We leave a way to see the week and a rule for saying not yet. Estimates stay rough on purpose. A precise plan that nobody updates is less useful than a rough one revised every week.

How it runs

List commitments
Estimate the real week
Mark collisions
Write the acceptance rule
Run two weekly resets

The view covers one team or one service line. It is not an enterprise planning rollout.

Who it is for

Teams that regularly miss the dates they promise, or that cannot see who is overloaded until someone says so.

Scope

Work already committed for one team or one line of service
A simple view of load against available time
A rule for accepting or deferring new requests
The person who may change the schedule
A weekly reset

Deliverables

Weekly load view
Acceptance and deferral rule
Reset agenda
Notes on work that should leave the schedule

Operational Reporting

Replace status hunting with a brief, repeated picture of the work.

What it is

Many status meetings are a search for information that should already be written down. An operational report answers a few stable questions: what is in progress, what is late, what is waiting on someone else, and what decision is needed.

We design the report around those decisions and tie each line to a routine that produces the fact. A report with no source becomes fiction by the second week. If a line is not used, we take it out.

How it runs

List the decisions
Cut the facts
Tie each fact to a source
Trial two cycles
Remove unread lines

We will not add a metric because it looks managerial. Every line has to earn its place in the second cycle.

Who it is for

Managers who chase updates, and teams who spend meetings reconstructing the week.

Scope

The decisions the report must support
The few facts those decisions require
The source routine for each fact
Who prepares the report, and when
Who reads it, and what they are expected to do

Deliverables

Report template
Source map
Preparation note
Reading note for the person who receives it

If you are not sure which area to start with, write anyway. The engagement path begins with a conversation about one problem, and the offer explains the three shapes of work. Or contact the desk directly.