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. The product was the same. The craft changed enough that the world noticed.

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. Each of those came from 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 creative craft and product work are the same discipline practiced in different rooms. Consider 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. Those 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. The stories are the curriculum.

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 earned and the advice 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. The actual job survives that, which is watching something happen and knowing what it means. A user hits a wall they can’t describe. A cultural shift shows up in three unrelated places at once. The leap from that observation to a decision requires genuinely caring about what you’re looking at.

The PM content machine will keep producing frameworks. Most of them will be useful for the next two or three years and quietly irrelevant after that. What you bring to them is the part that lasts.

Precision where it counts. Rebellion where it matters. Humanity always.