🛠️ The Business Analyst Blueprint: Analysis vs Communication Techniques
Laura Brandenburg just broke down her full technique framework:
🍩Business-Level:
Process Flow Diagrams – see the big picture
Business Process Models – map current/future state
🍩Software-Level:
Use Cases – force analytical thinking (user does this → system does that)
Wireframes – visualize the interface
User Stories – specific functionality
🍩Information-Level:
Entity Relationship Diagrams – model data relationships
Data Mapping – field mappings for migrations/integrations
Data Dictionary – all fields for a workflow or domain
💡 Controversial take on Agile: User stories alone aren’t enough. You need bigger-picture views (use cases, process flows) to:
– Stitch stories together coherently
– Think through exceptions and impacts
– Avoid looking at “one little piece at a time”
Use cases help user stories naturally fall out of well-formed analysis.
These techniques lead to better questions and clearer requirements.
What’s your go-to technique for holding requirements together?
With my co host Vanessa Grant at this month’s
#BadAssBA trailblazer session. 💪🏻
Links to YouTube and group below – set your filter to “Most Recent” as LinkedIn hides any comments with outgoing URLs 🙄
