Collection

Make the artifact easier to inspect, challenge and reuse

Turn documents, product hypotheses, external signals, AI reflection, parked ideas, visuals and test plans into reviewable artifacts with a next decision.

Explore in any order.

What’s included

2 checklists · 1 heuristic · 1 pattern · 3 protocols · 1 template

Narrow your search

8 ideas

Checklist

Review a document in layers

A single “proofread” pass asks your attention to catch structure, facts, language and formatting at once. Review in layers so each pass has one job and tools support rather than replace judgment.

Read the idea
Protocol

Map opportunities to solutions and tests

Jumping from a broad problem to a favourite feature hides the choices in between. Separate desired outcome, observed opportunities, candidate solutions and tests so the team can change one layer without pretending the whole tree is proven.

Read the idea
Checklist

Build a bounded industry radar

Staying informed should reduce surprise, not consume the day. Choose a small set of sources tied to decisions you actually make, review them on a cadence, and capture only signals that could change a plan.

Read the idea
Template

Park an idea with a return condition

Capturing an idea is useful only if it stops interrupting current work without creating an eternal idea graveyard. Record just enough context and define when it deserves another look.

Read the idea
Protocol

Structure dense writing for fast navigation

A dense document becomes easier to use when sections follow the reader’s task and each visual form earns its place. Headings, tables and diagrams are navigation tools, not decoration.

Read the idea
Heuristic

Follow an abstract point with a transferable example

An example earns space when it makes the mechanism or boundary visible. Choose one that shows how the idea works, then make clear which part transfers and which part belongs only to the example.

Read the idea
Protocol

Design test coverage from risk and boundaries

Coverage is not the number of test cases. Identify critical behaviors, partitions, boundaries and failure modes, then choose the smallest set of tests that can expose materially different defects.

Read the idea
Pattern

Keep one inbox for unassigned work

Loose tasks become expensive when each one invents its own storage place. Keep one small inbox for work that has no project yet, then review it often enough that the inbox remains a capture point rather than a second backlog nobody trusts.

Read the idea