Mapping a workflow is the least sexy and most underrated part of software design. I try not to hold workflow planning meetings right after lunch for fear everyone will fall asleep. But this is the skeleton from which the software is constructed. It needs to be perfect.
Once I have a more detailed map, I convene the group to confirm the key cases. Once they give it their final stamp of approval, there is no turning back. The fate of the software is sealed. Just kidding, software is always changing. That’s why we use agile. Speaking of Agile, I’m a Certified SCRUM Product Owner. I can write a mean story. Ask me about my business gherkin skills.
Now can we argue about colors? Not so fast! We’re still forming the information architecture that will guide our users effortlessly through the product. Since we all agreed on the "what", it’s now time to decide on the "how". This involves deciding on interactions and layout for each screen.