Why design thinking méthode became a theatre of post‑its
Design thinking méthode arrived in companies as a promise of creative innovation and fast problem solving. Many organisations adopted the design process as a universal solution, but the method often turned into a ritual where the team fills walls with sticky notes without touching real users. When this happens, the thinking process becomes a show and the design loses its power to address complex problems.
In a lot of workshops, people jump from vague problem statements to shiny ideas in a single stage, skipping the hard work of field research and user experience analysis. This shortcut breaks the human centered approach, because the users become personas on slides instead of people you have actually met and observed in context. When the design methods are reduced to templates, the design thinking label hides the absence of a robust process design and of any serious interaction design decisions.
Real design thinking is a thinking design discipline, not a brainstorming brand, and it relies on a clear sequence of stages design that connect research, synthesis, prototype building and test. The design council popularised this with the Double Diamond, which separates the stages of divergence and convergence to help teams define the problem before they chase any solution. When you respect these stages, the design process forces you to define problem statements based on evidence, then explore multiple solutions instead of falling in love with the first problem solution that sounds clever.
The real stages of a human centered thinking process
When you strip away the buzzwords, the design thinking méthode is a structured thinking process with distinct stages that alternate exploration and focus. A typical design process starts with immersion in the field to understand users, then moves to framing the problem, generating ideas, building a prototype and finally testing these solutions with real people. Each stage has its own goals, its own deliverables and its own risks if you rush it.
In the first stage, you observe users in their environment, you map systems thinking constraints and you collect stories about their problems with the current product or service. This human centered research will help you see not only individual pain points but also the wicked problems that emerge from organisational rules, legacy tools and interaction design patterns. When you come back from the field, you translate these observations into user centered insights that describe what people try to achieve, not what features they say they want.
The second and third stages design focus on reframing and ideation, where the team defines the problem in precise terms and then explores many ideas without judging them too early. Here, a strong facilitator keeps the centered design approach alive by constantly bringing the discussion back to users, their context and the systems that shape their experience. For readers who want to see how intentionality and responsibility change this approach in practice, the analysis of UX Days on ethical UX strategies shows how a design council mindset can coexist with critical reflection about the impact of innovative solutions.
From workshop theatre to grounded UX: fixing the process design
Many UX and UI teams feel that their design thinking méthode has turned into theatre because workshops are disconnected from delivery. Stakeholders enjoy the creative energy, but once the post‑its are photographed, the design process stops and the product roadmap follows old habits. This gap between thinking and doing is where most problems appear and where users lose.
To fix this, you need to treat every stage as a commitment, not as an event, and you must link the thinking process to concrete product decisions. When you define problem statements, you also define how success will be measured in the user experience, for example by tracking task completion time or error rates in a specific interaction design flow. During ideation, you prioritise ideas that can realistically become a prototype within days, because fast experiments will help the team learn which solutions actually reduce users’ problems.
Implementation also requires a clear handover between the UX équipe and the delivery équipe, with artefacts that translate centered design decisions into backlog items. In B2B platforms, for instance, a design thinking sprint that explores wicked problems around onboarding must end with interface specifications, content guidelines and systems thinking diagrams, not only with sketches. When outsourcing part of the UX work, aligning partners on this rigorous design process is essential, and resources about how to outsource UX design for better digital products show how a shared problem solution framework will help both équipes avoid superficial workshops.
What design thinking does uniquely well for UX and UI
When applied with discipline, the design thinking méthode brings something rare to digital projects : a human centered lens that connects business goals, technology constraints and user experience. The method forces the team to slow down before building, to define the problem clearly and to confront their ideas with reality through prototypes. This combination of empathy, experimentation and systems thinking is what makes design thinking a powerful design approach rather than a trend.
In UX and UI work, the early stages design are particularly valuable because they reveal misalignments between what people need and what the product currently offers. For example, a banking app redesign that starts with field interviews may uncover that users’ main problems are not visual but cognitive, such as understanding fees or predicting cash flow. By reframing the problem solution around clarity and predictability, the équipe can generate innovative solutions in interaction design, like progressive disclosure of information or simulations that show the impact of each action.
Prototyping is another area where the design process shines, because a low fidelity prototype reduces risk and invites feedback before heavy development. Testing several prototypes with different users will help you compare solutions, refine microcopy and adjust navigation patterns based on observed behaviour, not opinions. Over time, this iterative thinking design cycle builds a culture where problems are seen as hypotheses to test and where the design methods become a shared language between designers, developers and product managers.
Alternatives and complements: beyond a single design method
Relying only on one design thinking méthode can limit your perspective, especially when you face wicked problems that span multiple services and channels. UX équipes now combine the design process with other frameworks like Jobs to be Done, Lean UX and continuous discovery to keep their understanding of users fresh. This mix of design methods helps you adapt the thinking process to the scale and maturity of each product.
Jobs to be Done focuses on the progress people try to make in their lives, which deepens the way you define problem statements during the early stages design. Lean UX emphasises small experiments and shared learning, which aligns naturally with rapid prototype cycles and reduces the risk of over‑investing in untested solutions. Continuous discovery brings a rhythm where the team talks to users every week, so the human centered mindset does not disappear after the first workshop.
For complex systems like healthcare platforms or public services, systems thinking becomes essential because individual user experience issues are symptoms of deeper process design flaws. In these contexts, a centered design approach must consider policies, data flows and organisational incentives, not only screens and buttons. When you combine these perspectives with a rigorous design thinking process, you create space for innovative solutions that respect constraints while still improving life for users and frontline équipes.
How to know if your design thinking is working, not just noisy
One of the hardest parts of applying a design thinking méthode is evaluating whether it produces value or just noise. A useful test is to ask, after each stage, what changed in your understanding of the problem and in the shape of the solution. If the answer is vague, your thinking process probably stayed at the surface.
Start with the way you define problem statements : are they grounded in user data, or are they rephrased business goals. A strong design process turns fuzzy complaints into precise descriptions of users, contexts and constraints, which then guide the search for solutions. During ideation, you can measure quality by the diversity of ideas and by how clearly each idea links back to the original problems and to the user experience you want to improve.
On the delivery side, the impact of your prototype tests and interaction design changes should appear in concrete indicators like task success rate, support tickets or retention. If several cycles of centered design work do not change these metrics, you may be solving the wrong problems or ignoring systems thinking factors such as organisational rules. In mature équipes, the design council or design leadership reviews these results regularly, not to judge the designers, but to refine the design methods so that every new project will help the whole organisation learn how to tackle complex problem solution challenges more effectively.
Key figures about design thinking and UX practice
- According to a survey by the Design Management Institute, design driven companies outperformed the S&P 500 by more than 200 percent over a ten year period, which suggests that a strong design process can correlate with better business performance.
- Research from McKinsey on design index scores showed that organisations with mature design practices increased their revenues and shareholder returns at nearly twice the rate of their industry peers, highlighting the impact of user centered and human centered approaches.
- A study by the Nielsen Norman Group reported that involving users early in the design process can reduce development time by up to 50 percent and decrease the number of severe usability problems, which confirms that prototype testing with real users will help avoid costly rework.
- Data from the Interaction Design Foundation indicates that UX investments can deliver a return on investment of up to 9 000 percent in some cases, especially when design thinking is integrated into strategic decision making rather than limited to isolated workshops.
FAQ about design thinking méthode in UX and UI
How is design thinking different from a classic project process design ?
Design thinking differs from traditional project management because it starts with users and problems, not with predefined solutions or technical constraints. The method uses iterative stages design, including research, ideation, prototype creation and testing, to refine both the problem definition and the solution. This human centered and user centered approach reduces the risk of building products that people do not need.
Can design thinking work for small équipes and freelance designers ?
Yes, the design thinking méthode scales down well, because its core is a flexible thinking process rather than heavy documentation. A freelance designer can run lightweight stages, such as quick user interviews, paper prototypes and short feedback loops, to keep a centered design mindset. Even with limited resources, this approach will help you align your ideas with real user experience needs.
How do I avoid the “post‑it theatre” effect in workshops ?
The key is to connect every workshop to clear decisions and follow up actions in the design process. Before the session, define problem statements based on research, and after the session, select a small number of ideas to turn into a prototype within days. Sharing results with stakeholders closes the loop and shows that the design methods are tools for problem solving, not entertainment.
Is design thinking suitable for technical or back end products ?
Design thinking is relevant even for highly technical products, because there are always users, whether they are developers, operators or internal équipes. By applying systems thinking and interaction design principles, you can map their workflows, identify problems and test solutions that improve efficiency and reduce errors. The same stages design apply, but the prototypes may focus more on configuration screens, dashboards or APIs.
What role does the design council or design leadership play in this méthode ?
A design council or design leadership group ensures that the design thinking méthode is applied consistently across projects and that it stays aligned with organisational goals. They define standards for the design process, support équipes in complex problem solution work and protect time for research and testing. This governance structure will help transform isolated innovative solutions into a coherent, user centered strategy.