thirty one patterns

Thirty One Patterns: 31 Creative Designs, Ideas, and Inspiration

By Joseph King
AD

Thirty one patterns is more than a catchy phrase; it describes a practical pattern language for people who solve recurring problems in software, product design, operations, and teamwork. Instead of treating each challenge as entirely new, the thirty one patterns approach asks you to recognize familiar forces, name them, and apply a proven response with appropriate adjustments.

Whether you spell it thirty one patterns or 31 patterns, the value is the same: a compact library of ideas that is broad enough to cover common situations and small enough to remember under pressure. This article explains where the collection comes from, what makes each pattern useful, and how to apply the thirty one patterns without turning them into rigid rules.

The Foundations of Thirty One Patterns

Patterns are not templates that remove thinking. They are documented solutions that describe a context, a problem, the forces that pull in different directions, and a solution that resolves those forces well enough to repeat. The thirty one patterns concept builds on that tradition by grouping a focused set of recurring solutions into one accessible vocabulary.

AD
My Pretties
My Pretties
a poster with different patterns and colors on it
a poster with different patterns and colors on it
an image of different patterns and colors in the same color scheme, including pink, green,
an image of different patterns and colors in the same color scheme, including pink, green,

When a team shares this vocabulary, conversations become shorter and more precise. Someone can say, "This is a circuit breaker situation," or "We need a strangler fig migration," and the group immediately understands the shape of the problem and the trade-offs involved. That shared language is often more valuable than any single pattern in the set.

Where the Thirty One Patterns Come From

The roots of pattern thinking reach back to architecture and urban design, where Christopher Alexander and others described recurring solutions in the built environment. Software engineering later adapted the idea through design patterns, enterprise integration patterns, and architectural patterns. User experience, agile delivery, and organizational design added their own pattern catalogs.

a collage of different colors and patterns with the words wylong on it
a collage of different colors and patterns with the words wylong on it
Sierra Stripe Pattern by Thirty-One Gifts Thirty One Raised Embroidery Patterns, Aztec Pattern Names, Thirty One Raised Embroidery Designs, Vibrant Tumbler Patterns, Ornament Ethnic Stripes Vertical Coral, Thirty One Party Graphics, Thirty One Gifts Fabric, Tribal Stripes, Southwest Stripe
Sierra Stripe Pattern by Thirty-One Gifts Thirty One Raised Embroidery Patterns, Aztec Pattern Names, Thirty One Raised Embroidery Designs, Vibrant Tumbler Patterns, Ornament Ethnic Stripes Vertical Coral, Thirty One Party Graphics, Thirty One Gifts Fabric, Tribal Stripes, Southwest Stripe
many different patterns and colors are featured in this page for the quilter's guide
many different patterns and colors are featured in this page for the quilter's guide

The thirty one patterns collection draws from these traditions without being owned by any single one. Some patterns focus on code structure, such as factories, observers, and repositories. Others address system reliability, such as circuit breakers and bulkheads. Still others deal with human coordination, such as retrospectives, working agreements, and decision logs. The result is a cross-disciplinary toolkit rather than a narrow technical checklist.

Core Principles Behind Each Pattern

Every effective pattern respects context. A solution that works in a small startup may fail in a regulated enterprise, and a pattern that simplifies one system can add accidental complexity to another. The thirty one patterns are meant to be selected, combined, and adapted, not copied blindly from a catalog.

AD

Each pattern also carries consequences. Speed may improve while flexibility drops, or reliability may increase while latency grows. Mature practitioners make those trade-offs visible before committing. They document why a pattern was chosen, what alternatives were rejected, and what signals would indicate that the pattern should be replaced later.

