SHORT ANSWER
Four skills carry most of the job: customer discovery, prioritisation under uncertainty, written communication, and data literacy. In 2026 add two more: AI-assisted execution, and evaluation design for AI features. Frameworks, roadmapping tools and ceremonies are teachable in weeks; judgement about what not to build is the skill that separates senior PMs from everyone else.
Answered by Andrew Crossley, Fractional Chief Product Officer · Updated 2026-08-01
Job specs list twenty skills and hire on four. Knowing which four to build compresses years off a career path.
Teams also mis-hire by screening for framework vocabulary rather than evidence of decisions.
Running interviews that produce evidence rather than validation. Asking about past behaviour, not future intentions.
Sequencing under uncertainty and defending removals. The output of prioritisation is a shorter list, not a scored spreadsheet.
One-page specs, crisp decision records, honest updates. In distributed teams, writing is the product function's operating system.
Defining a metric properly, reading a cohort chart, knowing when a difference is noise. You do not need to be an analyst; you need to not be fooled.
Prototyping, synthesis and drafting with AI tooling, so more of your week is judgement and customer contact.
For any AI feature: what does good output look like, how is it measured, and what is the override rate.
FROM EXPERIENCE
The strongest signal in a product interview is a candidate describing something they killed: what it was, who wanted it, what evidence changed the decision, and what it cost them politically.
Anyone can list what they shipped. Very few can explain what they refused to ship and why they were right.
Enough to reason about trade-offs and build prototypes with AI tooling. Not enough to write production code.
Design judgement, yes; craft, no. You need to tell a good flow from a bad one and argue for simplicity.
Writing. It scales your thinking across the company without you in the room.
IN SHORT
What the role actually involves and how it differs from a classic PM.
Read moreContract, fractional and advisory engagements — current availability.
Read moreThe seven-stage framework that takes an idea to first revenue.
Read moreSeven stages from first idea to first revenue, with one output each.
Explore the Crossley MethodTHE FRAMEWORK
MORE ANSWERS
You become a product manager without a degree by producing evidence instead of credentials: ship something real, own a metric in an adjacent role, and document decisions publicly. Support, sales, operations and QA are the highest-converting entry routes because they give you customer contact and data. Hiring managers screen for judgement and shipped outcomes; almost none check for a degree at interview stage.
Product managers usually fail for structural reasons, not talent ones: no clear mandate, no owned metric, no direct customer contact, an organisation that rewards shipping over outcomes, and an unwillingness to create conflict by saying no. Four of those five are fixable by the company. The fifth — avoiding conflict — is the personal skill most often missing in PMs who stall at mid-level.
Product managers use AI to compress the artefact half of the job: synthesising interviews, drafting specs and tickets, building clickable prototypes, summarising support and review data, and pressure-testing decisions. The best PMs also use it inside the product, designing evaluation sets and quality metrics for AI features. What they do not delegate is the decision, the customer conversation or the accountability.
Product-market fit is the point where a defined group of customers keeps using and paying for your product without you pushing them, and demand grows faster than you can comfortably serve it. Practical signals: week-four retention that flattens rather than decays, over 40% of users saying they would be very disappointed to lose it, organic word of mouth, and shortening sales cycles.