Workflow: Decision Log

Every decision you make today
will be questioned tomorrow.
Will you have the answer?

Decisions don't fail because of bad judgment. They fail because 3 months later, nobody remembers the context, the alternatives, or the constraints that shaped them.

Start Your Decision Log See the workflow ▸

The Decay Problem

Context has a half-life

The moment a decision is made, its context starts decaying. In 6 months, the "what" survives but the "why" is gone.

Week 0
Crystal clear

You decide to defer the payment migration. Context is fresh. Everyone understands why.

Context
100%
Week 4
Details fade

You remember the decision but the specific constraints that drove it are getting fuzzy.

Context
75%
Week 12
Context lost

Someone asks 'why did we defer this?' — you remember the conclusion but not the reasoning.

Context
45%
Week 24
Decision questioned

New leadership asks to revisit. Without context, the same debate replays from scratch.

Context
20%

Knovya stops the decay at Week 0

The Knovya Way

Anatomy of a complete decision

A decision without context is just an opinion with a timestamp. Knovya captures the full anatomy — so decisions explain themselves months later.

Context

What situation triggered this decision? What was known at the time?

Alternatives Considered

What other paths were evaluated? Why were they rejected?

The Decision

What was decided, by whom, and with what confidence level?

Linked Evidence

What notes, data, or past experiences support this decision?

Expected Outcome

What should happen if this decision is right? When should it be revisited?

Decision: Defer Payment Migration
decisionp1sprint-18high confidence
Context
API team announced a 2-week freeze starting April 1. Payment migration depends on 3 API endpoints.
Alternatives Considered
Option A: Run in parallel (rejected — Sprint 14 showed this causes 3-day blocks) Option B: Reduce scope (rejected — migration is atomic, can't split)
The Decision
Defer payment migration to Sprint 20 as standalone goal. Decided by product + engineering leads. Confidence: High.
Linked Evidence
→ Sprint 14 Retro (87% similarity) → API Freeze Policy document → Q2 Roadmap Review
Expected Outcome
Sprint 20 should complete migration in one clean cycle. Revisit if API freeze policy changes or Sprint 19 frees unexpected capacity.

Temporal Memory

"What did we believe in February?"

Decisions evolve. Beliefs change. Knovya lets you time-travel through your knowledge — see what you knew, when you knew it, and what has changed since.

  1. Jan 2026 #1
    Triggering event
    Competitor launches free tier
    What we believed
    Our $29/mo pricing is competitive
    Related
    4
    Confidence
  2. Feb 2026 #2
    Triggering event
    User research: price sensitivity rising
    What we believed
    May need to reconsider pricing band
    Related
    7
    Confidence
  3. Mar 2026 #3
    Triggering event
    Decision: test $19/mo
    What we believed
    $19 captures 40% more market
    Related
    3
    Confidence
  4. Apr 2026 #4
    Triggering event
    Test results: 52% conversion lift
    What we believed
    $19 is the right price point
    Related
    5
    Confidence
  5. May 2026 #5
    Triggering event
    Board review: approve $19 permanent
    What we believed
    Pricing settled. $19/mo confirmed
    Related
    2
    Confidence
  6. Jun 2026 #6
    Triggering event
    Competitor matches at $19
    What we believed
    Need differentiation beyond price
    Related
    6
    Confidence

Each snapshot is its own version in knovya_history. Ask the AI "what did we believe about pricing in March?" and it answers from the version index — not from a guess.

Connected Decisions

Decisions don't exist in isolation

Every decision connects to other decisions, evidence notes, and outcomes. Knovya builds this graph automatically — so you see the full picture before deciding.

Defer Payment Migration
Sprint 14 Retro
API Freeze Policy
Q2 Roadmap Review
Sprint 20 Plan
Checkout Redesign v2
Decision Evidence Depends on Blocked by

AI Recall

Ask anything about
your decisions

Your AI reads your decision log. It doesn't just search — it understands the relationships, evolution, and patterns in your decisions.

Every example conversation below is a real prompt + answer pattern Knovya produces against a healthy decision log. The graph + history + Experience Envelope do the heavy lifting; the AI just narrates.

You

"Why did we defer the payment migration?"

Knovya AI
The payment migration was deferred in Sprint 18 (March 12) because it requires API endpoints that are affected by the API team's freeze. Sprint 14's retro showed that running payment work during API restrictions caused a 3-day block. 📎 Decision: Defer Payment Migration 📎 Sprint 14 Retro 📎 API Freeze Policy
You

"What pricing decisions have we made this year?"

Knovya AI
You've had 4 pricing-related decisions in 2026: 1. Jan — Maintained $29/mo (competitor launched free tier) 2. Mar — Decided to test $19/mo based on user research 3. Apr — Test showed 52% conversion lift at $19 4. May — Board approved $19 permanently Note: In June, your competitor matched $19 — you noted the need for differentiation beyond price. 📎 6 linked pricing notes
You

"What should I consider before making the auth decision?"

Knovya AI
Based on your past decisions, here are patterns I'd flag: ⚠️ Sprint 14 showed that auth + payment work in the same cycle causes blocks ✅ Staggered rollouts have worked well (Q2 launch precedent) 📋 3 past auth-related decisions exist — the most relevant is your OAuth2 migration from November Would you like me to create a decision note pre-filled with this context?

Your decisions deserve
permanent context.

Never lose the "why" behind the "what" again.

Start Your Decision Log →