Verified, Then Trust
Earn delegation by examining ground truth alongside the people doing the work
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 95%
Verified, Then Trust is a delegation model in which leaders establish enough firsthand understanding to judge work intelligently before granting broad autonomy. Verification means following claims to primary evidence: reading support tickets, examining data definitions, understanding operational procedures, querying code, and working alongside the responsible team. It is not a demand that the leader know every implementation detail or preapprove every action. Instead, the leader maintains broad context across the organization and goes deeply into selected high-priority areas, creating a T-shaped view of the business. Once the leader understands the mechanics and has observed the owner's judgment, delegation becomes informed trust. Periodic returns to ground truth keep that trust calibrated and make product reviews collaborative searches for the right answer rather than performances designed to secure approval.
Origin
Extracted from Lenny's Podcast, where Tom Verrilli contrasted Whatnot's approach with the maxim to hire great people and simply get out of their way.
Core principles
- 01Trust capable people without abandoning managerial understanding
- 02Verify through primary evidence rather than review theater
- 03Combine broad organizational context with selective depth
- 04Treat reviews as joint truth-seeking
- 05Delegate decisions only from an informed baseline
How to run it
- 1
Choose the Critical Area
Select the outcome or system where leadership understanding materially affects resourcing or decision quality. Focus verification on a small number of company priorities.
- 2
Follow Claims to Their Source
When a team cites a metric, label, customer problem, or system behavior, inspect how that evidence was produced. Continue until the decision-relevant ground truth is clear.
- 3
Work Alongside the Team
Join the team in examining tickets, data, code, and operational logic. Make the investigation collaborative rather than a remote demand for another presentation.
- 4
Establish the Baseline
Confirm that the leader and owner share an understanding of the mechanism, constraints, and desired result. Surface disagreements before delegating the next decision.
- 5
Delegate With Calibrated Trust
Give the informed owner room to execute while remaining available for consequential decisions. Refresh the leader's understanding as the system changes.
In the wild
A growth discussion treats a cohort as fraud because the dataset labels it that way. Leadership asks how the label is assigned, who applies it, and what standard operating procedure they follow. When the team cannot answer, it investigates the labeling pipeline instead of treating the field as ground truth, potentially strengthening both the analysis and the operational system.
→ The decision rests on verified evidence, and the underlying data process improves.
When Whatnot's CEO believes a review is wrong, he may clear the rest of his day and work with the team through support tickets, code, and data line by line. The group seeks the correct answer together rather than sending a document through another review cycle.
→ Leadership stays current, teams receive grounded feedback, and review becomes collaborative problem-solving.
Common mistakes
Confusing Verification With Micromanagement
Verification uses shared ground truth to improve decisions; uninformed direction from above is the behavior the model is designed to avoid.
Trusting Labels as Facts
Metrics and classifications are only as reliable as the definitions and operational processes that produced them.
Delegating All Detail
A leader who never understands the micro-level mechanism cannot reliably make macro-level resource and strategy decisions.
Is it for you?
Best for
It is best for senior leaders overseeing complex products who can selectively investigate the highest-priority systems in depth.
Not ideal for
It is not ideal for leaders who lack the time, technical access, or humility to investigate details collaboratively.
From the transcript
“But we tend to live in a verified then trust land as opposed to a like totally trust or even trust but verify”
“Let's literally pull up the tickets, let's literally pull up the code, let's like go through the data line by line and understand what's actually…”
“So you can't make good macro decisions without the micro.”
From the episode
This CPO regrets that product management exists