Understanding the difference between managed entities and buckets
In This Guide You Will Learn
- How to distinguish managed entities from simple buckets: and why confusing the two creates accountability, investment, and reporting problems.
- Why organizations accumulate multiple roll-up schemes: including strategic pillars, investment horizons, and BAU/RTB classifications that often coexist.
- How narrative slides and “pillar frameworks” actually function: as communication devices, elevator pitches, and information architecture rather than management systems.
- The hidden risk of the roll-up trap: where extra hierarchy layers exist only to aggregate work, not to provide accountability or insight.
- A third category to watch for — context trees: including product taxonomies, value architectures, and organizational structures that both organize work and require ongoing stewardship.
Two Types of Entities
Managed entities have an owner (or owners). You structure rituals to understand progress. They have “edges” — you can tell the things apart and understand where one stops and the other ends. People ask “How much have we spent on this?” or “Where are we at with this?” or “Who is working on that?”
Categories and buckets are helpful, but their primary utility is to aggregate things or categorize them. While the “strategic pillars” in the kickoff deck tell a story, they aren't really a thing. The things they group (goals, initiatives, workstreams, bets, experiments) are things, and the pillars operate more as tags, labels, and buckets.
Managed example: Mobile Checkout Redesign Initiative
Bucket example: Improve Conversion
You don't ship “Improve Conversion.” You ship the initiatives underneath it. Attach some goals and an owner to “Improve Conversion” and you have a managed entity.