Em design, troque o Intuitivo pelo Racional

Better design decisions start with reasoning

Business leaders are regularly approached with problems that need quick solutions. “The team will miss the deadline unless we do something” or “We’ve had some negative feedback and need to act. What should we do?” are familiar lines. Feeling the need to be helpful and decisive, many leaders quickly propose a solution: “Let’s hire freelancers to finish the project on time” or “Let’s offer the customer a free upgrade.”

Leaders become good at quickly assessing a situation and proposing a reasonable solution. Better solutions may exist, but speed is often valued more than perfection. The problem is solved, the obstacle removed, and both the leader and the team can get back to work with minimal disruption. Right?

System 1 thinking in product decisions

This intuitive, fast and natural approach, known as System 1 thinking, naturally extends into other areas, including product decisions. Executives, often with years of experience, believe they understand what customers need and how the industry works. A history of satisfied customers and steady growth reinforces that confidence. So when a product manager raises a problem, such as falling account activation, the executive quickly suggests a solution: “We need to improve onboarding. Let’s build an onboarding assistant.”

The suggestion goes into the feature backlog, and the leader feels they have made a decisive contribution. The product manager briefs the team, which starts building, often unhappy with the proposed solution.

Designers and System 2 thinking

Designers, meanwhile, want to avoid suboptimal solutions. They believe research will provide the right answers, making it impossible for leadership to ignore their findings. Questions such as “Where did this idea come from?”, “Have we spoken to users?”, “What problem is this meant to solve?” and “How do we know this is the right thing to build?” are common. But they can sound irritating, especially when a leader believes they already have a good solution.

To avoid being seen as obstacles, designers can encourage a more deliberate, analytical approach: System 2 thinking. Rather than asking for solutions, it is more effective to present possible solutions and a plan for testing them. For example: “We have three potential approaches. Let’s make lightweight prototypes, test them with a small number of users and see which works best.”

Making room for System 2 thinking

Encouraging System 2 thinking in design and product decisions requires changes to governance and the way leadership is organised. Here are some practices that can help:

1. Structure meetings around the problem

Regular problem reviews: Instead of simply adding solutions to a backlog, hold regular reviews of the main problems. Revisit the work in progress and explore different approaches using data and ongoing feedback.

Track problem statements (see HMW) rather than just backlogs: Keep a record of the problems being addressed and make the core questions visible throughout the experimental cycle. This helps the team focus on solving problems instead of implementing predetermined solutions.

2. Build a culture of experimentation

Experimentation cycles: Create cycles that allow for prototyping, testing with real users and analysing data before committing to a full implementation. This supports an iterative, evidence-based approach.

Document hypotheses and results: Record the initial hypotheses and the outcomes of experiments. Revisit and discuss this documentation regularly, adjusting the strategy in response to actual results and encouraging continuous learning.

3. Involve leadership

Active participation: Bring leaders into brainstorming sessions and experiment reviews. This encourages them to think more deeply and consider several perspectives before making decisions.

Training and development: Offer leadership workshops on the benefits and practices of System 2 thinking. This helps build a culture that values deliberate, data-informed decisions.

4. Make the work visible

Dashboards and visual reporting: Use data visualisation tools to track experiments and the results of tested hypotheses. Clear, accessible dashboards help keep leadership informed and involved in decisions.

KPIs and measures of impact: Define success measures that go beyond shipping features and focus on the actual impact of what is delivered. This directs decisions towards measurable outcomes.

Leaders, heads of departments and CEOs are trained to operate in the fast, intuitive style of System 1, and they are often good at it. As designers and product managers, we can get better results by helping decision-makers engage System 2, which is more deliberate and analytical. Decisions and actions can then be guided by practical tests and direct observation, using established frameworks to organise those experiments.

We can do this by framing our work carefully and structuring decision-making meetings to keep the problem in focus for longer, encouraging considered approaches over quick fixes. Experimentation cycles, active leadership involvement and useful management tools can create a culture of governance that supports critical thinking and informed decisions.