Your Day With PM33 — a quickstart day-in-the-life

Outline

1. Learning objectives — what changes about your daily flow when PM33 is in the loop
2. Key concept — PM33 is not a "PM tool" in the Jira sense; it's a closed-loop platform you participate in
3. Three daily flows — VOC triage, Brief authoring, outcome review
4. The morning routine — 15-min Pam standup
5. The afternoon routine — Brief refinement + sprint check-in
6. The weekly rhythm — sprint plan, mid-sprint check, end-of-sprint outcomes
7. What's NOT in your day with PM33 — what gets removed (status meetings, dependency hunting, attribution spreadsheets)
8. Hands-on — 10-min staging walkthrough
9. Further reading

Learning objectives

After this module you should be able to:

• Describe how your daily flow changes when PM33 is in the loop
• Name the 3 daily flows you'll do most often (VOC triage, Brief authoring, outcome review)
• Set up your first strategic objective
• Read what Pam surfaced overnight without getting overwhelmed
• Explain to a peer what stops happening when PM33 is doing its job

Key concept

PM33 is not a "PM tool" in the way Jira is a PM tool. Jira is a ticket database that you organize. PM33 is a closed-loop platform that you participate in — it has opinions about what to work on next, it has predictions about what will move the metric, and it has questions for you that it can't answer alone.

The shift in role: you stop being a ticket-mover and start being a judgment-maker. PM33 handles the moving. You handle the calls that require taste, customer empathy, and strategic context.

This sounds abstract. Here's what it actually means by Tuesday:

That's the day-to-day reframe. The closed-loop framing makes this possible.

Three daily flows

Flow 1 — VOC Triage (5-15 min, morning)

Voice of Customer (VOC) items — support tickets, sales feedback, customer interviews — flow into PM33 throughout the day. Pam triages them overnight:

• Scores against active strategic objectives
• Clusters duplicates
• Surfaces hot patterns (sudden spike in a complaint area)
• Drafts a Brief (or Idea, if not yet shaped) for the top items

Your job in the morning: spend 5-15 minutes looking at what Pam surfaced. Approve the ones that are clearly worth doing. Push back on the ones where Pam mis-scored. Ignore the noise.

You're not reading every VOC item. Pam already did. You're confirming or adjusting Pam's judgment on the top 5-10.

Flow 2 — Brief Authoring (15-30 min, when needed)

When you have a feature concept that needs to be specified, you don't write a 3-page PRD. You author a Brief. (Module 2 covers this in depth.)

The Brief is the atomic unit of agent-executable work. It has:

• A clear title in imperative form ("Add email verification to onboarding")
• Machine-verifiable acceptance criteria
• An outcomeHook declaring how success will be measured
• Specialist + LLM tier assignment (or you let Pam decide)
• TDD phases (RED → GREEN → REFACTOR → DELIVERY)

Most days you don't write Briefs from scratch — you refine ones Pam drafted from customer signals.

Time on this flow: depends on how many new initiatives are in flight. Some days zero. Some days an hour.

Flow 3 — Outcome Review (10-20 min, end of week or end of sprint)

Pam tells you which Briefs that shipped recently actually moved their target metric. This is the closed-loop moment.

Three things you do here:

1. Celebrate the wins — Briefs that moved the metric as predicted are evidence the team is shipping the right things
2. Investigate the misses — Briefs that shipped but didn't move the metric: were they the wrong frame? wrong target? wrong measurement window? feature flag still off?
3. Update strategy — areas where Briefs reliably move metrics get weighted higher in next sprint's planning; areas where they don't get scrutinized

This is the most strategic 20 minutes of your week.

The morning routine

A typical PM morning with PM33:

8:55 — Open Pam. Read the overnight summary.

Good morning Sarah.

