What's one decision this week where you trusted your judgment over the playbook? Where the "right answer" by any framework wasn't the one you went with? Walk me through what you weighed. (I'm publishing Sunday on the version of this that costs PMs interviews. If your story is good, I might pull from it — anonymously.) Subscribe to joshatlas.co/substack so the post lands in your inbox when it drops.

As AI takes more of the execution work off engineering's plate, the questions that shape what gets built matter more than ever. PMs are trained to ask "what problem are we solving for whom" before "what should we build." Engineers often aren't. Share a specific question you've started asking — in sprint planning, roadmap reviews, or stakeholder conversations — that changed the direction of a decision. What did it unlock?

Product sense isn't about having better ideas — it's about seeing the real problem before anyone else starts building. This week's LinkedIn and Substack content was all about that shift. Share a specific moment where you stopped before solving, named the tension, and changed the direction of a conversation or decision as a result. What did you notice that others had missed?

Product sense isn't something you either have or don't — it's a trained skill built through one specific shift: stopping before you solve. Most PMs jump to solutions because movement feels like progress. The ones who develop real product sense learn to sit with the problem first — naming why it exists, what makes it genuinely hard, and who feels it most acutely. Share the one shift in your thinking that changed how you approach problems, whether in interviews or in your day-to-day work.

AI is making it faster than ever to say yes to everything — generate the PRD, spin up the deck, ship the feature. But strategy is still defined by what you choose not to do. Share a specific no you made this week, whether it was a stakeholder request, a roadmap item, or a scope expansion. Tell us what saying no made possible.