intended outcome of the problem solving workshop

We are back in Europe and hope you join us!

Prague, Czech Republic, 15 – 17, May 2023

Evolving the Scaled Agile Framework:

Update to SAFe 5

Guidance for organizing around value, DevSecOps, and agility for business teams

• SAFe Contributors
• Extended SAFe Guidance
• Community Contributions
• SAFe Beyond IT
• Books on SAFe
• Download SAFe Posters & Graphics
• Presentations & Videos
• FAQs on how to use SAFe content and trademarks
• What’s new in the SAFe 5.1 Big Picture
• Recommended Reading
• Learn about the Community
• Member Login
• SAFe Implementation Roadmap
• Find a Transformation Partner
• Find a Platform Partner
• Customer Stories
• SAFe Training

Kaizen is about changing the way things are. If you assume that things are all right the way they are, you can’t do kaizen. So change something! —Taiichi Ohno

Inspect and Adapt

Inspect & adapt: overview.

The Agile Manifesto emphasizes the importance of continuous improvement through the following principle: “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”

In addition, SAFe includes ‘relentless improvement’ as one of the four pillars of the SAFe House of Lean as well as a dimension of the Continuous Learning Culture core competency. While opportunities to improve can and should occur continuously throughout the Program Increment (PI) (e.g., Iteration Retrospectives ), applying some structure, cadence, and synchronization helps ensure that there is also time set aside to identify improvements across multiple teams and Agile Release Trains.

All ART stakeholders participate along with the Agile Teams in the I&A event. The result is a set of improvement backlog items that go into the Program Backlog for the next PI Planning event. In this way, every Agile Release Train (ART) improves every PI. For large solutions , a similar I&A event is held by the Solution Train .

The I&A event consists of three parts:

PI System Demo

• Quantitative and qualitative measurement
• Retrospective and problem-solving workshop

Participants in the I&A should be, wherever possible, all the people involved in building the solution. These include for an ART:

• The Agile teams
• Release Train Engineer (RTE)
• System and Solution Architects/Engineering
• Product Management ,  Business Owners , and others on the train

Additionally, Solution Train stakeholders may attend this event.

The PI System Demo is the first part of the I&A, and it’s a little different from the regular system demos that happen after every iteration, in that it is intended to show all the Features that the ART has developed over the course of the PI. Typically the audience is broader, for example, customers or Portfolio representatives are more likely to attend this demo. Therefore, the PI system demo tends to be a little more formal, and some extra preparation and staging are usually required. But like any other system demo, it should be timeboxed to an hour or less, with the level of abstraction high enough to keep stakeholders actively engaged and providing feedback.

Prior to, or as part of the PI system demo, Business Owners collaborate with each Agile team to score the actual business value achieved for each of their Team PI Objectives .

Quantitative and Qualitative Measurement

In the second part of the I&A event, teams collectively review any quantitative and qualitative metrics they have agreed to collect, then discuss the data and trends. In preparation for this, the RTE and the Solution Train Engineer are often responsible for gathering the information, analyzing it to identify potential issues, and facilitating the presentation of the findings to the ART.

One primary metric is the program predictability measure. Each team’s planned vs. actual business value is rolled up to create the program predictability measure, as shown in Figure 2.

Reliable trains should operate in the 80–100 percent range; this allows the business and its external stakeholders to plan effectively. (Note: Uncommitted objectives don’t count toward the commitment but do count toward the actual business value achievement, as can also be seen in Figure 1.)

Retrospective

The teams then run a brief (30 minutes or less) retrospective, the goal of which is to identify a few significant issues they would like to address during the problem-solving workshop . There is no one way to do this; several different Agile retrospective formats can be used [3].

Based on the retrospective, and the nature of the problems identified, the facilitator helps the group decide which issues they want to tackle. Each team may work on a problem, or, more typically, new groups are formed from individuals across different teams who wish to work on the same issue. This self-selection helps provide cross-functional and differing views of the problem, and it brings together those who are impacted and those who are best motivated to address the issue.

Key ART stakeholders—including Business Owners, customers, and management—join the teams in the retrospective and problem-solving workshop. Often it is the Business Owners alone who can unblock the impediments that exist outside the team’s control.

Problem-Solving Workshop

For addressing systemic problems, a structured, root-cause problem-solving workshop is held by the ART. Root cause analysis provides a set of problem-solving tools used to identify the actual causes of a problem, rather than just addressing the symptoms. The session is typically facilitated by the RTE, in a timebox of two hours or less.

Figure 3 illustrates the steps in the problem-solving workshop.

The following sections describe each step of the process.

Agree on the Problem(s) to Solve

American inventor Charles Kettering is credited with the statement that “a problem well stated is a problem half solved.” At this point, the teams have self-selected the problem they want to address. But, do they agree on the details of the problem, or is it more likely that they have differing perspectives? To this end, the teams should spend a few minutes clearly stating the problem, highlighting the ‘what’, ‘where’, ‘when’, and ‘impact’ as succinctly as they can. Figure 4 illustrates a well-written problem statement.

Perform Root Cause Analysis

Effective problem-solving tools include the fishbone diagram and the ‘5 Whys.’ Also known as an Ishikawa Diagram , a fishbone diagram is a visual tool used to explore the causes of specific events or sources of variation in a process. Figure 5 illustrates the fishbone diagram with a summary of the previous problem statement written at the head of the ‘fish.’

For our problem-solving workshop, we preload the main bones with the categories people, process, tools, program, and environment. However, these may be adapted as appropriate.

Team members then brainstorm causes that they think contribute to the problem to be solved and group them into these categories. Once a cause is identified, its root cause is explored with the 5 Whys technique. By simply asking ‘why’ multiple times, the cause of the previous cause is uncovered, and added to the diagram. The process stops once a suitable root cause has been identified and the same process is then applied to the next cause.

Identify the Biggest Root Cause

Pareto Analysis , also known as the 80/20 rule, is a technique used to narrow down the number of actions that produce the most significant overall effect. It uses the principle that 20 percent of the causes are responsible for 80 percent of the problem. It’s especially useful when many possible courses of action are competing for attention, which is almost always the case with complex, systemic issues.

Once all the possible causes-of-causes have been identified, team members then cumulatively vote on the item they think is the most significant factor contributing to the original problem. They can do this by dot voting (five votes are allocated to each person, which can be spread among one or more items as they see fit) on the causes they think are most problematic. The team then summarizes the votes in a Pareto chart, such as the example in Figure 6, which illustrates their collective consensus on the most significant root cause.

Restate the New Problem

The next step is to pick the cause with the most votes and restate it clearly as a problem. This should take only a few minutes or so, as the teams have a good understanding of this root cause by now.

Brainstorm Solutions

