Paved Roads
Making the supported path the easiest path, with a way to leave it.
4 to work through
-
intermediate
An organisation builds a paved road and half the teams build their own infrastructure anyway. What does the adoption gap indicate?
2 min answer -
intermediate
How does a paved road achieve governance outcomes without a mandate, and what makes it fail?
2 min answer -
advanced
A company builds an internal platform to standardise how services are created and operated across hundreds of teams. What should it enforce, what should it leave flexible, and how does it avoid becoming an obstacle?
3 min answer -
advanced
From 2011 the UK's Government Digital Service required central approval for departmental digital spending above a threshold (about £100,000, and zero for some categories such as public-facing websites) alongside a published service standard and assessments. By 2026 the GDS-run controls had been retired in favour of departmental ownership with a much higher pipeline threshold. What did controlling the money achieve that a standards document could not, and where would copying it be a mistake?
4 min answer
4 terms in this topic
Golden Path
A generated, fully-configured starting point for a new service that arrives with observability, pipeline, identity, ownership and cost attribution al…
metricGolden Path Adoption
The proportion of teams voluntarily using the supported path, which is the honest measure of whether a platform is solving real problems.
patternPaved Roads
A supported, opinionated default path that is the easiest way to do the right thing — governance by convenience rather than by mandate.
practiceSpend Control Gate
Architecture governance applied at the point money is committed rather than at design review, so the conversation happens while the decision is still…
Neighbouring topics
Enterprise Architecture
General material on architecture at portfolio and estate scale.
EA Domains
Business, application, data and technology architecture as viewpoints.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
Technology Architecture
Platforms, runtimes and infrastructure standards across the estate.
Capability Maps in EA
The stable frame for hanging investment, ownership and health off.
Application Portfolio Management
Inventory, ownership, cost and health for every application.
Application Rationalisation
Retire, consolidate, replatform — and why retirement is under-applied.
Technology Standards
Guidance that teams follow because it helps, not because it is mandated.
Technology Radar
Adopt, trial, assess and hold — with movement, dates and owners.
Reference Architectures
Pre-approved templates for recurring solution shapes.
Architecture Governance
Preventive, automated controls rather than review meetings.
Architecture Review Boards
Thresholds, early engagement and a real route to accept deviation.
Enterprise Integration
Estate-wide integration strategy, standards and shared infrastructure.
TOGAF
The ADM as a checklist, tailored rather than followed literally.
EA Frameworks
Zachman, FEAF and others — vocabulary rather than method.
Architecture Roadmaps
Sequencing change across an estate with dependencies and funding.
Platform Teams
Reducing other teams' cognitive load, measured by adoption.
InnerSource
Open-source collaboration practices applied inside an organisation.
EA Metrics
Measuring whether architecture work changed anything.