SC
Strategy Map›Layer 4 · Product Strategy›Product Quality+ from outside the named canon

Novel Architecture

What is Novel Architecture?

The company builds its product on a different technical architecture from the incumbents it competes with (how data, compute, tenancy or components are arranged), and that arrangement delivers a benefit customers can see: speed, scale, cost, fewer upgrades, sharing or collaboration. An incumbent can match the benefit only by rebuilding its product, not by adding a feature.

How Novel Architecture works

Incumbents' products, organizations and customer installs are built around the old arrangement, so matching the benefit means a rebuild that strands their existing base (Henderson & Clark's architectural innovation). The lead lasts as long as that rebuild takes.

How companies won with Novel Architecture

From the win chains in Strategy Canon case studies: what the winner did, and what its rival did at the same step.

vs. Akamai · 2012–26

Cloudflare

Every server runs every service, sold up-market

What it did
Every server in every city runs every service on commodity hardware, 77% gross margin (2019)
Akamai
Bought Prolexic for $370M (announced Dec 2013) and runs its scrubbing centers apart from Kona Site Defender, priced per data-center location (2022)
Read the Cloudflare case study →
vs. Cerner · 1979-2003

Epic Systems

One clinician-shaped database for care and billing

What it did
Physicians define their own fields on one lifelong patient record (1979)
Cerner
Built department by department: PathNet lab (1984), then radiology, pharmacy and medicine systems (1987-89), unified as Millennium in 1997
Read the Epic Systems case study →
vs. PlanGrid · 2002–12

Procore Technologies

One shared record for every company on the job, on a multi-tenant cloud

What it did
A union-apprenticed carpenter turned software engineer web-enabled the schedule he ran with his remodel's subcontractors (2002)
PlanGrid
Founded 2011 by construction-management graduates as an iPad app to view and mark up blueprints for field crews (2012)
Read the Procore Technologies case study →
vs. Amazon Redshift · 2012-16

Snowflake

Innovation: the warehouse rebuilt for the cloud, storage separated from compute

What it did
Two Oracle database architects wrote a SQL warehouse from scratch to run only as a service: many compute clusters over one shared copy of data, no tuning, vacuuming or statistics (2012; paper 2016)
Amazon Redshift
Launched Nov 2012 on technology licensed from ParAccel
Read the Snowflake case study →

Also tagged: Adobe · Braze · Confluent · Dayforce · Fortinet · Guardant Health · Klaviyo · Nubank · Palo Alto Networks · Rubrik · Veeva · Workday · Xero

The question to ask of a company

What architectural choice differs from the incumbents', what customer benefit does it deliver, and what would an incumbent have to rebuild to match it?

Who names it

AuthorWhat they call it / where it appears
Henderson & Clark +Architectural innovation
Note. The benefit must be one customers experience and the incumbent must be shown lacking it; a new tech stack with no customer-visible difference does not count. When both the company and its rival adopted a new architecture against older incumbents, the tag does not separate them (Tableau vs Qlik). Business-model differences the incumbent will not copy are Counter-positioning; tag both when both apply. Owning more layers of the stack is Vertical Integration Strategy. A newly available platform the company rides (the iPad, the browser, the cloud) is Enabling technology shift in the Arena; tag this only for what the company built on it that rivals did not.