Understand our audience
- What are they thinking? Feeling? Saying? Doing?
- What do they wish they had?
- Where might they use it?
- What else is competing for their attention?
- What problem are they trying to solve?
- What motivates them?
- What expectations do they have?
Identify common personas
- Tech Coordinators
- Staff Developers
- Haven’t a clue and know it.
- Haven’t a clue and don’t know it.
Envision the use case scenarios
- What are the typical ways users would interact with the DLC?
- What are the desired outcomes of their interaction with it?
- What do they hope to achieve by visiting it?
- What behaviors are we hoping to elicit?
- What challenge or obstacle is removed by using the DLC?
Outline the core features
- What features are represented by the primary user scenarios?
- Which of these are missing from teach.oetc.org?
- What existing tools already provide a similar solution?
- If it could only do five, three, or just one thing, what does it absolutely have to do?
- What will change from creating the DLC?
- How much does this matter?
- What does success look like?
- How will we know?
Catalog the “knowns” and “unknowns”
- What are prerequisites to engineering a solution?
- What dependencies does our requirements/design document create?
- What ways can we reduce complexity to increase the success of the DLC?
Identify next actions
- Summarize our day’s work
- Review who’s doing what next