slide-deck.io

Tech Spec / RFC

Engineering design document for proposing and reviewing significant technical changes.

A complete 10-slide sample deck. The companies and figures in it are invented — slide-deck.io writes the same structure around your own topic, your brand colours and your data, and exports it as an editable .pptx.

Use this template
  1. RFC 214 — Event-Sourced Order State
    1

    This is an RFC walkthrough, not a decision meeting. The decision happens in the doc comments; this session exists so people read it.

  2. The order table is the bottleneck and the bug source
    2

    Lead with the incident count. Everyone in this room has been paged for one of those nine.

  3. Proposal: orders become a projection of an append-only event log
    3

    The read model keeping its shape is what makes this affordable. Read callers are untouched; only the seven writers move.

  4. How a write flows through the new path
    4

    The expected-version check is where the race conditions go away. Draw it on the whiteboard if the diagram is not enough.

  5. Three options considered
    5

    Be honest that locking is far cheaper. The argument for the expensive option is history and throughput, not correctness alone.

  6. What we gain and what we give up
    6

    The eventual-consistency cost is real and it will surprise someone in support tooling. Name it now rather than in the incident review.

  7. Projected write throughput at each stage
    7

    Phase 1 is slower than today. Say so plainly — dual write costs us throughput for about six weeks, and that is the price of a safe cutover.

  8. Migration in three phases, reversible until the last one
    8

    The config-flag rollback is the sentence that gets this approved. Nothing is irreversible until phase 3.

  9. Open questions I need answers to
    9

    These four are genuinely open. If nobody answers them in the doc this week, they get decided by whoever writes the code first.

  10. What happens next
    10

    End with the deadline. An RFC without a comment deadline never gets decided.

Build this deck around your own material.

Get started free