#VS-03A
VXVX-lead
Measure before you change
No intervention is proposed until we can show, in numbers, where capacity is being consumed. Opinions are welcome; they are not evidence.
Method over slogans
Productivity programs fail when they start with a reorganisation chart. Ours starts with the work. Four principles and a five-stage cycle keep engagements honest.
story points80%
definition of done
Four principles we will not trade away
#VS-03B
VXVX-lead
The front line is the expert
The people doing the work know where it breaks. We shadow, interview and observe before we redesign anything.
#VS-03C
VXVX-lead
Small teams, close to the work
Two to four consultants, embedded with the client team. Large teams distance us from the operating reality we are paid to understand.
#VS-03D
VXVX-lead
Leave the system behind
Every engagement ends with a transfer plan naming who owns each routine and how it is reviewed. Dependency is a design failure.
The five-stage cycle
Our delivery cycle borrows its discipline from software delivery: short, bounded work with a visible definition of done. The stages run in order but overlap deliberately, because measurement often surfaces a question that reframes the scope.
#S1
VXVX-lead
Frame
Agree the question, the population and the success measure. Written jointly with client leaders so the work is owned from day one.
#S2
VXVX-lead
Observe
Shadow real workflows, run structured interviews, extract system data. We build a picture of how work actually flows, not how the process map says it should.
#S3
VXVX-lead
Quantify
Turn observation into a baseline: lost capacity, delay sources, meeting load, handoff times. This is the evidence that justifies every later change.
#S4
VXVX-lead
Redesign
Co-design the new way of working with the people who will live in it. Test in one team before scaling across the function.
#S5
VXVX-lead
Embed
Coach managers, instrument the measures, and hand over a transfer plan so the client's own leaders keep the cycle running after the sprint closes.
Working in the open
Clients see our working notes, our interview themes and our open questions while the engagement is running. There is no black box and no dramatic reveal at the end. If a hypothesis is wrong, we say so on the day we learn it, and the backlog changes accordingly. This keeps trust high and keeps us honest, because the evidence is in the room throughout.
We also insist on measuring ourselves. At the close of every sprint we review three things with the client sponsor: did the measured signal move, did the client team learn something it could reuse, and did the transfer plan hold at day ninety. If any of the three is weak, that is the first item on the next sprint's board — not something we quietly leave behind in a final report.
None of this is novel in isolation. The difference is the discipline of applying it consistently, at the scale of a single function or an entire operating division, without letting a tooling vendor set the agenda.