Consulting Prep
Process Breakdown: Structure Cases by Steps
Achraf Darkaoui · April 2026 · 5 min read
Process Breakdown is the second tool in the MECE toolkit. When the problem involves a natural sequence of steps — operations, a customer journey, a workflow — you decompose it into those steps. Each step is distinct, the order is clear, and together the steps cover the full journey from start to finish.
It is the second most straightforward way to be MECE after Algebra. The chronological order itself guarantees structure. And it is the tool you reach for whenever the case is about efficiency, bottlenecks, or throughput.
Related: Practice structuring operational cases in the CaseSights problem-solving drills.
How Process Breakdown Works
You map the problem as a sequence of steps. The steps follow a chronological or logical order. Each step is a discrete stage that can be analyzed independently, and the full sequence covers the entire process.
The most common mistake is confusing a process with a list. A list of "things that affect profitability" is not a process — there is no order, no flow, no dependency between items. A process has directionality: step one leads to step two, which leads to step three.
Common Process Structures
Value Chain (Porter): R&D → Manufacturing → Sales and Marketing → After-Sales. This maps how a business creates and delivers value. It is the go-to process structure for understanding where in the business a problem originates.
Supply Chain: Sourcing → Procurement → Manufacturing → Warehousing → Distribution. This maps the flow of physical goods from raw materials to the customer. Use it when the case involves logistics, cost of goods, or delivery issues.
E-commerce Funnel: Landing on the website → Product selection → Add to cart → Payment. This maps the customer journey on a digital platform. Each step has a conversion rate, and the bottleneck is wherever the biggest drop-off occurs.
Patient Flow: Admission → Diagnosis → Treatment → Recovery → Discharge. This maps the patient experience in healthcare. The structure applies equally to any service process with intake, processing, and output stages.
Customer Journey: Awareness → Consideration → Purchase → Retention → Advocacy. This maps the full lifecycle of a customer relationship, not just the transaction.
When to Use Process Breakdown
The problem involves a sequence. If there is a clear "first this, then this, then this" structure, you have a process to decompose.
The case is about efficiency or bottlenecks. When a client asks "where are we losing time?" or "why is throughput down?", mapping the process is the natural first move. The insight comes from identifying which specific step is broken.
You need to find where value leaks. In any chain — supply, value, conversion — the question is always "which step is underperforming?" The process gives you the scaffold; the analysis isolates the problem step.
The Zoom Level Decision
One of the key judgments in process breakdown is how deep to go. You can stay high-level (Sourcing → Production → Distribution) or go granular (raw material identification → supplier qualification → RFP → negotiation → contracting → purchase order → quality inspection → inbound logistics).
The right zoom level depends on where the problem sits. If the case is broad — "assess the client's operational efficiency" — start high-level and drill into the problematic step. If the case is narrow — "why is our warehousing cost 30% above benchmark?" — start at the level of warehousing operations.
Your first-level process should have 4 to 6 steps. Fewer than that and you are too high-level to generate insight. More than that and you are too granular to see the structure.
Key Takeaways
Use it when there is a natural chronological or logical sequence. If the problem involves steps that happen one after another, Process Breakdown is your tool.
The decomposition depends on the zoom level. You can stay high-level or go granular. The right zoom depends on where the problem sits.
It works for any domain, not just operations. People default to supply chain and value chain, but process breakdown applies equally to customer journeys, hiring funnels, M&A workflows, product development — anything with sequential steps.
The insight comes from isolating the broken step. The process itself is just the scaffold. The real value is finding the step where the problem sits, then zooming into that step further.
How CaseSights Trains Process Thinking
The problem-solving course teaches process breakdown as the second MECE tool, with worked examples across operations, digital funnels, and service delivery. The Companion specifically probes whether candidates can identify the bottleneck step in process-based cases and zoom into it with the right level of detail.
Frequently Asked Questions
How is Process Breakdown different from Algebra? Algebra decomposes using math equations — addition and multiplication. Process decomposes using chronological sequence. Revenue = Customers × Price is algebra. Sourcing → Manufacturing → Distribution is process. Sometimes both apply to the same problem. Use Algebra for the quantitative structure and Process for the operational structure.
Can I use Process Breakdown at the top of my tree? Yes, when the problem is fundamentally about a sequential process. If the client asks "why is our delivery time increasing?" then the delivery process is the natural top-level structure. But for a question like "should we enter this market?", a process structure would be forced — use Concept instead.
What if the process has parallel steps? Some processes have steps that happen simultaneously rather than sequentially. In that case, group the parallel steps and present them as a single stage, or acknowledge the parallelism and analyze each branch. The MECE principle still applies — the stages should not overlap and should cover the full workflow.
How do I know if I have the right zoom level? If your process has fewer than 4 steps, you are probably too high-level. If it has more than 6, you may be too granular for a first pass. Start with 4 to 6 steps, present your structure, and offer to zoom into any step the interviewer finds most interesting.
Practice what you just read.
CaseSights drills score your structures on MECE-ness, sharpness, and specificity — in real time.
Try the Structuring Drills →