Business practice
Process and workflow.
The work your firm does every day, made visible, made simple, and made to run the same way twice.
A process problem almost never looks like one. It looks like a person problem, a tool problem, or a busy season that never ends.
Most firms do not have broken processes. They have invisible ones. The work gets done because specific people remember how, and the cost of that arrangement stays hidden until one of them is out for a week. What is undocumented cannot be delegated, priced, improved, or defended in an audit.
The remedy is not a binder of procedures nobody reads. It is a small set of written, owned, measured workflows covering the work that actually costs you money. We build that set with your team, in their words, starting with the single workflow where the pain is largest.
The approach
Three words we work by.
Measure.
Before anything changes, the current state gets a number. Hours per cycle, touches per handoff, cost per instance. Measured, not estimated, because improvement claimed against a guess is a story, and improvement claimed against a baseline is a result.
Simplify.
The first draft of every fix is subtraction. Steps that exist because they always have, approvals that approve nothing, tools that duplicate tools. Automation comes after simplification, because automating a bad process just produces bad outcomes faster.
Install.
A fix is not done when it works. It is done when it runs without us: written in a procedure your team drafted in their own words, assigned to a named owner, and reviewed on a cadence that catches drift before it becomes the new normal.
The work
Four workstreams, in sequence.
Workflow mapping
The highest-cost workflow documented as it actually happens, including the workarounds nobody mentions in meetings. The map is drawn from observation and interviews, then confirmed by the people who live in it.
Cost baseline
The mapped workflow gets its price tag: time consumed, error and rework rates, and where hours concentrate. This baseline is what every later claim of improvement is measured against.
Redesign and build
The future state, designed with the people who will run it. Steps removed, handoffs collapsed, and the one change most worth making built and put live, whether that is a rewritten procedure, a configuration of software you already own, or a small automation.
Procedure and cadence
The workflow written into a clear, tiered procedure, an owner named, and a review rhythm set. This is the workstream that makes the other three permanent instead of memorable.
Related reading.
All insights
Method
Why the SOP nobody reads is worse than no SOP
A procedure that does not match reality trains your team to ignore procedures. The fix is not enforcement. It is writing the document from observation of the real work, in the words of the people who do it, so that reading it feels like recognition instead of
Operations
The two-person dependency test
Pick any critical workflow and ask one question: if these two specific people were both unreachable for a week, what happens. If the honest answer is that things quietly stop, you have found the real risk register of your firm, and it does not appear in
Questions
Asked before, answered plainly.
It is the normal starting point, and it is partly why the engagement exists. We do not need documentation to begin. We need access to the people doing the work. The documentation is an output of the engagement, not a prerequisite for it, and it gets written in your team's words rather than in consulting language.
A tool automates whatever process you feed it, including a bad one. We fix the process first, then decide honestly whether a tool is even needed. In many engagements the fix is configuration of software you already pay for, or removal of steps, and no purchase happens at all.
The observation phase costs your team almost nothing, since watching work is not interrupting work. The total ask is about four scheduled hours across the engagement. The redesign is built around the team's input precisely so that adoption feels like relief from the old way, not a second job on top of it.
It is deliberately small in scope and deliberately large in proof. One workflow, measurably improved, with the discipline installed to repeat the method, beats ten recommendations that stay recommendations. The ninety-day roadmap sequences everything else. The single fix is what makes the roadmap believable.
Because the engagement does not end at the fix. It ends at the structure around the fix: a written procedure, a named owner, a review cadence, a team session so the knowledge is shared, and sixty days of coverage if the fix breaks inside scope. Durability is designed in, not hoped for.