Scan Before Deciding
Core Concept
Don’t jump to conclusions. Read the full landscape before making recommendations. Thoroughness earns trust; premature recommendations erode it.
The Pattern
You’re dropped into a new situation with lots of information. The temptation is to quickly scan a few key files/signals and make a bold recommendation. But incomplete scans lead to wrong assumptions, and wrong assumptions lead to plans built on fiction. The first session’s recommendations set the tone — if they’re grounded in thorough analysis, trust builds fast. If they’re built on assumptions that get corrected (“hosting migration is already done,” “I’m actually full-time”), credibility takes a hit.
Where I’ve Seen It
- Show Notes (Feb 2026): CEO’s first session scanned 80+ product ideas, 10+ projects, personal OS, and career context before proposing Show Notes as the company. The thoroughness earned trust. But three major assumptions were still wrong (hosting done, full-time capacity, Stripe ready) because the scan read files but didn’t verify with Dave. Lesson: scan artifacts AND verify facts with the human.
- General principle: Any new role, project, or engagement benefits from a “listen first” period. The OrangeQC turnaround started with 1:1s and observation, not mandates.
The Countermeasure
- Scan before recommending. Read the full landscape — files, people, context — before proposing a direction.
- Verify facts with humans. Files can be stale. Artifacts can be misleading. Always confirm assumptions with the person who knows.
- Name your confidence level. “Based on what I’ve read…” is more honest than presenting assumptions as facts.
- The first recommendation is the most important. Get it right, even if it takes longer.
Related Patterns
- Decisions-Get-Records — Once you’ve decided, record why
- Validate-Before-Building — Strategy without validation is fiction (same principle, different domain)