Week 11 Day 2: The Value Pyramid -- Revenue, Margin, Overhead

The Value Pyramid is a simple framework for understanding where money comes from and where it goes. Revenue is what customers pay. Margin is what remains after the direct cost of delivering the product. Overhead is everything else -- salaries, tools, office space, infrastructure. Most technical teams spend their days in the overhead layer without realizing it. Understanding the pyramid changes how you think about every task on your backlog.

Here is how to draw it. Take a whiteboard and draw a triangle divided into three horizontal layers. The top layer is revenue -- how does money come in? Subscriptions, one-time purchases, advertising, licensing. Label each revenue stream with its approximate size. The middle layer is margin -- what does it cost to deliver the product to one more customer? Hosting, bandwidth, payment processing, customer support per user. The bottom layer is overhead -- what do you spend regardless of how many customers you have? Salaries, tools, office costs, compliance. Now ask your team: which layer does your current sprint live in? Most of the time, the answer is overhead. That is not inherently wrong. But when your team understands that a particular feature directly expands the revenue layer or compresses the margin layer, their relationship to that work changes. It stops being another ticket and starts being a business decision they are part of.

The Value Pyramid framework draws on Porter's Value Chain Analysis (1985), which decomposes business activities into primary activities (directly creating value) and support activities (enabling value creation). The three-layer model simplifies this for non-business audiences while preserving the core insight: not all activities contribute equally to competitive advantage. Drucker (1954) made a similar distinction in 'The Practice of Management' between revenue-producing activities and cost-incurring activities, arguing that most organizations over-invest in the latter because costs are internally visible while revenue drivers are externally determined. The pyramid visualization leverages what Tufte (2001) calls 'data-ink ratio' -- maximum information with minimum visual complexity. In Lean methodology, Womack and Jones (1996) distinguish between value-adding and non-value-adding activities, with the observation that in most processes, less than 5% of elapsed time is spent on value-adding activities. The Value Pyramid makes this ratio visible at the organizational level.