Jason Shah on PMing in Web3, Pushing Back on Founders, and the Ladder Versus Map Framework

Jason Shah — VP of Product at Alchemy; formerly Airbnb, Amazon, do.com, Yammer — covers Web3 product management, how to influence founders without “pushing back,” the ladder-versus-map career framework, and a hiring philosophy that treats recruitment as a marketing and sales problem.

Key ideas

Reframe “pushback” as direction-shifting. The word “pushback” implies opposition; it puts people into a defensive stance. More effective than disagreeing is understanding the other party’s real goal and realigning the proposal around it. At Airbnb, reframing a chat product as “trip designers” — a simpler, more elegant experience — defused scope conflict by giving everyone what they actually wanted.
Amazon PRFAQ forces clarity. The press release + FAQ template (intro, problem, solution, customer quote, leadership quote, call to action) requires concrete language. The rule against “great” illustrates why: adjectives obscure strategy differences that nouns and numbers reveal. Fewer words means every word carries more weight.
Ladder vs Map. Ladder-thinkers optimise for title, influence, and upward trajectory. Map-thinkers follow what is interesting, accept discomfort as a feature, and build careers non-linearly. The ladder is often more fragile than it looks; the false precision of career planning leads people to foreclose on paths they haven’t explored.
Hiring is marketing + sales + product. Build a brand and personal reputation before candidates encounter a job posting (marketing). Understand what each candidate actually wants and whether the role delivers it (sales). Treat the job description the way you’d treat a product spec — iterate on it based on who you’re meeting and what the business needs (product).
Defining what problem matters is the core PM skill. Problem clarity drives everything downstream: what to build, what not to build, how to price, how to structure the team. Without it, product decisions devolve into feature lists or resource allocation games.

On reframing disagreement

The Airbnb “trip designer” case: a complex chat product was consuming too much scope. Rather than arguing for reducing scope, a senior leader reframed the destination as an elegant, minimal experience for a luxury travel context. Everyone aligned on the shared goal — a wonderful customer experience — and the scope reduction followed naturally.

Principle: work backwards from what the other party actually cares about (as you would in sales), then show how your proposal serves that goal better than the current direction.

On Amazon’s PRFAQ

Structure: (1) introduction announcing the product; (2) problem statement; (3) solution; (4) a customer quote in concrete language; (5) a leadership quote connecting to strategy; (6) a call to action with a specific rollout date or mechanism.

The customer quote is particularly important — it forces the PM to inhabit a specific user’s perspective rather than assume they represent the customer base. The writing is trained: Amazon employees attend a business writing class and keep a card of five style rules on their desk.

The PR differs from Airbnb’s “11-star experience” framing: Amazon works backwards from a launch moment in time; Airbnb works backwards from a quality standard.

On the Ladder vs Map framework

The ladder is a proxy. A career path can look clean and progressive while leading somewhere the person doesn’t want to go — or while the company’s fortunes make the ladder collapse mid-climb. The map framing prioritises lived experience, network building from interesting contexts, and the long view (a 30-to-40-year career has room for multiple 5-to-10 year chapters).

Sticking with interesting work is not incompatible with depth: Shah’s commitment to Web3 over a decade and staying at a company long enough to accumulate institutional knowledge are both part of the map approach.

On hiring

Three lenses: