How we work
Assess. Architect. Anchor.
This structure exists because the common failure mode in advisory work is confident recommendations built on assumed facts, followed by a plan nobody owns. Separating diagnosis from design, and design from adoption, makes each phase falsifiable — and makes it possible to stop early if the findings don't justify going further.
The full sequence
- Organic conversation→
- Discovery call→
- Priced proposal→
- Assess→
- Architect→
- Anchor
Assess
- Produces
- Findings, not decisions
- Timeframe
- Typically 2–3 weeks
We map how work actually moves — not how the process document says it moves. That means interviews with the people doing it, observation of the real sequence, a review of the systems of record, and a time-and-touch model for the workflows that matter most.
The deliverable is a findings document: where time is going, which constraints are structural versus habitual, what the current state costs in hours and delay, and a ranked list of interventions with rough effort and impact.
Assess deliberately stops short of recommending vendors or committing to a build. If the findings say the answer is a process change and a two-hour training, that is what they will say.
Architect
- Produces
- A sequenced roadmap and decision tree
- Timeframe
- Typically 3–6 weeks
Architect turns findings into a plan somebody can execute. Each intervention gets a target-state design, an owner, a definition of done, and a place in a sequence that respects dependencies and the organization's capacity to absorb change.
Where tooling is required, we run a structured evaluation: written criteria set before demos, the same test data through every finalist, references from comparable operators, and a total-cost view that includes the internal work the vendor won't do.
The decision tree is explicit about branch points — if adoption in phase one lands below a threshold, phase two changes shape. Plans that assume everything goes well are not plans.
Anchor
- Produces
- Change that survives contact with the quarter
- Timeframe
- Ongoing cadence, typically 3–12 months
Most initiatives fail after the consultant leaves, not during. Anchor is the cadence that prevents it: scheduled checkpoints against the metrics defined in Architect, named internal owners, and working sessions with the managers who have to enforce the new way.
We instrument what matters — throughput, exception rates, adoption by role — and review it on a fixed rhythm rather than by exception. When numbers drift, we adjust the design instead of asking people to try harder.
Engagements end with a final review: what held, what didn't, what the organization now owns, and what should be revisited in twelve months.
Book a discovery call.
Thirty minutes on how work moves through your business today. If the fit isn't there, we'll say so.