Software Engineering, Project Management, and Effectiveness
MadLibs can be an interesting approach to capturing or identifying principles, practices, values ... etc.
Here's an example attempting to encapsulate principles of agile development:
Here's one example:
Of course, you can also leave off the front and contrast with the behavior you'd like to change_________ ... over static and stale communication approaches.
Notice the ..x "over" ...y approach for the practices/principles above. Sometimes laws/principles/rules come across as common sense or "yeah, I already mostly do that" until you sharply contrast. It's a challenge to both the principle/practice author (am I striking the precise and accurate chord?) and the principle/practice follower (am I really changing behavior?)
This approach works for values too:
This is the approach used in the Agile Manifesto http://www.agilemanifesto.org/
So if you're responsible for identifying/documenting your organizations principles/practices/values, you might try using a MadLibs approach and a Wiki.
PingBack from http://actionable.pierresccservice.com/using-madlibs-to-create-actionable-principlespractices/
Awesome idea.You start with your guidance and someone else fills in the blank.Perfect