Editable Templates, Checklists & Examples Pack

Overview

Save time and start consistent practice fast. This pack contains editable, copy-ready templates your team can adopt and adapt for diagnostics, decisions, experiments, audits, onboarding, and recurring huddles. Each template comes with a short purpose statement, a suggested minimum adoption checklist, and a sample filled example to illustrate expected quality.

What's included

• Decision Record — lightweight template to capture context, options, rationale, decision, owner, and review date. Use for important operational and product choices.
• Experiment Log — hypothesis, design, metrics, results, and learning. Ideal for tests, process experiments, and small pilots.
• Audit Template — structured questions, evidence, findings, risk rating, owner actions, and verification. Use for safety, quality, and compliance snapshots.
• 30/60/90 Sprint Plan — focused short-term plan for onboarding, role transitions, or tactical improvement work.
• Onboarding Checklist — role-specific starter checklist to reduce first-90-day friction and preserve institutional context.
• KPI Huddle Agenda — agenda, data needs, RACI, improvement backlog, and short-term actions to make metric reviews productive.
• Sample Filled Experiment & Audit — two completed examples showing expected level of detail and how to record outcomes and next steps.

File formats and how to use

The pack is provided as editable files so teams can copy and tailor them. Suggested formats include DOCX/XLSX for local editing and PDF samples for read-only reference. After copying into your Hunger Engine, assign a local owner, record a version entry, and link the template into relevant team or domain pages.

How to adopt these templates (quick-start)

1. Pick one template that maps to an immediate need (e.g., Decision Record for a pending choice).
2. Assign a local owner to adapt language, fields, and required evidence to your context.
3. Run a single real use with the template and capture lessons in the Decision Record or Experiment Log.
4. Update the template based on the lesson and record a new version and owner.
5. Publish the adapted template inside your domain so teams can copy and use it, and schedule a periodic review (e.g., quarterly).

Practical guidance for adaptation

• Keep required fields minimal at first. Add optional fields that teams can choose to use.
• Localize language to match role names, local processes, and regulatory requirements.
• Attach short examples or a two-line help tip for each key field to reduce confusion.
• Designate an owner for each template and a cadence for review and retirement.

Ownership, versioning & lifecycle

Templates are living artifacts, not static checklists. For each template, capture these metadata fields when you create your copy:

• Owner (person or role)
• Version number and date
• Purpose and scope (where and when to use)
• Last-used example link
• Review cadence

Common mistakes to avoid

• Making templates too rigid—templates should guide, not enforce a single process across every context.
• Leaving templates orphaned—assign a clear owner and review schedule.
• Starting from blank—use the included filled examples to set expectations for quality and reduce onboarding friction.

Suggested roles and responsibilities

• Template Owner — keeps the template current and available.
• Local Adopter — person who customizes the template for a team or site.
• Reviewer — periodically checks that the template still meets needs and regulatory or operational constraints.

Examples of use

Decision Record — capture why a change to supplier selection was made and when to revisit it. Experiment Log — document a line change experiment with clear success metrics so the team can learn from results. KPI Huddle Agenda — convert monthly metric meetings into short, action-focused reviews that feed the improvement backlog.

Next steps and ways to extend this pack

• Convert high-value templates to interactive forms so teams can save submissions and build an organizational history of decisions and experiments.
• Create domain-linked versions (e.g., Safety Audit Collection) that inherit organization or site standards and allow local tailoring.
• Collect anonymized metadata from template use (frequency, owners, outcomes) to discover adoption gaps and improvement opportunities.

Where this pack fits in the Organizational Intelligence domain

This pack is a practical toolbox to accelerate good practice, preserve lessons, and reduce friction when teams try to capture knowledge. Treat these templates as starting points: adapt them, attach owners, and let usage drive future improvements.

Download & licensing

Use and adapt these templates freely within your organization. When copying into your domain, include the template metadata described above so templates remain traceable and maintainable.