Last 24 hours:
  3 Briefs shipped: BRIEF-2401, BRIEF-2403, BRIEF-2405
    BRIEF-2403 already showing 12% lift on its outcomeHook metric (signup→first-API-call within 24h). Predicted 15% ± 4%. Within band.

  1 Brief blocked: BRIEF-2407 (cross-team dependency on PAYMENTS-XX2; I've pinged that team)

  2 new VOC patterns:
    "Email verification too slow" — 7 tickets in 3 days. Cluster matches BRIEF-2412 already in backlog. Bumped to top of Sprint 51.
    "Sandbox API rate limits unclear" — 4 tickets, novel. I've drafted IDEA-3902. Want to review?

  Strategic objective drift alert:
    "Reduce TTFCV by 30% by Q4" is currently tracking at 22% with 4 weeks left.
    AR(1) forecast says we hit 27% by EOQ at current Brief throughput. To hit 30%, need 2 additional onboarding-area Briefs this sprint.

9:00 — Sarah skims, approves IDEA-3902 (writes one sentence of context Pam couldn't infer), and notes the drift alert. She'll talk to her eng lead at standup.

That's the morning routine. 5-10 minutes most days. The point is not to read every detail — it's to confirm Pam's read of the world.

The afternoon routine

2pm-2:30pm — Brief refinement window. Sarah opens her Brief queue. There are 4 Briefs Pam drafted from customer signals overnight that need her judgment.

For each Brief she:

• Reads the title and acceptance criteria
• Checks the outcomeHook makes sense
• Adjusts the predicted impact if Pam's estimate seems off
• Approves it into the backlog OR
• Sends it back with a one-liner ("this isn't worth doing — duplicates BRIEF-2390")

15-30 minutes total. Maybe an hour on big-decision days.

The weekly rhythm

The weekly cadence isn't different from your current cadence — same touchpoints, different content. What changes is what you DO at each touchpoint.

What's NOT in your day with PM33

Time savings come from things that stop happening:

• Status meetings — Pam's summary replaces 80% of status updates. Use the saved time for customer conversations, not for finding a 30-min slot for another meeting.
• Dependency hunting — the capacity scheduler surfaces dependencies. No more chasing 3 teams to figure out if PAYMENTS is on track.
• Attribution spreadsheets — built in. Don't build them.
• PRD writing for clearly-scoped features — Briefs replace 80% of PRDs. Save PRDs for genuinely novel directions.
• Translating Jira to roadmap — your roadmap IS the strategic objectives tree. The Brief backlog feeds it.
• Manual Brief grooming sessions — Pam grooms continuously. The 30-min weekly grooming is now a 5-min review.
• Quarter-end attribution scramble — your QBR data is sitting in PM33 already, automatically attributed.

If you find yourself doing any of these after 4 weeks on PM33, something is configured wrong. Ping #pm33-help or your CSM.

Hands-on (optional, 10 minutes)

On the staging environment, do this morning routine yourself:

# 1. Read Pam's morning summary
mcp__pm33-staging__pm33_query_alerts

# 2. Look at active strategic objectives + their trajectory
mcp__pm33-staging__pm33_get_delivery_confidence

# 3. Read the VOC triage queue
mcp__pm33-staging__pm33_voc_get_triage_queue

# 4. See last week's completed Briefs and their attribution
mcp__pm33-staging__pm33_query_backlog filterStatuses='["done","outcome_attributed"]' limit=10

You should see the staging workspace's actual state. Note how the data is structured around objectives → epics → Briefs → outcomes (the closed loop you saw in slide 01).

Further reading

• PM Module 2 — Authoring Briefs that Convert to Done (outlined)
• PM Module 3 — Reading Outcome Attribution (outlined)
• Engineer Module 2 — The Brief Lifecycle — the full state machine
• Engineer Module 4 — Outcome Attribution & Recalibration — the AR(1) math
• Strategic objectives spec (if it exists in your repo)

What to do after this module

If you're new to PM33:

1. Spend a week using just the morning routine. Get comfortable with Pam's summary.
2. Then add Brief refinement (Module 2)
3. Then add outcome review (Module 3)
4. Sprint planning + Pam delegation (Modules 4 + 5) once you have a sprint of Brief data

If you're already a regular PM33 user and reading this for a refresher:

• Module 4 (sprint planning) is where most PMs find new wins
• Module 5 (Pam delegation) is the lever for getting >5 hours/week back