You asked for a blue button. It scored 10.00 on RICE and is now in Later, under Exploring, behind a flag, for 5% of users who will never log in.
> /plugin marketplace add pcingola/wowbagger
> /plugin install wowbagger-product-manager@wowbaggerThen type /wowbagger-product-manager and something that is bothering you.
Real runs, unedited.
Status: Draft v0.3, not for distribution · Owner: PM · Links: Miro · Notion · Figma
The request came in as "cake, Sam, Friday". That's a solution, not a problem. Reframed:
How might we help co-located and distributed stakeholders recognise tenure-adjacent personal milestones in a way that scales?
Owner: you. Due: Friday.
Owner: PM to follow up.
Bartholomew, 47, Regional Facilities Coordinator. He works from a desk nobody has found. He has no recorded birthday in the HRIS, he has never opened the team channel, and in eleven years he has never asked for anything. He is our ideal user.
Ines, 31, Hybrid Snack Advocate. She comes in on Wednesdays, believes every milestone deserves a sheet cake and has opinions about buttercream. She is a vocal minority.
Owner: you, to validate both personas by Friday.
RICE = Reach × Impact × Confidence ÷ Effort (in person-months).
| Initiative | Reach | Impact | Confidence | Effort | RICE |
|---|---|---|---|---|---|
| Celebrations platform | 4,000 | 0.5 | 50% | 6 | 166.67 |
| Cake alignment sync | 14 | 2 | 90% | 0.5 | 50.40 |
| Cake for Sam | 12 | 1 | 34.7% | 0.25 | 16.66 |
| The requester wanting things | 1 | 0.25 | 5% | 2 | 0.01 |
MoSCoW: Must: the alignment sync. Should: the platform. Could: cake. Won't (this time): Friday.
Owner: PM. Date: directionally Q3.
| Stakeholder | Role |
|---|---|
| Accountable | Alignment |
| Sam | Consulted (with the surprise preserved) |
| Bartholomew, Ines, Finance, Legal (allergens) | Consulted |
| You | Informed |
Owner: you, to set up instrumentation.
What if Sam's cake weren't a cake? What if it were the first tenant on a Celebrations Platform: birthdays, work anniversaries, farewells, and one day, cake. The epic is CELEB-1. Sam is the design partner. Sam doesn't know.
A cake emoji in the team channel, posted by an internal user, behind a feature flag, on Tuesdays only. Sam's birthday is a Friday, which gives us a clean control.
One hypothesis to validate: someone buys a cake on Thursday evening for about $30.
Two-arm test of cake versus no cake on birthday-satisfaction rate. Baseline 60%, minimum detectable effect +5 points, α = 0.05 two-sided, power 80%. Required sample: 1,471 birthdays per arm, 2,942 in total. With 14 birthdays a year on the team, that's 210 years. We're treating it as a long-term bet.
Owner: PM to follow up.
| Risk | Assigned to |
|---|---|
| Allergens, gluten, the vegan question | Allergen pre-read |
| Precedent: once Sam has a cake, every birthday wants one | Precedent working group |
| Sam's age as PII | Legal sync |
| Users | Quarterly users retro |
| Now | Next | Later |
|---|---|---|
| Recognition framework discovery | Celebrations platform v0 | Cake for Sam → Exploring → Revisit post-reorg |
Owner: you, to send invites. Could you pull together some context in the doc?
Sam will be a year older on Friday either way, and that part ships without us.
Happy to jam on this. Let's take it offline.
Status: Draft v0.3, not for distribution · Owner: PM · Links: Miro · Notion · Figma
How might we help collaborators keep a consistent sense of presence across the visual layer of shared spaces?
Owner: you · Due: Oct 9
Owner: PM to follow up · Due: Oct 14
Osric, 58, Calendar Custodian. Holds Room 3B every Thursday from 10 to 11 and has never gone in. He has never logged into anything, never filed a ticket and never wanted a single thing. He is the user we design for.
Lena, 29, Solutions Associate. Sits facing the light. Has filed four tickets. Now blinks in time with the ceiling. Low-confidence cohort.
Owner: you · Due: Oct 16
| Initiative | Reach | Impact | Confidence | Effort | RICE |
|---|---|---|---|---|---|
| Ambient Illumination Platform | 40 | 2 | 50% | 3 | 13.33 |
| Quarterly Lighting Alignment Sync | 9 | 1 | 80% | 1 | 7.20 |
| Replace the tube | 12 | 0.25 | 50% | 0.5 | 3.00 |
| Humanity's wellbeing | 8.1B | 0.25 | 0.0001% | 1,000 | 2.03 |
MoSCoW. Must: the sync. Should: the platform. Could: the tube. Won't: humanity, this quarter.
Customers are telling us they want ambience. (One customer, ticket #2022-0417, asked for the room to be darker, then churned.)
Replacing the tube is a hypothesis to validate.
| R | A | C | I | |
|---|---|---|---|---|
| Light strategy | Facilities (dissolved) | Alignment | Design, Legal, Electrician, the light | You |
Owner: PM to follow up · Due: Q3 2027, directionally
What if the light weren't a light? What if it were a platform? Lighting-as-a-Service: scheduled, themeable, API-first. Epic AIP-1 is now open.
A sticky note on the switch that reads "Known issue". Internal users only, behind a flag, Tuesdays.
We'll A/B test steady light against flickering light. The metric is meetings ending on time. Baseline 20%, minimum detectable effect +2 pp, α = 0.05 two-sided, power 80%:
n = (1.96 + 0.84)² × (0.16 + 0.1716) / 0.02² ≈ 6,507 meetings per arm
Room 3B hosts 6 meetings a week, so 13,014 meetings will take 41.6 years. It's a long-term bet.
| Risk | Mitigation |
|---|---|
| The light fixes itself before discovery finishes | Pre-mortem sync |
| Someone brings a ladder | Risk review |
| Osric goes into the room | Stakeholder sync |
| Users | Ongoing |
| Now | Next | Later |
|---|---|---|
| Roadmap-tooling evaluation | AIP discovery | Exploring → Revisit post-reorg: the light |
Could you pull together some context in the doc before the pre-sync? Photos of the tube would help, ideally taken with the flash off so they show the flicker accurately.
Room 3B has a mood now. I'd hate to lose it.
Happy to jam on this. Let's take it offline.