Six steps for adapting your design solutions to the right context

3. ‘High Level Requirements’ or ‘Coming up with a list of what you need a solution to do’
User stories – while guiding – often don’t bring us closer to potential solutions. The next step is essentially to translate the user stories into the high-level requirements of a / many solution(s). This can require a little technical knowledge to understand how things fit together, what technology can/can’t do and where you might need different types of interventions to address certain other aspects of the solution. This can be as holistic or as specific as you might need. Generally more detailed ‘business requirements’ might be too specific for an agile process, but high-level requirements can essentially re-frame and ‘translate’ the user stories in a way that fits with the creation of the tools. As mentioned, while this is traditionally from a software perspective, it could also apply to a process i.e. how each user sees the process might differ from overarching process flow and design which takes a more systems approach.