4 phases.
One goal:
your autonomy.
Proven across more than 30 engagements. Framed in time. The first operational decisions land during the diagnosis, not in month three.
Duration depends on the scope of the work. It is set during scoping, not before.
Everything is connected.
Not everything needs rebuilding.
We look at the system as a whole. Then we step in where the leverage is highest.
No transformation for transformation’s sake.
No new tool by reflex.
No 80-page audit before acting.
Diagnosis & scoping
See the system before touching a single brick.
We look at how the work comes in, flows, gets decided, gets documented and gets measured. Only then do we decide where to step in.
- Targeted interviews with 3 to 5 key people: head of legal, practitioners, IT, security, finance, executive sponsor if relevant
- Quick mapping of current critical workflows
- Identification of priority pain points and those that can wait
- Impact
- What does it actually change?
- Effort
- What does fixing it take?
- Dependencies
- What is it blocking, or what has to be settled first?
The best first move is not always the most visible one. It is the one that unblocks the rest.
Co-build
Build with the people who will have to live with it.
Adoption starts during design, not at training. A system nobody uses is not a successful system.
- Co-build sessions with the teams who will use the tool
- Rapid prototyping: playbooks, dashboards, workflows, Q&A agents
- Testing in real conditions on a sub-scope
Roll-out
Not a pilot. A new habit.
Progressive rollout, training on real work, support through go-live. We do not install a tool: we install a way of working that outlasts us.
- Gradual rollout by team or file type
- Hands-on training in daily use
- Close support during the production rollout
Measure and transfer
Does it work? Does it work without us?
Two questions, two answers expected. A system that only runs with the consultant is not a successful system.
- Measurement of the success indicators defined in phase 1
- Full documentary handover (architecture, maintenance, possible evolutions)
- Training of internal champions on maintenance
Before and after, on the indicators set at the start. Time, turnaround, workload, cost, quality, adoption.
Documentation, architecture, maintenance, training of internal owners, skills handover.
The diagnosis changes.
The method does not.
Start with the right problem.
One hour to look at your system, identify what genuinely deserves to be tackled first, and what can wait.
1 hour to see clearlyNo commitment. No audit first.