Decision & Learning Process
Iterative Decision-MakerThe 60% Rule
Executive Summary
Josh operates at the 60% certainty threshold - sufficient confidence that the directional vector is correct and risks are mapped, but accepting of iteration-driven refinement. He's not afraid of small, consistent failures in the process as long as the overall direction has strong ROI potential. The goal is to avoid operational debt, decision debt, and technical debt without over-analyzing.
The 60% Rule
Critical insight: Josh operates at ~60% certainty, not 100%. The 60% threshold means enough information to know you're headed in the right direction. Primary concern: 'Did we cover our risks and bases?' After 60%, it's time to execute and use feedback loops for iteration. Goal: Avoid operational debt, decision debt, and technical debt without over-analyzing. Why this works: He's not afraid of small, consistent failures in the process as long as the overall direction has strong ROI potential.
Decision Validation Process
How Josh validates decisions before committing:
- Confirm a real problem exists
- Assess who experiences pain and at what intensity
- Evaluate if market already attempts to pay for solutions
- Calculate ROI potential
- Map risks versus upside
Confidence to Commit
What gives Josh confidence: Clarity that there's real ROI, having done the work upfront (his rigorous analysis process), and having a feedback mechanism in place for iteration. Decision pattern: Commits to fewer ideas overall. When he commits, goes all in. Not anxious about being first. More focused on having covered risks and validated ROI.
Problem-First Filter
When hearing a new idea or solution, Josh immediately asks:
- What actual problem does this solve?
- Who is facing this problem?
- How painful is it?
- How many people/companies face it?
- Are they already trying to pay to solve it?
- Do they know they have this problem?
Information Scanning Approach
How his attention moves when exploring a topic: Scans rapidly (hates videos because he can't control pace; prefers transcripts). Pattern recognition - looks for common patterns across systems, problems, solutions. Seeks the delta - 'What's new? What's different? What's the aha moment?' Skips the setup - doesn't need code details or formulas. Wants the concept - what did you do differently? What's your unique approach?
Flow State Triggers
Signs Josh is in flow and what triggers it:
- Triggered by: challenging work with measurable impact
- Triggered by: autonomy to design approach
- Triggered by: big-picture contribution visibility
- Triggered by: rapid feedback loops confirming value creation
- Physical manifestation: hunched posture, multi-hour deep focus sessions
- Emotional state: excitement, energy, sense of being close to breakthrough