Structured Thinking: 8 Essential Consulting Frameworks

This is a working reference guide for the analytical frameworks that unlock faster problem-solving in client engagements. Each framework solves a specific consulting challenge: from turning decisions into accountability, to drilling past symptoms to root causes, to structuring persuasive communication that actually drives action.

These are not theoretical models. They are tools you use in the room, in real time, with stakeholders watching. They are designed to be applied under pressure when stakes are high and time is short.

---

1. What-by-When (Accountability Framework)

Purpose

Vague agreements don't get done. "We'll improve customer experience" is not a plan. What-by-When converts fuzzy consensus into concrete commitments with owners, specific dates, and tracked dependencies. It is the framework that transforms a good meeting into actual work.

When to Use

• Immediately after any decision, workshop, steering committee, or strategic planning session
• When you notice people leaving the room with different interpretations of what was agreed
• During post-engagement handoff to ensure the client can execute without you
• Weekly status reviews and progress tracking
• Escalation: When commitments slip and accountability gets murky

The Structure

| Action | Owner | Deadline | Dependencies | Status | |--------|-------|----------|--------------|--------| | [Specific, verb-driven action] | [One person, by name] | [Specific date, MM/DD/YYYY] | [Blocked by? Enables?] | [On track / At risk / Complete] |

Rules That Matter

One Owner Per Action Do not write "Finance and Operations will align on the new policy." That is not an owner. That is a committee. Committees do not own accountability; they distribute it. You need a name: "Sarah Chen (Finance) leads alignment with Ops lead Marcus." This creates friction in the room sometimes, but that friction is productive—it forces the real decision about who is accountable.

Dates Must Be Specific "Next month" is not a deadline. "ASAP" is not a deadline. "End of Q2" is not a deadline when Q2 has 13 weeks. Write MM/DD/YYYY. If a deadline is truly uncertain, write the latest defensible date and flag it as "date subject to resource availability from IT" in the dependencies column. At least it is explicit.

Dependency Tracking Every action in a sequence either "enables" or is "blocked by" something else. Before you leave the room, verify that the first action has no blockers and that later actions are sequenced properly. Nothing derails a 90-day program faster than discovering in week 3 that you needed approval from the board before you could start.

Status Tracking Cadence Do not create a What-by-When and never look at it again. Review it weekly. Any item overdue by 3+ days without explanation or revised deadline gets escalated to the sponsor. This is not punishment. It is early warning that something is stuck.

Worked Example: Marketing Transformation Program

| Action | Owner | Deadline | Dependencies | Status | |--------|-------|----------|--------------|--------| | Conduct customer interview study (3 weeks, 15 interviews) | Julie Martinez (Marketing) | 02/28/2025 | None—start immediately | On track | | Compile interview findings into trend report | Julie Martinez (Marketing) | 03/07/2025 | Blocked by: customer interviews complete | On track | | Present findings and draft strategy to leadership team | Julie Martinez + VP Marketing | 03/14/2025 | Blocked by: findings report ready | On track | | Finance to model budget impact of three strategic options | Brian Walsh (Finance) | 03/21/2025 | Blocked by: strategy options finalized | At risk—needs data from Julie by 03/17 | | Board to approve chosen strategy and budget | CEO + CFO | 03/28/2025 | Blocked by: Finance modeling complete, Board agenda confirmed | On track | | Marketing operations to map talent gaps against new strategy | Marcus Lee (Ops) | 04/04/2025 | Blocked by: strategy approved, org structure decisions made | Not started—waiting on board approval | | Schedule recruiting kick-off for open roles | HR Lead Priya Desai | 04/11/2025 | Blocked by: talent mapping complete, hiring approvals in place | Not started |

Anti-Patterns to Avoid

Shared Ownership: "Marketing and Sales will work together on the segmentation model." When it fails (and it will), both teams point at the other. Instead: "Sarah owns the segmentation model. She will co-design with Sales but carries the deadline."

Vague Deadlines: "We'll finalize the proposal soon." Soon is not a date. A client executive might hear "three weeks." The project lead might hear "two months." By the time they talk again, trust is already damaged.