At this point, the restated problem will start to imply some potential solutions. The team brainstorms as many possible corrective actions as they can think of within a fixed timebox (about 15–30 minutes). The rules of brainstorming apply here:

• Generate as many ideas as possible
• Do not allow criticism or debate
• Let the imagination soar
• Explore and combine ideas

Create Improvement Backlog Items

The team then cumulatively votes on up to three most likely solutions. These are rephrased as improvement stories and features to be fed directly into the PI Planning event that follows. During that event, the RTE helps ensure that the relevant work needed to deliver the identified improvements is planned. This closes the loop, thus ensuring that action will be taken and that people and resources are dedicated as necessary to improve the current state.

In this way, problem-solving becomes routine and systematic, and team members and ART stakeholders can be assured that the train is solidly on its journey of relentless improvement.

Inspect and Adapt at the Large Solution Level

The above describes a rigorous approach to problem-solving in the context of a single ART. If the ART is part of a Solution Train the I&A event will often include key stakeholders from the Large Solution level. In larger value streams, however, an additional large solution level I&A event may be required, following the same format.

Due to the number of people in a Solution Train, attendees at the large solution I&A event cannot include everyone, so stakeholders are selected that are best suited to address the problems faced. This includes the primary stakeholders of the Solution Train, as well as representatives from the various ARTs and Suppliers .

Last update: 10 February 2021

Privacy Overview

Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.

Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.

Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

• Skip to content

Problem-solving workshop: Step-by-Step

A problem-solving workshop is held by the Agile Release Train and its purpose is to address systematic problems. The workshop that concentrates on identifying the problems, not just addressing the symptoms, is facilitated by the Release Train Engineer and time-boxed to maximum of two hours. What are the six steps of the workshop?

In SAFe® (Scaled Agile Framework for Enterprises®), problem-solving workshop is done during the Inspect & Adapt (I & A) event. I & A  is held at the end of each Program Increment, and it forms the basis for relentless improvement, one of the four pillars of the SAFe House of Lean , and a dimension of the Continuous Learning Culture core competency.

During the three parts of I & A event (PI System Demo, Quantitative and Qualitative measurement, and Retrospective and problem-solving workshop), the ART demonstrates and evaluates the current state of the solution and teams reflect and identify improvement backlog items. In this article we are going to concentrate on the last part of the event, problem-solving workshop, during which teams systematically address the larger impediments that are limiting velocity.

Problem-solving workshop consists of 6 steps

Step 1: agree on the problem to solve.

Clearly stating the problem is key to problem identification and correction. It enables more focused investigation, time-saving, and avoids ‘ready, fire, aim’ approach. On the other hand, a problem that is not well defined, may result in failure to reach the proper countermeasure. To identify and agree on the problem to solve, the teams should spend a few minutes clearly stating the problem, highlighting the ‘what’, ‘where’, ‘when’, and ‘impact’ as succinctly as they can.

Step 2: Apply root-cause analysis and 5 whys

The Root-cause analysis and the ‘5 Whys’ technique is used to explore the cause-and-effect relationships underlying a particular problem. It helps to avoid assumptions and logic traps, trace the chain of causality in direct increments from the effect to a root cause.

The root cause analysis (fishbone or Ishikawa) diagram features 5 main ‘bones’ that represent typical sources of problems in development (tools, people, program, process, environment). Team members then brainstorm causes that they think contribute to the problem to be solved and group them into these categories. Once a cause is identified, its root cause is explored with the 5 Whys technique. By simply asking ‘why’ multiple times, the cause of the previous cause is uncovered, and added to the diagram. The process stops once a suitable root cause has been identified and the same process is then applied to the next cause (© Scaled Agile, Inc.).

Step 3: Identify the biggest root-cause using Pareto analysis

Team uses Pareto analysis (or 80/20 rule) to narrow down the number of actions that produce the most significant overall effect. It is based on the principle that 20% of root causes can cause 80% of problems and it has proved useful where many possible sources and actions are competing. Once the team writes down all the causes-of-causes, they identify the biggest root-cause using dot-voting – every team member has five dots on its disposal, and he can allocate them to one or more items he thinks are most problematic. Then they summarize votes in Pareto chart that shows collective consensus on the most significant root-cause.

Step 4: Restate the new problem for the biggest root-cause

Team picks the most voted item from Pareto chart. They restate it clearly as a problem and add economic impact of the problem to the description.

Step 5: Brainstorm solutions

During the brainstorming activity that lasts about 15 – 30 minutes, team brainstorms as many possible corrective actions as possible. The goal of activity is to generate as many ideas as possible, without criticism or debate. Team members should let their imagination soar and explore and combine all the ideas that arise and in the end dot-vote to identify top contenders.

Step 6: Identify improvement backlog items (NRFs)

In the end of the problem-solving workshop, up to three most voted solutions are identified. Solutions are then rephrased as improvement stories and features to be fed directly into the PI Planning event that follows the I & A event. During that event, the RTE helps ensure that the relevant work needed to deliver the identified improvements is planned. This closes the loop, thus ensuring that action will be taken, and that people and resources are dedicated as necessary to improve the current state. In this way, problem-solving becomes routine and systematic, and team members and ART stakeholders can be assured that the train is solidly on its journey of relentless improvement (© Scaled Agile, Inc. ).

You may also like

Mastering SAFe: What Every Business Professional Should Know

Anti-Patterns in SAFe Implementation

• Shop Card Decks
• Video Libary

Engineering , Leadership , User experience , User experience , Product management

Problem-Solving Workshop

A collaborative learning environment designed to help participants develop skills to identify and solve problems. product glossary problem-solving workshop also called: problem-solving session and problem-solving exercise see also: how might we , hypothesis statement , premortem , problem statement , swot analysis , affinity diagram , circles method , design thinking , jobs-to-be-done framework (jtbd) relevant metrics: attendance and engagement, pre- and post-workshop assessments, goal achievement, participant satisfaction, knowledge retention, application of skills, networking and collaboration, and commitment to continuous improvement in this article what is a problem-solving workshop.

A Problem-Solving Workshop is a collaborative event in which a group of people come together to identify and solve a problem. It is a structured process that involves brainstorming, analyzing, and developing solutions to a problem. A problem-solving workshop is a rapid session that helps you:

• Unlocking the Core of the Issue . A problem-solving workshop serves as an accelerated session designed to delve into the underlying cause of a dilemma, enabling participants to better comprehend its complexities.
• Generate ideas . With a deeper understanding of the problem at hand, participants rapidly brainstorm potential solutions. They then carefully assess these ideas, ensuring their feasibility and effectiveness in addressing the issue.
• Evaluating ideas . Participants scrutinize their proposed ideas, determining their robustness and ability to withstand potential challenges to ensure that only the most viable and reliable solutions are considered for implementation, enhancing the likelihood of successfully resolving the problem.
• Make a plan to test or implement . Equipped with a well-rounded perspective and carefully evaluated solutions, the workshop empowers attendees to devise a strategic plan for testing or implementing their chosen resolution, ultimately guiding them toward the ideal solution to their problem.

