Design thinking in B2B: how to shorten the path from problem to implementation

The product team gets a signal from sales: customers don't understand why they need the new module in the system. Three months of work, two presentations, zero implementations. The next meeting starts with the question "so what do we do next?" and once again a list of ideas appears, each sounding reasonable until it has to be defended in front of the board. And this is exactly where design thinking stops being a buzzword from a conference and becomes a tool for breaking the loop. Before we get into specifics, though, it's worth seeing where this method delivers the most in B2B.

Where design thinking genuinely helps in B2B

Design thinking is described as a method for working on complex tasks, based on the way designers operate. In practice it comes down to a sequence: observation, understanding, brainstorming, building a prototype, refinement, and implementation. Klaus Kreutzer in Toolbox für Marketing und Management (2019) points out that you can return to these phases multiple times to maximize the learning effect. That statement is worth taking literally: the design thinking process is not a production line, it is a loop.

In B2B, however, this loop carries different loads than in consumer products. The purchasing decision goes through several people, the sales cycle lasts for months, and the cost of a mistake can be high. That is why design thinking in B2B is not about inventing breakthrough concepts. It is about stopping the building of things nobody will buy, and about seeing early where the customer's process actually breaks.

Typical places where this method delivers the most:

• a new subscription service that nobody has bought yet, and the team doesn't know how to price it,
• a rebuild of the purchasing path where the customer gets lost between the offer, the contract, and implementation,
• communication for a new product category, where the market doesn't yet know the name of the problem,
• customer onboarding after signing the contract, when the first 30 days decide retention.

In each of these cases, the starting point is the question "what exactly does our customer do today and where do they stop".

The design thinking process step by step, without academic baggage

Below is a version you can run in a B2B company within four to six weeks, without hiring an external facilitator full-time.

1. Observation: go where the work happens

This is not about a satisfaction survey. It is about watching how the customer performs the task your product is meant to solve. In B2B this usually means two or three client visits, a conversation with the person who actually uses the tool, and with the person who bought it. The difference between these two perspectives can be greater than between two companies from different industries.

2. Understanding: turn notes into a single problem statement

After observation, the team usually has dozens of quotes and observations. The task is to find the pattern and write it as a statement: "[customer type] is trying to [goal], but [barrier], because [cause]". If you can't write it in one sentence, you don't have a problem, you have a wish list.

3. Brainstorming: ideas for the barrier, not for the product

The most common mistake is generating ideas for features. It is better to generate ideas for removing a specific barrier from the written statement. That way, even rejected concepts leave knowledge behind, because it is clear which barrier they addressed.

4. Prototype: something you can show in 15 minutes

A prototype in B2B is rarely an app mockup. More often it is a one-page process description, a sketch of a new offer section, a sales conversation script, or a manually prepared report that the system would normally generate. The goal is to check the reaction, not to build the product.

5. Refinement and implementation

After testing, you return to earlier phases, usually to understanding the problem, because the first attempts show that the barrier was different than it seemed. Only after two or three iterations does a conversation about implementation and budget make sense.

Design thinking in practice: what to collect and from whom in B2B

Customer-centered design in B2B most often breaks down because the team collects data from one easily accessible group: the people who buy. But the purchasing decision in companies plays out among at least three roles: the user, the person who approves the budget, and the person who has to implement the solution. Each of them looks at a different set of criteria.

In practice, it is worth keeping three separate observation logs:

• the user: what they do every day, where they lose time, what they avoid,
• the decision-maker: how they justify the purchase to the board, what numbers they use, what they are afraid of,
• the implementer: how much work it takes to launch, what can go wrong, who needs to be informed.

When these three perspectives are kept separate, it very often turns out that a product that "does not work" has no problem with its features at all. Its problem is that the decision-maker cannot show its value in their own language, and the implementer never received a plan for the first two weeks.

It is also worth remembering that observation material does not have to be collected only in the field. Sales conversations, support tickets, demo recordings, and threads from implementation meetings are a ready-made base. In B2B, the place and moment in which the client sees your message changes its meaning, so it is worth testing prototypes in the real context of a sales conversation, not only in a workshop room.

A prototype you can show to the sales department

The greatest value of a prototype in B2B is that it gives salespeople something they can take into a conversation and test with three or four clients within a week. This changes the nature of the discussion: instead of arguing about whether the idea is good, the team collects concrete reactions.

Three formats that work most often:

1. A one-page description of the solution with the barrier it addresses highlighted. The salesperson reads it to the client and notes down questions.
2. A conversation script with a new opening question that comes from observation rather than from a list of features.
3. A manually prepared report or calculation that the system is ultimately meant to generate. It checks whether the client even wants that kind of output.

After every attempt we return to the understanding phase. Kreutzer describes this as the ability to move between phases multiple times, and that is the essence: a prototype is not meant to confirm that an idea is right, it is meant to gain information that was not available before.

When design thinking fails and what to do about it

Design thinking is not a universal tool, and in several situations it simply does not work.

• No access to the client. If the team cannot talk to users or watch them work, the process turns into an internal workshop about nothing. The fix: start with the data you already have and treat it as temporary material for observation.
• The problem is operational, not a design problem. If a client does not buy because delivery takes three weeks, no prototype iteration will fix that. Process first, design second.
• The team has no mandate to change anything. A workshop without someone who can approve implementation ends with a report on a shelf. Invite the decision-maker to the understanding phase, not just to the results presentation.
• There is no time for iterations. A one-off workshop is not a design thinking process. If you only have one day, it is better to do a solid problem analysis than to fake a full cycle.

It is also worth distinguishing design thinking from marketing research. Research answers the question of what is, while design thinking tries to build something that does not exist yet and test it in action. One does not replace the other.

How to embed design thinking in your B2B marketing strategy

Design thinking works best when it is part of everyday work on communication, the offer, and the customer journey. It delivers the most value when it becomes the way you carry out that work. In practice, this means three changes in daily operations.

First, marketing briefs start with a statement of the client's problem, not with a list of features to promote. Second, sales materials are tested on clients before publication, not after the campaign. Third, the team has a steady rhythm for collecting observations: a monthly review of sales conversations and support tickets, which produces candidates for the next iterations.

This approach fits well with a broader action plan in which marketing is a system of decisions based on knowledge about the client. Most companies that implement design thinking do so as part of a broader B2B marketing strategy, where this method is one of the tools, not a goal in itself.

At Growth Group we work with companies across the region. According to our internal data, over 16+ years we have run projects for more than 60 clients, with substantial advertising budgets under our care. In practice, we see that teams which regularly return to client observation are less likely to burn budget on campaigns nobody needed.

If you want to check where design thinking will deliver the fastest results in your marketing process, a good starting point is a review of your current B2B marketing strategy and finding the place where decisions are made without contact with the customer.