No Follow-Up Cadence: If you build the What-by-When and walk away, it will not be maintained. Assign a program manager or sponsor to own the weekly review. Make it 15 minutes. Same time, same day, every week. By week 3, people will stop "forgetting" their deadlines.

Circular Dependencies: "A blocks B, B blocks C, C blocks A." This happens when multiple teams are working in parallel without clear sequencing. When you spot it, escalate immediately to the sponsor. It usually means the phases were not designed correctly.

Integration: Feeding Into Status Reporting

A well-maintained What-by-When becomes your weekly status report. Count the number of items: on track, at risk, overdue. Track completions. When you roll this into a steering committee update, you have objective data about execution velocity. Red items automatically escalate to the committee. At-risk items show where you need help. On-track items build confidence.

Many consultants make the mistake of writing elaborate status narratives. Skip that. Show the What-by-When table. It tells the story faster and more honestly.

---

2. Crawl-Walk-Run (Phased Implementation)

Purpose

Every transformation looks impossible if you try to build the final state all at once. Crawl-Walk-Run breaks any initiative into three maturity stages with clear success criteria and gates between them. It makes the impossible feel inevitable.

When to Use

• Implementation roadmaps for any transformation or capability-building program
• Technology adoptions (new platform rollouts, cloud migration, system implementations)
• Organizational restructures and process redesigns
• Market expansions or new business ventures
• Skill-building initiatives across teams

The Three Phases

Crawl (Months 1–3): Foundation and Minimum Viable State

• Focus: Establish the basics, prove the concept works, minimize risk
• Scope: The 80/20—the subset of features or processes that deliver 80% of the value with 20% of the complexity
• Audience: Small group, willing early adopters, or controlled pilot environment
• Success looks like: Proof that the approach works, lessons documented, team has foundational skill
• Example: A new customer journey platform goes live for one product line, not all products
• Deliverables: Minimum viable operating model, training for pilot group, 30-day feedback loop
• Typical duration: 1–3 months

Walk (Months 3–9): Scale and Optimize

• Focus: Broaden adoption, refine based on Crawl learnings, measure performance rigorously
• Scope: Roll out to additional teams, functions, or geographies; incorporate feedback loops
• Audience: Growing user base, including early skeptics (who are now seeing results)
• Success looks like: 60–70% adoption, measurable improvement in key metrics, processes stable
• Example: Expand the platform to three more product lines, add advanced features, optimize workflows
• Deliverables: Updated playbook based on learnings, trained super-users, performance dashboard
• Typical duration: 3–6 months

Run (Months 9+): Full Capability, Continuous Improvement

• Focus: Achieve full organization adoption, embed continuous improvement mindset
• Scope: Everyone is using the system or process; it is now business-as-usual
• Audience: Entire organization or target population
• Success looks like: 85%+ adoption, sustained performance improvement, competitive advantage is clear
• Example: All product lines are using the platform; the team is running quarterly optimization sprints
• Deliverables: Embedded centers of excellence, automation of routine processes, quarterly capability upgrades
• Typical duration: 6–12+ months

Gate Criteria: Clear Permission to Move Forward

Gate from Crawl to Walk Before you scale, answer these questions:

• Is the core concept proven? (Do the metrics show improvement?)
• Is the team stable? (Have turnover or absences blown the pilot apart?)
• Are there documented learnings? (Can you tell the story of what worked and what did not?)
• Is the scalable process documented? (Is it repeatable, or was it a one-off because someone heroic drove it?)

If any answer is "no," stay in Crawl. Build the missing element. Do not move to Walk hoping to fix it later.

Gate from Walk to Run Before full rollout, verify:

• Has adoption reached at least 50–60%? (If it has not reached half the target audience, something is wrong. Find out what.)
• Are there measurable results? (Revenue up, cost down, cycle time shorter, quality higher—pick your metric.)
• Has the team internalized the new way of working? (Or are they just executing the process because you are watching?)
• Is the change sustainable without ongoing consulting support? (This is the true test of readiness.)