The workshop typically begins with a discussion of the problem and its context. Participants then brainstorm potential solutions and evaluate them based on their feasibility and potential impact. After the brainstorming session, the group works together to develop a plan of action to address the problem. This plan may include changes to existing processes, new procedures, or other solutions.

The Problem-Solving Workshop is an effective way to identify and solve problems in the context of Product Management and User Experience. It allows for a collaborative approach to problem-solving, which can lead to more creative and effective solutions. It also allows for a structured approach to problem-solving, which can help ensure that the problem is addressed in a timely and efficient manner.

Where did Problem-Solving Workshops come from?

The idea of coming together to solve problems can be traced back to ancient human societies that held gatherings to discuss issues and find solutions. In modern times, problem-solving workshops have been shaped by developments in various fields like psychology, education, management, design, and innovation.

Some significant influences on problem-solving workshops include:

• Brainstorming . Alex Osborn, an advertising executive, introduced brainstorming in the 1940s as a group creativity technique to generate ideas and solve problems. This method encouraged people to share their ideas freely, no matter how wild, and suspend judgment during the idea-generation process. Brainstorming has since been incorporated into many problem-solving workshops.
• Quality circles . In the 1960s, Japanese companies introduced quality circles, which are small groups of employees who meet regularly to discuss and solve work-related problems. These circles aimed to improve the quality of products and processes by involving employees in problem-solving and decision-making. The concept of quality circles has inspired many problem-solving workshops in various industries.
• Design thinking . The design thinking methodology, pioneered by companies like IDEO and Stanford University’s d.school, has played a crucial role in shaping modern problem-solving workshops. Design thinking is a human-centered approach to problem-solving that encourages empathy, experimentation, and collaboration. It involves a series of steps, such as empathizing, defining, ideating, prototyping, and testing, which can be adapted to various problem-solving workshop formats.
• Lean and Agile methodologies . Lean and Agile methodologies, which originated in the manufacturing and software development sectors, respectively, have also influenced problem-solving workshops. These approaches emphasize collaboration, continuous improvement, and rapid iteration to achieve better results.
• Facilitation techniques . The growth of professional facilitation has also impacted problem-solving workshops. Skilled facilitators use various tools and techniques to guide groups through problem-solving processes, ensuring that the workshop’s objectives are met and that participants stay engaged and focused.

Why should I conduct a problem-solving workshop?

Conducting a problem-solving exercise can be beneficial in several ways. It can help individuals or teams to:

• Identify the root cause of a problem . By engaging in a structured problem-solving exercise, participants can gain a deeper understanding of the issue and identify the underlying causes.
• Generate new ideas and solutions . By brainstorming and evaluating various solutions, individuals or teams can develop creative and effective solutions that they may not have thought of otherwise.
• Encourage collaboration and teamwork . Collaborative problem-solving exercises can foster a sense of teamwork and create a shared sense of ownership and responsibility for the problem and the solution.
• Improve decision-making . By evaluating various options and considering different perspectives, participants can make informed and effective decisions that take into account a wide range of factors.
• Enhance learning and development . Problem-solving exercises can provide opportunities for individuals or teams to learn new skills, practice critical thinking, and develop problem-solving abilities that can be applied to future challenges.

How to run a problem-solving workshop

Step 1: assemble a well-rounded team.

Gather individuals with diverse backgrounds, skill sets, and perspectives who are relevant to the problem at hand. This may include team members, cross-functional collaborators, subject matter experts, or stakeholders. A diverse group will enhance the ideation process and facilitate a more comprehensive understanding of the issue.

Consider the following factors:

• Diversity . Assemble a team with a mix of expertise, backgrounds, perspectives, and roles relevant to the problem. Diversity encourages creative thinking and helps avoid groupthink or blind spots.
• Relevant stakeholders . Ensure that key stakeholders, including decision-makers, subject matter experts, and those directly affected by the problem, are included in the workshop. Their insights and buy-in are crucial for the success of the proposed solutions.
• Size of the group . Aim for a group size that allows for effective collaboration and communication. Ideally, the group should be large enough to generate a variety of ideas but small enough to facilitate productive discussions. Typically, a group of 6-10 participants is considered optimal for a problem-solving workshop.
• Team dynamics . Select participants who are open-minded, willing to collaborate, and capable of engaging in constructive discussions. The right balance of personalities is essential for fostering a positive atmosphere and effective teamwork.
• Establish clear roles . Assign roles and responsibilities to participants, such as a facilitator to guide the workshop, a timekeeper to monitor progress, and a note-taker to document key points and decisions. Clearly defined roles help ensure the smooth flow of the workshop.
• Preparation . Communicate the workshop’s purpose, goals, and expectations to participants beforehand. Encourage them to familiarize themselves with the problem and come prepared with any relevant data or insights. This will enable a more focused and productive discussion during the workshop.

Step 2: Establish the Objective and Scope

Clearly define the purpose and goals of the workshop. Ensure that all participants understand the problem to be addressed, its context, and any constraints or limitations. Set a time limit for the workshop to maintain focus and efficiency.

Consider the following:

• Preparation and research . A facilitator should be well-prepared with a thorough understanding of the problem, its context, and the workshop’s objectives. This may involve conducting research, reviewing relevant materials, and consulting with key stakeholders or subject matter experts beforehand.
• Active listening . Practice active listening during the workshop to ensure participants feel heard and understood. Encourage questions and clarifications to address any misunderstandings or ambiguities regarding the problem, scope, or objectives.
• Flexibility and adaptability . Be prepared to adjust the workshop’s objectives or scope if new information or insights emerge during the discussion. Maintain an open-minded approach and adapt to the needs of the group while ensuring that the workshop remains focused and productive.
• Time management . Monitor the workshop’s progress and allocate time appropriately for each stage. If necessary, intervene to refocus the discussion, maintain momentum, or transition to the next step in the problem-solving process.

Each of the following workshop exercises can contribute to the success of establishing a clear objective and scope by helping participants gain a deeper understanding of the problem, its context, and the needs of those affected, leading to a clearer definition of the objective and scope:

