I get a version of the same question at least twice a week. "We know design should be entering our programs earlier. We've known it for a while. Where do we actually start?"
The question comes from CEOs running programs in powersports, power equipment, agricultural machinery, defense, automotive aftermarket, commercial vehicles. Companies doing anywhere from $20M to $500M in revenue, building real products that have to compete in real markets.
They're not asking me to explain why design matters. They already know. They've felt it — in a product that came out of tooling looking assembled rather than designed. In a launch that should have commanded a premium but got squeezed on price because nothing distinguished it from what was already on the shelf. In a program that went over schedule and over budget because problems that should have been caught at concept were caught at production.
They're asking something harder: given where we are today, with the programs we have running, with the team we have — what's the actual first move?
You Don't Have to Overhaul Everything. You Have to Answer One Question Honestly.
The first move in Design Intelligence isn't a process change. It isn't a hiring decision. It isn't a new framework or a consultancy engagement. It's a single, honest diagnostic question:
At what point in your product development process does design actually shape a decision — not a render, not a surface, a decision?
— The question every manufacturing CEO needs to answer honestly
Not when do you bring in a designer. When does design thinking influence what gets built, who it's for, how it sits in your portfolio, what the customer will pay for it, and why it's defensible against the competition?
If the answer is "after engineering sets the architecture," you have a sequencing problem. If the answer is "when we're ready to show customers something," you have a sequencing problem. If the answer is "we don't really have a formal answer to that question," you definitely have a sequencing problem.
That sequencing problem has a cost. Every week design is absent from that first 20% of the program is a week those decisions get made without the discipline that exists to make them better. That's not a design argument. That's a capital allocation argument.
The Five Components — And Which One You're Actually Running
Design Intelligence is a system with five components. Most mid-market manufacturers are running one, maybe two of them.
1. Market Intelligence
Understanding who the customer actually is, what they value, and what they'd pay more for — before a single program assumption is made. Not what you think they want. What the research says they need that they're not getting.
2. Portfolio Intelligence
Designing your product line as a coherent system, so every product earns its place and strengthens the whole. The question isn't just "what should this new product be?" It's "where does it sit relative to everything above it, below it, and across from it in the competitive set?"
3. Product Intelligence
Defining what the product is — and what it isn't — with design thinking shaping feature architecture alongside engineering, not after it. This is where the sequencing decision gets made. This is where most mid-market manufacturers lose the most value.
4. Design Execution
The actual industrial design, engineering, CMF, and visual brand language that turns strategy into something you can hold. This is the component most people think of when they say "design." It's the most visible. It's also the least differentiating if the first three components aren't already doing their job.
5. Execution Intelligence
The standards, systems, and processes that make design-led development repeatable across programs, teams, and years. Visual brand language documentation. Design review protocols. The mechanisms that prevent coherence from being dependent on one person who happens to carry the brand in their head.
When I ask a CEO which of these five they're running, the most common answer is four — with occasional, inconsistent contributions from three. The companies running all five are the ones that, from the outside, look like they just make better products. They do. But it isn't talent. It isn't luck. It's sequence and system.
Where to Start, Based on Where You Are
The right starting point depends on your situation. Here are the three most common ones.
You have a program that just launched and it's underperforming.
Don't start upstream. Start with a post-program diagnosis. Sit in a room with the honest people on your team and answer three questions: What did we know about the customer before we committed the tooling budget? What design decisions got made before a designer was in the room? And if we had to describe the product's visual brand language in writing — rules a new engineer could follow on day one — could we do it? The answers will tell you where the sequencing failed. That's your starting point for the next program.
You have an active program in development.
Find the nearest decision point that design can still influence and get design into that room. Not to approve aesthetics — to ask the market questions that prevent the sequencing failure you've made before. Who is this for, specifically? What will they pay a premium for that we haven't built in? Does this product look and feel like it belongs in our line? The earlier you can get those questions on the table, the cheaper the answers are.
You're planning a new program.
This is where the full five-component system pays off most. Before engineering writes a spec, before product management writes a brief, run a discovery sprint. Two to four weeks. Market research. User insight. Competitive mapping. A clear answer to the question: what would this customer pay more for that nobody is currently giving them? Build the brief from that answer. Let engineering respond to that brief. That sequence — customer insight first, engineering response second — is the difference between a product that commands price and a product that competes on price.
The Argument in One Paragraph
Companies in the top quartile of design performance generate 32% more revenue than their industry peers over five years — not because they hired better designers, but because they integrated design earlier and deeper into strategic decision-making. The sequencing decision — when design enters the program — is the single highest-leverage variable in product development. And for mid-market manufacturers building real products in competitive markets, it's almost entirely under leadership control. No new budget required. No new headcount required. A different sequence, a different set of questions asked earlier, and a deliberate decision about which outcomes design is responsible for shaping.
That's where Design Intelligence starts. Not with a redesign. With a question asked one phase earlier than you're currently asking it.
