Context Trees and the Three Categories
Durable structures that describe how the organization understands itself
There is one important category we haven't discussed yet: structures like value architectures, product taxonomies, and organizational groupings.
These play a kind of double duty.
On one hand, they are actively managed. People maintain them, update them, and revisit them over time. They are not trivial to design or maintain. In many organizations, entire teams spend time refining these structures because they influence how work is organized and understood.
On the other hand, they also serve as powerful aggregation schemes. They group work, provide context, and help people understand how things relate to one another.
Characteristics of Context Trees
- They are tree-like structures. Entities roll up into higher-level entities.
- The entities inside them are real things that involve people (teams, products, capabilities, domains).
- They carry a lot of meaning and context for how the organization works.
- They are critical categorization schemes used throughout the company.
- They are actively maintained and debated, because changes to them affect how work is organized.
Most importantly, they are not time-bound intent (like a goal, initiative, etc.). An initiative exists for a period of time. A strategic theme might exist for a planning cycle. But these structures last as long as they reflect reality. When they stop reflecting reality, you change them. They are less like plans and more like maps of how the organization sees itself and its work.
The Three Categories
| Structure Type | What It Is | Typical Shape | Time-Bound? | Ownership / Rituals | Primary Purpose | Examples |
|---|---|---|---|---|---|---|
| Managed Entity | A concrete piece of work or intent that someone is responsible for delivering | Connected entities, sometimes nested, but not primarily a roll-up structure | Yes. It has a start and end. | Clear owner, regular reviews, funding, and progress tracking | Execution and delivery | Mobile Checkout Redesign Initiative, New Pricing Experiment, Platform Migration Project |
| Category / Bucket | A label or grouping scheme used to organize work, spending, or narrative themes | Often DAG-like or tree-like roll-up structures used for aggregation | Usually tied to a planning cycle, reporting view, or classification scheme | May have a sponsor or steward, but rarely real delivery accountability | Aggregation, storytelling, reporting, and classification | Improve Conversion, Run the Business (RTB), Business as Usual (BAU), Capex vs Opex, Delighters vs Table Stakes |
| Structural Architecture | A durable structure describing how the organization sees its domains, products, teams, or capabilities | Tree-like hierarchies with meaningful entities | No. It persists until reality changes. | Actively maintained and debated, but not reviewed like initiatives | Context, structure, and long-lived categorization | Product Taxonomy, Capability Map, Value Architecture, Org Structure |