• Six Thinking Hats . This exercise, developed by Edward de Bono, encourages participants to approach the problem from six different perspectives, represented by metaphorical “hats.” These perspectives are: facts and information (white hat), emotions and feelings (red hat), cautious and critical thinking (black hat), optimistic and positive thinking (yellow hat), creative and alternative thinking (green hat), and process and organization (blue hat). This technique can help the group establish a more comprehensive understanding of the problem, its context, and potential constraints, leading to a clearer definition of the objective and scope.
• Stakeholder Mapping . In this exercise, participants identify and analyze the key stakeholders involved in or affected by the problem. This helps the group understand the different perspectives, priorities, and needs of these stakeholders, providing valuable context for the problem-solving process. By considering stakeholder needs and concerns, the workshop can better define the objective and scope while ensuring that potential solutions address relevant issues.
• Empathy Mapping . This exercise helps participants gain insight into the needs, motivations, and challenges of the individuals affected by the problem, such as customers, users, or team members. By creating an empathy map, the group can better understand the problem from the perspective of those who are directly impacted. This understanding can help the group establish a clearer and more focused objective and scope for the workshop, ensuring that potential solutions address the most critical concerns of the affected individuals.

Step 3: Identify the Right Problem and Root Cause

Begin the workshop by collectively discussing the problem to gain a deeper understanding of its nuances. Use techniques like the 5 Whys or Fishbone Diagram to identify the root cause of the problem, ensuring that the team’s efforts are directed towards solving the underlying issue rather than merely addressing symptoms.

Approach this step with a well-defined strategy that guides participants through the process of understanding the problem and its underlying factors. The facilitator plays a pivotal role in creating an environment that encourages open and honest dialogue, allowing participants to share their insights and collectively work towards identifying the root cause.

Strike a balance between allowing sufficient time for discussions and ensuring that the workshop maintains momentum and stays on track. The facilitator may need to intervene occasionally to refocus the conversation or steer the group towards the desired outcome.

Be prepared to adapt to the evolving dynamics of the workshop. They must be flexible and responsive to new insights or challenges that emerge during the discussions. If necessary, the facilitator may need to adjust the workshop’s objectives, scope, or methodology to ensure that the group remains focused on addressing the problem’s root cause.

Consider using one of these workshop exercises to identify the right problem:

• Five Whys . This technique involves asking “Why?” repeatedly to dig deeper into the problem and uncover the root cause. By using this approach in the workshop, participants can move beyond surface-level symptoms to identify the true source of the issue. The facilitator can guide the group through the Five Whys exercise, ensuring that the discussion stays focused and productive.
• Fishbone Diagram . Also known as the Ishikawa or cause-and-effect diagram, this tool visually represents the relationship between a problem and its potential causes. Participants brainstorm and categorize potential causes into distinct branches, which can help the group identify the root cause. The facilitator can lead the group through the Fishbone Diagram exercise, encouraging them to consider various aspects of the problem and promoting a comprehensive understanding.
• Round Robin . This brainstorming technique involves giving each participant a chance to contribute an idea or perspective on the problem in a structured and organized manner. This ensures equal participation and helps to gather diverse insights. Using the Round Robin method, the facilitator can facilitate discussions on the problem’s root cause by encouraging participants to share their thoughts and perspectives without interruption.
• Force Field Analysis . This exercise helps participants identify the driving and restraining forces that influence a problem. By analyzing these forces, the group can gain a deeper understanding of the underlying factors contributing to the issue. The facilitator can guide participants through the Force Field Analysis, helping them to identify and assess the various forces at play and facilitating discussions on how these forces might relate to the root cause of the problem.

Step 4: Generate Ideas to Solve the Problem

Encourage participants to brainstorm solutions, emphasizing the importance of open-mindedness and creativity. Utilize techniques like mind mapping, round-robin, or the six thinking hats to foster an environment conducive to idea generation. Ensure that all participants have an opportunity to share their thoughts, and discourage judgment or criticism during this stage.

Make sure that all participants feel comfortable sharing their ideas, no matter how unconventional they may seem. This requires the facilitator to create a non-judgmental and supportive atmosphere that promotes inclusivity and equal participation.

One critical aspect for the facilitator is the use of various brainstorming techniques and ideation exercises that can stimulate creative thinking and encourage diverse perspectives. By employing a mix of individual and group activities, the facilitator can cater to different thinking styles and preferences, ensuring that everyone contributes to the ideation process.

These workshop exercises are great for generating ideas to solve the problem you identified:

• Mind Mapping . This technique helps to visually organize information around a central concept, allowing participants to generate ideas in a structured manner. It encourages them to think about the problem from different perspectives and make connections between seemingly unrelated ideas, which can lead to creative solutions.
• Crazy Eights . In this exercise, participants are given eight minutes to sketch out eight different ideas on a piece of paper. The time constraint forces them to think quickly and encourages them to generate a wide variety of ideas. By sharing and discussing their sketches afterward, the group can build upon each other’s ideas and develop more innovative solutions.
• Reverse Brainstorming . This technique prompts participants to think about the problem from an opposite perspective, by asking them to come up with ways to make the situation worse. By challenging conventional thinking, reverse brainstorming helps uncover new insights and approaches that may not have been considered otherwise.
• How Might We . This exercise frames the problem as an open-ended question, starting with the phrase “How might we…?”. This positive and optimistic framing encourages participants to think creatively and generate ideas without constraints. The open-ended nature of the question also promotes collaboration, as participants can build on each other’s ideas to find innovative solutions.
• Forced Analogy . In this exercise, participants are asked to draw analogies between the problem at hand and unrelated objects or scenarios. This encourages them to think about the problem from a new perspective and come up with creative ideas that they may not have considered otherwise. The forced analogy technique can reveal hidden connections and inspire innovative solutions.
• SCAMPER . This is an acronym for Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, and Reverse. Participants are prompted to think about the problem and generate ideas using each of these seven approaches. The SCAMPER technique encourages participants to look at the problem from different angles and find unique solutions.

Step 5: Evaluate and Refine Ideas

Once a range of potential solutions has been generated, evaluate their robustness and viability. Encourage participants to consider potential challenges, drawbacks, and risks associated with each idea. Use a decision matrix, SWOT analysis, or other evaluation tools to help compare and prioritize the proposed solutions.

Seek to create an environment where participants feel comfortable sharing their opinions and ideas while also being open to constructive feedback. The facilitator must balance encouragement and critical thinking, promoting an atmosphere where ideas are assessed objectively, and their merits and drawbacks are examined thoroughly.

Be aware of any biases, power imbalances, or dominant personalities that may influence the evaluation process. By skillfully navigating these dynamics, the facilitator can ensure that all voices are heard and that the evaluation process remains objective and fair.

These workshop exercises are great for evaluating and refining ideas.