Fabulous Floral Thirty One Fabric Ideas, Thirty One Bag Ideas, Thirty One Fabric Patterns, Thirty One Island Damask Pattern, Thirty One New Day Tote Bag Pattern, 31 Bags Ideas Organizations, Thirty One Woodblock Floral, Thirty One Get Creative Bags, Thirty One Gifts Fabric
Fabulous Floral Thirty One Fabric Ideas, Thirty One Bag Ideas, Thirty One Fabric Patterns, Thirty One Island Damask Pattern, Thirty One New Day Tote Bag Pattern, 31 Bags Ideas Organizations, Thirty One Woodblock Floral, Thirty One Get Creative Bags, Thirty One Gifts Fabric
a blue and white polka dot pattern with the words navy lotsa dots
a blue and white polka dot pattern with the words navy lotsa dots
the new patterns for spring are here
the new patterns for spring are here
the fall 2020 thirty - one prints
the fall 2020 thirty - one prints
a poster with the words which is your new favorite print? in different colors and patterns
a poster with the words which is your new favorite print? in different colors and patterns
Thirty One Canvas Boat Tote, Thirty One Navy Blue Tote, Thirty One Fabric Color Chart, Thirty-one Utility Tote Options, Brush Strokes Pattern, Thirty One Thermal Cinch Sack, 31 Totes Catalog, Utility Tote, Thirty One Ultimate Beach Mat
Thirty One Canvas Boat Tote, Thirty One Navy Blue Tote, Thirty One Fabric Color Chart, Thirty-one Utility Tote Options, Brush Strokes Pattern, Thirty One Thermal Cinch Sack, 31 Totes Catalog, Utility Tote, Thirty One Ultimate Beach Mat

Applying Thirty One Patterns in Real Work

The best way to use thirty one patterns is to start with symptoms, not solutions. If releases are painful, if incidents repeat, if teams argue about priorities, or if a codebase resists change, those symptoms point toward specific pattern categories. Diagnosis comes before prescription, even when the pattern names sound appealing.

After identifying the problem, map the forces at play: time, cost, risk, team skill, regulatory constraints, customer expectations, and existing architecture. Then review the thirty one patterns for candidates that address those forces. Choose the smallest pattern that creates meaningful improvement, and plan to revisit the decision after real-world feedback.

AD

Patterns for Software and System Design

In software, thirty one patterns often include structural and behavioral solutions such as adapter, facade, observer, strategy, repository, and dependency injection. Reliability patterns like circuit breaker, retry with backoff, bulkhead, and timeout prevent small failures from becoming cascading outages. Data and integration patterns such as CQRS, event sourcing, saga, and outbox handle consistency across distributed systems.

a poster with some different types of items in the shape of letters and numbers on it
a poster with some different types of items in the shape of letters and numbers on it
the fall 2013 prints are shown in different colors
the fall 2013 prints are shown in different colors
Thirty One fabric pattern wallet.
Thirty One fabric pattern wallet.
Thirty-One Gifts' Spring'14 pattern collections: Paradise Pop, Bold Bloom, Citrus Medallion, Plum Awesome Blossom Thirty One Bag Ideas, Thirty One Bags And Accessories, Thirty One Bags And Purses, 31 Bags Ideas Organizations, Thirty One Get Creative Tote, Thirty One New Releases, Colorful Thirty-one Bags, Thirty-one Patterned Bag, Budget-friendly Thirty One Products
Thirty-One Gifts' Spring'14 pattern collections: Paradise Pop, Bold Bloom, Citrus Medallion, Plum Awesome Blossom Thirty One Bag Ideas, Thirty One Bags And Accessories, Thirty One Bags And Purses, 31 Bags Ideas Organizations, Thirty One Get Creative Tote, Thirty One New Releases, Colorful Thirty-one Bags, Thirty-one Patterned Bag, Budget-friendly Thirty One Products

These patterns become more powerful when combined. A service might use a bulkhead to isolate resources, a circuit breaker to stop calls to a failing dependency, and an outbox to publish events reliably. The goal is not to use as many patterns as possible, but to compose a few that reinforce one another and keep the system understandable.

Patterns for Collaboration and Productivity

Human systems have patterns too. Retrospectives, daily coordination meetings, working agreements, pairing, mob programming, and decision logs are all repeatable responses to common team frictions. They create transparency, reduce ambiguity, and help groups learn faster than they would through ad hoc communication alone.

AD

Productivity patterns such as timeboxing, kanban limits, definition of done, and async updates work best when they are adapted to the team's actual workflow. A pattern that feels ceremonial should be simplified or retired. A pattern that exposes problems is doing its job, even if the first few weeks feel uncomfortable. Over time, the thirty one patterns become less of a checklist and more of a shared operating system for getting meaningful work done.

If you want to make thirty one patterns useful rather than theoretical, start with one recurring frustration and one candidate pattern. Run a small experiment, observe what changes, and keep the parts that reduce friction. Share what you learn with your team, because pattern languages grow stronger through use, critique, and refinement. The next problem you face may already have a pattern waiting for you; your job is to recognize it, adapt it, and pass the insight forward.

AD