;

Project Model Integrations

Featured Image

The twentieth century didn’t just change what we made. Instead, it changed how we worked together. When someone says, “Let’s throw some people at it,” what they really mean is: add headcount, not insight. A bit like throwing something at a wall and hoping it will stick. 

That thinking shaped much of the last century - and design hasn’t been immune.

As industries scaled, the old giants like Ford, Coca-Cola, Levi’s, and Kodak gave way to new players - IBM, GE, Atari, Microsoft, Apple. Growth meant volume. Volume meant visibility. Visibility demanded advertising. And advertising demanded design that could move as fast as the market.

Big agencies evolved alongside these brands, building new delivery models to keep up. They weren’t just producing campaigns; they were engineering processes - blending design, operations, and communication into an early form of organisational integration.

But with growth came fragmentation. Local agencies ran local work. Reuse and consistency barely existed. A family on one coast rarely saw the same ad as another. Each region interpreted the brand in its own dialect.

It wasn’t until the internet that everything converged. Suddenly, every brand needed a single face - everywhere, in every language. Centralised websites replaced regional campaigns. Design systems replaced design departments.

The world had become integrated. But not necessarily coordinated.

BOK – Project Model Integration.
BOK – Project Model Integration.

Horizontal Integration

Horizontal integration was the first wave of growth.

A business expanded by adding new products or markets - widening, but not deepening. If one product sold, another followed. A shoe store became a shoe company. A local brand became a national one.

But horizontal growth has limits. Every new product requires a new team, a new supply chain, a new message. You can sell more, but you can’t necessarily connect more.

For design, it’s the difference between running multiple projects and building a platform. You grow wider, not smarter.

BOK – Project Model Integration.
BOK – Project Model Integration.

Vertical Integration

Then came vertical integration - companies expanding up and down their value chains.

Factories opened franchises, brands controlled distribution, and retail became an empire. From the 1950s to the 1980s, this was how you scaled: own more of the journey from creation to consumption.

But it introduced a new challenge. This was coherence.

Each franchise hired its own agency. Each agency built its own design language. Consistency became chaos. Costs rose, messages clashed, and brands diluted themselves trying to manage it all.

By the 1990s, the internet promised to fix this. It didn’t. It just made the inconsistency visible in real time.

Design decisions made on the West Coast could define user experiences in Europe or Asia - often without context. 

“Global coordination became a paradox: everyone connected, no one aligned”.

BOK – Project Model Integration.
BOK – Project Model Integration.

Functional Integration

Functional integration was the next evolution. And the one that most resembles today’s design maturity.

Instead of simply expanding output, companies began connecting functions. Products, services, and data began to inform one another.

Knowledge became the shared infrastructure.

Teams learned to treat information as capital. Meaning something to be invested, refined, and redistributed. Without that shared understanding, organisations couldn’t adapt fast enough to stay relevant.

But adaptation isn’t comfortable. Even startups struggle with perpetual change. Functional integration demands a new kind of discipline: teams that learn faster than they build.

Take the shoe industry again.

Baťa’s factories were masters of efficiency - linear, predictable, built for volume. But they couldn’t scale functionally. Their systems were optimised for production, not learning.

Nike, by contrast, designed its business like a feedback loop. The company merged digital and physical experiences long before “omnichannel” was a buzzword. Data from Nike Run and FuelBand (now Apple Watch) feeds directly into product design and marketing. The result is a living brand — part software, part sport, part social ecosystem.

“Nike doesn’t just sell shoes; it sells participation. That’s functional integration - a company that learns in real time”.

Exponential Integration

The latest evolution is Exponential Integration - a term popularised by Salim Ismail, Peter Diamandis, and Michael Malone in Exponential Organisations.

They identified eleven attributes shared by the world’s most adaptive companies: Massive Transformative Purpose, Staff on Demand, Community and Crowd, AI and Algorithms, Leveraged Assets, Engagement, Interfaces, Dashboards, Experimentation, Autonomy, and Social Technologies.

Individually, they’re tools. Together, they form a mindset.

Exponential organisations don’t just optimise operations, but they reinvent them continuously. They grow by learning faster than scale can limit them.

