Reusable Patterns & Anti‑Patterns

Apply proven approaches and skip familiar mistakes: a compact library of repeatable patterns, ready templates, and explicit anti‑patterns you can adapt to your team, process, or project.

Why this matters

Discovery and innovation learn faster when teams reuse what works and avoid what doesn’t. This resource collects concise, actionable patterns and their matching anti‑patterns so you can shorten experiments, reduce rework, and make clearer decisions when designing processes, products, or research.

What you'll understand and be able to do

After exploring this collection you will be able to:

• Recognize repeatable tactics that map to common hungers—e.g., rapid prototyping, customer interviews, audit routines, handover checklists.
• Apply compact templates and playbook steps to a local problem with minimal translation.
• Identify anti‑patterns that often cause delays, safety issues, or lost learning and consciously avoid them.
• Adapt, combine, or extend patterns into your own team’s Hunger Engine or toolkit.

Who benefits

This resource helps practitioners and improvers across roles and sectors—small business owners, operations managers, service teams, manufacturing supervisors, researchers, nonprofit leaders, educators, and product teams—who need repeatable, low‑friction approaches they can trust and tailor.

Practical examples

Use cases include:

• A maintenance supervisor using a standardized troubleshooting pattern plus a local checklist to cut mean time to repair.
• A restaurant manager adopting a service recovery pattern and avoiding an anti‑pattern that delays refunds and harms retention.
• An R&D team applying a hypothesis‑driven experiment pattern and logging outcomes so future teams don’t repeat failed setups.
• A nonprofit creating a donor‑engagement playbook and noting anti‑patterns that reduce trust or transparency.

How to use these patterns in your organization

Start by scanning the Reusable Patterns & Anti‑Patterns Index to find patterns relevant to your hunger. Read the matching sector compendium entries for context and trade‑offs. Copy or adapt a concise template into your team’s working documents, and record what you change so the pattern evolves with your experience.

If you operate within a Hunger Engine, consider acquiring or copying a pattern collection as a starting toolkit and then tailoring it to local risks, standards, and technologies—converting static checklists into interactive forms or saved audits when you need to collect observations or track improvement over time.