Operating System for Fast Ships
Most teams do not have a speed problem. They have a decision-latency problem. When priority changes daily, the backlog becomes a stress artifact instead of a planning tool. The ...
— writing
PMF, building with AI, growth, delivery, lessons. New posts most weeks. Honest, occasionally uncomfortable, never corporate.
— featured this week
the one to read first
Most teams do not have a speed problem. They have a decision-latency problem. When priority changes daily, the backlog becomes a stress artifact instead of a planning tool. The ...
— recent posts
— the archive
20 more posts
The biggest change AI made to how I work wasn't the one I expected. I thought it would be research. Faster market analysis, quicker competitor reviews, better synthesis of user ...
There's a version of this story that plays out at almost every startup that gets traction. Early stage: one PM, close to the product, close to the users, making fast decisions. ...
Every PM knows the frameworks. RICE, MoSCoW, Kano — they're in every product course, every PM interview, every roadmap conversation. The problem isn't that teams don't know they...
The roadmap is a business document. Users don't care about it. They care about whether the product solves their problem. They care about whether it's fast, clear, and worth comi...
Most stakeholder communication problems aren't communication problems. They're system problems. The meeting happens late. The update goes out after the decision has already been...
The hardest stakeholder situation isn't a difficult personality. It's a reasonable person asking for something that would break the product. A difficult personality you can mana...
Every team motivation conversation eventually lands on the same suggestions. Recognition programmes. Team lunches. Retrospective shoutouts. Slack emoji reactions to shipped feat...
A large onboarding rewrite sounds exciting. It also hides where the gains actually come from. We split onboarding into five tiny decisions and tested them independently over two...
Most prioritisation conversations start in the wrong place. The question teams usually ask is: what should we build next? The question they should be asking is: what do we know,...
The job description is the same. The context is completely different. At a large company, product management is about navigating process. There's a structure, a roadmap cadence,...
Nine years in product and the problems are always the same. Different industries, different team sizes, different tech stacks — the surface changes. Underneath it's always some ...
The pattern shows up everywhere. Different company, different product, different team — same problems underneath. After enough engagements you stop being surprised by what's bro...
Founders often report traction as a single number in a deck. But traction is not one screenshot. It is a repeated behavior pattern over time. Useful traction questions - Are use...
The point of an MVP isn't to ship a small successful product. It's to find out, as quickly and cheaply as possible, what users actually want. Most teams forget that. They build ...
Saying yes feels collaborative. Saying no feels like a fight. That asymmetry is why most product teams accumulate scope they don't actually believe in. The yes is one conversati...
Most teams treat discovery as a phase. There's a kickoff, a few weeks of research, a synthesis deck, and then the team moves to build. Discovery is something you do at the start...
Pricing is the highest-leverage thing on the product surface and the thing teams touch the least. The same team that runs ten experiments a quarter on onboarding will leave the ...
The business analyst is usually the first role to get cut on a lean team. It looks like overhead. The PM does requirements, right? The engineers can ask questions. Why pay for a...
Empathy gets dismissed as a soft skill. Something for the people side of the job, irrelevant to the actual decisions about what to build. That framing is wrong twice over. First...
Read enough product post-mortems and the same pattern starts showing up. The vocabulary changes — "ahead of its time", "wrong execution", "team didn't sell it well", "bad market...
Subscribe via X (@abdibedellab) or LinkedIn for new posts. No newsletter. No inbox guilt.
— honest, occasionally uncomfortable, never corporate