What connects these companies isn’t size; it’s velocity of intelligence.

They use data, automation, and community not to replace people, but to amplify them. Their systems think, adapt, and evolve - just like organisms, but not like factories.

In practice, this means reimagining how design operates inside business.

Design at Scale™ sits at the centre of this shift. It’s where disciplines intersect - where engineering meets emotion, and data meets meaning. Everyone wants a piece of that clarity, which is why so many teams now borrow design frameworks for their own processes.

And that’s fine - as long as design remains the connective tissue, not the casualty.

Because design’s real power isn’t ownership. It’s orchestration.

We’re not here to defend territory; we’re here to define flow.

Integration - horizontal, vertical, functional, or exponential - isn’t just a management model. It’s a mindset that values knowledge over control, learning over hierarchy, and connection over competition.

When design operates at that level, it stops being a department and becomes what it was always meant to be: a system of intelligence, shaping how everything else works.

Happy scaling through design!

Hey, I’m Jiri Mocicka.
London-based Product Design Director, Trusted Advisor and Author of Design at Scale™. The method that empowers individuals to shape the future organisation through design.
If you have a question, join our Community and reach out to like-minded individuals who scale design propositions. An online Academy can help you to define teams of 01, 10, and 100, and 1% supported by Grid Magazine and Supply section, where we bring more insights weekly on how to become a design leader in your Agentic Organisation

Author's Name

AVATAR

inResearch

32

inWriting

65

Released

240
EMT

Related.

Featured Image
In our digitally mediated age, user interface design is no longer a mere decorative advantage of commerce. It has become the very engine room …
January 20, 2026
 · 
5 min read
Featured Image
If Ford built the rhythm of production. Toyota taught us to improve it. And Baťa gave it purpose. Then along came digital and transformed …
March 19, 2025
 · 
4 min read
Featured Image
If Ford industrialised production and Toyota humanised it, Tomas Baťa managed to socialise it. In the early 1900s, the young Czech entrepreneur reimagined what …
March 8, 2025
 · 
4 min read
Featured Image
In 1945, Kiichiro Toyoda set his company a challenge: Catch up to America. At the time, Japan had few resources and even fewer machines. …
February 26, 2025
 · 
3 min read
Featured Image
It’s a common misconception that Henry Ford invented the automobile.The reality is, he didn’t. What he did invent was scale, however.  Ford’s true genius …
February 19, 2025
 · 
3 min read
Featured Image
If we want to understand where design is heading, we need to remember where it came from. Historically, design was a sequence: sketch, refine, …
February 12, 2025
 · 
2 min read
Featured Image
In early 2026, we all saw some experiments and prototypes in which one node connected to another could transform an image into a series …
January 6, 2026
 · 
6 min read
Featured Image
Design has never stood still. Over the past century, it has transformed again and again. Each shift in form or function reflects a deeper …
January 1, 2025
 · 
4 min read
Featured Image
In the early 1900s, a cobbler knew every curve and stitch of the shoe they made. They built by hand, understood materials intimately, and …
January 22, 2025
 · 
3 min read

GRID Magazine

Explore OUR 
Articles

Every week we bring set of stories reflecting on communication, operation and technology.

Newsletter

Subscribe.

We share our 20 years of experience in creating, managing and scaling products and services that allow individuals to shape organisations through design.

Design at Scale™

LINE_MAGENTA_050_301

Categories

LINE_MAGENTA_050_301

Data

LINE_MAGENTA_050_301

Share

Internal

Collaborate

Resources

IBM PlexSan
Regular
Charcoal

Design at Scale™ is defined by three models, which form the Method. Each model operates in a different part of the business and collects and informs parties on design and engineering decisions that have a direct impact on the delivery.

All brands and trademarks presented on the Design at Scale™ website are owned by their relevant companies or agencies. The projects represent collaborations between designers, developers and product owners. Do not copy or publish any of the projects shown here without written approval from Design at Scale™ (alternatively GIVE™, 9V™) and/or relevant companies and agencies.

SOC_Twitter
SON_LinkedIn
SON_Instagram
SOC_-Medium
View