• SWOT Analysis . This exercise requires participants to analyze the strengths, weaknesses, opportunities, and threats associated with each proposed solution. By conducting a SWOT Analysis, the group can thoroughly evaluate the viability and potential impact of each idea, identifying potential challenges and opportunities.
• Pros and Cons . In this exercise, participants list the advantages and disadvantages of each proposed solution. This method encourages participants to think critically about the potential outcomes of each idea, enabling the group to make a more informed decision.
• Poster Session . In this exercise, each proposed solution is presented on a poster, and participants are given time to review and provide feedback on each idea. The Poster Session promotes thoughtful consideration of each solution and allows for open discussion and collaborative evaluation.
• Plus/Delta . This exercise involves participants identifying the positive and negative aspects of an idea or solution. It can help to refine ideas by focusing on the strengths and weaknesses of each one.
• Affinity Mapping . This exercise involves grouping similar ideas together and can help to identify common themes and patterns. It can help to refine ideas by clarifying the relationships between different solutions.
• Assumptions Collection . This exercise involves identifying assumptions that have been made about the problem or solution and testing them to see if they are valid. It can help to refine ideas by identifying any flawed assumptions and correcting them.
• Force Field Analysis . This exercise involves identifying the forces that are supporting and opposing a proposed solution. It can help to refine ideas by addressing the barriers and challenges that need to be overcome for the solution to be successful.

By incorporating these workshop exercises, participants can thoroughly evaluate the proposed ideas to ensure they are robust and viable. These

Step 6: Select the Best Solution

As a group, decide on the most promising solution(s) based on the evaluation process. Discuss the reasoning behind the selection and ensure that all participants are on board with the decision.

To promote objectivity, encourage the use of predefined criteria or frameworks for evaluating the proposed solutions. By providing a structured approach to decision-making, participants will be better equipped to weigh the pros and cons of each idea, ultimately leading to a more informed choice.

This will also help you maintain a neutral stance throughout the selection process, allowing the group to discuss and debate the merits of each solution without bias. As a facilitator, your goal is to ensure that the group focuses on the problem at hand and avoids getting sidetracked by personal preferences or interpersonal conflicts.

If you see that the group is struggling to reach a consensus, you might need to guide them toward a decision. By summarizing the key points of the discussion and highlighting the most promising solutions, the facilitator can help the group make a well-informed decision that best addresses the problem.

The following workshop exercises are great for facilitating the selection process:

• Dot Voting . This method helps participants prioritize solutions by giving them a limited number of dots or stickers that they can distribute among the proposed ideas. The solutions with the most votes are considered the most promising and can be further discussed or refined.
• Fist to Five . This technique allows the group to quickly gauge the level of support for each solution. Participants indicate their level of agreement by raising a certain number of fingers (1 to 5), with five fingers signifying strong support. The solutions with the highest average scores are deemed the most favorable.
• Stack Ranking . In this exercise, participants rank the proposed solutions in order of preference, assigning a unique position to each idea. The facilitator then tallies the rankings and determines the overall order of preference for the group. This helps identify the top solutions based on collective input.
• Trade-off Sliders . This method encourages participants to consider the pros and cons of each solution by using sliders to represent various criteria, such as cost, time, or quality. Participants adjust the sliders to visually represent the trade-offs they are willing to make, and the facilitator synthesizes the results to identify the most viable solutions.
• SWOT Analysis . By evaluating each solution’s strengths, weaknesses, opportunities, and threats, participants can gain a comprehensive understanding of the potential outcomes and risks associated with each idea. This structured analysis helps the group make a more informed decision about which solution is best suited to address the problem.
• Decision Matrix . The facilitator creates a matrix with the proposed solutions as rows and the evaluation criteria as columns. Participants then score each solution based on how well it meets the criteria. The solution with the highest total score is considered the best option. This method promotes objective decision-making and allows for a clear comparison of the proposed solutions.
• Priority Mapping . This technique involves visually mapping ideas based on their importance and urgency. By using Priority Mapping, the group can quickly identify the most critical and time-sensitive ideas, ensuring that the most pressing solutions are prioritized for implementation.

Step 7: Develop a Plan for Implementation or Testing

With the chosen solution(s) in hand, create a detailed plan outlining the steps required for implementation or testing. Assign responsibilities, establish deadlines, and set milestones to ensure accountability and progress. Consider creating a pilot project or running tests to validate the effectiveness of the solution before a full-scale implementation.

Seek to guide the group in setting realistic timelines and defining clear roles and responsibilities. This involves promoting open communication, ensuring that everyone’s input is valued, and addressing any concerns that may emerge.

You might also consider to spend time establishing key metrics for monitoring success and setting up checkpoints to evaluate the success of the implementation, enabling the team to learn from their experiences and iterate on the solution as necessary.

The following workshop exercises work great for exploring an creating an implementation plan.

• Project timeline . A project timeline is an effective way to help the team map out the key milestones, tasks, and deadlines involved in implementing the chosen solution. It allows the team to visualize the project’s overall progress and identify potential issues that may arise during the implementation process.
• Future-Back Planning . Future-Back Planning is a technique that helps the team envision what success will look like in the future and work backward to identify the necessary steps to achieve that success. This approach can help the team develop a clear vision and strategy for implementing the solution.
• RACI Matrix . A RACI Matrix is a tool that can be used to clarify roles and responsibilities during the implementation process. It helps ensure that each team member understands their role in the project and can help prevent confusion or misunderstandings.
• Dependency Map . A Dependency Map is a visual tool that helps the team identify the interdependencies between different tasks or components of the project. This can help the team develop a more realistic and feasible plan for implementing the solution.
• Sailboat . The Sailboat exercise can be used to help the team identify potential obstacles or challenges that may arise during the implementation process. It involves visualizing the solution as a sailboat and identifying the factors that may help or hinder its progress towards the desired destination. This exercise can help the team proactively address any potential roadblocks and develop a plan to overcome them.

Step 8: Follow Up and Iterate

After the workshop, monitor the progress of the solution’s implementation or testing. Gather feedback, evaluate results, and make any necessary adjustments or refinements. Encourage open communication among participants, and consider scheduling follow-up meetings to review progress and address any emerging challenges.

The solution that was chosen may need to be adjusted or refined based on feedback or unexpected challenges that arise. As a facilitator, you should encourage team members to share their thoughts and ideas and foster an environment where experimentation and iteration are encouraged.

Find ways celebrate successes and acknowledge the efforts of the team throughout the process. This can help maintain morale and motivation for continued improvement and innovation.

Typical pitfalls when running a Problem-Solving Workshop

• Finding the Right Facilitator . Finding a facilitator who is knowledgeable and experienced in problem-solving techniques can be a challenge. It is important to find someone who can effectively lead the workshop and ensure that all participants are engaged and productive.
• Establishing Clear Goals . Establishing clear goals for the workshop is essential for its success. Without a clear understanding of the objectives, it can be difficult to ensure that the workshop is productive and successful.
• Creating an Engaging Environment . Creating an engaging environment for the workshop is key to its success. Participants need to feel comfortable and be able to focus on the task at hand.
• Managing Time . Time management is essential for a successful workshop. It is important to ensure that the workshop is structured in a way that allows for productive discussion and problem-solving.
• Ensuring Participation . Ensuring that all participants are actively engaged in the workshop is essential. It is important to create an environment where everyone feels comfortable to contribute and share their ideas.

