YYoung and Profiting
← All frameworks
StrategyMaria Brito

Deconstruct-or-Aggregate Lens

Generate business options by separating a system or combining more value into it.

Difficulty
Moderate
Time to result
~weeks to results
Steps
5
Confidence
98%

This lens generates opposing strategic options from the same system. Deconstruction takes the system apart: isolate a component, remove unnecessary elements, or turn one constrained feature into a focused standalone offer. Aggregation moves the other way: combine complementary functions so users can complete more of an activity in one place. Start by mapping the current components and customer purpose. Then create one serious concept in each direction rather than assuming that more features or greater simplicity is always correct. Compare the concepts by user value, distinctiveness, complexity, and execution burden. Brito’s examples contrast Twitter’s original focused microblogging with Facebook’s accumulation of social functions. The value of the framework is not choosing a permanent ideology; it is selecting the direction that best fits what the business needs now.

Origin

Brito explains the opposing concepts through Picasso, Zenith’s remote control, Twitter’s original microblogging model, and Facebook’s expanding platform.

Core principles

  • 01Subtraction and addition are distinct paths to innovation.
  • 02A component may create more value after separation.
  • 03A platform may create more value by combining related activities.
  • 04Neither direction is universally superior.
  • 05Simple concepts can outperform needless complexity.

How to run it

  1. 1

    Map the whole

    List the components, functions, and user activities in the current system. State the central job the whole system performs.

    Pro tip Include components users may take for granted.

  2. 2

    Deconstruct it

    Ask which component could be isolated, simplified, or removed. Design a focused concept around the strongest separated value.

    Pro tip Look for one constrained feature that could become the entire proposition.

    Watch out Simplicity is useful only if the remaining piece solves a real need.

  3. 3

    Aggregate it

    Ask which complementary functions could be added or combined. Design a concept that reduces fragmentation for the user.

    Pro tip Aggregate around a coherent activity, not a random feature list.

    Watch out More functions can increase operating burden and obscure the core value.

  4. 4

    Compare the opposites

    Evaluate both concepts against user value, distinctiveness, complexity, and feasibility. Decide which direction fits the current business problem.

    Pro tip Do not assume one direction is inherently more innovative.

  5. 5

    Test the chosen direction

    Build the smallest test that reveals whether customers prefer the separated or combined value. Use evidence to keep, revise, or reverse the choice.

    Pro tip When value appears equal, test the lower-complexity concept first.

In the wild

Zenith separates the remote

Brito says television controls were once attached to the set by wires. Zenith separated the control panel from the television and created the remote as its own useful object, illustrating how deconstruction can turn one attached component into a broader product category.

A separated component became a widely reused product concept.

Twitter focuses while Facebook combines

Early Twitter reduced blogging to a limited number of characters and focused on microblogging. Facebook pursued the opposite logic by adding photos, likes, messaging, shopping, games, business functions, and other experiences intended to keep people within one community.

Both subtraction and aggregation produced distinct, large-scale platform strategies.

Common mistakes

Adding without a user purpose

Aggregation becomes complexity when added functions do not strengthen one coherent customer activity.

Worshipping simplicity

Deconstruction can remove the elements that make an offer valuable if subtraction is treated as the goal rather than a strategic option.

Is it for you?

Best for

It is best for teams rethinking a mature product, service, workflow, or business model.

Not ideal for

It is not ideal when the core customer problem is still unknown and there is no existing system to map.

From the transcript

the construction is taking the pieces apart

Maria Brito · 64:00

aggregation is the the opposite

Maria Brito · 66:00

both are you know it's it's not that one is better than the other or anything it's just that they are very different ways of…

Maria Brito · 66:30

From the episode

Maria Brito: Harnessing Your Creativity

Maria Brito