kas-madrigal
commented
3 months ago Why? We are in such a moving system! Quite a few teams internally are heavily dependant on small pieces of data from the school journey, plus all the dependencies we are not aware of! This impact analysis is just a way to try and predict what impact the selected changes are going to have on the wider teams at CPD (their tools and systems i.e. finance tool) as well as our end users (which could fall under prototype testing)
What? This could look like in different ways!
- Actual prototype testing
- guerrila testing! grab any random team member to check the new changes
- Go through insights from internal research and mark dependencies
- Highlight changes to other teams in a large internal email so people flag if it affects them (this could get out hand if it's not managed correctly cause everyone's a critic, but maybe something simple like a bullet point list of things we will track/not track on a journey? no visuals, they'll go nuts)
- Make team map and add which parts of database/user journey they interact with
- workshop with PMs from other teams
claire-hughez
Why?
We are in such a moving system! Quite a few teams internally are heavily dependant on small pieces of data from the school journey, plus all the dependencies we are not aware of! This impact analysis is just a way to try and predict what impact the selected changes are going to have on the wider teams at CPD (their tools and systems i.e. finance tool) as well as our end users (which could fall under prototype testing)
What?
This could look like in different ways!
Helpful links or other information