Google is known for its commitment to fostering a culture of innovation and continuous improvement. The company regularly conducts workshops, hackathons, and brainstorming sessions to encourage creative problem-solving among employees. Google’s “20% time” policy, which allowed employees to dedicate 20% of their time to side projects, has led to the development of successful products like Gmail and Google Maps.

IDEO, a global design consultancy, is renowned for its human-centered, collaborative approach to problem-solving called “design thinking.” The company conducts workshops, both internally and for clients, to tackle complex challenges and create innovative solutions. This approach has helped IDEO to develop breakthrough products, such as the Apple mouse and the Palm V PDA.

Procter & Gamble (P&G)

P&G is a consumer goods company that has leveraged problem-solving workshops and open innovation programs to drive growth. They have held workshops and innovation sessions, such as the “Clay Street Project,” where cross-functional teams come together to tackle complex challenges and create new products. The company’s innovation initiatives have resulted in successful products like Swiffer, Febreze, and Mr. Clean Magic Eraser.

LEGO, the toy company known for its iconic plastic bricks, has used problem-solving workshops to foster innovation and drive business growth. The company has employed design thinking workshops to explore new product ideas and refine existing ones. LEGO’s commitment to problem-solving and innovation has led to the creation of successful product lines such as LEGO Mindstorms, LEGO Architecture, and LEGO Ideas.

• What is the purpose of the workshop?
• What are the objectives of the workshop?
• Who will be attending the workshop?
• What topics will be covered in the workshop?
• What methods will be used to facilitate problem-solving?
• What is the expected outcome of the workshop?
• How will the success of the workshop be measured?
• What is the timeline for the workshop?
• What is the budget for the workshop?

You might also be interested in reading up on:

• How Might We
• Hypothesis Statement
• Problem Statement
• SWOT Analysis
• Affinity Diagram
• CIRCLES Method
• Design Thinking
• Jobs-To-Be-Done Framework (JTBD)
• Tim Brown @tceb62
• Tom Kelley @TomKelley74
• Jeanne Liedtka @jeanneliedtka
• Tendayi Viki @tendayiviki
• Dave Gray @davegray
• Lateral Thinking : Creativity Step by Step by Edward de Bono (1970)
• Thinkertoys : A Handbook of CreativeThinking Techniques by Michael Michalko (1991)
• Problem Solving and Decision Making : A Guide for Managers by Barry K. Baines (2000)
• The 5 Elements of Effective Thinking by Edward B. Burger and Michael Starbird (2012)
• Six Thinking Hats by Edward de Bono (1985)
• Innovation Games : Creating Breakthrough Products Through Collaborative Play by Luke Hohmann (2006)
• Gamestorming by Dave Gray (2010)

Want to learn more?

Receive a hand picked list of the best reads on building products that matter every week. Curated by Anders Toxboe. Published every Tuesday.

No spam! Unsubscribe with a single click at any time.

Community events Product Loop

Product Loop provides an opportunity for Product professionals and their peers to exchange ideas and experiences about Product Design, Development and Management, Business Modelling, Metrics, User Experience and all the other things that get us excited.

• Become a mentee
• Become a mentor
• Product Management glossary
• User Experience glossary
• Product playbooks
• Product & UX video library
• Privacy Policy
• Terms and Conditions
• Code of Ethics

Made with in Copenhagen, Denmark

Want to learn more about about good product development, then browse our product playbooks .

Download your Free Persuasive Pattern samples

Sign up to our newsletter to download a free copy of our top rated cards in the Persuasive Pattern card deck. Link to download sent via e-mail.

Confirm your e-mail & start downloading

Thank you for your interest in our card deck. We've emailed you a newsletter confirmation link. Click it and we will send you another email with a download link.

Back to Guides

How to run a problem-solving workshop.

What is a problem-solving workshop?

A problem-solving workshop is a rapid session that helps you:

• Understand the root cause of a problem
• Quickly generate ideas to solve it
• Evaluate the ideas to ensure they’re robust
• Make a plan to test or implement the solution

This workshop critically assesses what’s going wrong and helps you find out what your options are to solve it, before you decide on the perfect solution.

Who should run a problem-solving workshop?

Product team leads, such as designers, product managers or engineers can run this type of workshop. There’s no one right person to lead something as important as this.

In fact, the core of your product development should start with the problem rather than the solution itself. It can be tempting to jump straight into features, but until you understand the problem well, you can’t begin to solve it.

When to run a problem-solving workshop

This workshop can be used in various circumstances:

• A show-stopping problem that grinds everything to a halt
• An intermittent problem that you want to get to the bottom of
• A customer or user problem, such as a pain point when using a service or product
• A high-level business problem, for example “too many customer complaints”, “conversion rate is too low”, or “operating costs are too high”

1. Get the right people together

2. identify the right problem.

• 3. Come up with ideas to solve the problem

4. Evaluate the ideas to ensure they’re robust

5. make a plan to test or implement the solution.

Read on to find out how to do all that, and more.

Invite all affected parties to a session. These are people that the problem has a direct impact on. Including those that aren’t impacted may offer a more objective view, but ultimately; more people equals more time. We want to solve problems with haste, so we can find out if it’s the right solution sooner rather than later!

What may appear like the problem, could be one of many observable results of a deeper underlying problem. To identify the ‘right’ or ‘true’ problem, we need to delve into it. This method is often called “Root Cause Analysis”.

There are many ways to conduct a Root Cause Analysis, but the easiest and most pragmatic way is to use the  Five Whys Analysis tactic .

Simply put, asking “why?” at least five times will lead you to the real problem. Solving this root problem subsequently solves all of the surface problems associated with it.

Learn how to run the Five Whys Analysis tactic

3. Come up with ideas to solve your problem

What normally follows identifying the right problem is a flurry of ideas. This usually takes the form of blurting them out at each other – but there are better, more structured ways to capture ideas.  Generating ideas in a structured way gives you time and space to think, as well as building on others’ ideas. The result means more thorough and refined ideas, over a back of the napkin sketch that the loudest person in the room decides is the best thing to do.

Idea-generation tactics for problem solving:

• Mind Map  – Get your brain on to paper, so you can start to form ideas for the methods below.
• Crazy Eights  – Eight ideas in eight minutes
• Reverse Brainstorm  – Come up with ways to make the problem  worse,  then reverse it to get the solution
• Round Robin  – Generate an idea, then have the person next to you build on it
• Storyboard  – Turn your idea into a sequence of events to understand how it might actually work in reality

Once you have a suite of ideas, you’ll want to review them and try some  evaluative tactics .

If you have a lot of ideas, you might want to prioritise the most promising ones to take forward with a decision tactic such as  Priority Map  or  Blind Vote .

