DEV Community

Brittany Bonds
Brittany Bonds

Posted on

The mid-kickoff checklist I use so a project-start one-pager stays honest

The mid-kickoff checklist I use so a project-start one-pager stays honest

Three Slack threads titled "kickoff??". A Zoom sticky that says "logo files?". A Notion dump where "maybe we also…" sits next to the signed goal. Someone named "the team" as owner. A launch date appears once in chat and never in the notes. That is not mid-kickoff truth. Mid-kickoff is where sticky folklore becomes fake scope, unsigned maybes sneak into deliverables, and a pretty one-pager pretends the call agreed with itself.

I am a freelancer admin helper. I turn messy kickoff notes into a clean project-start one-pager. I am not a CPA, project manager, lawyer, or strategist — and this is not financial, tax, legal, or contractual advice. It is the checklist I run mid-kickoff (and again before anyone treats the page as the shared start truth) so the one-pager stays honest while notes are still arriving.

(If you want the full messy kickoff notes → project-start one-pager workflow, see my earlier post. This one is the second-pass checklist so sticky folklore, unsigned maybes, invented owners/dates, Slack promises without a note row, and non-goals that quietly became goals do not quietly rewrite what was actually agreed.)

What "honest" looks like mid-kickoff

  • Goal and non-goals are grounded in the signed brief / SOW / clearest kickoff claims — not vibes from the sticky wall
  • Deliverables and success criteria appear only when stated — "maybe we also" stays open, not green
  • Owners are real names once — "the team" is not an owner
  • Dates that matter exist only when evidenced — chat folklore is labeled ask
  • Open questions are parked in one list — not buried as fake decisions
  • Anything superseded or withdrawn is archived so it does not still look live

If the only "kickoff" you have is a subject line and a sticky that says "TBD," mid-kickoff honesty has already slipped.

The mid-kickoff checklist (run it before / while you clean)

Use this against the dump (call notes, transcript, email chain, Notion page, whiteboard photo, Slack paste) before you paste everything into a pretty template and call the page aligned.

1. Inventory the kickoff dump

  • [ ] Soft cutoff is named (this call / since date X) — older noise stays out or flagged
  • [ ] Every scrap is listed once: source, claim type (goal / deliverable / owner / date / risk / open), notes
  • [ ] Duplicate paste of the same ask across Slack + email + Notion is labeled duplicate — not counted as three opens
  • [ ] Partial claims ("maybe next week," a screenshot with no ask) are labeled incomplete — not invented into tidy scope
  • [ ] Anything clearly superseded, withdrawn, or already answered is labeled stay-off-opens — do not resurrect as this mid-kickoff live ask

2. Lock goal, deliverables, and opens before you trust the sticky

  • [ ] Goal (1–3 lines) is grounded in signed scope / clearest kickoff claims or labeled ask — sticky weather is not a goal
  • [ ] Non-goals are explicit when stated — unsigned "we might also" stays ask, not a deliverable
  • [ ] Deliverables and success criteria exist only when named — blank cells that look scoped are worse than an honest gap
  • [ ] Owners are one real name per workstream — "the team" / emoji reactions stay ask
  • [ ] Dates (start, first draft, review, go-live) exist only when evidenced — otherwise ask
  • [ ] Skim test: a new teammate can answer "what are we building, what’s out, who owns what, what’s open?" without replaying the call

3. Kill sticky / maybe / Slack-promise inflation

  • [ ] Conflicting goal statements are labeled conflict — not averaged into one green paragraph
  • [ ] Sticky folklore and whiteboard photos are listed with claim type or ask — photos are not signed scope
  • [ ] Slack promises without a note row are not promoted to decisions
  • [ ] "Maybe we also…" piles are parked as opens — not smuggled into deliverables
  • [ ] Private / pricing / legal lines the client said to keep out stay out — do not invent redaction by guessing
  • [ ] Auto-summaries and AI meeting notes are not treated as human-locked decisions unless the client confirmed them

4. Park open asks, invented dates, and superseded noise

  • [ ] Invented due dates are either evidenced or labeled guess / ask — not locked because the table looked empty
  • [ ] Open asks (who owns X, what is out of scope, which "yes" locked the goal) sit in one list — not scattered across stickies
  • [ ] Superseded or withdrawn asks are archived once so they do not still look live
  • [ ] Audience for the one-pager (client / internal / future you) is written once so tone does not rewrite facts
  • [ ] Anything still incomplete stays incomplete — do not greenwash a mid-kickoff dump into a closed start page

Soft CTA

If you want the kickoff cleaned into a project-start one-pager for you: kickoff notes in, one-pager out in 24 hours — $12 on Gumroad. Code ADMIN12 takes $2 off. Full catalog: shop · GitHub Pages.

Not financial, tax, legal, or contractual advice. I organize the notes; you own the decisions and the scope.

Top comments (0)