Imagine youāve been tasked with navigating a very important ship containing valuable cargo from a port in Venice, Italy, to a port in Cape Town, South Africa. As an experienced captain, youāve navigated this route dozens of times before, so itās second nature to you, but your crew has never sailed to South Africa. Instead of using a map, however, you decide to adopt an unconventional new technique: youāre simply going to verbally describe the route in detail.
Thatās not going to end well. And, unsurprisingly, neither will any business analysis documents that donāt include strategic visuals. Here, weāll go over the types of visuals you should be sure to include in your business requirements documents to ensure the best outcome possible.
What is a business requirements document?
A business requirements document (BRD) details a solution for a project. For instance, if youāre planning on increasing product sales through virtual try-ons, a business requirement document would lay out a plan in detail for all stakeholders.Ā
A BRD normally includes:
- Current business processes
- Proposed business processes
- Goals and objectives
- Constraints and risk factors
- The reason for implementing the solution
- User needs and expectations
- Deliverables required for a projectās completion
- Personnel requirements
- Functional requirements
- Timeline and delivery schedule
- Benefits and costs
- Financial statements
- Summary
- Objectives
- Scope
- Features
- Assumptions
This business requirements document is similar to a map: it shows where the business is currently and where it would like to go, as well as what the organization would like to achieve by taking the journey. And, just like a map, itās much more effective when itās an exercise in showing and not just telling.
In short, visuals make for stronger, more compelling BRDs and help communicate goals, current/future states, and proposed solutions.
Thereās another issue that most of us are hesitant to talk about, but itās real and it needs to be addressed: as a society, we no longer read the way we used to. Consider the way youāve likely been reading this blog. Youāve probably been skipping around, missing some sentences and skimming through to get a general gist of things in the most efficient way possible.Ā
That same approach applies to how your stakeholders will consume your BRD. And thatās a problem because, if youāre only relying on text, a stakeholder may well miss something vital to the success of the solution. By incorporating visuals, you force the reader to stop skimming text and pay attention to the presentation in a different manner. Visuals just may be the key to getting your solution adopted and implemented correctly.
How to write a BRD
While writing a BRD is a complicated process, hereās a general overview of the steps involved:
-
Gather informationāConduct interviews with various stakeholders to determine the correct direction for your solution and what the requirements should be.
-
Detail key attributesāExplain what your solution should include to meet customer needs.
-
State the scopeāThis is important for managing the project and avoiding scope creep.
-
Outline the processāDescribe the steps that should be taken for the solution to be implemented and how those steps tie into one another.
-
Understand the impactāShow how processes, technology, individuals, and products will be impacted.
What kind of visuals should you be using?
A business requirements document is customized to a specific businessās needs. With that in mind, here are some key sections to include.
BRD scope models
The scope model visually represents what is and is not part of the scope of the solution. This detailed breakdown is important because even the most seemingly easy projects are subject to āscope creep,ā which can make the cost of a solution balloon. Itās much easier to visually represent this scope than rely on a pages of text. This is an important feature of your BRD because it also outlines what canāt be fixed through the implementation of your solution. This establishes clear expectations from the outset.
Hereās a helpful template to follow when organizing your BRD and establishing scope.Ā