Problem framing

Problem framing is a problem-solving method that’s designed to align the entire team with one solution for a project by structuring the issue’s details in a digestible and collaborative way. So, when your team can’t agree on a solution, use this play to take a step back and align on the problem you are solving for.

Prep time

5 mins

Run time

30 mins

Persons

3-10

people floating

Prep time

5 mins

Run time

30 mins

Persons

3-10

What you will need

Remote

  • Video conferencing with screen sharing

  • Digital collaboration tool (see templates)

In-person

  • Whiteboard

  • Sticky notes

  • Markers

  • Timer

Instructions for running this Play

1. Prep

Est. time:

5 MIN

For remote teams, create a collaboration document using one of the templates above if you’d like. Share the document in advance with your team.

For in-person teams, book a room and prepare sticky notes and markers. Divide the whiteboard into four quadrants: who, what, why, where.

Send any relevant supporting data you have in advance to the team.

Pro tip: Your customers’ shoes

If the problem is around your customers, prepare the team by gathering and sending them as much relevant customer information as possible.

2. Set the stage

Est. time:

2 MIN

Let your team know that the goal today is to understand and define the problem, not to solve it.

3. Brainstorm

Est. time:

10 MIN

Ask the team to take a step back and think about the problem as a whole from the perspective of the people affected by it.

Set a timer for 10 minutes for the team to add their ideas to the collaboration document or on sticky notes to the whiteboard.

Pro tip: Who

Who is experiencing this problem? How do we know that they are experiencing it? What feedback have we received from them on it?

PRO TIP: WHAT

What is the nature of the problem? What signs point to there being a problem?

PRO TIP: WHY

Why is the problem worth solving? What's the impact on the people experiencing the problem? What happens if we don’t solve it?

PRO TIP: WHERE

In what circumstances is this problem occurring? In what circumstances does it not occur?

4. State the problem

Est. time:

10 MIN

Using the ideas generated by the team, craft one concise problem statement that sums up the issue from the customer’s perspective. 

The problem statement should include who is affected, what is affecting them, why it needs to be solved, and where the problem is happening.

Example: final statements

Here are some problem statements that various teams formed at the end of running the Problem Framing play.

Confluence template

Follow-up

Make it visible

Post your problem statement somewhere highly visible to the team - in your online space or in your physical workspace. This will keep the problem at the top of everyone’s mind.

Next steps

Now that you’ve clearly defined the problem, assemble the appropriate team members together to create a plan for solving it. Running a Disruptive Brainstorming Play to generate ideas is a good place to start.

1. Prep

Est. time:

5 MIN

For remote teams, create a collaboration document using one of the templates above if you’d like. Share the document in advance with your team.

For in-person teams, book a room and prepare sticky notes and markers. Divide the whiteboard into four quadrants: who, what, why, where.

Send any relevant supporting data you have in advance to the team.

Pro tip: Your customers’ shoes

If the problem is around your customers, prepare the team by gathering and sending them as much relevant customer information as possible.

2. Set the stage

Est. time:

2 MIN

Let your team know that the goal today is to understand and define the problem, not to solve it.

3. Brainstorm

Est. time:

10 MIN

Ask the team to take a step back and think about the problem as a whole from the perspective of the people affected by it.

Set a timer for 10 minutes for the team to add their ideas to the collaboration document or on sticky notes to the whiteboard.

Pro tip: Who

Who is experiencing this problem? How do we know that they are experiencing it? What feedback have we received from them on it?

PRO TIP: WHAT

What is the nature of the problem? What signs point to there being a problem?

PRO TIP: WHY

Why is the problem worth solving? What's the impact on the people experiencing the problem? What happens if we don’t solve it?

PRO TIP: WHERE

In what circumstances is this problem occurring? In what circumstances does it not occur?

4. State the problem

Est. time:

10 MIN

Using the ideas generated by the team, craft one concise problem statement that sums up the issue from the customer’s perspective. 

The problem statement should include who is affected, what is affecting them, why it needs to be solved, and where the problem is happening.

Example: final statements

Here are some problem statements that various teams formed at the end of running the Problem Framing play.

Confluence template

Follow-up

Make it visible

Post your problem statement somewhere highly visible to the team - in your online space or in your physical workspace. This will keep the problem at the top of everyone’s mind.

Next steps

Now that you’ve clearly defined the problem, assemble the appropriate team members together to create a plan for solving it. Running a Disruptive Brainstorming Play to generate ideas is a good place to start.

Variations

Craft a customer

If the people affected by your problem are your customers, have each team member build a persona for a customer prior to the session. During the session, have them embody that persona and explain the problem as that customer.

Still have questions?

Start a conversation with other Atlassian Team Playbook users, get support, or provide feedback.

Stay up to date

Get the latest Plays and work life advice when you sign up for our newsletter.

Stay up to date

Get the latest Plays and work life advice when you sign up for our newsletter.