The Antimatter Pattern – Update

Last year I published a post “The Antimatter Pattern” which provided an Alexandrian-style pattern setting out how the Antimatter Principle provides a solution to one of the most intractable problems in modern business:

Problem: How to create a climate, context, or situation in which folks will want to change their behaviours to the benefit of all.

Or, how to set about fixing the pandemic of workforce disengagement and disinterest so widely reported in the past few years.

I just updated the original StartingTheWheelOfChange pattern (pdf, version 1.1a) which appeared in that post to a newer version: StartingTheWheelOfChange pattern (pdf, version 1.2a).

– Bob

The Antimatter Pattern


Some fifteen years ago now, patterns seemed like they might become a widely adopted way of capturing and sharing knowledge and know-how. It also seems like they never really caught on in the software development field.

Personally, I still find them useful for organising and recording my own thoughts, and, occasionally, for sharing those thoughts with others. This post presents the StartingTheWheelOfChange pattern, which proposes the Antimatter Principle as a solution to one of businesses’ most widespread and seemingly intractable of problems:

Problem: How to create a climate, context, or situation in which folks will want to change their behaviours to the benefit of all.

What Is A Pattern?

A pattern is the formalization of a problem/solution pair, potentially useful in making design decisions. The purpose of a pattern is to codify existing design knowledge/experience so that folks can avoid constantly re-inventing the wheel. Also, by naming such patterns, people can more easily reference and share them. The term pattern was first popularised by the architect Christopher Alexander working in the fields of e.g. building design and town planning.

Some folks refer to collections of patterns – relating to a common domain or discipline – as Pattern Languages. My interest these days is primarily in Pattern Languages for business management and organisational improvement.

My Pattern Form

Most of the patterns I’ve written over the years have shared a common form. You can see an example of this form in the StartingTheWheelOfChange pattern which is the subject of this post. Briefly, this form starts with a header, and then has the following various sections below that:

  • Context: The context(s) in which the pattern might be relevant.
  • Problem: The problem this pattern purport to solve.
  • Forces: The forces at play in the problem domain described by the problem and context sections. Sometimes also known as the trade-offs.
  • Solution: The solution which proposes to solve the stated problem, in the stated context, and resolving the stated forces.
  • Examples: One or more practical examples taken from the author(s)’ personal experience in applying the solution to real-world instances of the stated problem.

Starting The Wheel of Change

The StartingTheWheelOfChange pattern suggests a solution to the question of “How to encourage widespread learning and improvement in a community such as a for-profit organisation. The full pattern is presented as a pdf.

– Bob

%d bloggers like this: