Is a product managerabove the AI?
Below the line: work that can be generated. Above it: the objective, the authority to act, the evidence, and who owns the exception. This is the typical product manager week, split along that line. Yours will differ. That is the point of checking.
No link, or a private profile? instead.
[ II ] The week, split
Above the line
15% of the week
Deciding scope cuts to hit dates
15%The rare moment you actually get to use the authority your job title implies.
Below the line
85% of the week
Writing specs and user stories
20%A highly structured exercise in translating obvious needs into ticket format.
Synthesizing customer interviews
15%Summarising thirty-minute conversations into the three feature requests you already planned to build.
Grooming the backlog
15%Moving low-priority tickets from this month's sprint to next year's graveyard.
Running sprint ceremonies
10%Acting as a human calendar invite and timekeeper for quiet developers.
Chasing designers and engineers for estimates
15%Extracting numbers that everyone in the room knows will be wrong anyway.
Assembling the monthly roadmap update
10%Formatting slides to reassure stakeholders that things are on track when they are merely in progress.
[ III ] Move the number
This number can move.
Drafting user stories and specs can be handed to a system trained on your existing templates. This frees up hours of routine writing so you can focus on the hard trade-offs of scope and strategy.
That is a build, not a discipline problem, and it does not need AI expertise in house: Above The AI brings the system, the person keeps the objective, the authority, the evidence and the exception.
[ IV ] Your number, portable
This card travels with the link. The sentence ships ready to paste, and a low number pastes best as a dare.
Drafted in one pass from what you gave us. A toy, with one serious idea inside: the line is real even when the number is rough. Nothing is stored, and no name appears anywhere, unless you publish your page yourself.