From Pixels to Punk: A Manifesto for the New Era of Product Management
Before Ufotable animated Episode 19 of Demon Slayer, the manga was selling 50,000 copies a week. After it aired, it sold 100 million.
Nobody optimized their way to that. One studio made a creative bet: CGI backgrounds, a full orchestral score, an action sequence treated like an art installation. It changed everything. The product was the same. The craft changed. The world noticed.
That’s the argument this blog is making.
Product management has spent twenty years building infrastructure around a lie: that great products come from better process. Better frameworks, better prioritization, better stakeholder management. Process matters but process is not what made Demon Slayer or Jujutsu Kaisen or Evangelion or NieR or YOASOBI or Green Day or HAGANE matter to people. What made those things matter was a creative decision made by someone who understood something the market didn’t yet.
That’s the PM skill nobody is teaching because nobody knows how to put it in a course.
FromPixelsToPunk exists because these two things (creative craft and product work) are not different disciplines. They’re the same discipline practiced in different rooms.
The mangaka who spent 18 years getting canceled before Spy x Family. The game director who hid from his publisher and built a product that lies to you for 20 hours. The band that lost three-fifths of its members and came back fiercer. The J-pop duo who turned “every song must start with someone else’s story” from a constraint into the reason they made history.
These aren’t metaphors for product management. These are product management: the instinct to know what to build, why it will matter and what to protect when everyone around you is asking you to compromise.
Every post on this blog starts with the story. The PM lesson comes from the story because that’s where it actually lives. The observation is specific. The bridge is earned. The advice is real.
AI will not change what the job actually is.
AI speeds up the execution layer: the specs, the wireframes, the coordination and the alignment docs. All of that gets faster and eventually gets automated. What remains is the thing that was always the actual job: watching something happen and knowing what it means. A user hitting a wall they can’t describe. A cultural shift showing up in three unrelated places at once. The leap from observation to decision that requires genuinely caring about what you’re looking at.
The PM content machine will keep producing frameworks. Most of it will be useful for the next two or three years and quietly irrelevant after that. The question is not what tools you’re running. The question is what you’re bringing to them.
The answer to that question is what this blog is about.
◆ Before you read on
What's the PM move here?
Think about a decision you made recently because you saw something before the data did — what was it?
You predicted:
Precision where it counts. Rebellion where it matters. Humanity always.
This is product management. Rewritten.
◆ Your Take
When did you last make a product decision because you saw something before the data caught up — and were you right?
When you read this before, you wrote:
Your takeaway: