Closing the gap: from assumptions to solutions
I’ve been a User Researcher for over six years. I have found assumptions workshops a useful way to discuss problem statements.
What are assumptions workshops?
An assumptions workshop is a meeting to discuss the limitations of what the user-centred design team (UCD) knows about users, and the questions they might still have about them. The UCD team can use them to define next steps. This might be something like, what is our biggest priority to find out next and why?
For example, if a page is long, an assumption could be that people will only read the headers. The UCD team could find out if people understand other information on the page and test this assumption to determine the best way to redesign the content.
So, in this example the assumptions workshop would help plan the team’s approach to solving the problem in a user-centred way.
Four misconceptions about assumptions workshops
Lots of people have misconceptions about them, they think they are not helpful because they:
1. are a thing of the past.
2. invite conflict and “too many” ideas.
3. might slow the project down.
4. are ineffective when moving from problem space (or discovery phase) to solution space.
In this post I will explain why these misconceptions might be dangerous or misguided.
They are not a thing of the past — they are increasingly popular
There have been a lot a lot of negative connotations around assumptions in the language people use to talk about them.
We are told from a very early age: “Don’t assume! Don’t be judgemental!” In the workplace, we are told assumptions can significantly impact our relationships because we tend to pass judgments on three key aspects:
1. the behaviour of stakeholders
2. the intentions of stakeholders
3. our own actions and motivations
These things can make it difficult for people to feel they can make a safe expression of judgement based on the information they have.
But this is an outdated view. We all pass judgments, and they can help us move forward.
They invite conflict which can be a positive thing
Traditionally, we think of conflict as a blocker rather than an avenue for positive change, iterative design and creativity.
But, as a User Researcher, you should lead with a positive attitude towards conflicting ideas so that people can challenge each other’s assumptions in a controlled environment. You should also teach others to do the same.
For example, the more you all disagree during your assumptions workshop and the more conflicting ideas you can bring to the table, the better! You’ll be able to get lots of ideas out quickly and dismiss the ones that won’t work, fast. Conflict is the energy that you need in the room to make that happen.
Assumptions don’t slow you down, they speed you up
An assumptions workshop can help you deal with conflict so effectively that your project moves more swiftly from problems to solutions.
There are lots of ways assumptions can speed things up.
One option is thematic analysis where similar themes are grouped together. This helps you to see patterns between the assumptions of different people.
Prioritisation matrices can also be helpful. They often employ a grid with each section representing a unique priority. For example:
- top left: High importance assumptions, high urgency
- bottom right: Low importance assumptions, low urgency
When you are creating one, this is where everyone in the workshop needs to know they are entering the solution space! People can jump to conclusions and assume things. It is in fact required.
Assumptions are effective but how can you run a workshop?
1. They don’t have to take hours to organise
You might ask your attendees to populate a board first with their assumptions, then meet later, for 30–45 minutes, to discuss them or add any additional ones.
2. Bring at least one of each discipline you need to the table
For example, have at least one Business Analyst or Product Owner in the room.
3. Make sure you have a fair balance between disciplines
You should include UCD, data, engineering, and product people at the workshop.
4. Don’t ignore salespeople if you can
They can sometimes imagine the best way to promote what you are designing, and we can all learn something from them. They know what might sell which can make them very user centred.
5. Assumptions can express varying degrees of confidence or show attitude and bias, and that’s OK
They can be expressed as, for example:
- “I know I might be wrong, but I have this funny feeling that ….”
- “This might be idiotic, but I am concerned that …”
With this kind of language, it’s great for people to bring their personality to an assumptions workshop. They shouldn’t be afraid to do so. Their own view can help the team to look deeper at a range of perspectives and this can give the product a unique edge.
