-
I take any opportunity to practice #WardleyMapping 😄 In this case, I wanted to map my side project @cognitive_load. When I finished mapping it, I have to say that I asked myself if I was going in the right direction 🤨 You might help me to answer that question! 1/10
-
If you want to learn more about why Cognitive Load take a look at this post. And if you want to join the beta, subscribe 🧡 2/10 cognitiveload.substack.com/p/why-cognitiveloaddev?showWelcome=true
-
Starting from the anchor, the customers. 👉 Tech Leader: Needs to have short feedback loops on teams' cognitive load to ensure a fast flow of change 👉 Developers: Provide their Developer Experience so that it can improve over time instead of never-ending increasing CL 3/10
-
Currently, I'm using Team Cognitive Load Assessment from #TeamTopologies (see Cognitive Load Survey Off the Shelf Component on the map). It covers the format to gather the data. It doesn't provide short feedback loops. 4/10 github.com/TeamTopologies/Team-Cognitive-Load-Assessment
-
The customers' needs are: 👉 Cognitive Load Historic: See how it evolves over time 👉 Manage Teams and Members: Knowing if adding a platform team caused a reduction in CL 👉 Communicate DX: Using the CL Survey, Developers able to share their pains 5/10
-
The #NoCode movement or SaaS should cover part of those needs. Part of publishing this thread is to see if we can create situational awareness together to improve that map and, consequently, how I'm implementing the side project. 7/10
-
A little demo for you 😊 10/10 loom.com/share/add8f8310f9d4b8db5147c758a9dc49a