If you’re building an app helping teams order lunch every day, the workflow might look like this: 1. Someone gets hungry. 2. He or she communicates this to the rest of the team. 3. Debate ensues about whether to go out or order in. 4. Second debate about where to order from. 5. Menus for different restaurants are passed around. 6. A decision is arrived at quickly. 7. One person is appointed to gather everyone’s orders. 8. That person then places order. 9. That person communicates delivery time & cost to everyone 10. Time passes. 11. Food arrives, and is eaten. 12. Orderer checks if everyone paid enough & who still owes money. 13. Finances are settled, or the settlement is postponed until tomorrow. 14. Some will talk about the food on Twitter or Facebook. Some will post pictures on Instagram. Others will review on Yelp. 15. Everyone returns to work. When you understand the full workflow, you can focus on the most concise, painful subset your product solves, or alternatively the piece you can make more fun or interesting. Ask yourself – is my product a vitamin or a painkiller? Where should you start? Start your product at the first step where you can add value. For our lunch example, that’s probably step four. Starting any earlier would mean taking on chat products or email, rarely a good idea. 25