I was first introduced to the concept of design patterns when working as a software developer. Design patterns, or simply ‘patterns’, are used to describe common solutions to common problems. Collections of patterns are called pattern languages.

The term ‘Pattern Language’ was coined in the 70’s by architect Christopher Alexander. His book 1977 book “A Pattern Language: Towns, Buildings, Construction” outlined 253 patterns that could be used to solve architectural design problems at any scale, from laying out a town to the placement of doorknobs. It was intended for use by non-experts, simplifying the otherwise complex process of construction.

Recently, the City of Calgary and the United Way began a long term process aimed at poverty reduction. It got me thinking: what do we know about reducing poverty? While much has been said about the millions leaving poverty in the developing economies of China, India and Brazil, here at home it remains a persistent problem.

Is it possible to create a pattern language for poverty reduction? Poverty is a complex phenomenon that might benefit from some simplification. But while the problem is readily identified, given is persistence can we be confident solutions even exist? It may be that no single solution exists to fix poverty, but a range of strategies and techniques, at different scales, might lead to incremental progress. This seems well suited to a pattern approach.

The following are a few random examples of what these patterns might look like:

Be Interested, Not Interesting
Problem: Humans spend a lot of time worrying about whether they fit in to the group.
Solution: Ask questions and be an active listener.

Teach A Man To Fish
Problem: People do not have skills to find employment that gives them sufficient income.
Solution: Provide access to skill development and education.

Progressively Tax Consumption
Problem: We tax income, which diminishes the incentive to earn it.
Solution: Tax consumption progressively. The more you consume, the more tax you pay.

At some point I’ll try throwing together a quick web app that will keep these patterns organized, allowing the language to incrementally grow.