Design decisions are bidirectional

Proving biz impact
1

Been running into this scenario more often.

When a business problem is fuzzy, product and design leaders get stuck. Teams either accept a stakeholder-defined problem as complete or treat the situation as too complex to tackle. Work continues, but it circles the problem instead of solving the actual problem

The solution is to reframe the problem. Design decisions can move in both directions.

Sometimes they start with user needs and move toward business outcomes. Other times they start with business goals and work backward to design choices. Each direction requires different questions. Starting from the business side can help clarify what matters, reduce fuzziness, and unblock progress.

1 Like
2

Love this… orienting around the business needs feels like one of the best ways to “ground” a team to real problems to do work that actually matters.

3

“When business goals and capabilities are the starting point, they become real constraints. Users are introduced as friction in the system.”

So introducing friction in the system is sometimes necessary?

4

Not just friction, but adding the users as friction.

Most design teams aim to optimize the user experience. I’m suggesting that’s the push method, and it is often difficult to create influence when used alone.