IndumetrixAcademy
08Day-31

Day-31 Deliverable

On day 31 you ship one artifact that proves the muscle is built:

For Project Manager, the deliverable is a **week-in-review** covering one real Senzary account or initiative. It must include: the situation, what skills you loaded, what artifacts you produced (with links), what you handed off (and to whom), and what's queued for next week with owners and dates.

Eric will read it. The good ones get circulated. The mediocre ones get the kind of feedback that's a chapter in itself. Either way you'll know where you stand.

Teaching Moments

How Eric talks about this

ship the week-in-review
Day-31 deliverable · session e18f7c9e

The day-31 artifact. A real, written, linked week-in-review covering one Senzary initiative. Eric reads these. Good ones get circulated to the team.

don't pad it
Standing rule · session 8de8e280

Eric corrected me here. Long week-in-reviews that hide a lack of progress are worse than short ones that show real work. Trim until every line earns its place.

next step with owner and date
Standing rule · session e18f7c9e

The day-31 artifact applies the same rule as everything else: 'next step with owner and date'. Every claim in the week-in-review must be linked, dated, and ownerd.

Prompts referenced

Try these exact phrasings

Hands-on

Try it yourself

Write your day-31 week-in-review. Cover one real Senzary initiative you worked on. Include: situation, skills loaded, artifacts produced (links), handoffs (to whom, with what), next-week queue (owners + dates). Submit as a Confluence page link.

Pass criteria
  • covers one real initiative (not hypothetical)
  • every claim has a link
  • next-week queue has owners and dates
Self-check

Quick check

  1. 1. What's the day-31 deliverable?

    • a. A retrospective slide
    • b. A linked week-in-review covering one real initiative
    • c. A satisfaction survey
    • d. Nothing — informal review
    Reveal answer

    Day-31 is the written, linked week-in-review. Eric reads them. Good ones get circulated.

  2. 2. What makes a week-in-review good?

    • a. Length
    • b. Every claim is linked, every queued item has an owner and a date
    • c. Lots of emojis
    • d. Optimistic tone
    Reveal answer

    Same rule as everything else: linked, dated, ownerd. Trim until every line earns its place.

  3. 3. If the day-31 review is padded, the right move is:

    • a. Submit it anyway
    • b. Trim until every line earns its place, then submit
    • c. Skip it
    • d. Ask for an extension
    Reveal answer

    Eric corrected me here. Padded reviews hide a lack of progress. Trim ruthlessly. Short and real beats long and vague.

← Back to Project Manager← Chapter 7

Built 2026-07-31 · 3 teaching moments · 1 prompts