user story, requirement, design

User story, no requirement needed

Toby Elwin Blog Archive, Marketing, Portfolio Planning 0 Comments

Good design meets end-user need. Bad design wastes time and money. The difference is not about requirements. Requirements are your great, grandparent’s design directive. Effective design is about empathy and to understand empathy you need to understand the user story requirement. Before development, every project team needs to understand what to build. In project management requirements gathering provides that essential view of what the project delivers. Good requirements assumes what the build is what the end-user requires. This up-front effort to understand user need is shared across many professions: In communications, start with know your audience; In product management, starts with know your market; In software development, start with user requirements; and Is digital marketing, start with know your persona Whether the user had to sit through a presentation, scour documentation, search software, or fumble through a webpage on their smart phone, bad design creates bad feelings. A requirements document is not a …