At The Toolworks we apply proven business and software patterns to help solve problems.

The leading architectural thinker Christopher Alexander described a language for architectural patterns in the 1970's. These are in effect a set of rules that can be drawn on and applied to building design problems. The concept has since evolved far beyond architecture taking in software development and business design.

Patterns are often defined using a common structure or ‘pattern language’ which describes the problem, its context and a potential solution:

• Name: A suitably descriptive name for the pattern
• Context: Where the pattern might be used
• Bigger patterns: Other patterns that might be need to be considered first
• Problem: A description of the problem that pattern aimed to solve
• Solution: A description of the solution used to solve the problem in this context
• Smaller patterns: Other patterns that might be considered next

We have described many of our experiences in business consulting, software development and design as patterns and in our assignments we always look to see if aspects of the specific problem have been described before.

We have created or sourced patterns in many areas including:

And are actively creating and sourcing new patterns.