Scientific Definition
Software architecture mirrors org structure.
Plain-English Definition
Software architecture mirrors org structure.
Feynman Explanation
Your product is your org chart in production.
Core Principle
Software architecture mirrors org structure.
Mechanisms
Pending editorial review.
Software architecture mirrors org structure.
Pending editorial review.
Pending editorial review.
Pending editorial review.
Pending editorial review.
Tech architecture as a function of human architecture.
Inputs (Triggers)
Pending editorial review.
Outputs (Behaviors)
Pending editorial review.
Behavioral Signature
Your product is your org chart in production.
Examples
- Microservices teams produce microservices.
- Tech architecture as a function of human architecture.
Pending editorial review.
Famous Experiments
Pending editorial review.
Design Principles
- Design the org you want the product to reflect.
Measurement Approaches
Pending editorial review.
Evidence
Pending editorial review.
Pending editorial review.
The Perverse Incentive Lens™
How this behavior is exploited — and how to redesign around it.
- Design the org you want the product to reflect.
Pending editorial review.
Pending editorial review.
Interactive Mini Network
Click any neighbor to re-center the graph and follow the threads of connection.
Knowledge Graph Neighbors
Auto-linked to the rest of the Human Behavior Taxonomy by family, domain, dimension, and shared keywords.
Combining substances to create a new material stronger than its parts.
A single constraint limits the throughput of an entire system.
A system's throughput is constrained by its single slowest step.
Small visible disorders signal that bigger ones will be tolerated.
Adding manpower to a late software project makes it later.
Adding people to a late project makes it later.
A substance that speeds up a reaction without being consumed.
Nonlinear systems are highly sensitive to initial conditions.
Inputs combine under conditions to produce new outputs — sometimes irreversibly.
Working together has a cost that scales with the number of people.
The threshold at which a system becomes self-sustaining.
Designing systems for the lowest-capability user produces resilience for everyone.