Walk into planning to decide, not discover

Email Carly before planning and she'll pull the backlog, read last week's funnel, and drop a one-page brief in Notion with P0/P1/slip recommendations and the data behind each call — so a squad with a full backlog and no consensus on priorities walks into planning ready to decide.

Linear PostHog Notion

What Carly does

1. 01 Pull issues sized for the next sprint — triaged, scoped, not started
2. 02 Query last week's funnel and week-over-week deltas
3. 03 Map each issue to the funnel step it most directly affects
4. 04 Recommend P0 / P1 / slip based on funnel impact, with the delta as justification
5. 05 Write the brief to Notion — recommendations, data, and open questions

Planning meets to decide, not discover

Tomorrow's planning opens with the brief already on screen. The team argues trade-offs instead of priorities — and the meeting ends in 30 minutes, not 90.

Email this to Carly to kick it off.

Hey Carly,

We've got sprint planning tomorrow and the backlog is a mess. Could you pull all the issues from Linear that are triaged, scoped, and sized for the next sprint, then query last week's funnel from PostHog with week-over-week deltas? Map each issue to the funnel step it most directly affects, and recommend P0 / P1 / slip based on funnel impact — using the delta as justification. Write the whole brief into Notion with recommendations, data, and open questions, so we walk in to decide instead of discover.

Thanks!

More recipes for product & design teams

Synthesize a week of user interviews

Notion transcripts → 3–5 themed insights with verbatim quotes linked back to sources.

Read →

Turn a Figma flow into a spec and tickets

Figma → Notion spec → Linear issues, each linked and assigned by area owner.

Read →

Launch recap: did it move the needle?

Adoption + retention for the launch cohort, posted to #product as a 4-line verdict.

Read →