Reusable Patterns & Anti‑Patterns Index

Purpose

This index collects repeatable discovery and innovation patterns along with common anti‑patterns and recommended mitigations. It helps teams find an approach, understand the context and trade‑offs, adapt the pattern to local constraints, and measure whether the adaptation works. Use this index to accelerate experimentation, avoid repeated mistakes, and document what actually worked.

What you will find here

• Practical pattern entries: name, intent, problem solved, context, steps, variants, example, and measurable outcomes.
• Anti‑pattern entries: observable symptoms, likely underlying causes, remediations, and prevention notes.
• Quick links to playbooks, templates, checklists, and experiments that implement each pattern.
• Guidance for adapting patterns safely and testing them with lightweight experiments.

How entries are structured (standard template)

Every pattern or anti‑pattern follows a consistent structure so readers can compare, adapt, and reuse reliably.

Pattern Entry Template

• Name: Concise label teams can reference.
• Intent / When to use it: Desired outcome and trigger conditions.
• Problem it solves: The specific need, waste, or uncertainty addressed.
• Context & constraints: When this pattern is likely to succeed or fail.
• Steps (practical): Clear, actionable steps a team can follow.
• Variants / shortcuts: Lightweight versions, scaling notes.
• Example: A short real or realistic example showing application and results.
• Success metrics: Suggested measurements to know if the pattern worked.
• Trade‑offs & risks: Known compromises or failure modes.
• Adaptation notes: How to tailor to local systems, stakeholders, or regulations.
• Related playbooks / templates: Links to deeper tools or interactive forms.
• Owner / maintainers: Who is responsible for the entry and updates.

Anti‑Pattern Entry Template

• Name / label
• Symptoms: Observable signs you may be falling into this trap.
• Underlying causes: Common root reasons.
• Why it hurts: Typical negative consequences.
• Immediate remediations: Steps to stop harm quickly.
• Longer term fixes / prevention: Process or governance changes to avoid recurrence.
• Related patterns to prefer: Safer alternatives or complementary practices.

Quickstart: find, adapt, test

1. Find: Search the index for a pattern matching your intent and constraints.
2. Read its context & trade‑offs: Confirm the pattern applies to your environment.
3. Adapt: Use the adaptation notes to tailor steps, owners, and metrics.
4. Run a lightweight experiment: Define a simple hypothesis, measurement, timeline, and exit criteria.
5. Capture results: Record outcomes, learnings, and suggested changes back to the pattern entry.

Example entries (short)

Pattern: Opportunity Scan

Intent: Rapidly discover and prioritize low‑cost improvement opportunities in a process or product area.

Problem it solves: Teams waste time chasing low‑impact ideas because they lack a fast, shared method for scanning and prioritizing opportunities.

Steps:

1. Gather a cross‑functional 60–90 minute workshop (3–6 people).
2. Map the high‑level process or user journey on a whiteboard.
3. Timebox 15 minutes of individual idea generation (silent).
4. Cluster ideas, vote using 3 dots each on impact vs. effort, and capture top 3 candidates.
5. Define a simple experiment for the top candidate with one metric and a 2‑week trial.

Success metrics: Number of validated experiments, reduction in cycle time, customer satisfaction delta.

Adaptation notes: For regulated contexts, add a compliance checkpoint before running experiments.

Anti‑Pattern: Solution First

Symptoms: Team rushes to design a solution, skips problem framing, and uses anecdotes as evidence.

Underlying causes: Confirmation bias, schedule pressure, or incentives that reward output over learning.

Immediate remediation: Pause the work, run a 1‑hour problem framing session (who has the problem, how big is it, evidence?), and define a hypothesis to test.

Longer term fixes: Create a policy requiring documented problem statements and an experiment plan before development intake is accepted.

Related patterns: Opportunity Scan, Evidence‑First Interview.

Playbooks, templates, and links

Each pattern links to implementable playbooks or templates (checklists, experiment templates, interview scripts, data queries). Where available, link to interactive forms or worksheets teams can copy into their own domain.

Metadata and tagging recommendations

To make the index discoverable and copyable, every entry should include the following metadata:

• Tags (e.g., discovery, experiment, customer, operations, AI, research)
• Applicable roles (e.g., product manager, engineer, quality lead)
• Estimated time to run
• Estimated cost / required resources
• Risk level / regulatory sensitivity
• Related content IDs / playbook links
• Owner / steward and last updated date

Contributing and governance

Contributions should include evidence or tested examples when possible. Maintain a clear owner for each entry. Use these rules:

• Prefer documented experiments and outcomes over anecdotes.
• State trade‑offs explicitly; do not present a single case as universal.
• When adapting, record what changed and the measured result back into the entry.
• Review entries periodically (suggested cadence: 6–12 months).

Using platform capabilities (practical notes)

This index is designed to pair with platform features:

• Make pattern entries copyable so teams can acquire a pattern and tailor it in their own domain.
• Provide interactive submission and edit forms so teams can submit new patterns or experiment results.
• Link playbooks to checklists, audits, and experiment templates so teams can run and record trials directly.

Why this matters (alignment with hungers)

Well‑structured patterns help teams stop reinventing common approaches, reduce wasted effort, surface hidden trade‑offs, and move faster from problem to validated solution. Clear anti‑patterns help teams detect and stop harmful habits early.

Use to

• Accelerate discovery and experimentation.
• Onboard teams quickly with proven approaches and playbooks.
• Avoid repeated mistakes and capture organizational learning.
• Create a living library that teams can copy and tailor to their context.

At the bottom of each entry you will find "Try this" links: quick copy buttons to bring the pattern, its playbook, and experiment template into your owned domain so you can adapt and track results locally.