Hierarchies of Business Model Elements
This tool arranges a business model in layers, from the foundations you run on - resources, activities, partners - up through the value you deliver and the customer relationship, ending in the revenue and cost result those choices produce, so you can spot which layer is actually broken instead of redesigning everything at once.
Layers stack one above another, with the operational foundations at the bottom and the revenue and cost result those foundations produce at the top.
Reach for this when…
- A business model 'isn't working' but nobody can say which part.
- You are about to redesign the whole model when only one layer needs fixing.
- Growth has exposed cracks and you need to know if it's a foundation problem or a front-end problem.
How to run it
- List your foundational layer: key resources, activities, and partners.
- List your middle layer: value proposition and how you deliver it.
- List your channel layer: how customers reach you and the relationship you have with them.
- List your top layer: the revenue and cost structure those choices produce.
- Trace which top-layer symptom traces back to which foundation-layer cause.
- Fix the lowest broken layer first - higher layers rarely hold if the foundation is wrong.
A worked example
Situation. Emily Carter ran a small vineyard and winery in the Texas Hill Country near Austin, United States, and could not work out why direct sales kept underperforming despite a strong tasting-room experience.
Applied. Mapping the layers, she found the top layer - the customer experience - was fine. The break was in the foundation: her key activity, harvest timing, was misaligned with her key resource, a small ageing crew, so bottling was always late for the peak season.
Result. She hired seasonal harvest help two months earlier than usual. The tasting room didn't change at all, but on-time bottling fixed the sales problem within a year.
The catch
The layering implies a clean hierarchy, but real business models have loops - a channel problem can break a resource, not just the other way round. It also tempts people to treat the top layer, the visible customer-facing part, as the whole model when the real fault is buried lower. Use it as a diagnostic lens, not a strict cause chain.
If you keep fixing the top layer and the same symptom returns, you are treating the wrong layer.