Skip to main content

Inheritance, Conflict & Constraints

DNA isn’t static. It evolves. But evolution isn’t random—it follows rules. This page explains the physics of how your company’s DNA changes and self-organizes.

Inheritance: How Genes Extend

Inheritance is when a new gene builds on an existing one.

Example: Color Hierarchy

When Brand.ColorPrimary changes, all descendants automatically update.

Why Inheritance Matters

Without inheritance:
  • Change brand color
  • Manually update 47 places
  • Miss 3 of them
  • Product feels inconsistent
With inheritance:
  • Change brand color (one gene)
  • All descendants update automatically
  • Zero manual work
  • Perfect consistency

Conflict: When Genes Contradict

Sometimes genes contradict each other. This is not a bug—it’s information. Conflicts reveal hidden tensions that need resolution.

Example: Speed vs. Security

What do you do?

Conflict Resolution Strategies

1. Prioritization

Decide which gene wins.

2. Synthesis

Create a new gene that satisfies both.

3. Context-Dependent

Both genes apply in different contexts.

4. Deprecation

One gene is outdated.

Conflict as Signal

Conflicts are valuable. They show:
  • Where your company is growing
  • Where old assumptions no longer fit
  • Where implicit values need to become explicit
Don’t avoid conflicts. Resolve them explicitly.

Constraints: How Genes Limit Each Other

Constraints are when one gene restricts possibilities for another. This isn’t conflict—it’s physics. Some genes naturally limit others.

Example: Tech Constrains UI

Tech gene creates boundaries that UI genes must respect.

Common Constraint Patterns

Tech → UI/UX

Brand → Product

Security → Data

Product → AI


Why Constraints Are Good

Constraints:
  • Prevent bad decisions before they happen
  • Clarify boundaries between systems
  • Force creativity within limits
  • Make dependencies visible
Constraints are not limitations—they’re guardrails.

The Constraint Graph

Your DNA forms a directed acyclic graph (DAG) of constraints.
Arrows = “constrains” This graph shows:
  • Which genes depend on which
  • What order to make decisions
  • Which changes will ripple through the system

Constraint Conflicts

Sometimes constraints form impossible situations.

Example: Impossible Triangle

This is real tension that needs resolution. Options:
  1. Relax Product.FeatureRichness (ship MVPs)
  2. Extend Tech.FastShipping (2-week cycles)
  3. Grow Team.SmallTeams (hire more engineers)
  4. Reduce Product.FeatureScope (build less)
The constraint conflict forces an explicit strategic decision.

Evolution: How DNA Changes Over Time

DNA evolves through four mechanisms:

1. Mutation (Gene Change)

A gene changes because context changed.

2. Insertion (New Gene)

A new gene is added.

3. Deletion (Gene Removal)

A gene becomes obsolete.

4. Recombination (Strand Reorganization)

Genes move between strands.

DNA Versioning

Every change to DNA should be versioned.
Versioning lets you:
  • Track changes over time
  • Communicate updates to the team
  • Roll back if needed
  • Understand why decisions were made

The Self-Organization Property

Here’s the magic: When DNA is explicit, companies start self-organizing.
  • Engineers check Tech genes before building
  • Designers reference UI genes before designing
  • Product checks constraints before proposing features
  • Sales applies Brand genes when talking to customers
You don’t need to be in every meeting. The DNA guides decisions.

The DNA Equation

More explicit genes → more alignment More active constraints → fewer bad decisions Less entropy → more coherence DNA increases the numerator and decreases the denominator.

Next: Maturity Levels

Now you understand how DNA works. Let’s see where your company sits on the evolution scale.

DNA Maturity Levels

Where your company sits on the evolution scale