Approach
How a McBix engagement runs.
Four phases. One engagement. Every discipline — process improvement, project delivery, SOP development, change management — applied where and when the project needs it.
01
Discovery
2–4 weeks
Current-state mapping. Where the hours go, where the friction is, what's actually working.
- Stakeholder interviews with the people doing the work — not just the people sponsoring the project
- Process mapping: every step, every handoff, every wait time
- Data collection: cycle times, error rates, volume, cost per transaction
- Root cause analysis: not what's broken, but why it's broken
- Deliverable: a current-state assessment with a prioritized improvement plan and realistic timeline
02
Rollout
8–16 weeks
System implementation with project management rigor. Timelines, milestones, risk mitigation.
- Project charter with scope, timeline, milestones, and success criteria
- Sprint planning and execution — actual iterative delivery, not Agile theater
- Vendor coordination: we manage their timeline so you don't have to
- Risk and dependency management: problems surfaced before they stall the project
- Weekly status reporting: where we are, what's next, what needs a decision
03
SOP Rewrite
Concurrent with rollout
Every process documented, optimized, and built for the new system — not copy-pasted from the old one.
- Workflow redesign: processes rebuilt for the new system, not the old one
- SOP documentation: step-by-step procedures your team can actually follow
- KPI design: metrics tied to outcomes, not vanity numbers
- Role-specific documentation: different procedures for different roles, not one generic manual
- Version control and governance: SOPs that stay current, not artifacts that rot
04
Adoption
4–8 weeks post-launch
Change management that closes the gap between deployment and daily use. Training, coaching, measurement.
- Stakeholder analysis and communication strategy — started in Phase 01, not Phase 04
- Role-specific training tied to actual workflows, not feature tours
- Adoption measurement: usage metrics, proficiency assessments, feedback loops
- Resistance management: identified early, addressed directly
- Sustainment: post-go-live support, refresher training, process refinement
Principles
What you should expect from us.
We work inside your operations, not above them.
No fly-in, fly-out consultants. We embed with your team, use your tools, attend your standups. The engagement produces working systems, not recommendations.
We measure outcomes, not activities.
Hours saved, errors reduced, adoption rates. If we can't put a number on the improvement, we haven't improved anything.
We build for sustainment, not dependency.
Every SOP, dashboard, and process we create is designed for your team to own after we leave. We don't create consulting annuities.
We tell you what we can't do.
If the project isn't a fit, we'll say so. If we're not the right firm, we'll tell you who is. We'd rather have a good reputation than a bad engagement.
Ready to start with Discovery?
The first conversation is free, direct, and honest. We'll tell you what we see, what we'd recommend, and whether we're the right fit.