The 80/20 of Complexity Principle

Never start with the full feature set or the complete process redesign. Identify the 20% of the new capability that delivers 80% of the value. In Walk, you add the next 30%. In Run, you add the rest. This buys you time to build organizational readiness while still demonstrating early wins.

Example: New procurement platform

• Crawl: Basic purchase-to-pay for routine office supplies (high-volume, low-complexity category)
• Walk: Expand to MRO (maintenance, repair, operations) and expand approval workflows
• Run: Add strategic sourcing, supplier management, contract tracking, analytics

The hard parts (strategic sourcing, supplier relationships) are saved for Run, when the organization has momentum and training is embedded.

Worked Example: Digital Transformation of a Procurement Function

Crawl (Jan–Mar 2025): Proof of Concept

• Scope: Implement new e-procurement platform for indirect spend (office supplies, IT equipment)
• Pilot: One business unit (150 people), 8 super-users trained
• Timeline: Platform selection (2 weeks) → Configuration (4 weeks) → Pilot go-live (2 weeks) → Feedback (2 weeks)
• Key action: Build a case study showing cost savings and process time reduction
• Gate review date: 03/31/2025
• Success criteria: 70% of pilot users able to place orders without help desk support; 15% cost reduction in pilot category

Walk (Apr–Aug 2025): Scale and Optimize

• Scope: Roll out to all business units; add supplier catalog and real-time spend visibility
• Users: Full procurement team (30 people) + 80 decentralized requesters across all units
• Timeline: Roll-out planning (2 weeks) → Expanded training program (4 weeks) → Phased go-live across units (6 weeks) → Stabilization and optimization (6 weeks)
• Key action: Build feedback loop; hold monthly "optimization sprints" with super-users
• Gate review date: 08/31/2025
• Success criteria: 65% self-service rate; average order cycle time reduced from 5 days to 2 days

Run (Sep 2025+): Full Capability and Continuous Improvement

• Scope: Full process automation, supplier relationship management, strategic sourcing analytics
• Users: Entire procurement organization + all business units
• Timeline: Advanced automation build (8 weeks) → Integration with financial systems (8 weeks) → Supplier onboarding (ongoing)
• Key action: Establish center of excellence; quarterly capability releases
• Success criteria: 80%+ self-service; procurement headcount reduced by 20% through automation; supply chain cost reduced by 12%

Common Pitfall: Executive Impatience

The most dangerous moment is the handoff from Crawl to Walk. Executives see early progress and want to skip Walk and go straight to Run. They say, "We do not have time for a slow rollout. Roll it out to everyone now."

This almost always fails. You end up with:

• Insufficient training for the full population
• Design flaws that were never caught because the pilot was too small
• Overwhelmed help desk and support teams
• Loss of credibility when the system breaks under load

Your job is to protect the gate. Show the business case for Walk: "If we roll out to the full organization now and only 40% adopt the platform, we spend the money and get no return. The two-month Walk phase costs $200K but ensures we hit the 70% adoption target we need to break even. The gate review will trigger full rollout only if Walk hits its metrics."

Variation: Crawl-Walk-Run-Fly

For transformations with significant upside or competitive advantage, consider adding a "Fly" phase:

• Fly (12+ months): Stretch goals, optimization, innovation on top of the baseline capability
• Example: Once procurement is running smoothly, Fly might be: automated supplier negotiation, AI-driven spend analytics, predictive demand modeling

Do not talk about Fly until Run is stable. But it is worth signaling to the organization that continuous improvement is the expectation, not a one-time project.

---

---

References

For detailed templates, frameworks, and field-level guidance, read:

• references/structured-thinking-reference.md — Complete framework details, templates, and examples

Read this file when the task requires:

• 3. Five Whys (Root Cause Analysis)
• 4. 2x2 Matrix (Prioritization and Classification)
• 5. Storyline (Consulting Narrative Structure)
• 6. Red-Amber-Green (RAG) Assessment
• 7. Elevator Pitch (Rapid Communication)
• 8. Day-One Plan (Initiative Launch)
• Combining Frameworks