Schedule Time & Gather Materials
- Time Needed: 4 Hours
Can be split over two days
- Notebook & Pen
Carry Out This Method
Before the meeting, compile a list of key questions:
- What is the current status of this project? Is it a redesign? Is it a new product for an established company? Is it a new product for a startup?
- What is the business purpose of the product?
- What user needs are you hoping to meet with this product? What are your users going to be able to do that they can’t do now?
- What tasks do your users need to complete in order to meet their needs?
- What have you already tried? What worked? What didn’t?
- Who are the users you’re targeting?
- Who are the users you do not plan on targeting?
- Who are your main competitors?
- Do you want to attain the same level of success as your most successful competitor?
- Does your product need to differentiate itself from the competition?
- What are the organizational requirements for this product?
- Is it more important that this product is easy-to-use and easy-to-learn, or is it more important that it have robust, less-easy-to-learn features?
- What are the technological constraints? What can the hardware support? What can developers support? Will other products or services impact this product?
- What are the branding requirements, including logos, colors, etc?
- What will you expressly say “no” to? What are you absolutely opposed to? Why?
At the meeting, have everyone introduce themselves and their role. This ensures that the team understands each participant’s point of view. Ask about the needs of absent stakeholders. Make sure this information is recorded.
Review your list of questions. Stakeholders may need to discuss unresolved issues. As facilitator, you will need to redirect the discussion back to requirements gathering; if the conversation gets off track, offer to continue the discussion at a later date, after stakeholders have had a chance to resolve the issue.
After the meeting, record the requirements and e-mail them to stakeholders. Keep in mind these are preliminary requirements. Individual stakeholder interviews will likely surface additional requirements, constraints and opportunities. Personas, created from user interviews and Ethnography, will be used to write User Scenarios and identify user needs and goals. Final requirements will need to be re-approved after user requirements are identified.
Try These Tips
- If stakeholders do not have a list of preliminary user tasks, suggest performing a Backcasting session, or Brainstorming method.
- If you are asked to redesign a product, ask for Voice of Customer feedback (including common complaints and trouble tickets submitted to support), Web Analytics, Clickstream data, and reviews.
- The facilitator must be firm but tactful – kickoff meetings are often derailed by churn and debate.
- Discovery Studios can help determine more detailed usability and functionality requirements.