This is a Request For Comments about how to structure doctrine in terms of microdoctrine (a pattern language for implementing and learning doctrine)
Any value we create is through meeting the needs of others. A mantra of “not sucking as much as the competitors” is not acceptable. We must be the best we can be.
Needs of others are not static, we must pay attention in case they change.
Establish a mechanism to listen to your users. This can range from conversations with users, to surveys, to research and discovery. These can happen at regular intervals or ad-hoc. A regular cadence for contact may be useful. It is important that some way of listening to the users is present. We do this to confirm that we Know Who Are Your Users and that we Know What Your Users Are Trying To Achieve. We should be able to determine whether we are contributing. Avoid surveillance.
STOP READING, TAKE ACTION
Focus On User Needs
Reproduced and adapted from writings by Simon Wardley under Creative Commons Attribution-ShareAlike 4.0 International License.