John Cutler Challenges Traditional ‘Value Tree’ Models on LinkedIn

In a recent LinkedIn post, John Cutler critically examines the common hierarchical “value tree” or “value pyramid” structures often used in business and project management. These models, typically illustrating relationships from high-level goals down to individual tasks (e.g., pillars >> programs >> initiatives >> epics >> stories), are frequently employed to map out how work contributes to strategic objectives. However, Cutler argues that these rigid frameworks often misrepresent the complex realities of how value is actually created and delivered.

John Cutler highlights five key fallacies inherent in these traditional tree structures. The first, which he terms “Single Lineage,” points out the flawed assumption that a piece of work can only contribute to one single objective higher up the chain. “Tree models assume that work lower in the structure can only impact one and only one thing higher up,” Cutler writes. “In reality, a single effort often influences multiple levers, multiple goals, or multiple initiatives.” This, he contends, forces an inaccurate representation of actual impact.

The Overloaded Edge and Container Path Dependency

Delving deeper, Cutler identifies the “Overloaded Edge” fallacy. This occurs when a single connection point (an “edge”) in the hierarchy is expected to represent all types of relationships between parent and child items. In practice, these connections can signify requirements, optional tactics, inputs, outputs, or mere organizational containers. “The hierarchy treats all of these as the same relationship. So it becomes impossible to tell what the edge is supposed to mean,” Cutler explains. He further elaborates on “Container Path Dependency,” arguing that these models incorrectly assume impact must flow strictly through a predefined stack of containers. Real-world work, he notes, often bypasses these artificial layers to directly influence higher-level goals.

“Creating artificial parents just to satisfy the hierarchy is a modeling flaw, not a reflection of how value flows.”

Critique of One-Size-Fits-All Objects and Exception-Driven Layers

Another significant issue Cutler raises is the “One-Size-Fits-All Object” fallacy. This problem arises when a single label, such as “initiative,” is burdened with too many disparate meanings. “The model presupposes that duration is the most important trait, so everything under three months becomes an initiative,” Cutler observes, pointing out that this ignores crucial differentiating factors like risk, uncertainty, cost of delay, and reversibility.

Finally, Cutler addresses the “Exception-Driven Layer” fallacy. This occurs when new layers or object types are introduced into the hierarchy solely to accommodate infrequent exceptions, such as particularly long-running projects or complex cross-dependency efforts. “These situations might occur only 10 to 20 percent of the time, yet the hierarchy expands for everyone,” he writes, leading to increased administrative overhead without benefiting the majority of cases. According to Cutler, when exceptions dictate the architecture, the model becomes bloated and less effective for the typical workflows.

In summary, John Cutler’s analysis on LinkedIn provides a compelling critique of conventional value tree methodologies, urging a move towards more flexible and accurate models that better reflect the nuanced nature of value delivery in modern organizations.