Your Machine Factory Needs a Design Strategy
Why the next competitive advantage in manufacturing won’t come from engineering alone
There is a type of company that rarely appears in the pages of business magazines or on the stages of innovation conferences. It makes industrial equipment, or precision components, or packaging machinery, or systems for food processing. It has been doing so for twenty, forty, sometimes eighty years. It has deep engineering expertise, long client relationships and a quiet confidence rooted in making things that work.
It also has a problem it hasn’t fully reckoned with.
The problem is not that the machines have stopped working. They work beautifully. The problem is that the definition of what a machine is (and what a machine company sells…) is changing underneath them. And the companies that see this shift clearly are pulling ahead of those that don’t, not by making better hardware, but by rethinking what surrounds it.
The platform shift
For most of their history, industrial manufacturers have competed on mechanical performance. Precision, throughput, reliability, energy efficiency. These are the metrics that defined excellence, and rightly so. A machine that runs faster, breaks less and uses less power is a better machine. Full stop.
But something has changed in the past decade that makes mechanical performance necessary but no longer sufficient. Sensors have become cheap. Connectivity has become ubiquitous. Computing power that once required a server room now fits on a chip the size of a postage stamp. The result is that machines can now generate data about their own performance, about the materials they process, about the environment they operate in. And that happens to take place at a scale and granularity that was unimaginable fifteen years ago.
This changes the competitive equation fundamentally. The machine is no longer just a machine. It is a platform, a node in a larger system of data, services and decision-making. The manufacturers who understand this are building digital layers on top of their hardware: predictive maintenance systems, remote monitoring dashboards, performance optimisation algorithms, digital twins. Not as afterthoughts or marketing exercises, but as integral parts of the value proposition.
The ones who don’t understand it are still competing on spec sheets. They will continue to win orders for a while, on the strength of their engineering reputation. But the margins will compress. The differentiation will erode. And one day they will discover that their client has switched not because the competitor’s machine was better, but because the competitor’s ecosystem was.
The Nokia problem
There is an objection that comes up almost every time I raise this with an industrial client. It is sincere, it is understandable, and it is wrong. The objection is: “Our customers aren’t asking for this.”
Of course they aren’t. Customers describe their needs in the language of what already exists. They ask for faster machines, not for platforms. They ask for lower maintenance costs, not for predictive algorithms. They ask for better documentation, not for digital twins. This is not a failure of imagination on their part. It is simply how demand works: people optimise within the frame they know.
Nokia’s customers weren’t asking for a touchscreen either. They were asking for better battery life, more durable casing, a slimmer profile. All perfectly reasonable. All entirely beside the point once the frame shifted.
The lesson is not that you should ignore your customers. The lesson is that listening to customers will tell you how to improve your current offer. It will not tell you when the offer itself needs to change. That requires a different kind of attention, a willingness to look at your product not as your engineering team sees it, but as someone might see it five years from now, when the expectations around it have changed.
Why technology alone isn’t the answer
Here is where the story usually goes wrong. A manufacturer recognises the shift. The board agrees that “digitalisation” is important. A budget is allocated. A technology partner is hired. Sensors are installed. A dashboard is built. Data starts flowing.
And then nothing happens.
The dashboard exists, but nobody looks at it. The data is there, but nobody acts on it. The system technically works, but it has not been integrated into anyone’s workflow, decision-making or daily reality. The operator on the factory floor finds it confusing. The maintenance engineer doesn’t trust it. The client who was promised “smart manufacturing” sees a login screen they’ve opened once.
This is not a technology failure. It is a design failure.
Not design in the sense of making things pretty. Design in the sense of making things work for people. The discipline of understanding who will use a system, in what context, under what constraints, and shaping the system to fit that reality rather than expecting people to adapt to the system.
Industrial design has always been central to manufacturing, in the physical sense. The ergonomics of an operator interface, the layout of a control panel, the accessibility of maintenance points. These are design decisions, and good manufacturers take them seriously. But when it comes to the digital layer, many of the same companies abandon this discipline entirely. They hand the interface to software developers, the user experience to whoever has time, and the workflow integration to the client’s IT department.
The result is predictable: technology that is technically capable and practically useless.
The design gap in digital transformation
What makes this problem particularly stubborn is that it sits between traditional responsibilities. The engineering team owns the machine. The software team owns the digital platform. Nobody owns the experience of using them together.
This is not an organisational oversight. It is a conceptual one. Most manufacturers still think of the physical product and the digital product as two separate things… (yes they still exist…) one that they know how to do and one that they’re learning. In reality, the customer doesn’t experience them separately. They experience one thing: a machine that either helps them do their job better or doesn’t. The seam between hardware and software, between the physical interface and the digital one, between the machine’s behaviour and the data it produces. That seam is where most digital transformations fail.
Closing that seam requires a particular kind of design thinking. Not the Post-it note variety, the engineering variety. Industrial design that extends from the physical product into the digital experience. Service design that maps the entire lifecycle of the machine, from installation through daily operation to maintenance and eventual replacement. Interaction design that treats the dashboard not as a reporting tool but as a decision-making environment.
This is detailed, technical, deeply contextual work. It requires spending time on factory floors, understanding shift patterns, watching how operators actually interact with equipment rather than how the manual says they should. It is the kind of design work that cannot be done from a studio in a capital city. It has to be embedded in the engineering process, not layered on top of it.
Why the traditional consulting model doesn’t work here
A manufacturer facing this challenge has several options, and most of them are inadequate.
Option one: hire a strategy consultancy. They will produce an excellent analysis of the market opportunity, a digital maturity assessment, and a transformation roadmap. The deck will be compelling. It will also be almost entirely abstract. The strategy team does not design interfaces, prototype services or test propositions with users. They tell you what to do, not how it should feel.
Option two: hire a technology firm. They will build the platform, install the sensors, connect the systems. The technology will be sound. But it will be built to technical specifications, not human ones. The software team knows how to make data flow. They do not necessarily know how to make a fifty-year-old maintenance engineer trust it.
Option three: hire a design agency. They will make it look beautiful. The interfaces will be clean, the branding will be consistent, the presentation will impress the board. But they may not understand the strategic logic behind the platform, or the technical constraints of industrial IoT, or the business model that needs to support it.
Each of these options addresses one dimension of the problem. None of them addresses the problem itself, which is fundamentally multi-dimensional: strategic, technological and experiential at the same time.
The case for a Hybrid approach
What manufacturers actually need is someone who can hold all three conversations simultaneously. Someone who understands the strategic logic, why the shift from product to platform matters, how it affects pricing, positioning and competitive dynamics. Who understands the technology, what sensors can and cannot do, how data architectures work, where the realistic boundaries of AI and machine learning lie today. And who understands design — how to translate all of that into something a human being can use, trust and integrate into their daily work.
This is not a matter of assembling a team of three specialists and hoping they align. The magic (if that’s the word…) is in the integration. When the same mind that shapes the strategic direction also shapes the user experience, the result is different in kind, not just in quality. There is no handoff. There is no brief that gets misinterpreted. There is no moment where the design team discovers that the strategy doesn’t work in practice, or where the technology team builds something that nobody asked for.
This is what we mean by the hybrid approach. Not a multidisciplinary team, but a transdisciplinary method. Strategy, design and technology as one integrated practice, applied to problems that don’t respect the boundaries between them.
For manufacturers, this approach is not a luxury. It is arguably more relevant here than in any other sector, because the gap between the physical and the digital, between the engineering culture and the design culture, between the traditional product and the smart product, is wider in manufacturing than almost anywhere else. Bridging that gap requires someone who lives on both sides of it.
Starting small, with direction
None of this requires a company to reinvent itself overnight. The most successful transitions I’ve seen start modestly: one engineer who develops a genuine understanding of sensor technology. One pilot project with a client willing to experiment with data-driven maintenance. One design sprint that reimagines the operator experience for a single machine in the fleet.
But modesty should not be confused with lack of ambition. The pilot needs to be connected to a larger vision; a clear idea of where the company is heading and why. Otherwise it becomes an isolated experiment, another innovation theatre production that delivers a demo and dies.
The companies that do this well share a few characteristics. They have leadership that understands the shift is real, not a trend. They invest in capabilities, not just projects. They treat the digital layer not as a bolt-on but as integral to what they sell. And they design for adoption from the start, not as an afterthought.
The coming divide
Five years from now (and five years is generous!) the industrial manufacturing landscape will look different. Not because the machines will be radically different. The core mechanical engineering will evolve incrementally, as it always has. What will change is the wrapper: the services, the data, the digital experience, the business models that surround the hardware.
The manufacturers who have invested in that “wrapper”, thoughtfully, with strategic clarity and design discipline, will have transformed from suppliers into partners. They will be embedded in their clients’ operations in ways that make switching costly and loyalty natural. They will command margins that their product-only competitors cannot match. Pure synergy.
The manufacturers who haven’t will still make excellent machines. But they will sell them in an increasingly commoditised market, competing on price and specs against rivals who compete on ecosystems and experiences.
The difference will not be technology. Technology is available to everyone. (hello AI!) The difference will be design: how well the technology was shaped to fit into someone’s world. And strategy: how clearly the company understood why that mattered before it was obvious.
If you run a machine factory and you’re reading this, the question is not whether this shift is real. It is. The question is whether you’re approaching it as a technology project or as a fundamental rethink of what your company offers and how it offers it.
The former will get you a dashboard. The latter will get you a future.