Evaluate and Evolve everything

In a learning and dynamic organization, it’s important to simply start doing things, once we’ve a good enough for now, safe enough to try soltution to a Driver. We do this until the next review. Regular reviews of agreements, domains and behavior is an essential practice to evolve our organization.

s3 kaizen
This helps us to
  • Adapt agreements to suit changing context.

  • Stop doing things which are a waste (don’t help us).

  • Integrate learnings to make agreements more effective.

We therefore ensure all agreements have an appropriate review date.

This is the main reason we should track as many agreements and domains as possible as VIPs - VIPs have a due-date for agreements and agreements will pop-up in the accountable circle on that day, so that we don’t forget to start the review.

Evaluating agreements can be as simple as checking that an agreement is still relevant, and there is no objection to keeping it as it’s. Usually done in Governance Meetings or dedicated meetings to review a specific agreement or domain.

Examples

Meetings

Most organizations have a lot of (recurring) meetings. We should always be clear about the Driver (the Why) of a meeting, even when the Driver isn’t written down. Do short Meeting Evaluations at the end of meetings, from time to time.

  • If the Driver is no longer relevant consider dropping the meeting.

  • If the meeting doesn’t have the intended effect, change the meeting (agenda, participants, length, moderation, etc.)

Domains

Are we really doing what’s written in our Domain description? Check actual progress, behavior and success by looking at the Evaluation criteria in the Domain description. Add new evaluation criteria through every review, to make it easier to review it again and again.

Agreements

Are we actually doing what we agreed to and does this have the intended effect in regards to the Driver behind the Agreement? Did we actually solve or address the problem or opportunity described in the driver?