Been thinking about Wardley Doctrine and how to make it consumable without an inherent need for a guide (guides are helpful, and an opt-in), but can we do something to improve learning the doctrine?
#WardleyMaps
#WardleyMaps
What if we were to organize Wardley Doctrine into snippets labeled with Category, Principle, and Practice? A sort of small package format that provides a packet of doctrine information. A microdoctrine.
#WardleyMaps
#WardleyMaps
For example:
—
Category: Development
Principle: Know your users
Practice: Know who are your users
Look at transactions over last x years. Pareto filter it and group into recognisable buckets of users
—
#WardleyMaps
—
Category: Development
Principle: Know your users
Practice: Know who are your users
Look at transactions over last x years. Pareto filter it and group into recognisable buckets of users
—
#WardleyMaps
Another example:
—
Category: Development
Principle: Know your users
Practice: Know what they are trying to achieve
- what is their “official” purpose (f.e. reduce unemployment, help their customers)?
- what drives them (bonuses, return on investment,challenge,…
—
#WardleyMaps
—
Category: Development
Principle: Know your users
Practice: Know what they are trying to achieve
- what is their “official” purpose (f.e. reduce unemployment, help their customers)?
- what drives them (bonuses, return on investment,challenge,…
—
#WardleyMaps
They don’t have to be short snippets, here’s an example of a microdoctrine in form of a book:
—
Category: Development
Principle: Focus on user needs
Practice: Conduct user needs research
See https://jdittrich.github.io/userNeedResearchBook
—
#WardleyMaps
—
Category: Development
Principle: Focus on user needs
Practice: Conduct user needs research
See https://jdittrich.github.io/userNeedResearchBook
—
#WardleyMaps
Currently, adopting doctrine is a daunting task. There is so much of it. Breaking down Wardley Doctrine into microdoctrine snippets could afford smaller chunks to assimilate, while maintaining the overall structure, intent, and direction.
#WardleyMaps
#WardleyMaps
We also know that the application of doctrine across companies can vary, because companies are different, operate in different contexts, etc.
Having microdoctrine, I can have a large selection of Practices for a given Category and Principle that I could pick from
#WardleyMaps
Having microdoctrine, I can have a large selection of Practices for a given Category and Principle that I could pick from
#WardleyMaps
Microdoctrine can be taylored to an organization by picking and choosing specific snippets.
I can imagine various consultants providing their snippets to the community and enriching our collective microdoctrine while still being able to serve as guides if needed
#WardleyMaps
I can imagine various consultants providing their snippets to the community and enriching our collective microdoctrine while still being able to serve as guides if needed
#WardleyMaps
Also.. the unit of contribution is much less. I don’t need to be a full blown consultant to contribute to doctrine, I can be an expert on a specific practice and share my microdoctrine for a Category + Principle + Practice and be done.
#WardleyMaps
#WardleyMaps
I think organizing Wardley Doctrine into microdoctrine could drive productization of doctrine which seems to be very much in custom area today
(end of thread)
#WardleyMaps
(end of thread)
#WardleyMaps