Design > Requirements Analysis
requirements analysis
Ideally requirements should stem from user needs. Sometimes, however, you don't have access to users or perhaps you're developing a novel product for which it can be more difficult to collect user needs. For these situations, I've developed requirements analysis skills to ensure I can deliver a product for the business that is still usable and designed for the customer.
CAse study - requirements gathering for a new payments system
With no access to users, we held a week-long HCL-Deutsche Bank workshop with product owners and SMEs to understand the current landscape and business/ user requirements.
During these sessions, I sketched out user and information flows with the client, to help gather contextual information and understand what might be required from the new system.
I then transformed this insight into user flows and a working requirements document detailing high and low level requirements. This provided a solid foundation for us to develop a working relationship with the client and a working document from which we could review and enhance the requirements.
Example User Flow
Example User Flow
Excerpt from the High Level Requirements document
Excerpt from the Detailed Level Requirements document
From here I continued to produce concept designs, which evolved into the final implemented product.