Dissing the Default
Defaults are decisions you didn’t make
Years ago Joel Orr told me something I didn’t
fully understand at the time:
Structure is destiny.
Orr was an early CAD pioneer and systems thinker who spent decades watching organizations adopt powerful new tools and struggle with the same old structural problems. He wasn’t being philosophical. He was being literal.
Structure decides outcomes.
And most organizations aren’t designing their structure anymore.
They’re inheriting it.
Inherited structure produces inherited destiny.
That’s the quiet danger of the platform era: not bad tools, not weak technology — but the rise of default thinking.
And default thinking isn’t lazy thinking.
It’s the absence of thinking.
The default is running the organization
We now operate inside a world of ready-made systems:
default software
default workflows
default templates
default dashboards
default best practices
Each one removes friction. Each one promises speed. Each one says: you don’t have to decide this.
That’s useful — until it isn’t.
The moment the default becomes a substitute for judgment, design disappears. Work keeps moving, but no one is shaping it. The organization isn’t choosing how it behaves. The system is.
From that moment on, destiny is inherited, not intentional.
And inherited destiny always converges toward sameness.
Platforms don’t create outcomes
Substack proves this brutally.
Every writer gets the same infrastructure:
same publishing system
same delivery rails
same monetization tools
Yet outcomes spread from invisible newsletters to cultural institutions.
The platform didn’t pick winners.
It exposed structure.
The successful publications have a designed container:
a clear promise
a recognizable lens
consistent framing
intentional sequencing
a sense of direction
That’s not tooling. That’s structure expressing itself.
An unknown publication isn’t hidden because Substack failed. It’s still searching for the structure that gives the work gravity.
Platforms amplify design.
They don’t replace it.
Infrastructure isn’t strategy
Operational platforms tell the same story:
Microsoft 365
Google Workspace
Salesforce
HubSpot
ERP stacks
Their purpose is stability, not uniqueness. They industrialize the commodity layer so you don’t waste energy reinventing plumbing.
That’s great up to a point.
The mistake is expecting advantage to emerge from infrastructure.
Which CRM will save us?
Which integration will unlock productivity?
Which dashboard will create clarity?
Those are design questions disguised as purchases.
Infrastructure can support design. It cannot supply it. Structure is still a decision.
Where to standardize, where to design
Dissing the default doesn’t mean rejecting platforms.
It means refusing to let them think for you.
Standardize aggressively where uniqueness has no strategic value:
infrastructure
commodity workflows
coordination hygiene
Design intentionally where advantage lives:
decision-making
priorities
interpretation
customer experience
organizational behavior
Confuse those layers and you scale mediocrity. Separate them and you scale intelligence.
The platform era didn’t remove the need for design. It removed the excuses for avoiding it.
You can inherit structure. Or you can design it. One path produces intentional destiny. The other produces whatever the defaults happen to allow.
Defaults are not neutral. They are decisions you didn’t make.