Heuristic
Break a dependency before optimizing inside it
Coupling can dominate local efficiency.
Before you use it
- Use when
- When local performance tuning keeps failing because every change waits on another component or organization.
Keep this limit in mind
- Modularity trades coordination inside a boundary for coordination across interfaces. Do not split systems simply to make diagrams or org charts look cleaner.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Before squeezing another few percent from a component, test whether removing, stabilizing or making asynchronous a dependency would reduce larger coordination and waiting costs.
An example
A team spends days coordinating a synchronous approval for a task that takes minutes; decoupling the approval path matters more than optimizing the task.
Check your result
The selected optimization targets the larger end-to-end cost rather than the most visible local step.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingBreak a dependency before optimizing inside it
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaMake dependencies directional where possible
Evidence and sources
Simon described complex systems as often hierarchical and near-decomposable, motivating analysis of relatively strong within-subsystem interactions and weaker cross-subsystem interactions.
Near decomposability is a conceptual property, not evidence that any chosen boundary is correct.
The Architecture of Complexity · Near-decomposability discussion
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.