{"id":9177,"date":"2026-11-19T11:36:23","date_gmt":"2026-11-19T06:06:23","guid":{"rendered":"https:\/\/nextagile.ai\/blogs\/?p=9177"},"modified":"2026-11-19T11:37:58","modified_gmt":"2026-11-19T06:07:58","slug":"design-thinking-for-leaders-and-teams","status":"publish","type":"post","link":"https:\/\/nextagile.ai\/blogs\/design-thinking\/design-thinking-for-leaders-and-teams\/","title":{"rendered":"Design Thinking for Leaders and Teams: What Each Role Does Differently"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Design thinking for leaders and teams is a human-centred approach to solving business problems, improving experiences and developing practical solutions through collaboration and experimentation. While leaders establish strategic direction, allocate resources and create an environment for innovation, teams investigate user needs, challenge assumptions, develop ideas and test potential solutions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The distinction is important because successful innovation requires more than creative thinking. Leaders must identify the right problems and give teams the autonomy to explore solutions. Teams must translate those priorities into meaningful improvements supported by user research, experimentation and evidence.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When both roles work together, design thinking becomes more than an innovation exercise. It becomes an organisational capability that helps businesses improve customer experiences, strengthen internal processes and respond to changing market expectations.<\/span><\/p>\n<h2><b>Key Takeaways From This Blog<\/b><\/h2>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Leaders establish strategic priorities, sponsor innovation and create the conditions for experimentation.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Managers connect leadership expectations with team activities, resources and implementation responsibilities.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Teams use research, empathy mapping, problem reframing and prototyping to develop user-centred solutions.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cross-functional collaboration helps organisations solve problems that cannot be addressed effectively by individual departments.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Design thinking initiatives should be measured through validated learning, user outcomes and business improvements.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Leadership support is essential for moving successful experiments from prototypes into everyday operations.<\/span><\/li>\n<\/ul>\n<h2><b>Why Leaders and Teams Need Different Approaches to Design Thinking<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Consider an organisation experiencing declining customer satisfaction. Senior management believes a new digital platform will improve the customer experience, while customer service employees believe the real problem is slow complaint resolution.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The technology team starts exploring possible solutions, operations identifies process bottlenecks and customer service highlights communication gaps. Everyone wants to improve the experience, but each department sees the problem differently.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This is where design thinking becomes valuable. It helps leaders establish the business challenge while enabling teams to investigate actual user experiences before committing to solutions. Instead of assuming what needs to change, the organisation develops a shared understanding of the problem.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Design thinking is therefore not limited to product designers or innovation specialists. It is equally relevant to executives making strategic decisions, managers coordinating teams and employees working directly with customers and internal processes.<\/span><\/p>\n<h3><b>Leadership and Team Responsibilities in Design Thinking<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Although leaders and teams follow the same overall approach, their responsibilities differ at each stage.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Responsibility<\/b><\/td>\n<td><b>Leaders and executives<\/b><\/td>\n<td><b>Managers and teams<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Problem identification<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Identify strategic business challenges.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Investigate specific user and operational problems.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">User understanding<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Provide access to customers and stakeholders.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Conduct interviews, observations and research.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Problem framing<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Establish business context and desired outcomes.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Translate insights into actionable problem statements.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Ideation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Encourage exploration and challenge assumptions.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Generate and evaluate potential solutions.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Experimentation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Allocate resources and establish boundaries.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Build prototypes and test assumptions.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Decision-making<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Make strategic and investment decisions.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Recommend improvements based on evidence.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Implementation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Remove organisational barriers and establish priorities.<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Collaborate with delivery teams to implement validated solutions.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">The distinction is important because leadership without team involvement can produce solutions based on assumptions. Similarly, teams without leadership support may develop promising ideas but struggle to secure resources or implement them.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Understanding the<\/span><a href=\"https:\/\/nextagile.ai\/blogs\/design-thinking\/design-thinking-principles\/\"> <span style=\"font-weight: 400;\">design thinking principles for business problem-solving<\/span><\/a><span style=\"font-weight: 400;\"> helps organisations establish a common approach to identifying opportunities, understanding users and evaluating solutions.<\/span><\/p>\n<h2><b>What Leaders Own in Design Thinking<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Design thinking for leaders involves creating the conditions in which innovation can happen consistently. Leaders are not expected to generate every idea or participate in every research activity. Their responsibility is to ensure that teams are solving meaningful problems and have the support needed to explore possible solutions.<\/span><\/p>\n<p><a href=\"https:\/\/nextagile.ai\/corporate-leadership-training\/\"><span style=\"font-weight: 400;\">Effective leadership<\/span><\/a><span style=\"font-weight: 400;\"> also requires knowing when to provide direction and when to step back. Too little involvement can leave teams without clarity, while excessive control can discourage experimentation and prevent employees from exploring alternative approaches.<\/span><\/p>\n<h3><b>Sponsoring Innovation and Protecting Time for Experimentation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Innovation requires more than asking employees to think creatively. Teams need time, resources and access to relevant information before they can investigate problems and test potential improvements.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Leaders should protect time for experimentation, provide access to customers and employees, and remove approval barriers that unnecessarily delay small experiments. They should also make sure that teams have the right combination of business, operational and technical expertise.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, an organisation experiencing high employee turnover may initially consider introducing a new onboarding platform. Leadership can instead sponsor an investigation into employee experiences, allowing the team to identify whether unclear responsibilities, inconsistent communication or limited manager support are the real issues.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This approach helps organisations avoid investing in solutions before understanding the problem. It also creates opportunities to test smaller improvements before committing to larger initiatives.<\/span><\/p>\n<h3><b>Design Thinking for Executives: Setting Direction and Decision Rights<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Design thinking for executives requires connecting human-centred problem-solving with organisational strategy. Executives must determine which challenges deserve attention and establish the boundaries within which teams can experiment.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This includes defining strategic priorities, approving appropriate budgets, clarifying decision-making authority and agreeing on how outcomes will be evaluated. Teams should understand which decisions they can make independently and which require leadership involvement.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, an executive may identify customer retention as a strategic priority without prescribing a particular technology or service improvement. Cross-functional teams can then investigate customer experiences and recommend solutions based on their findings.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This balance gives employees the freedom to explore alternatives while ensuring that innovation remains connected to business objectives.<\/span><\/p>\n<h3><b>Reviewing Research Findings, Prototypes and Business Opportunities<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Leaders must evaluate evidence rather than favouring ideas simply because they appear innovative or align with existing assumptions. Research findings and prototype feedback should form the basis of investment and implementation decisions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A useful approach is to evaluate potential solutions through three dimensions:<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Decision factor<\/b><\/td>\n<td><b>Question leaders should ask<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Desirability<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Does the solution address a genuine customer or employee need?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Feasibility<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Can the organisation realistically develop and implement it?<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Viability<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Does the solution support business priorities and long-term value?<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">For instance, a prototype may receive positive feedback from a small group of customers but require substantial operational investment. Leaders should consider whether the opportunity justifies further testing before approving a wider rollout.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The objective is not to select the most impressive idea. It is to identify solutions that create user value, can be implemented effectively and make business sense.<\/span><\/p>\n<h3><b>Creating Psychological Safety for Innovation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Employees are more likely to identify problems and suggest improvements when they feel comfortable expressing different opinions. This is particularly important when design thinking requires teams to challenge established processes or question decisions made by senior stakeholders.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Leaders can encourage this behaviour by welcoming constructive disagreement, asking open questions and treating unsuccessful experiments as opportunities to learn. Building <\/span><a href=\"https:\/\/nextagile.ai\/workshop\/emotional-intelligence-for-leaders\/\"><span style=\"font-weight: 400;\">emotional intelligence for leaders<\/span><\/a><span style=\"font-weight: 400;\"> also helps them respond to disagreement with curiosity rather than defensiveness. They should also recognise employees who identify overlooked problems rather than rewarding only successful implementations.<\/span><\/p>\n<p><a href=\"https:\/\/nextagile.ai\/blogs\/leadership\/building-a-culture-of-psychological-safety\/\"><span style=\"font-weight: 400;\">Psychological safety<\/span><\/a><span style=\"font-weight: 400;\"> does not remove accountability. It allows employees to investigate ideas, share evidence and learn from mistakes without fearing unfair criticism.<\/span><\/p>\n<h2><b>The Leadership Balancing Act: Control Versus Autonomy<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">One of the biggest challenges in design thinking in leadership is finding the right balance between organisational control and team autonomy. Leaders must maintain accountability while allowing employees enough freedom to discover solutions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Three common leadership dilemmas illustrate this challenge.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Leadership dilemma<\/b><\/td>\n<td><b>Recommended approach<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Business targets versus experimentation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Protect limited time and resources for structured experiments.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Strategic control versus team autonomy<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Set clear boundaries but allow teams to develop solutions.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Speed versus user validation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Encourage rapid testing instead of premature implementation.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Managers play an important role in maintaining this balance. They translate strategic priorities into achievable team objectives, coordinate resources and ensure that experiments do not disrupt essential business operations.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, a team investigating customer complaints may be allowed to test a revised service workflow with a limited customer group. Leadership establishes the scope and success criteria, while the team determines how to improve the experience.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This creates accountability without restricting problem-solving to predetermined solutions.<\/span><\/p>\n<h2><b>Five Leadership Mistakes That Stall Design Thinking Initiatives<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Even organisations that understand the value of design thinking can struggle to make it part of everyday work. The problem often lies in how leaders introduce the approach and whether they support it beyond the initial initiative.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The following mistakes can limit innovation and prevent teams from converting ideas into meaningful outcomes.<\/span><\/p>\n<h3><b>1. Starting With a Predetermined Solution<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Leaders sometimes approach an organisational challenge with a preferred solution already in mind. For example, they may decide to introduce a new customer service platform before investigating why customers are dissatisfied.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This limits exploration and encourages teams to validate an existing decision rather than understand the underlying problem. Leaders should begin with an open-ended challenge and allow research findings to guide solution development.<\/span><\/p>\n<h3><b>2. Treating Design Thinking as a One-Time Exercise<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A single brainstorming session can generate interesting ideas, but it cannot replace continuous research, experimentation and refinement. Without follow-up responsibilities, teams may struggle to move beyond initial concepts.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Leaders should integrate design thinking into regular business activities. Establishing checkpoints for prototype testing, feedback and implementation helps maintain momentum and creates opportunities for continuous improvement.<\/span><\/p>\n<h3><b>3. Ignoring User Research and Employee Feedback<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Internal assumptions do not always reflect actual customer or employee experiences. A solution that appears practical from a management perspective may introduce additional complexity for the people expected to use it.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Leaders should ensure that teams regularly interact with users through interviews, observations and feedback sessions. These insights provide a stronger basis for decisions and reduce the risk of developing irrelevant solutions.<\/span><\/p>\n<h3><b>4. Expecting Immediate Results Without Allowing Experimentation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Innovation involves uncertainty, and teams may need several iterations before finding an effective solution. Expecting immediate results can encourage employees to choose familiar approaches instead of investigating alternatives.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Leaders should establish realistic experimentation timelines and measure early progress through learning, validated assumptions and user feedback. Business outcomes can then be evaluated as solutions become more mature.<\/span><\/p>\n<h3><b>5. Failing to Connect Prototypes With Implementation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A prototype is useful only when its findings inform future decisions. Promising ideas can lose momentum when there is no clear ownership, implementation plan or connection with business priorities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Leaders should define who will evaluate successful experiments, allocate implementation resources and coordinate with delivery teams. This ensures that validated solutions have a practical route towards adoption.<\/span><\/p>\n<h2><b>What Teams Do During the Design Thinking Process<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">While leaders establish direction, teams are responsible for translating business challenges into practical solutions. This requires understanding users, identifying underlying problems and exploring different approaches before committing to implementation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Design thinking for teams is an <\/span><a href=\"https:\/\/www.nngroup.com\/articles\/design-thinking\/\" rel=\"nofollow noopener\" target=\"_blank\"><span style=\"font-weight: 400;\">iterative process<\/span><\/a><span style=\"font-weight: 400;\"> rather than a fixed sequence of activities. Teams may return to earlier stages when research reveals new information or testing challenges an existing assumption.<\/span><\/p>\n<h3><b>User Research and Empathy Mapping<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Teams begin by understanding the people experiencing the problem. Customer interviews, employee discussions, observations and feedback analysis help identify behaviours, frustrations and unmet needs.<\/span><\/p>\n<p><a href=\"https:\/\/nextagile.ai\/blogs\/design-thinking\/the-essential-guide-to-empathy-maps-and-user-personas\/\"><span style=\"font-weight: 400;\">Empathy mapping<\/span><\/a><span style=\"font-weight: 400;\"> organises these findings into what users say, think, do and feel. It helps participants move beyond assumptions and develop a shared understanding of the experiences they are trying to improve.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, a customer service team may discover that customers are not only frustrated by delayed responses but also uncertain about whether their complaints are being addressed. This insight reveals an opportunity to improve communication and visibility.<\/span><\/p>\n<h3><b>Problem Framing and Reframing<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Once research findings are available, teams need to define the actual problem. A broad statement such as improve customer experience does not provide sufficient direction for developing meaningful solutions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Teams should convert research insights into focused problem statements. For example, how might we help customers track service requests without repeatedly contacting support?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Problem reframing encourages employees to question existing assumptions and consider alternative explanations. It also prevents teams from jumping into solution development before understanding the underlying need.<\/span><\/p>\n<h3><b>Ideation and Collaborative Solution Development<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Ideation allows teams to explore different ways of addressing a clearly defined problem. Structured brainstorming, divergent thinking and collaborative evaluation help participants generate possibilities before selecting ideas for further investigation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Cross-functional participation is particularly valuable because different departments understand different aspects of the same challenge. Operations, technology, marketing and customer service employees may identify opportunities that would otherwise remain unnoticed.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Teams should evaluate ideas based on user value, feasibility and business relevance. This creates a stronger foundation for selecting concepts that deserve further testing.<\/span><\/p>\n<h3><b>Prototyping and Experimentation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Prototyping helps teams turn ideas into simple representations that can be evaluated by users. These may include paper models, screen layouts, workflow diagrams, service blueprints or simulated customer interactions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Low-fidelity prototypes are particularly useful during early experimentation because they are inexpensive to create and easy to modify. Teams can test important assumptions without investing in complete solutions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, an employee onboarding team could create a sample onboarding journey and ask recently recruited employees to review the information, sequence and support activities.<\/span><\/p>\n<h3><b>Testing and Refining Solutions<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Testing helps teams understand whether a proposed solution addresses the original problem. Participants observe user interactions, collect feedback and identify areas that require improvement.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Feedback may reveal usability issues, missing information or assumptions that need to be reconsidered. Teams can then modify the prototype, conduct another test or return to problem framing.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This iterative process helps organisations make decisions based on evidence rather than committing significant resources to unvalidated ideas.<\/span><\/p>\n<h3><b>Connecting Leadership Expectations With Team Actions<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The relationship between leadership and team activities becomes clearer when both roles work towards the same business outcome.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Leadership expectation<\/b><\/td>\n<td><b>What the team actually does<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Improve customer retention<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Interviews customers who discontinued the service.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Reduce employee onboarding time<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Maps the current onboarding journey.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Improve operational efficiency<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Identifies process bottlenecks and dependencies.<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Improve service quality<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Tests alternative service workflows.<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Managers connect these activities by coordinating participants, removing day-to-day barriers and communicating progress to leadership.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This creates a clear relationship between strategic priorities and the practical work required to deliver improvements.<\/span><\/p>\n<h2><b>Design Thinking Exercises for Teams<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Practical exercises help employees apply design thinking concepts to real organisational challenges. They are most useful when participants work with a specific problem rather than focusing exclusively on creative idea generation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The following exercises can be adapted for customer experience, employee engagement, operational improvement and service delivery initiatives.<\/span><\/p>\n<h3><b>Empathy Mapping: Understanding User Needs<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Objective: Develop a shared understanding of user experiences and challenges.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Teams identify a specific user group and organise research findings into what users say, think, do and feel. They then look for recurring frustrations, behavioural patterns and unmet needs.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For an employee onboarding initiative, the team may identify that new employees understand their job responsibilities but struggle to find information about internal systems and approval processes.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Expected output: A documented set of user insights that can guide further investigation.<\/span><\/p>\n<h3><b>Problem Reframing: Challenging Existing Assumptions<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Objective: Convert broad organisational challenges into actionable problem statements.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Teams begin with an initial problem, identify assumptions and review available evidence. They then explore alternative interpretations and create focused How Might We questions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, the problem of low training completion may be reframed as how might we make mandatory learning more accessible and relevant to employees&#8217; daily responsibilities?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Expected output: A focused problem statement that provides direction for ideation.<\/span><\/p>\n<h3><b>Rapid Prototyping: Testing Ideas Before Implementation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Objective: Evaluate potential solutions before committing significant resources.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Teams select an idea, identify the assumption that needs testing and create a simple representation using paper, diagrams, mock-ups or process maps. Relevant users then review the prototype and provide feedback.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">An onboarding team could create a sample employee checklist to test whether new recruits can easily understand their first-week responsibilities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Expected output: Initial feedback about usability, relevance and improvement opportunities.<\/span><\/p>\n<h3><b>Design Thinking Team Building Through Cross-Functional Collaboration<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Objective: Bring employees from different functions together to solve shared organisational challenges.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Participants describe how the problem affects their departments, map dependencies and identify opportunities for improvement. They then develop a shared problem statement and select an idea for further testing.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, HR, IT and department managers may collaborate to improve employee onboarding. Each function contributes knowledge about recruitment, system access and role-specific responsibilities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Expected output: Shared ownership, stronger communication and a more practical approach to solving the problem.<\/span><\/p>\n<h2><b>A Practical Example: Improving Employee Onboarding<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Consider an organisation where new employees receive inconsistent information across departments. Some struggle to access systems, while others are unclear about their responsibilities during the first few weeks.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A cross-functional team involving HR, IT, managers and recently recruited employees can investigate the issue using the exercises discussed above.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The team begins with empathy mapping and discovers that employees experience confusion because onboarding information arrives from several different sources. Problem reframing helps identify the lack of coordinated communication as a central challenge.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The team then prototypes a standard onboarding checklist and communication sequence. After gathering feedback, leadership reviews the findings and supports implementation across departments.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The improvement is not necessarily a new technology platform. It may simply be a more coordinated process with clearer ownership and communication.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This example demonstrates how design thinking team building can help organisations move beyond departmental assumptions and develop solutions around actual employee needs.<\/span><\/p>\n<h2><b>A Half-Day Design Thinking Agenda for Leaders and Teams<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Organisations can introduce these practices through a structured half-day session focused on a real business challenge. The objective is to understand the problem, explore user needs and develop initial solutions that can be tested further.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The following agenda is illustrative and can be adapted according to the complexity of the challenge and the experience of participants.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Duration<\/b><\/td>\n<td><b>Activity<\/b><\/td>\n<td><b>Participants responsible<\/b><\/td>\n<td><b>Expected output<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">30 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Business problem definition<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Leaders and facilitators<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Agreed challenge and strategic context<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">45 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">User insights and empathy mapping<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Cross-functional teams<\/span><\/td>\n<td><span style=\"font-weight: 400;\">User needs and pain points<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">30 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Problem framing<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Teams with leadership input<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Clear problem statements<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">45 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Ideation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Cross-functional teams<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Shortlisted solution ideas<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">45 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Rapid prototyping<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Teams<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Low-fidelity prototypes<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">30 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Feedback and evaluation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Users and stakeholders<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Improvement opportunities<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">15 minutes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Next steps and ownership<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Leaders and team representatives<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Agreed actions and responsibilities<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Total duration: 4 hours.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The session should not end when participants present their ideas. Leaders should establish an implementation checkpoint, assign ownership for further testing and determine which proposals require additional resources.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This follow-through is what helps organisations convert a productive session into sustained business improvement.<\/span><\/p>\n<h2><b>How to Measure Whether Design Thinking Is Working<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">The real measure of design thinking is not how many ideas a team generates, but how many assumptions it validates, user problems it resolves and measurable improvements it delivers.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For business leaders, innovation becomes valuable when learning translates into better customer experiences and stronger operational performance. Measurement should therefore evolve as initiatives move from exploration to implementation.<\/span><\/p>\n<h3><b>Measuring Learning and Experimentation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">During early stages, organisations should evaluate how effectively teams are investigating problems and testing assumptions. Useful indicators include the number of assumptions validated, user insights identified, experiments completed and prototypes tested.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Teams should also monitor how quickly they move from identifying a problem to testing an initial solution. These indicators reveal whether employees are learning efficiently and using evidence to guide decisions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">An unsuccessful prototype can still represent valuable progress if it reveals why an assumption was incorrect. Leaders should recognise this learning rather than evaluating experimentation only through successful ideas.<\/span><\/p>\n<h3><b>Measuring Business and Operational Outcomes<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Once solutions have been tested and implemented, organisations should assess their impact on users and operations.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Business area<\/b><\/td>\n<td><b>Potential indicators<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Customer experience<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Customer satisfaction, complaint frequency and customer effort<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Employee experience<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Employee satisfaction, onboarding completion and feedback<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Operational efficiency<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Process cycle time, error rates and manual effort<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Product adoption<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Usage rates and task completion<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Service delivery<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Response times and resolution times<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Implementation<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Time taken to move validated solutions into operational use<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><span style=\"font-weight: 400;\">Metrics should reflect the specific problem being addressed. A customer service initiative and an employee onboarding initiative will require different indicators of success.<\/span><\/p>\n<h3><b>Connecting Innovation Outcomes With Business Priorities<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Leaders must evaluate whether tested solutions contribute to wider organisational objectives. Positive user feedback is important, but it should be considered alongside implementation feasibility and business value.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, improving an internal approval process may reduce employee effort and shorten turnaround times. Leaders should assess whether these improvements also support productivity and operational efficiency.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This creates a stronger connection between innovation activities and business performance. It also helps organisations prioritise solutions that offer meaningful value rather than investing in ideas simply because they are new.<\/span><\/p>\n<h2><b>When to Bring in External Design Thinking Support<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Internal teams may understand their business challenges but still need external expertise to manage complex discussions, improve collaboration or connect innovation activities with organisational priorities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">External support becomes particularly valuable when initiatives involve several departments, conflicting stakeholder expectations or significant changes to existing ways of working.<\/span><\/p>\n<h3><b>When Internal Teams Need Facilitation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Teams may struggle to agree on the underlying problem, challenge established assumptions or manage discussions involving senior stakeholders. In such situations, an experienced facilitator can provide structure and encourage balanced participation.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A structured<\/span><a href=\"https:\/\/nextagile.ai\/workshop\/design-thinking-masterclass-workshop\/\"> <span style=\"font-weight: 400;\">design thinking workshop<\/span><\/a><span style=\"font-weight: 400;\"> can help employees understand the methodology and apply practical problem-solving techniques to relevant organisational challenges.<\/span><\/p>\n<h3><b>When Organisations Need Leadership Alignment<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Innovation initiatives can lose momentum when executives, managers and delivery teams have different expectations. External support can help clarify strategic priorities, decision-making responsibilities and success criteria.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Organisations can also strengthen leadership capabilities through relevant<\/span><a href=\"https:\/\/nextagile.ai\/case-studies\/leadership-development-case-studies\/\"> <span style=\"font-weight: 400;\">leadership development programmes<\/span><\/a><span style=\"font-weight: 400;\"> that support collaboration, effective decision-making and organisational change.<\/span><\/p>\n<h3><b>Connecting Design Thinking With Wider Transformation Initiatives<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Design thinking can contribute to wider transformation when it becomes part of how organisations identify opportunities and improve existing processes.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It complements Agile by helping teams understand which problems are worth solving, while Agile supports iterative development and continuous delivery. Business agility extends this capability across the organisation, helping it respond to changing customer and market expectations.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Organisations pursuing<\/span><a href=\"https:\/\/nextagile.ai\/agile-transformation-consulting\/\"> <span style=\"font-weight: 400;\">enterprise Agile transformation<\/span><\/a><span style=\"font-weight: 400;\"> can use design thinking to strengthen customer understanding, cross-functional collaboration and evidence-based decision-making.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The<\/span><a href=\"https:\/\/nextagile.ai\/case-study\/agile-culture-case-study-in-fmcg\/\"> <span style=\"font-weight: 400;\">Agile culture transformation case study<\/span><\/a><span style=\"font-weight: 400;\"> also provides a relevant perspective on the importance of developing collaborative and adaptive organisational behaviours.<\/span><\/p>\n<h2><b>Conclusion<\/b><\/h2>\n<p><span style=\"font-weight: 400;\">Organisations do not build innovation capabilities simply by teaching employees to generate better ideas. They build them by changing how leaders define problems, how teams challenge assumptions and how decisions are made across functions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Leaders establish direction, provide resources and create the conditions for experimentation. Managers connect strategic expectations with everyday activities, while teams translate user insights into practical solutions through research, prototyping and testing.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When these responsibilities work together, design thinking moves beyond an innovation initiative and becomes an organisational capability. It helps businesses make informed decisions, improve experiences and respond more effectively to complex challenges.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At NextAgile, we help organisations strengthen design thinking and business agility capabilities through practical interventions that connect people, processes and business priorities. If your organisation wants to build a stronger culture of innovation, improve collaboration and solve complex business challenges, adopting design thinking can make a meaningful difference. NextAgile&#8217;s <\/span><a href=\"https:\/\/nextagile.ai\/design-thinking-consulting-services\/\"><span style=\"font-weight: 400;\">design thinking and business agility consulting<\/span><\/a><span style=\"font-weight: 400;\"> can help you co-create practical approaches that align leadership priorities with team capabilities and business objectives. Reach out to us at <\/span><a href=\"mailto:consult@nextagile.ai\"><span style=\"font-weight: 400;\">consult@nextagile.ai<\/span><\/a><span style=\"font-weight: 400;\">, and we would be happy to explore how we can support your organisation&#8217;s transformation journey.<\/span><\/p>\n<h2><b>Frequently Asked Questions<\/b><\/h2>\n<h3><b>1. Is design thinking still relevant in the AI era?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Yes. Design thinking remains relevant because technology does not eliminate the need to understand human needs, define meaningful problems and evaluate potential solutions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">AI can support user feedback analysis, idea generation and prototype development. However, people must still interpret insights, challenge assumptions and evaluate ethical and business implications.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Design thinking helps ensure that AI-enabled solutions address genuine user problems rather than introducing technology without a clear purpose.<\/span><\/p>\n<h3><b>2. Design thinking vs Agile: Which should organisations use first?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Design thinking helps organisations understand user needs, identify the right problems and explore possible solutions. Agile provides an iterative approach to developing, delivering and improving those solutions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A common approach is to use design thinking before and alongside Agile delivery. Teams can investigate user needs and validate initial concepts before committing to development.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, the two approaches are complementary rather than strictly sequential. Design thinking can continue throughout Agile delivery as teams gather feedback and discover new opportunities.<\/span><\/p>\n<h3><b>3. Can design thinking work for remote or hybrid teams?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Yes. Remote and hybrid teams can apply design thinking through virtual interviews, collaborative digital whiteboards, online ideation sessions and digital prototypes.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Organisations should establish clear participation guidelines and ensure that research findings and decisions are accessible to everyone.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Combining live discussions with asynchronous collaboration also helps distributed teams contribute effectively across different schedules and locations.<\/span><\/p>\n<h3><b>4. Does design thinking apply outside product teams?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Yes. Design thinking is relevant wherever organisations need to understand problems and develop better solutions.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">HR teams can improve employee onboarding, operations teams can identify process inefficiencies, and customer service teams can improve support experiences. Marketing, finance and leadership functions can also use the approach to understand stakeholder needs and simplify internal processes.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Its human-centred nature makes it applicable across departments rather than limiting it to product development.<\/span><\/p>\n<h3><b>5. Do leaders need a design background to lead design thinking initiatives?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">No. Leaders do not need formal design qualifications to support design thinking.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Their responsibility is to establish strategic direction, encourage collaboration, provide resources and ensure that innovation initiatives remain connected to business priorities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Understanding the fundamental principles of empathy, problem framing, ideation, prototyping and testing is useful. More importantly, leaders should be willing to listen to different perspectives and make decisions based on evidence.<\/span><\/p>\n<h3><b>6. What is the difference between design thinking and human-centred design?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Design thinking is a structured approach to understanding problems, exploring opportunities and developing solutions through experimentation.<\/span><\/p>\n<p><a href=\"https:\/\/www.iso.org\/standard\/77520.html\" rel=\"nofollow noopener\" target=\"_blank\"><span style=\"font-weight: 400;\">Human-centred design<\/span><\/a><span style=\"font-weight: 400;\"> is a broader design philosophy that places people&#8217;s needs, experiences and contexts at the centre of the design process.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The two are closely connected. Design thinking commonly applies human-centred design principles through user research, empathy mapping, problem reframing, prototyping and testing.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Design thinking for leaders and teams is a human-centred approach to solving business problems, improving experiences and developing practical solutions through collaboration and experimentation. While leaders establish strategic direction, allocate resources and create an environment for innovation, teams investigate user needs, challenge assumptions, develop ideas and test potential solutions. The distinction is important because successful&#8230;<\/p>\n","protected":false},"author":2,"featured_media":9178,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[4],"tags":[],"class_list":["post-9177","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-design-thinking"],"_links":{"self":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/9177","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/comments?post=9177"}],"version-history":[{"count":1,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/9177\/revisions"}],"predecessor-version":[{"id":9179,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/9177\/revisions\/9179"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media\/9178"}],"wp:attachment":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media?parent=9177"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/categories?post=9177"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/tags?post=9177"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}