The tentative proposal (I’ll update that section in response to the discussion):
Know your users (e.g. customers, shareholders, regulators, staff)
Desired practices and behaviours
- Know who are your users, f.e. customers, regulators, employees, etc.
- Know what they are trying to achieve:
a. what is their “official” purpose (f.e. reduce unemployment, help their customers)?
b. what drives them (bonuses, return on investment, challenge, inertia)?
c. if they are driven by other users (f.e. the board put under pressure by investors), you have to understand both groups, and their options
- Monitor feature requests and bug reports - if they are difficult to understand, the customer situation may be different from what it appears.
- If you can, experiment to uncover needs that have not been yet verbalised.
Knowledgable people in the field
to give you a bit of a context - I have created a clickable version of Simon’s doctrine table at doctrine.wardleymaps.com. A screenshot below:
One of the first comments was to add some sort of tooltip explanation of what specific patterns mean, and how they can be assessed. I must admit - I tend to be opinionated about those, but I would love to hear your opinion first.
What is your ‘Know your users’ checklist?
How do you know whether you know enough?
Do you have any useful resources or specific people to follow?
Hopefully, together, we will create an entire doctrine handbook :-), but for a starter, I propose to discuss items one by one.