Potential-Over-Experience Hiring
Assess how candidates solve hard problems, not whether they have repeated one playbook.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 98%
Start by defining the hard problems the role must solve rather than listing familiar employers, titles, or campaign types. For each candidate, investigate how they diagnosed a difficult situation, separated causes from symptoms, generated options, and adapted when an approach failed. Then test whether that reasoning can transfer to the economics, market maturity, team structure, and constraints of the new company. Experience remains an input, especially where domain knowledge is essential, but it does not become the primary proxy for ability. The output is a hiring decision based on demonstrated learning speed, intellectual range, and capacity to solve the next set of problems rather than merely repeat a playbook that worked under different conditions.
Origin
Extracted from Marketing Against The Grain during Kip Bodner and Kieran Flanagan's discussion of why founders overvalue candidates who have already performed an apparently identical role.
Core principles
- 01Past success is specific to its original situation.
- 02Complex problem-solving ability can transfer across functions.
- 03Relevant experience matters, but it should not dominate the decision.
- 04Hiring for an old playbook can select against future growth.
How to run it
- 1
Define the Real Problems
Write down the concrete business problems the hire must solve, including the company's stage, economics, market conditions, pace, and team dependencies.
Pro tip Describe outcomes and constraints before writing experience requirements.
Watch out A vague role specification causes irrelevant experience to look more valuable than it is.
- 2
Set the Experience Floor
Identify only the experience that is genuinely necessary to begin operating safely and credibly in the role.
Pro tip Separate mandatory knowledge from skills a strong learner could acquire quickly.
Watch out Do not turn every desirable background trait into a mandatory checkbox.
- 3
Inspect Hard Problems Solved
Ask candidates to explain difficult problems they have personally helped solve, including their diagnosis, decisions, experiments, and contribution relative to the team.
Pro tip Probe for the candidate's own reasoning rather than accepting a polished company success story.
Watch out Team results do not automatically reveal an individual's contribution.
- 4
Test Transferability
Present unfamiliar problems from your environment and evaluate whether the candidate can transfer their reasoning without blindly copying an old playbook.
Pro tip Look for thoughtful questions and adaptation to constraints.
Watch out Familiar terminology can disguise weak contextual reasoning.
- 5
Balance Experience and Potential
Compare candidates using both their relevant foundation and their demonstrated ability to learn, adapt, and solve future problems.
Pro tip Give explicit scoring weight to problem-solving and learning potential.
Watch out Do not let a prestigious title or employer silently outweigh stronger evidence.
In the wild
A startup considers a candidate who has led difficult demand-generation turnarounds but has not held a product-marketing title. Instead of rejecting her, the founders ask her to diagnose positioning and adoption problems in their market. She identifies customer-research gaps, distinguishes messaging from channel issues, and proposes small tests before a broader rollout.
→ The company discovers transferable diagnostic ability that a title-based screen would have missed.
A founder interviews an executive who scaled demand generation at a company with cheaper acquisition channels and a weaker incumbent. The founder tests the candidate against the startup's saturated channels and difficult category leader. The candidate insists on repeating the former playbook without adapting its assumptions.
→ The founder avoids hiring experience that is impressive but poorly matched to the new situation.
Common mistakes
Treating Titles as Proof
A matching title shows where someone worked, not how they reasoned or what they personally contributed.
Ignoring Situational Differences
A playbook that succeeded with different economics, channels, leadership, or market conditions may fail in the new company.
Eliminating Adjacent Talent
Rejecting candidates because they have not performed the exact task can hide people with exceptional transferable problem-solving ability.
Is it for you?
Best for
It is best for founders and leaders hiring adaptable marketers or senior operators into changing environments.
Not ideal for
It is not ideal for regulated or highly technical positions where verified credentials and exact prior experience are mandatory.
From the transcript
“the number one mistake you will everybody listening to this podcast right now is making a hiring is overhiring for experience versus potential.”
“I think marketing or most disciplines like that are just a collection of problems to be solved.”
“we're gauging people too much on what they have done versus what they can do.”
From the episode
Is Traditional Hiring a Broken System?