Worked project map
Client decision: How can a neighborhood gym add $250,000 of annual operating profit without opening another location?
Workstream 1 — Revenue: Determine whether price, membership volume, retention, classes, or personal training can add profitable revenue.
Workstream 2 — Cost: Identify avoidable labor, vendor, equipment, marketing, and overhead cost without damaging service.
Workstream 3 — Feasibility: Test customer reaction, staff capacity, implementation cost, timing, and risk.
Final pyramid: Recommend the two actions first; then show the revenue impact, cost impact, operational requirements, and risks supporting them.
What a workstream actually contains
A workstream should have five visible fields: question, owner, evidence, output, deadline. “Customer workstream” isn't enough. “Determine why weekday member visits fell and recommend two retention actions by Friday” is clear enough to manage.
Consulting begins with a client decision
A project should be framed around a decision rather than a topic. “Study the market” is incomplete. “Should the company enter the market in the next two years, and through which route?” defines an action, time horizon, and output.
From question to issue tree
Write the decision at the top. Break it into smaller questions that can collectively support the answer. For a market-entry decision, branches may include market attractiveness, customer need, competitive advantage, economics, capabilities, entry mode, and risk.
The branches should be distinct enough to analyze and complete enough to avoid omitting a decisive issue. MECE is a diagnostic, not a requirement that reality fit perfectly into boxes.
Workstreams
A workstream is one defined branch of the project. It should state:
- question;
- owner;
- evidence;
- method;
- output;
- deadline;
- decision affected.
A “customer workstream” is too broad. “Determine why enterprise customers aren't renewing and identify the two most effective retention actions” is manageable.
Hypothesis-led work
A hypothesis is a provisional answer that directs attention. It isn't a conclusion that the team protects. If early evidence suggests the problem is customer retention rather than acquisition, the team should prioritize cohort and customer work but remain willing to change direction.
Common project types
Consultants work on strategy, growth, pricing, operations, organization, technology, analytics, transactions, restructuring, risk, implementation, and transformation. A strategy project can end with a decision and roadmap. An implementation project can involve operating cadence, systems, pilots, and adoption over months or years.
Evidence and analysis
Teams use client data, interviews, market research, customer work, financial models, process observation, benchmarks, experiments, and expert knowledge. The analysis must be traceable to the recommendation. A sophisticated model isn't useful if it doesn't answer the client’s decision.
Synthesis
The final communication should lead with the answer, followed by the supporting reasons and evidence. This is the Minto Pyramid. Risks and next steps belong in the answer rather than being hidden at the end.
Implementation
A recommendation should identify action, owner, timing, cost, expected impact, risk, and first checkpoint. Consulting doesn't end with a presentation when the engagement includes implementation or capability building.