Why bridging business strategy and design takes more than a handoff

Somewhere in your company there is a slide, or a doc, or a set of notes from an offsite, that defines who you sell to, what you charge, and why you win. Somewhere else, usually a different tool, a different team, a different week, there is a set of Figma files defining what the product actually looks like and how it behaves. The two are rarely opened in the same meeting. That gap, business strategy and design living as two separate rooms inside the same company, is where most complex B2B products actually go wrong.

This is a sequencing default, not a decision anyone consciously made. Strategy gets settled first: the ICP, the positioning, the roadmap priorities. Once it feels finished, it gets written up and handed over, as a brief, a spec, a set of Notion pages, and design starts from there. By the time a designer opens a canvas, the strategic decisions already look fixed. Revisiting them feels like rework, not progress, so mostly, nobody does.

This is worth naming precisely, because the usual explanation, that design agencies "don't understand the business", puts the blame in the wrong place. Plenty of design partners try hard to understand the business before they start. The deeper problem is structural, not a matter of effort: whatever design discovers while actually building the product, that a feature nobody wants was in the roadmap, that the ICP definition doesn't hold up once real users are in the room, has nowhere to go back to. There is no loop built into the process for it. The fix is keeping strategy and design mutually editable for as long as the product is still being built, rather than treating either one as finished before the other starts.

What breaks when strategy and design drift apart

The output of this sequencing is usually fine on its own terms: the product looks coherent, it functions, and individually most of the screens make sense. What breaks is the fit between the product and everything else the company says about itself, the sales deck, the website copy, the positioning a prospect heard on a call two weeks before the demo. Each of those artefacts was accurate when it was written. None of them were updated when the others changed.

Buyers notice this even when they can't name it. Across nearly 4,000 B2B decision-makers surveyed in 13 countries for McKinsey's 2026 Global B2B Pulse Survey, inconsistent information between teams has become the top reason buyers walk away from a supplier, ahead of struggling to reach someone knowledgeable. A product built by a design team working from a six-month-old strategy document, sold by a team using this quarter's positioning, is exactly the kind of inconsistency that stat is describing. The design itself is rarely the problem, the drift between it and everything else is.

What it looks like when strategy and design don't hand off

Removing the boundary between strategy and design, rather than scheduling more meetings between the people who own each one, is what actually closes this gap: a change in one becomes a change in the other automatically, instead of something that has to be communicated, scheduled, and implemented three sprints later.

Noel Braganza, co-founder of Up Strategy Lab, puts it plainly: "In order to design a good product, you need to understand the sales gaps and other hindrances holding back growth. Same goes for marketing communication and design." The point isn't that one person needs to own all three. It's that none of them can be run as a closed process the others only hear about after the fact.

This isn't just a design studio's house opinion. Roger Martin, former Dean of the Rotman School of Management, spent six years proving the same point inside Procter & Gamble: a programme called DesignWorks that folded design directly into strategic planning instead of running it afterwards, first piloted in P&G's hair care division in 2005 and rolled out company-wide from there.

This is why the opening phase of every Up Strategy Lab engagement is a knowledge transfer: two weeks spent understanding the product, the ICP, and the sales process as deeply as the client does, before any design decisions get made.

That is exactly what happened with Viking Analytics, an AI-driven industrial predictive maintenance company. The engagement combined strategy workshops on ICPs, buying journeys, sales motion, and partner model with a full website rebuild, SEO and blog content, partner program development, and the redesign of MultiViz 2.0, run as one long-term engagement rather than separate contracts handed off between teams. MultiViz 2.0 launched as a fully reimagined version of the platform, built in close collaboration with users, reliability engineers, and partners.

What a knowledge transfer actually involves, and what it looks like when a design partner runs it properly, is worth reading in more detail if you are already comparing design partners for a complex B2B product.

Where the gap between strategy and design actually shows up

The clearest symptom is not a bad screen. It is a good screen that answers a question nobody is asking anymore: a permissions model built for an ICP the company has since narrowed, an onboarding flow that assumes a buyer persona that got cut from the positioning deck two positioning cycles ago. Individually, each of these reads as a reasonable decision: correct when someone made it, never revisited, because revisiting it wasn't anyone's job.

The fix has less to do with process than with proximity. Positioning conversations need someone in the room who will have to build the thing being positioned, not to approve it, but to ask the questions that only come up when you are trying to make an idea real. Design conversations need access to whatever changed since the brief was written, not as a courtesy update, but as an input worth acting on. Neither of these requires a reorganisation. It requires accepting that the strategy document was never actually finished, only paused.

Frequently asked questions

What does it mean to bridge business strategy and design?

It means treating strategic decisions, like who the product is for and why it wins, as inputs that keep updating throughout the design process, rather than a finished document handed to design once and left alone. In practice, this means the people making strategic calls stay involved while the product gets built, not just before it starts.

Why do strategy and design usually happen as separate phases in B2B companies?

Mostly because of sequencing, not intent. Strategy work, like positioning and ICP definition, tends to get finished and documented before design begins, and once it's written down it starts to feel fixed. Design then treats that document as a stable input rather than a hypothesis, so new information the design process surfaces rarely makes its way back into the strategy.

How does separating strategy from design actually damage a product?

The product itself usually still functions and looks coherent. What breaks is its consistency with everything else the company says about itself, in sales conversations, on the website, in positioning. Because strategy and design update on different schedules, those things drift out of sync with each other, and buyers notice the inconsistency even when they can't point to a specific screen that's wrong.

What does it look like when a company integrates strategy and design instead of sequencing them?

The same people, or a genuinely integrated team, hold both functions at once, so a change in positioning or ICP becomes a change in the design brief immediately, not three sprints later. Up Strategy Lab's work with Viking Analytics is a working example: strategy workshops on positioning, buying journeys, and partner model ran alongside the redesign of their MultiViz platform as one continuous engagement, not two sequential ones, so a decision made in either could still change the other while both were still in progress.

If your product already looks finished but keeps needing to be re-explained to match what your sales team is currently saying, the fix usually sits in how the two are sequenced, not in the design itself. If you're already comparing partners, how to choose a design partner for a complex B2B product is the more practical next read. If you want to talk through where the gap actually sits in your product, let's talk.