Organizational Intelligence Starter Kit

Organizational Intelligence Starter Kit — Quick Start

This starter kit gives a team a repeatable, low-friction way to begin improving learning, decisions, and knowledge flow. It includes six ready-to-use artifacts with field-level guidance and a simple two‑week plan so you can run an initial cycle in under two weeks.

Why this kit matters

Many improvement efforts stall because teams lack a clear, small, repeatable workflow and searchable artifacts. This kit focuses on the smallest useful set of templates that, used together, capture learning, make decisions visible, measure outcome, and create momentum.

What’s included

1. One‑page Diagnostic Checklist — Knowledge & Decision Health

   Purpose: Rapidly surface gaps in knowledge, decision practices, onboarding, and feedback loops.

   Suggested fields / items (fillable):

   • Team / Unit
   • Date
   • Is there a clear owner for each recurring decision? (Yes/No)
   • Do we record the rationale for major decisions? (Yes/No)
   • Are critical processes documented and accessible? (Yes/No)
   • Are recent experiments and outcomes logged? (Yes/No)
   • Onboarding time for typical role (days)
   • Score overall knowledge health (1–5)
   • Top 3 knowledge risks or gaps (text)
2. 30/60/90 Sprint Plan Template

   Purpose: Structure immediate improvement work into short, reviewable phases.

   Suggested fields:

   • Objective (30/60/90)
   • Owner
   • Key actions
   • Success metrics
   • Dependencies / blockers
   • Review date

   Use this to align short experiments and operational fixes with a simple metric-based definition of success.

3. Lightweight KPI Huddle Agenda

   Purpose: Run fast, regular check-ins that connect metrics to actions and experiments.

   Suggested agenda (15–30 minutes):

   • Quick metric snapshot (owner, trend, one-sentence reason)
   • One risk or blocker
   • One experiment or improvement in flight
   • Action owners and next check-in
4. Decision Record Template

   Purpose: Make decisions visible, capture rationale, and enable review.

   Suggested fields:

   • Decision ID
   • Title
   • Date
   • Owner / approver
   • Context / problem statement
   • Options considered
   • Chosen option
   • Rationale / evidence
   • Assumptions
   • Risks & mitigations
   • Review / revisit date
   • Outcome metrics to track
5. Experiment Logging Card

   Purpose: Run small, time‑boxed tests and capture what you learn.

   Suggested fields:

   • Experiment title
   • Hypothesis (if X then Y because...)
   • Primary metric
   • Success criteria
   • Owner
   • Start date / end date
   • Steps / design
   • Results
   • Learnings
   • Next steps (scale / abandon / iterate)
6. Starter Taxonomy Checklist

   Purpose: Keep artifacts discoverable and reusable.

   Checklist items / conventions:

   • Top-level categories: Decisions, Experiments, Playbooks, Metrics, People, Tools
   • Naming convention: YYYY-MM-DD___
   • Required metadata: owner, created date, tags, review date
   • Storage location(s): canonical folder or repo + link
   • Archival policy: review & archive cadence

Two‑week quick‑start plan (run an initial cycle)

Goal: Produce one decision record, one experiment log, and a baseline diagnostic plus a 30/60/90 plan.

1. Day 1 — Kickoff (60–90 minutes)
   • Run the one‑page diagnostic together and agree on top knowledge/decision gaps.
   • Select one tangible problem to address in a 30/60/90 sprint.
2. Days 2–4 — Draft & Assign
   • Create a Decision Record for the selected change (capture rationale and measures).
   • Create a 30/60/90 plan with owners and success metrics.
3. Days 5–8 — Run an Experiment
   • Design and start a small experiment. Log it with the Experiment Card.
   • Use KPI Huddle agenda to check progress mid‑experiment.
4. Days 9–12 — Evaluate & Adjust
   • Capture results and learnings. Update the decision record if needed.
   • Refine 30/60/90 plan according to real data.
5. Day 13–14 — Share & Standardize
   • Share findings in a short team review and add artifacts to the canonical taxonomy.
   • Schedule the first recurring KPI Huddle and a follow-up review.

Suggested KPIs to track early

• Time to onboard a new person into this workflow (days)
• Percent of major decisions with recorded decision records
• Experiment cycle time (days from hypothesis to result)
• Number of artifacts reviewed or updated in the last 90 days
• Knowledge health score (from diagnostic)

Common pitfalls & how to avoid them

• Avoid turning artifacts into busywork: require only the fields that directly support action and learning.
• Don’t assume tech solves culture: pair templates with a short meeting rhythm (KPI huddle + experiment review).
• Resist one‑size-fits-all templates: tailor the included fields to your team’s cadence and domain.
• Prevent orphaned docs: assign ownership and a review date for every artifact.

How to tailor and scale

Start small and iterate. Use the diagnostic score to prioritize where to apply the kit. When a pattern emerges that multiple teams need, consider packaging team‑level templates into a shared domain or collection that other teams can copy and adapt.

Examples (short)

Decision Record — Example fields filled:

Title: Standardize weekly KPI huddle format
Owner: Product Ops
Context: Huddles vary by team; no consistent actions recorded.
Chosen option: Adopt the lightweight KPI huddle agenda and require one recorded experiment per sprint.
Review date: 2026-10-15
Outcome metric: Percent of huddles with recorded actions (target 90%)

Next steps for implementers

• Copy the templates into your team’s doc repo and enforce simple ownership and review dates.
• Try the two‑week quick start and capture feedback from participants.
• Iterate: remove fields people don’t use and add a field only when it helps decision making or onboarding.

Platform & capability notes

This HTML toolkit describes the templates and field-level structure. For immediate operational value, consider converting the Decision Record and Experiment Card into interactive forms so teams can save submissions, search, and build dashboards. See Capability Enhancement notes for practical suggestions.