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 it all into code.

The late twentieth century marked a profound transition: from physical systems to digital ones, from factories to frameworks. And with that shift, design itself was redefined.

By the early 1970s, incremental and adaptive software development had begun to influence how teams worked. By the 1980s and 1990s, the creative world was moving online. Basic HTML pages became the new storefronts. Design was no longer confined to paper - it was rendered in pixels.

The old agency model - brief, design, deliver - struggled to keep pace. What once worked for print and broadcast became too rigid for a medium that could change overnight. Clients wanted flexibility; developers demanded structure. The result was tension. And out of that tension emerged something new: digital project management.

Early digital studios, the forerunners of today’s consultancies, started to experiment with development methodologies borrowed from engineering. They needed predictability without paralysis. Waterfall was the default - clear, sequential, and familiar - but it couldn’t handle iteration.

In traditional agencies, project managers orchestrated timelines like conductors. The sequence was fixed: strategy → design → production → delivery. But software didn’t behave like print. Bugs appeared. Requirements shifted. Suddenly, the creative process needed to become a living process.

The clash between creative agencies and development houses became notorious. Designers spoke in emotion and metaphor; engineers spoke in logic and code. Each side needed the other but spoke a different language.

Briefs grew into huge documents - exhaustive manuals describing how to build even the simplest site. Offshore teams followed these scripts line by line, cutting costs but also cutting context. Phrases like “make it pop” or “colour it in” became shorthand for a growing disconnect between intent and execution. It was hard to hear. It still is. 

As projects grew larger, so did the gulf between design vision and digital delivery.

By the late 1990s, the internet demanded speed. Clients wanted results faster; agencies needed to adapt. 

Enter the era of agile methods.

Studios like R/GA, Sapient, Huge, and Accenture Interactive began experimenting with lighter-weight approaches: Rapid Application Development (RAD), Unified Process (UP), DSDM, Kanban, Scrum. Each promised flexibility, faster delivery, and more collaboration.

In 2001, a group of software pioneers published the Agile Manifesto, crystallising these ideas into four principles:

Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan.
It was meant to humanise engineering. Ironically, it also sidelined design.

As Agile spread through tech, “working software” became the dominant mantra. And design often got reduced to a service layer. UX and UI became checkboxes in Jira tickets. “Design thinking” was invoked often, but practised rarely.

Budgets tightened, documentation vanished, and design consistency suffered. Designers found themselves adapting to engineering timelines rather than shaping them.

Some agencies embraced the shift. They embedded designers inside development teams. Others resisted, clinging to the waterfall’s predictability. But across the industry, one truth became clear: 

“Design had lost ownership of the process it helped invent.”

By 2015, the pendulum began to swing back. Organisations started recognising that agility without alignment was chaos. Testing returned as a discipline. Knowledge management became essential again. Yet many design teams still struggled to find their place within the agile machine.

The problem wasn’t talent; it was translation.

Designers and engineers were using the same words - iteration, testing, feedback - but meant different things. Designers sought insight; engineers sought velocity. The result was cultural friction disguised as process inefficiency.

Authors Jeff Gothelf and Josh Seiden captured this perfectly in Sense and Respond: The End of Assembly Line Management. Their message: the digital revolution isn’t about doing more - it’s about learning faster.

To truly design at scale, organisations must rethink everything: team structures, process ownership, and even what “delivery” means. Software has become part of everything - every product, every service, every decision. The winners aren’t those who ship faster, but those who learn continuously.

Over the past decade, I’ve spoken with more than ninety design directors from global organisations about who inspires them - who they look to when building their own models of integration. The same names surfaced again and again: Google, IBM, McKinsey, IDEO, Frog, Airbnb.

Each represents a different response to the same question: How do we scale design in a digital world?

Google built ecosystems. IBM rebuilt its culture. McKinsey formalised design as strategy. IDEO taught the world to prototype. Frog shaped experience design before the term existed. Airbnb turned brand and product into one seamless human narrative.

Together, they illustrate the new model of integration - part Ford, part Toyota, part Baťa - where process, improvement, and purpose merge into a digital operating system for creativity.

This is the landscape Design at Scale™ was born into: a world where software defines experience, experience defines value, and design defines both.

The industrial era was about building things. The digital era is about building systems that build things better.

And in that transition - from factories to frameworks - design didn’t just change its tools. It changed its role in the world.