How do I analyze big initiatives? Part 1 visualizes the BRD
Where there is a new initiative, how would you start the analysis?
I currently work on a significant initiative in my company. All I have is a BRD (Business Requirement Documentation) provided by the PMO.
I don’t know how do you feel about BRD. I think it is not that human friendly. May because I am a visualized person.
So the first thing I do is visualize all the BRD requirements.
- I created a Miro board first.
- Put each requirement in the BRD as a sticky note on the Miro board.
- Brainstorm all the possible user segment
- For each user segment, draft the backbones, a high-level user journey. Note that this might change as we dive deep into the detailed tasks. Don’t think the backbone is a one-time job, and don’t panic if you find it completely wrong or out of order later on. We need to embrace change.
- Have a read of each sticky note with the requirement, and put them under the corresponding backbone list. Note here that some of the requirements might be non-functional requirements. We should put them into another space to chat with Engineers later on.
Then the magic happens from here. You will find it is so easy to find the missing parts, and you will have a better understanding of what we would love to build.
In Part 2, I will share how I work with UX on new initiatives.
