Wardley Mapping Team Cognitive Load - Part 2/2
Wardley Mapping Team Cognitive Load - Part 2/2
Making sense of the TO-BE
If you didn’t read the first part, I recommend you do it before continuing!
The map
Based on what we learned, we could say:
But building on top of google sheets feels odd right? Let’s rethink the map with other components that fulfill those needs.
Rethinking the components
All the components I mentioned were used because the Team Cognitive Load Assessment uses Google Forms and google sheets underneath. Those two components influenced everything else we built on top.
Let’s start from scratch.
I will add another need that was implicit in the previous map, managing teams and their members.
What is needed to fulfill those needs?
We need four main components:
Running the survey. Which notifies the team members to respond to the survey for a specific time frame.
Team<>Members ’ relationship to know who belongs to which team when the survey is sent.
Cognitive load survey results to calculate the teams’ cognitive load at one point.
Cognitive load historic to see the evolution of teams’ cognitive load over time.
Those components will use off-the-shelf components such as:
Notification system: either Slack or email
PostgreSQL: because not building on top of spreadsheets should be obvious
Now it’s more clear what the project will do and what I should custom build :D
Next post: Team Cognitive Load tech stack
I will share what I decided to use to custom-build those components. I will share things such as:
Libraries/Frameworks
Deployment strategy
Monitoring
Databases
Authentication system
Do you want to join the private beta when available?
Add your email to the next link, and I will contact you when it's available.