Comparisons
Pairs engineers genuinely confuse — goal and implementation, MVP and bad prototype, prototype and spike, reversible and irreversible. Neither column wins; what decides is the problem. Each record leads with the confusion, because the confusion is what it costs.
Walking skeleton vs MVP
The skeleton is shown to a stakeholder as if it were the MVP ("look, it is deployed") or the MVP is attempted without a skeleton and integration is discovered on the last day. They are different distances along the same path: the skeleton is the first slice and proves connectivity and nothing else; the MVP is the set of slices that proves the idea. The honest cost of the skeleton is that it looks like nothing — one product on one page — and a team under pressure to show progress is tempted to skip it, which is exactly how the environment problems arrive at the worst moment.
Day one or two. It proves the environment, the seams and the deployment before there is anything in them.
Weeks later. It is the skeleton grown until a customer can complete the core workflow.
| Aspect | Walking skeleton — the thinnest path through every layer, deployed, doing almost nothing | MVP — the smallest version that proves the core idea to real users |
|---|---|---|
| Proves | The layers connect and the deployment works | The core idea works for real users |
| Content | One row, one endpoint, one page | Products, cart, order, payment |
| Audience | The team | Customers |
| Time | A day or two | Weeks |
| What it does not prove | Anything about the product | Anything about scale |
| Mistake | Skipped as "too trivial" | Attempted without a skeleton |