Skip to content
All posts

2 min readcareerproductlearning

The product skills that actually compound

Most skills a PM learns depreciate — tools change, frameworks rotate. A few appreciate with every year and every job. Optimize for those.

A decade into product work — through agencies, a global marketplace, and fintech — I’ve noticed that my skills sort into two piles. One pile depreciates: tool fluency, process trivia, whatever framework the industry is rotating through this year. The other pile appreciates: it gets more valuable with every year, every company, every domain switch.

Career advice usually pushes the first pile because it’s easy to list on a CV. Certifications have their uses, but the second pile is where the compounding lives. Here is what’s in mine.

Writing things down

Not “communication”. Writing. The unglamorous discipline of turning a fuzzy situation into two pages someone else can disagree with. A written decision can be reviewed, challenged, and — most importantly — checked against reality a year later. A meeting evaporates.

Writing compounds twice: the document outlives you, and the act of writing is where your thinking actually happens. Every hard product disagreement I’ve untangled was untangled in prose before it was untangled in a room. It is also, not coincidentally, how I run my own distribution — the writing habit and the personal brand are the same muscle.

Reading systems, not features

The ability to look under a product and see the machine: what the data model allows and forbids, where the incentives point, which metric will lie to you and when. This is the skill that transfers across domains — marketplaces, agencies, fintech — because systems rhyme even when industries don’t. Scaling a delivery organization is the same skill pointed at people and process instead of tables.

You build it by asking “what would have to be true” and “what breaks at 10x” until it becomes involuntary.

Talking to users without flinching

Everyone endorses user research; few people regularly sit with a churned customer and ask what we got wrong. The compounding part isn’t the technique — it’s the calibration. After hundreds of conversations you develop a prior for how real users differ from the personas in the deck, and that prior follows you to every future product. It is the cheapest form of judgment you can buy.

Saying no with a reason

Focus is usually framed as a virtue. Operationally, it is a skill: the ability to decline a plausible idea with an articulated reason that survives scrutiny. “Not now, because it doesn’t serve the segment we’re winning first” builds trust even in refusal. Small markets teach this brutally — you simply cannot afford everything — but the skill pays anywhere.

Teaching what you know

The fastest way to find the holes in your understanding is to explain it — to a junior PM, a conference room, or a blog. Teaching forces compression, compression exposes hand-waving, and the reputation compounds socially: the person who explains the system becomes the person people bring the hard problems to.

The meta-skill

Notice what these have in common: none requires permission, budget, or a particular employer. They are all practicable this week, in whatever job you have. That is what makes them compound — the streak never has to break.

Tools will keep changing; lately they change monthly. The pile that appreciates is the one that makes you better at deciding what the tools should do. Invest accordingly.

Keep reading

Get the next essay

Product, growth, and AI-assisted engineering — straight to your inbox, once in a while. No spam, unsubscribe anytime.