Plain-language guides for Business Analysts. Templates, techniques, and real examples — no filler, no theory-only content.
Educational content: All articles on this blog are for general educational and informational purposes. They represent professional frameworks and best practices in business analysis. Always adapt guidance to your specific organisational context and consult qualified professionals for complex or regulated projects.
Most BRDs are written for the author's peace of mind, not the reader's understanding. This guide shows you how to write one that gets signed off fast — with a complete template.
User stories that say "As a user, I want to login" are useless. This guide shows you how to write stories that development teams can actually build from — with acceptance criteria that become test cases.
Swimlanes are the most misused diagram in business analysis. This guide explains the three rules that make a swimlane useful versus decorative, with worked examples from banking, retail, and healthcare.
NFRs that say "the system must be fast and secure" are not requirements. They are placeholders. Here is how to write NFRs with real numbers that developers can actually implement and testers can actually verify.
Entity-relationship diagrams are not just for database administrators. Every BA working on a system with data (that is all of them) needs to understand ER diagrams. This guide makes them approachable.
Most RACI matrices are created in a spreadsheet, presented once, and never looked at again. This guide shows why that happens and how to create a RACI that genuinely clarifies ownership.
The BA toolkit has changed significantly in the last 3 years. This guide covers the tools that productive BAs actually use — not the ones that appear on job descriptions nobody reads.
In most projects, 90% of requirements are listed as Must Have. That means MoSCoW has done nothing. This guide explains how to apply MoSCoW correctly — with a facilitator's script for prioritisation workshops.
The most common mistake in process mapping is drawing the process the way management thinks it works. This guide shows how to capture the real As-Is process and design a realistic To-Be that will actually be adopted.
The standard BA interview questions ("Tell me about a time you gathered requirements") tell you nothing. These 12 questions reveal how a BA thinks — and the answers show you what to look for.
The debate about use cases versus user stories misses the point. They answer different questions and serve different audiences. This guide explains when to use each, with templates for both.
Most gap analyses end with a list of gaps nobody does anything about. This guide shows how to structure a gap analysis so it produces a prioritised initiative list that actually gets funded.