playbook.crastinating.pro
Frameworks · Rubrics · Defaults

The Decision Playbook

Most engineering decisions aren't novel — they're variants of forks every roadmap eventually hits. Build vs. buy. One-way vs. two-way. Strangler vs. big-bang. The Playbook is an opinionated set of rubrics for those forks: the criteria that actually decide it, the red flags that mean you're solving the wrong problem, and a default pick when the meeting is going in circles.

Frameworks
6
Categories
6
Avg. read
4 min
Linked briefs
3

Framing

1 playbook
Framing3 criteria

Two-way vs. one-way door

Two-way

Before any other decision criteria — figure out if this is a door you can walk back through.

Default pick
When in doubt, treat it as two-way and ship behind a flag. Most decisions are more reversible than the meeting suggests; the ones that aren't are usually obvious.
3 min read
  • framing
  • reversibility
  • risk

Build vs. buy

1 playbook
Two-way

When the next 'we'll just write a small internal tool' is sitting on the agenda — a four-question filter.

Default pick
If it's not your moat, buy. Especially for security, identity, billing, and observability — the cost of getting these subtly wrong dwarfs the price of the vendor.
4 min read
  • build vs buy
  • tooling
  • cost

Lifecycle

1 playbook
Lifecycle4 criteria

Deprecating an internal API

One-way

Killing a piece of internal surface area — when, how loud, and what the deadline actually means.

Default pick
Pick the deadline first, then work backwards. A deprecation without a date is a backlog item; a deprecation with a date is a project. Default cadence: announce → 8 weeks soft warnings → 4 weeks hard warnings → cut.
4 min read
  • deprecation
  • api design
  • lifecycle

Scope

1 playbook
One-way

Three honest shapes for any migration. The wrong shape is the most common failure mode.

Default pick
Strangler-fig migration. Stand up the new thing alongside the old, route traffic by shape, and shrink the old one's footprint until it has zero callers. Pick a real end-of-life date the day you start.
5 min read
  • migration
  • scope
  • risk

Process

1 playbook
Process4 criteria

Setting a tech-debt budget

Two-way

How much of next quarter to spend on debt — without writing a manifesto, and without backsliding the quarter after.

Default pick
20% of engineer-weeks for the next two quarters, ring-fenced and reported on like feature work. Pick the top three items. Stop adding new ones until the three are done.
4 min read
  • tech debt
  • planning
  • engineering management

People

1 playbook
Two-way

A piece of work has shown up. Three honest shapes for staffing it — and a default that's right more often than you'd think.

Default pick
If the work is bounded and the skill is non-core, contract. If the work is unbounded or the skill is core, hire. Stretch the existing team when there's an internal candidate who'd grow — and put real coaching around them.
4 min read
  • hiring
  • staffing
  • engineering management

Got a fork that isn't here?

The Playbook is opinionated by design — we'd rather publish a strong default than a checklist. If your team has a fork we haven't covered, run it through crastinating and we'll consider it for the next release.