We don’t need no stinkin’ requirements….

The therapy tent at #occupyPDX looks like a good place for stakeholder interviews….

Pressed to explain that context scenarios don’t just come out of thin air — I put together a list of questions we need to have answered before we can write some narratives about users solving their problems….

So pull up a chair with your favorite stakeholder and start digging in…..

Product Manager Interview Outline – User Experience Requirements Gathering
(the goal for this interview is to elicit enough information to derive a set of context scenarios to begin elaborating)Product (or Project) Name:
Who is being interviewed?
Who is doing the interviewing?

Business Objectives:

  • What is  THE  primary business objectives (for our company) for the product — ( the number one reason why  it did or should be funded?) :
    Other business objectives for the product?:
  • Please identify the main business problem for our primary buyer you hope to solve by offering this product.
  • Please identify the main business problem for our primary user you hope to solve by offering this product.
  • How do you plan to measure the business success of this product?
  • Known Business requirements?
  • Known Technical requirements?
  • Key differentiators that will make us successful?

User Goals:

List all the different types of users you think will interact directly (configure, view data, generate reports) with this feature / function / product.
1.
2.
3.

List all the different types of users you think will interact indirectly (get reports, tell people to do something with…) with this feature / function / product.
1.
2.
3.
For each direct (and indirect)  user, do as many of these as necessary:

From your perspective, describe user type ____________ interaction:

  1. What is this user’s primary goal?
  2. Is this a critical goal for them?  For us?
  3. What does success look like for them (when they are finished using this feature/function/product what have they accomplished?)
  4. What feature(s) are they using to accomplish what they set out to accomplish ?
  5. How long do they spend meeting their goal?
  6. How much time elapses before they use this feature, function again?
  7. How frequently are they using this feature/function to accomplish this goal?
  8. Is this something they are currently doing?
  9. How are they doing it now?
  10. How you think they would like to be able to do it?

Repeat questions 2-10 for another goal…..Have Fun!

Published by JB

@uxsuccess Lean User Experience; Agile software development @Tellagence, I believe user success = business success. I talk about that here: uxsuccess.com Personal blog - http://staticpoetboy.com

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s