framing the problem

As a member of several working groups who are trying to change the status quo, I am struck by the effort it takes to turn the institutional tanker. 

This list of questions frames things in a different light. 

Asking the right questions to frame the problem

Framing the problem is vital for designers. We need to be relentlessly talking about the core benefits that a product or service delivers, and why.

I’ve found that framing the problem is something that teams really struggle with. This should be something we constantly refer back to as we look to iterate and improve what we’re working on. Framing the problem should provide the constraint and reasoning behind new features, or be used to guide the prioritisation of any content and design changes.

This is my approach. I spend most of my time at the moment asking people 5 questions (or variations of each of these questions):

Why are we doing this work?
or What is our motivation for building this product or service?

Who are our users?
or Who do we think would need to use this product or service?

What outcome will users get from this service?
or What problem will it solve for people?

What outcome are we looking for?
or What problem will it solve for our organisation?

What are our key metrics?
or What do we need to measure against these outcomes?

via {hollidazed}