Make Product Management Fun Again: Reclaiming the Craft from the Chore
You got into product to build things people love — not to chase Slack threads. Here is how to give the 80% you hate to AI and keep the 20% that is the real craft.
You Didn't Get Into Product to Chase Slack Threads
Think back to why you took a product job. It wasn't the status meetings. It was the craft: finding a real problem, shaping a sharp solution, watching people use the thing you imagined. Somewhere along the way, that part shrank to about 20% of the week. The other 80% became chore — chasing feedback across Slack, Gong, and Jira; turning that noise into a PRD; then hunting for the one customer quote that proves you're right before the roadmap meeting.
That's not a motivation problem. It's a job-design problem. And it's why so many good PMs quietly burn out — surveys on product roles keep landing on the same culprit: too much time on coordination and busywork, too little on actual product judgment.
The Chore Isn't the Job — It's the Tax on the Job
Here's the reframe that matters: the busywork was never the value you add. Nobody hired you to copy-paste from Slack into a doc. They hired you for judgment — knowing which problem is worth solving and being able to defend it.
The trap is that the chore feels like progress. You spent four hours assembling context, so it feels like work. But context-assembly is exactly the part a machine should do. The judgment — the 20% — is the part only you can do, and it's the part that made the job fun in the first place.
Give the 80% to the Machine, Keep the 20%
The goal isn't "PM productivity." It's narrower and more human: hand the chore to AI so the craft is what's left on your plate. Concretely:
- Feedback → spec, automatically. Raw complaints from every channel become a drafted problem statement, so you start from a sharp first draft instead of a blank page.
- Evidence on tap. Every claim links back to the actual customer who said it — so "defending the call" stops being an evening of archaeology and becomes a glance.
- The connective tissue maintained for you. Research, decisions, and outcomes stay linked, so the map of you're building never rots.
Keep reading
The PM Role Is Splitting: Which Product Manager Are You Becoming?
The generalist PM is becoming the hardest role to hire for — because the job is splitting. The specialize-vs-AI-generalist fork, the four flavors of "AI PM," and the one career question that now matters most.
Jobs to Be Done: Why Your Customers "Hire" Your Product (and What That Changes)
Customers don't want your product — they hire it to get a job done, and fire it when something does the job better. Here's how Jobs to Be Done reframes discovery, prioritization, and messaging.
Continuous Discovery: How to Talk to Customers Every Week (Without It Eating Your Roadmap)
Most teams do discovery in bursts, then build on stale assumptions for months. Continuous discovery — small, weekly customer touchpoints — keeps you close to reality. Here's how to make the habit stick without it eating your roadmap.