A working prototype often says more than a 10-page PRD. You can build faster than you can explain. And if something runs, it’s easier to rally people around it.But this isn’t really about writing. It’s about bad writing and shallow product artefacts.Bloated PRDs no one reads. Strategy decks that signal alignment but avoid decision. Words that sound... See more

The opposite of process is chaos, but an in-between is rapid adaptation, emphasis on rapid . Limit scope as much as possible, ship small things fast, and react to feedback quickly.

The design process assumes that dev time is the utmost priority, and this moves a bulk of labor into the design process. This is a faulty premise. The most valuable thing... See more

1. You have to prioritize execution over vision/strategy.Web3 instead requires PMs to be more focused on execution: quickly hammering out a spec over Telegram with devs, QA’ing carefully and setting up a smart contract audit given the risk of vulnerabilities, building hype on Twitter, launching—and repeating.

Times of War: There is a heavy workload, with rapid and frequent deliveries, strict deadlines, and a less relevant hierarchy. The key is to launch the product or feature as quickly as possible, even if it isn’t perfect.