Career journal for

Product Managers

PM work is half decisions and half organizational gravity. The decisions evaporate fast and the gravity is impossible to attribute without dated capture.

Bloom is the career journal built for the moments the work actually happens, not the night before the review.

A captured day for a Product Manager

1. 01

   9am: synthesized the user-interview notes from yesterday's 4 sessions; the password-rule issue is real.

2. 02

   12pm: design crit with Lena on the new onboarding flow; her concern about progressive disclosure changed my spec.

3. 03

   3pm: roadmap call with the PM team; pushed back on the proposed Q3 scope.

4. 04

   5pm: paired with Sarah (junior PM) on her first PRD.

What a Product Manager captures

• Features and products shipped with measurable impact
• Decisions that proved right
• Engineering and design partnerships
• PRDs and strategy docs authored
• Cross-functional alignment moments

Owned activation rebuild (D7 38% to 47%). Killed wizard in week 3 based on tree test; saved 6 weeks of build. Mentored 1 junior PM through L4 promotion.

Promotion rubric, mapped to capture

• Top accomplishmentsCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Where your judgment got sharperCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Leverage on the teamCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Priorities for the next periodCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.