Diagnosis → Plan → Implementation → Control
A lot of people think consulting is calls, slide decks, and smart-sounding words. Sometimes it is. But that’s not consulting, that’s paid therapy for a CEO.
Real consulting is setting up a management system that produces outcomes: deadlines become more predictable, the team stops drowning in chaos, and the CEO stops acting as the dispatcher for literally everything.
The most workable model is simple: diagnosis → plan → implementation → control.
1) Diagnosis: Find Where Results Leak
The goal of diagnosis is straightforward: understand why “there’s a lot of work, but very little impact.”
What happens in practice
- Interviews with the CEO and key roles (sales, delivery/operations, finance, HR).
- Review of 10–20 real cases: projects, tasks, “fires,” stuck decisions.
- Map of processes “as-is”: task setting, approvals, control, communication.
- Metrics check: what you measure and what you don’t see (blind spots).
- Role audit: who makes decisions, who owns outcomes, who is just “in the loop.”
What you usually find (almost always)
- No process owners (everyone helps, nobody is accountable).
- Too many priorities, everything is “urgent.”
- Tasks without a clear “done” definition and no deadline.
- Decisions aren’t documented and agreements get forgotten.
- Control is situational, there’s no consistent operating rhythm.
- Metrics aren’t tied to goals (or there are 50 metrics that change nothing).
Diagnosis output (artifacts)
- Top 10 problems with root causes (not symptoms, causes).
- Bottlenecks along the chain: “idea → task → execution → result.”
- Quick wins for the next 7–14 days.
- Risk list: where you lose money/time/quality.
2) Plan: Turn the Diagnosis Into an Implementation Queue
A diagnosis without a plan is just “we understood everything” and nothing changes.
What the plan includes
- One measurable 90-day goal (not “growth,” but something concrete: margin, speed, conversion, fewer overdue items).
- 2–3 bets: key changes that move the goal.
- Implementation backlog: what happens first, what comes later.
- RACI/owners: who is responsible for implementation and outcomes.
- Definition of Done: what counts as “implemented,” not “discussed.”
- Stop-doing list: what you drop to create time and focus.
A common mistake
They plan “everything at once.” Result: they implement nothing.
Survival rule: fewer initiatives, but finish them into a working routine.
3) Implementation: The Hardest Part and the Only One That Matters
Implementation is the moment of truth. This is where you discover the company doesn’t run on documents, it runs on habits.
What “adult” implementation looks like
- Set a management rhythm:
- weekly planning (30–60 min),
- task/blocker status (15–30 min),
- problem-solving review (60 min),
- monthly metrics/priorities review.
- Introduce one task standard:
- goal, expected outcome, deadline, owner,
- “done” criteria,
- priority and dependencies.
- Assign process owners (onboarding, sales, delivery, finance, support).
- Remove the “grey zone” where decisions live in private chats and disappear.
- Train key people and run the first cycles together (otherwise it snaps back).
What must be true for this to count as “implemented”
- The team actually follows the rules for 2–4 consecutive weeks.
- Tasks stop disappearing.
- Decisions are documented.
- Metrics get updated on schedule.
- Blockers and owners are visible.
If you don’t have that, it wasn’t consulting, it was “a nice talk.”
4) Control: So It Doesn’t Slide Back
Control isn’t needed because “people are lazy.” It’s needed because any system without control falls apart.
What control looks like in real life
- Weekly execution check (plan vs actual).
- Monthly metrics review and priority adjustment.
- Quality control: spot-check cases/tasks/projects.
- Follow-up on problems: what was fixed, what wasn’t, and why.
Minimal control metrics (example)
- % of tasks completed on time;
- number of blockers older than X days;
- execution speed (cycle time);
- quality (repeats, rework, returns);
- load: where the team is overloaded and why.
What the Business Gets Out of It
When it’s done properly, five effects usually show up:
- Transparency: you can see what’s happening and where it breaks.
- Focus: fewer parallel initiatives, more finished outcomes.
- Speed: shorter time from “idea” to “result.”
- Quality: fewer reworks and fewer “fires.”
- CEO relief: management stops being held together by one person.
Who Needs This Most
- The CEO is tired of firefighting and wants a real operating system.
- The company grew, but management stayed “charisma-based.”
- Deadlines keep slipping and accountability is blurry.
- The team is busy, but outcomes don’t match the effort.
- You tried processes, but they keep rolling back.
FAQ
How long does the diagnosis → plan → implementation → control cycle take?
Early improvements usually show up in 2–4 weeks. A stable effect typically needs 1–2 quarters. If someone promises “a full system in 3 days,” that’s usually stage magic for optimists.
How do you know you need consulting, not just “more people”?
If new hires drown in the same chaos and speed doesn’t improve, the problem is the management system, not headcount.
What should the result be, besides a report and a presentation?
Artifacts people actually use: meeting rhythm, task templates, process owners, metrics, escalation rules, a knowledge base. Most importantly: team habits that don’t collapse in a week.
Why does implementation often “not stick”?
Because people write documents without embedding them into routine: no owners, no control, no metrics, no stop-doing list. Teams return to familiar chaos because it’s easier.
Can you implement a management system without bureaucracy?
Yes. “System” doesn’t mean “100 policies.” A minimum viable system is a handful of rules repeated weekly that produce predictable outcomes.
