Starting to think Product Management will be overtaken by Product Engineering.
Engineers are learning product. PMs aren’t learning how to build.
Reminds me of “information architects” in the old days arguing that nobody understood how important they were. Then they disappeared.
Ryan Singer
1,333 posts
Product end-to-end. Creator of Shape Up. Prev: 37signals. [email protected]
- “The difference between an idea and a product is that you’ve solved the problems.” - Jony Ive
- Everybody has a text editor. This is my work editor. Here's what it looks like to kick off a new project. Private alpha version.
00:00 - Tools like Cursor hint at where AI-driven user interfaces are going. Chat is only 10%. Most of the output (and UI) is a domain-specific representation of the state of the work. In the case of AI coding, 90% of what you're looking at and thinking about is the IDE, the diffs, the
- I'm starting to think the UX field is overdue for a good primer on how to really *do* interaction design. Current education is way too focused on polished deliverables. Not enough on-your-feet skills and thinking techniques.
- Interesting asymmetry. When shaping, it's important to have one narrow problem and multiple paths to solving it. Agreeing on the problem prevents us from getting frustrated. Finding multiple paths ensures we don't miss opportunities.
- I have officially been through enough loops to say this now: Doing Figma LAST really works. What devs need to start is the wiring. Not the final interior. Just like the contractors building your house need to know where the sink is, not the color of the tile or the faucet
- Excalidraw is good for making a breadboard while shaping. Faster than hand-drawing, and the rough look communicates that it's work-in-progress.
- Palantir's "Forward Deployed Engineer" role. Good example of engineering taking more responsibility for problem definition and shaping. Opposite of ticket takers. Palantir's Ted Mabrey said "We think of the FDE model as one of our greatest secrets." jobs.lever.co/palantir/dab39…
- When projects take longer than expected, people usually think the problem was at the end of the project. The problem is almost always at the start. The team didn't have a process for breaking apart the work, seeing how the pieces fit, and choosing what to do first.
- Async collaboration is essentially additive. It’s easy to add a comment, add an objection, add more code, add to the scope. That works when implementing pieces of an agreed concept. It doesn’t work when we need to change direction, remove something, or make trade-offs.
- Looks like Figma's idea of improving designer-developer relations is helping designers dictate MORE decisions up front. They're even helping designers create Jira tasks from inside Figma! Be suspicious when 8000 designers in a room clap for features made for developers to use.
- FINISHED filming my new course "Shaping in Real Life." Comprehensive, detailed, REAL how-tos on every phase of product development: from framing problems, carving time, shaping, spiking, to hand-off and delivery. Even more content than Shape Up, and for a wider variety of teams.
- Replying to @JosephNWalker and @nntalebI didn’t understand what he meant by “kernel” at first. Looking it up in Statistical Consequences helped.