Once you have a shortlist of ideas it can be tempting to go with the one that appears most promising. If time is of the essence, and it’s low risk – it might be the right call to just try it out.

However, it’s vital to evaluate ideas for solutions that may be more costly or complicated. Kick the tyres, so to speak.

Evaluating ideas gives you the confidence that your promising idea truly is promising, and is worthy of taking forward to the next stage: prototyping and implementation.

Evaluation tactics for ideas:

• Idea Beetle  –  a set of questions that help you assess if your idea is robust before you progress with it
• Rose, Thorn, Bud  –  a way to review the good, the bad and the potential of an idea
• SWOT Analysis  –  articulate an idea’s strengths, weaknesses, opportunities or threats

If you still have a lot of ideas, you might want to prioritise the most promising ones to take forward with a decision tactic such as  Priority Map  or  Blind Vote .

Now you should have one or two (or more!) evaluated, robust and promising ideas that you want to try out to solve the problem.

Whether you need to work out how to prototype and test the idea, or go ahead and implement the solution right away – you need a plan.

To work out a plan, use the  Sticky Steps tactic , which mentally starts you off at having the solution implemented or prototype tested, then works backwards to today in order to see what steps you need to take.

Once you have a solid plan, create accountability by creating a list of tasks to do, and assigning them to people with a deadline. You can do this with the  Who, What, When tactic .

2 thoughts on “How to run a problem-solving workshop”

Hi I’d love to know approx about how long it should take to run one of these workshops. If you could include that in your very helpful summaries – I think that would be very helpful to plan and market these types of servies.

Appreciate all you do! R

All activities are very helpful.

Appreciate you Nazia Psychologist

Leave a Comment Cancel reply

Let us know what thoughts or questions you have about this guide so we can improve it.

If you leave us your email, we'll let you know if we update this guide based on your feedback.

How To Prepare For A Problem-solving Workshop

Imagine sitting in a room with a firm of doctors. Each specialist carefully analyses every facet of a patient’s case. Everyone with their knowledge at play is geared to provide viable solutions to address the challenges they face.

Although the software design world may seem like a far cry from the medical field, they share a fundamental similarity: both revolve around problem-solving. Designers apply multiple practices to validate and authenticate solutions with our partners.

To align everyone, we set up Problem-Solving Workshops (PSWs). At its core, PSWs are a space to solve problems. Our team will dissect every aspect of the problem, identify potential challenges, and find the best solutions. Finally, we validate the process through testing.

Neil Webb, Design Producer and problem-solving workshop facilitator at MOHARA, shed light on how this process works by answering a few of our probing questions.

What Are Problem-Solving Workshops?

A problem-solving workshop is a collaborative event or session where participants come together to identify, analyse, and develop solutions for a specific problem or set of problems.

It could be a show-stopper of a problem that has stopped work or a way to identify improvement backlog items for your next sprint. The main goal of this process is to foster creative thinking, encourage teamwork, and facilitate learning by sharing ideas, experiences, and perspectives.

A typical problem-solving workshop can take many forms but include the following steps:

➡️ Define the problem: Clearly define and understand the problem(s) to be addressed.

➡️ Brainstorming: Encourage open discussion and the sharing of ideas, allowing participants to think freely and creatively.

➡️ Analysis and evaluation: Analyse and evaluate the proposed ideas, considering their feasibility, effectiveness, and potential impact.

➡️ Solution development: While considering available resources and constraints, develop and refine the most promising ideas into actionable solutions.

➡️ Implementation planning: Create a detailed plan for implementing the chosen solution(s), including timelines, responsibilities, and resource allocation.

At MOHARA, our problem-solving workshops are our take on a Google design sprint . It is a time-constrained, rapid five-stage process to answer essential product questions. It speeds up the design process and lets you quickly test and iterate your ideas.

As a result, you can shortcut the endless debate cycle and compress months of thinking and iteration into a single idea. Therefore, you are reducing risk at a basic level and saving a founder time and money.

What Are the Fundamentals of Setting Up a Problem-Solving Workshop?

Running a successful problem-solving workshop needs the founder’s support. Given that it is their idea and they have already devoted considerable time and effort to research, their insights are extremely valuable. Communicate the workshop’s objectives and deliverables to get the founder’s buy-in.

Assemble a workshop team of five to seven people including a Facilitator, a Lead Designer, a Lead Engineer, and possibly an Engagement Lead. In the case of a large organisation, including more than one stakeholder from the company – ideally subject matter experts – enriches the collaboration and decision-making process.

How Do You Facilitate a Problem-Solving Workshop?

The process should begin with a week of research, onboarding, and setup. To start with, one has to understand the most significant root cause of any given problem.

To achieve this, we interview the client and other key stakeholders and ask them to fill out a pre-workshop questionnaire. This information helps the MOHARA team understand the founder’s vision and long-term goals.

A traditional in-person workshop happens over four to five days. The activities on the first day are all about aligning ourselves as a team to understand the users, their needs, and the different challenges they may face during the product development cycle.

Several problem-solving techniques can be used to brainstorm solutions and get the best outcome. The idea is to choose your product’s most suitable and effective strategy.

How Does Conducting Remote Problem-Solving Workshops Impact the Process?

The shift to remote work has altered our approach to conducting workshops. While we at MOHARA are accustomed to working remotely, the absence of in-person sessions does pose some challenges.

Usually, we can go through the different phases within a week. But, remotely, it’s slightly different: you can’t have someone in a workshop call all day long; the sessions are intense and require a lot of focus.

We must slow things down for the sake of everyone taking part because these sessions help us understand whether users will receive a feature or product well.

We split the PSWs into one or two workshops a week. We then build the prototype, providing daily feedback and ensuring the founder understands what we’re doing, and why.

Having the Right Setup Is Essential for a Remote PSW

For a problem-solving workshop to be successful, the right setup is critical. When we are conducting a session remotely, we do the following:

➡️ Prebuilt templates: Templates are designed in advance for different sessions. The templates help guide all participants through multiple activities and checkpoints and revisit relevant information at any point.

➡️ Set up whiteboard software: We also use interactive whiteboard products to create a space for collaboration and review. Timelines, key deliverables, and communication are other significant factors in ensuring the process is smooth, and that the client feels comfortable and understands where we are going.

What Are the Next Steps?

Participants envision the solution to an identified problem during an ideation session where they sketch out ideas and concepts. The aim is to look for as many ideas as possible and examine examples and relevant cases they have come across elsewhere.

The team will then consider how certain features could resolve a critical challenge. There may be many ideas on how to solve the challenge faced, so the next decision-making stage is very valuable. The team and stakeholders decide which solution and critical features they would like to test and then turn that solution into a high-fidelity prototype.

