Introductions
Hello everyone I would like to show off a Wardley map of the Anoma Product that I’ve made.
Since this is my first Wardley map posting here on the forums I’d like to explain briefly what they are.
Wardley map’s are a way of charting out dependencies and concerns.
Usually they are created by first considering what a user of some product cares about, and then mapping out the chart on how one can supply the value to the user.
These maps work best when collaboration is had, as we can start to spot discrepancies on the position of nodes on the map which opens up for refinement, reflection, and discussion.
Further, they work well, when people with context create them in a group fashion, I for example don’t know the intricacies of Namada development, however a map of the efforts would help my understanding and open the floor to questions about both the tactical and strategic choices employed.
Wardley mapping has been used in a wide range of contexts from: GCHQ to big corporations.
On the Anoma Node team, we have been using mapping (inspired directly!) to successfully chart out dependency structures and their visibility to the end user:
About the Anoma Product Map
This map aims to map the value and concern that developers and users of Anoma would care about.
What I hope for in posting this is:
- For anyone point out where I misplaced nodes on the chart
- For anyone to point out where I missed major components
- For the visibility of everyone on how our work affects the end user/developer.
After the discussion and suggestions are finalized, I want to port the suggestions to an Anoma wiki along with a link to this discussion forum.
Further for the sake of easier discussion, I will try in the future to find a way to port my diagrams to excalidraw, for easier collaborations and suggestions. At which point I’ll port it back to my model.
I can also post the pages that contain these models publically in the future, as a lot of my pages can be very helpful for other organizations or anyone who manages projects.
The Wardley Map
Without further ado here is the Anoma Product Map:
This map contains the current state of the Anoma implementation and specs via the nodes:
- Anoma Node v1
- Specs V1
I’ve also charted out the evolution that I think these particular components will take and their effects on the ecosystem.
These nodes are realized by the red nodes:
- Specs V2
- Node V2
- Node V3
Further I suspect once we have V2 ready, that more applications will be written and in V3, that we will start having more graphical applications being made ontop of Anoma.
One of the defining features of Anoma is that it’s a live distributed operating system, and live systems are amenable to live visualization that should support good UX.
In green I’ve highlighted the way that we currently hold discussions:
- Slack is currently our goto for synchronous discussions
- The Research Forums are a great place for debate and getting a look at the org
Further I’ve broken down the dependencies of the Node into various sub components in which I’ve charted their maturity.
I’ve probably forgot some key important pieces please let me know if you’ve spotted anything.
Also the Multi chat nodes are mostly a stub, I hope in the future to expand the Applications node in the future into a full fledged map separate from this one.
Further organization
I am using glamorous toolkit to map these nodes, and in doing so I gain extra modeling abilities:
The post:
Evaluating multiple Wardley Maps through node profile diagrams in Glamorous Toolkit
shows how we can do analysis on multiple maps at once. I think it would be great if we could map more concern areas, so we can better increase the visibility of sub-areas of Anoma along with cross correlating differences in thought about the maturity of certain choices.
I’ve started very briefly on this with my own meta node of the organization, that I will refine at some point and post to the forums!
Thank you everyone for reading this post, I hope this brings more clarity and good discussions.