Design Thinking for Leadership, Not Just Products
In this BLISS Monologue, Tullio Siragusa makes the case for design thinking for leadership rather than products only, and walks through the four questions that turn a recurring organizational problem into one small, testable design move.
Design thinking for leadership starts from the same place the product version does, with empathy, and that is exactly why it belongs in the leadership toolkit. In this BLISS Monologue, host Tullio Siragusa reframes a method most people associate with user interfaces and innovation workshops as a way to design the conditions a team actually works inside.
In this episode we explore:
• The three misdiagnoses leaders make: pressure, control, and urgency
• Why metrics tell you what happened and empathy tells you why
• How defining the problem too quickly guarantees the wrong solution
• Where force field analysis and OKRs fit into a leadership design loop
• A 30 minute Design Thinking Leadership Sprint you can run this week
Three Problems Leaders Keep Solving With the Wrong Tool
Tullio names the pattern in three lines. Leaders “try to solve execution problems with pressure when the real issue is design.” They “try to solve accountability problems with control when the real issue is unclear ownership.” They “try to solve performance problems with urgency when the real issue is emotional friction.” In each case the intervention is aimed at the symptom, and the symptom keeps coming back.
Design thinking, he argues, is what slows a leader down just enough to design the right system instead. The starting move is empathy, and the reason is practical rather than sentimental: “Metrics tell what happened. Empathy explains why it happened.”
Most Organizations Solve the Wrong Problem
The second step is where he spends the most time, because it is where the damage is done. “People need to be more accountable” sounds like a problem statement, but Tullio lists what it usually turns out to mean: decision rights are unclear, priorities are conflicting, the team is over-committed, people are afraid to surface bad news, or the process is simply broken. Define it wrong and “every solution creates more frustration.”
His tool here is force field analysis, which maps the driving and hindering forces around a desired outcome. The value is not the diagram. It is that the conversation moves “away from blame and towards systems truth.” Once the right problem is defined and a design move is chosen, OKRs give it focus and measurement: an objective like improving cross-functional execution, with key results such as reducing project delays by 30 percent, clarifying decision rights on top priorities, and moving a team clarity score from a six to an eight.
Leading by Designing, Not by Answering
The shift he is describing is a change in what a leader's job is. “We stop imposing answers, and we start designing environments. We stop reacting to symptoms, and we start solving the root causes of problems.” And the definition of BLISS gets sharper alongside it: “Bliss is not just people feeling good. Bliss is people feeling understood, focused, and empowered.”
The practical version fits in half an hour. Take one recurring problem and run a Design Thinking Leadership Sprint around four questions: what is the real experience people are having, what is the actual problem rather than the symptom, what are three possible design moves, and what is one small test we can run this week. His instruction is to not overcomplicate it, just practice leading this way.
The same discipline is what separates marketing that works from marketing that is busy. At Zero Company the equivalent question is whether a campaign is solving the audience's real problem or the one that was easiest to write a brief about, and the answer usually comes from listening before building.
Key Takeaways
• Design thinking is not only a product method: it starts with empathy, “and empathy is the foundation of every healthy, high-performing organization.”
• Misunderstand the team and you design the wrong culture, the wrong operating model, and the wrong expectations, the same way misunderstanding the customer produces the wrong offer.
• Three recurring misdiagnoses: execution problems answered with pressure, accountability problems answered with control, performance problems answered with urgency.
• Empathy earns its place on evidence, not sentiment: “Metrics tell what happened. Empathy explains why it happened.”
• The four empathy questions: where are we getting stuck, what is harder than it should be, what feels unclear, and “what are we pretending is working that is not working?”
• “People need to be more accountable” is rarely the real problem. It usually means unclear decision rights, conflicting priorities, over-commitment, fear of surfacing bad news, or a broken process.
• Force field analysis identifies driving and hindering forces and moves the conversation “away from blame and towards systems truth.”
• OKRs come after the problem is defined, not before: improve cross-functional execution, reduce project delays by 30 percent, clarify decision rights, raise a team clarity score from six to eight.
• The leadership shift: “We stop imposing answers, and we start designing environments.”
• This week's move: a 30 minute Design Thinking Leadership Sprint on one recurring problem, using four questions and ending with one small test.
FAQ
What is design thinking for leadership?
Tullio Siragusa uses it to mean applying the design thinking sequence, empathy, problem definition, options, and small tests, to organizational problems rather than product problems. The leader designs the conditions people work inside instead of pushing harder on the symptom.
Why do leaders solve the wrong problem?
Because they define it too quickly. Tullio Siragusa's example is “people need to be more accountable,” which usually turns out to mean unclear decision rights, conflicting priorities, or fear of delivering bad news, and every solution built on the wrong definition creates more frustration.
How do you run a design thinking leadership sprint?
Tullio Siragusa's version takes 30 minutes and four questions: what is the real experience people are having, what is the actual problem rather than the symptom, what are three possible design moves, and what is one small test we can run this week.
This is Episode 4 of the BLISS Monologue Series. The next one, Rules of Engagement Shape the Culture, applies the same lens to everyday behavior. More from the BLISS Monologue Series.