The last part of the problem-solving workshop focuses on qualitative testing. We want to gain valuable feedback from actual users, so selecting them carefully is imperative. We ask participants to perform tasks, usually using specific user interfaces. While the participant completes each task, we observe the participant’s behaviour and listen for feedback.

What Role Does Prototyping Have in a Workshop Process?

Much of this process is about speed. We do not want to start building anything in code at this stage. Instead, using Figma – our prototyping tool of choice – the designer will lay out various screens and connect them with the specific steps we want users to take.

Based on some of the critical questions defined in our sessions, we will share a link with the users and then give them particular tasks we want them to carry out. We can then test which, if any, of our assumptions were correct, and start to think about some of the primary user journeys, the user experience, and other core features.

What Are the Most Overlooked Aspects of a Problem-Solving Workshop?

There are three aspects of a problem-solving workshop that is often overlooked:

🔶 It’s not a design sprint

It’s important to understand that the entire process is not just about design. There needs to be some technical expertise as well. That is why we don’t call these Design Sprints but rather PSWs. It’s about using design and engineering to solve a problem.

🔶 It’s essential to keep the energy up

One of the significant challenges regarding remote workshops is how much energy is required. If you’re in a room full of people like we used to be, you could generate solutions, get everyone together and build up the excitement.

However, doing it over a screen is tricky. It’s challenging to keep things energised and to avoid reviewing the same points and using valuable time.

🔶 Inclusion is also essential

The idea, especially with remote PSWs, is to ensure everyone has a voice. Only some people will speak up in a session. Naturally, some people are more vocal than others, and these people will generally lead the conversation.

If someone else, however, is given the opportunity to share even the slightest valuable insight, it could change the whole direction of the team’s solutions. It only takes one comment, or perhaps a note. For this reason, everyone must have a voice.

Are There Any Pitfalls?

Several things can go wrong during the process. Someone might drop off a call or have connectivity issues interrupting the flow. We’ve also had situations where the hardware doesn’t work correctly.

From a facilitation point of view, having a plan for each product-solving workshop and a clear outline of what will take place, are essential. That means mapping out the different activities and ensuring people know how long each activity will take. This plan keeps everyone aligned, and the PSW will only be successful with it completed ahead of time.

Lastly, user testing has to be qualitative rather than quantitative because, at this point, you’re asking for detailed information and feedback on the tasks they’ve had to do, particularly to identify any problems. You would need more than quantitative research to get that kind of data.

Do You Have to Check In with Various Stakeholders After the Workshop?

Yes. Client feedback is always valuable. It’s essential to get an update on how they are getting on from a product perspective, as well as gather their insights and feedback on the PSWs process.

Suppose we agree with the client to do further design work post-prototyping or engineering (or both). We would already have discussed those later-stage design phases in more detail during some of the sessions. By the way, this is another reason why having an engineering representative there during these sessions is so valuable.

During the PSWs, we would then compile a list of challenges to write up as questions that we aim to answer with our solution by the end of the workshops. After the PSWs have concluded, we provide feedback in the form of reports with user testing results, including data, a breakdown, and evidence of all the conducted activities.

What Do You Enjoy Most About Setting Up Problem-Solving Workshops?

It’s creative problem-solving at its finest! I enjoy engaging with founders and experiencing their passion for their products. It’s also great to work with the engineers, watch how they engage in the sessions, and identify solutions; having those different viewpoints is essential.

Setting up the workshop is enjoyable, too, because it involves using design tools that are constantly evolving; I am a designer at heart, after all.

Effective planning is the way to foresee risks and aim for success. Now that you have the lowdown on Problem-Solving Workshops, we suggest calling the relevant troops to get started.

It takes a team of experts to navigate challenges and produce a product that makes one proud. So get your tools packed; with Neil’s guidance and tips, you’re certainly off to a good start!

If you find you need more help with problem-solving, why not get in touch with MOHARA?

Related Insights

Exploring the Impact of AI in Fintech For Startup Entrepreneurs

12 months in AI: A Case Study of MOHARA’s AI Projects

Get Your Business Off the Ground: How To Approach Fintech Software Development

Pioneering together.

Laxmi Building 57 Bermondsey Street London SE1 3XJ

6th Floor, The Hudson 30 Hudson St De Waterkant Cape Town 8001

26th Floor, 246 Times Square Shopping Center Sukhumvit 12-14 Road Khlong Toei Thailand 10110

WeWork, 5th Ave, Manila, 1634 Metro Manila, Philippines

Guadalajara

Colabora Av Chapultepec Sur 480, 44140 Guadalajara, Jalisco, Mexico

WeWork, 240 Richmond Street W, Toronto, ON, M5V 1V6

Join our newsletter

We’ll bring you the latest updates from our ventures, share exciting news from MOHARA and offer insights from our latest blog posts.

Our Partners

© MOHARA 2024. All rights reserved.

Privacy Policy   |  Cookie Policy   |  Terms and Conditions

• Practice Exam

Navigating the Inspect & Adapt Workshop: The Key to Continuous Improvement in SAFe

0  Comments

In the dynamic world of Agile, the Inspect & Adapt Workshop stands as a cornerstone in the Scaled Agile Framework (SAFe). It’s a pivotal moment where Agile teams converge to reflect, learn, and plan for the future. But what exactly are the outcomes of this workshop? Today, let’s delve into the heart of this process and understand why “Identifying and prioritizing process improvements” is not just an option, but the primary outcome of the Inspect & Adapt Workshop.

The Essence of the Inspect & Adapt Workshop

At its core, the Inspect & Adapt (I&A) Workshop is a structured problem-solving session. It marks the end of the Program Increment (PI) and serves as a critical reflection point. Teams gather to inspect their achievements and adapt their processes, learning from their experiences. It’s not just about what we did, but how we did it and how we can do it better.

Why Process Improvement is Key

Among the options provided – creation of user stories, release of the product to customers, and setting the agenda for the next PI – identifying and prioritizing process improvements stands out. Why? Because continuous improvement is the lifeblood of Agile. While releasing products and creating user stories are essential, they are part of the ongoing Agile process. The I&A Workshop’s unique contribution is its focus on elevating the process itself.

Real-Life Application

Imagine a team working on a software development project. They’ve had a successful PI, with several user stories completed and features shipped. However, during the I&A Workshop, they realize that certain bottlenecks in communication slowed them down. By identifying and addressing these issues, the team sets the stage for more efficient sprints in the future, ultimately leading to better products and happier customers.

The Inspect & Adapt Workshop is more than a routine meeting; it’s an opportunity for genuine growth. By focusing on process improvements, SAFe practitioners ensure that their Agile journey is not static but a path of continuous evolution and enhancement

You may also like

The three skills of an effective safe scrum master: communication, coordination, cooperation, building trust in planning: the team’s commitment in safe, get in touch.

Session expired

Please log in again. The login page will open in a new tab. After logging in you can close it and return to this page.