#Things to consider
- Don’t write requirements—tell stories instead. People can relate much more to a story than a dry word document.
- Record everything you talk about; take photos and videos of any whiteboard drawings and document the journey.
- Create a discovery team to figure out what’s the most valuable-usable-feasible solution to your problem.
- You don’t want people to be polite about your product, you want people to actually use it.
- Don’t risk listening only to the HIPPO - HIghest Paid Person in the Organization.
- Tasks are short verb phrases that describe what people do.
- Stories get their name from how they’re supposed to be used, not from what you’re trying to write down.
- Really talk about who is going to use this, talk about the customers.
- A good title is the most valuable part of your story, rewrite it if people are confused by it, you should be able to quickly reference it by its title.
- A triad is a group of people in the discovery team for figuring out the valuable-usable-feasible, this includes user experience, design, and technical experience.
- Have conversations about opportunities.
- Design by community isn’t the same as design by committee.