In any design process, assumptions are inevitable. Teams often make assumptions based on past experiences, industry norms, or a limited understanding of the problem space. However, these assumptions can easily go unchallenged and become hidden risks, which could lead to misalignment, wasted resources, or even project failure. Helping teams surface their assumptions early and often is critical to achieving clarity and alignment in design. Here are effective strategies to guide teams in recognizing and addressing their assumptions.
1. Foster a Culture of Openness
Creating an environment where team members feel comfortable expressing doubts and uncertainties is the first step in surfacing assumptions. This is especially true for cross-functional teams where expertise and perspectives vary. Establishing psychological safety is key here—team members must know that their questions, concerns, and uncertainties are welcomed and valued.
Start by explicitly encouraging openness during the early phases of a project. This could include:
-
Explicitly acknowledging that assumptions are part of the process: When beginning a design task, state that it’s natural to make assumptions but that it’s critical to surface and test them early.
-
Modeling vulnerability: As a facilitator or leader, actively share your own assumptions and uncertainties. This signals to the team that it’s okay to do the same.
2. Use Structured Techniques for Assumption Mapping
One practical tool to help surface assumptions is an Assumption Mapping exercise. This structured approach helps teams identify their assumptions systematically and then prioritize them based on risk.
Here’s how it can be done:
-
Identify Assumptions: Ask the team to list out assumptions they’re making in the design process. These might relate to user behavior, technological feasibility, business constraints, etc.
-
Categorize: Sort the assumptions into categories, such as:
-
Known: These assumptions are backed by data or research.
-
Unproven: These assumptions need validation through testing or further inquiry.
-
-
Prioritize: Rank assumptions based on their potential impact on the design and the risk they pose if proven false. Focus the team’s attention on high-priority assumptions.
-
Test Assumptions: Create an action plan to validate the most risky or unproven assumptions. This could involve user testing, prototyping, or further research.
This structured technique not only brings assumptions into the open but also ensures that the team prioritizes them in a way that reduces potential risks early in the design.
3. Ask Powerful Questions
Encouraging critical thinking through specific, open-ended questions is one of the best ways to surface assumptions. Use questions that challenge the status quo and prompt reflection on the team’s thinking.
Examples of questions that can help surface assumptions include:
-
“What do we know for sure?”: This question helps the team distinguish between facts and assumptions.
-
“What might we be assuming about our users’ needs?”: This question can bring assumptions related to user behavior or preferences to the forefront.
-
“How might our assumptions change if we had more data?”: This prompts the team to think about the lack of evidence behind their assumptions and the need for validation.
-
“What happens if this assumption turns out to be false?”: This encourages thinking about the consequences of incorrect assumptions.
These kinds of questions not only surface assumptions but also challenge the team to think about how these assumptions could impact the design and project outcome.
4. Conduct Assumption-Validation Workshops
In larger teams or cross-functional environments, it may be helpful to facilitate a workshop that’s focused specifically on validating assumptions. The workshop can be structured in a few different ways depending on the team’s needs.
-
Assumption Storming: Have the team list out their assumptions related to the project or design challenge. Encourage rapid brainstorming and capture all assumptions, both big and small.
-
Assumption Ranking: After listing the assumptions, the team can rank them based on potential risk, impact, and the difficulty of validating each one. This helps to highlight the most critical assumptions that should be tested.
-
Testable Outcomes: Break the assumptions down into clear, testable hypotheses that can be verified with data or user feedback. This shifts the conversation from vague beliefs to actionable insights.
This collaborative approach not only surfaces assumptions but also gives the team a shared understanding of what needs to be validated.
5. Use Real Data or User Feedback
Sometimes, assumptions can be rooted in beliefs that aren’t actually reflective of the user’s needs or the project’s reality. To challenge these assumptions, use real-world data or feedback wherever possible. This could include:
-
User Research: Regularly conducting user interviews, surveys, or usability tests can help challenge assumptions about user needs, behaviors, or preferences.
-
Analytics: Use existing product data or industry benchmarks to validate assumptions about the market, user behavior, and trends.
-
Prototyping: Rapid prototyping and testing with real users can often reveal whether a team’s assumptions about design solutions are on target or need adjustment.
By actively incorporating user feedback or real-world data into the design process, teams are less likely to rely on unsupported assumptions and more likely to make decisions based on evidence.
6. Promote the Practice of Iterative Design
Assumptions don’t need to be surfaced all at once. A more organic approach is to adopt an iterative design process where assumptions are challenged incrementally. Each design iteration becomes an opportunity to test, validate, and refine assumptions.
As teams work through iterations, they can focus on refining their understanding of both the problem and solution space. This provides multiple opportunities to address any assumptions that may have been hidden earlier.
Some key activities that promote iterative testing include:
-
Rapid Prototyping: Create early, low-fidelity prototypes to test assumptions quickly without significant investment.
-
Regular Reviews: Set up regular review sessions where the team can share insights, challenges, and learnings that might reveal underlying assumptions.
-
User Testing Cycles: Perform continuous user testing throughout the design process, rather than just at the beginning or end.
By iterating, teams can test assumptions more frequently and adjust their designs based on the latest information, keeping the process grounded in reality.
7. Build Cross-Disciplinary Collaboration
Assumptions are often influenced by the expertise of specific team members, whether they are engineers, designers, or product managers. It’s important to bring all perspectives to the table to surface these assumptions, as each role brings different assumptions to the design process.
Foster cross-disciplinary collaboration by:
-
Encouraging diverse input: Make sure that different stakeholders (e.g., developers, designers, business analysts) are involved in assumption-mapping and validation sessions. Each discipline may bring different assumptions about the design.
-
Shared decision-making: Involve the entire team in critical design decisions that could be based on assumptions. When everyone is part of the conversation, assumptions become harder to overlook.
Conclusion
Surface assumptions early and often, and turn them into an integral part of the design process. By cultivating an open, collaborative environment, using structured exercises, and validating assumptions with real data, teams can make more informed decisions and avoid the risks associated with hidden assumptions. The goal is not to eliminate assumptions but to ensure they are surfaced, understood, and tested, which will ultimately lead to stronger, more robust design outcomes.