Episode Story
Logan Yonavjak on Measuring Founder Readiness
Logan Yonavjak explains Readiness Engine, vertical development, coachability, and language-based leadership assessment while Dalton tests the method and its limits.
Logan Yonavjak on Measuring Founder Readiness
Logan Yonavjak is trying to give investors and organizations a more structured view of leadership capacity. Instead of asking a person to choose from fixed personality statements, Readiness Engine analyzes how that person explains real decisions, pressure, feedback, tradeoffs, and complexity.
In episode 104 of Venture Step, Dalton Anderson takes the interview-based assessment and then asks the harder question: when does a structured signal improve judgment, and when does it turn uncertainty into a score that looks more certain than the evidence?
That question matters more than the novelty of the AI.
Founder Readiness Institute became Readiness Engine
The episode was recorded under the Founder Readiness Institute name. The organization now operates as Readiness Engine. Its current media page explicitly identifies Founder Readiness Institute as the prior name.
The current company describes Logan Yonavjak as co-founder and CEO and Benji Whitehurst as co-founder and CTO. It has also moved beyond a founder-only position toward leadership development, succession, promotion readiness, coaching, teams, and investors.
The historical name should stay attached to the episode. The current name should control profiles, URLs, policies, and present-tense product descriptions.
Dalton took the assessment without receiving the result on air
Dalton describes a guided interview with open questions, examples, and time limits. He says the structure encouraged detailed stories about decisions and work. He does not disclose the private questions.
The transcript records his experience taking the assessment. It does not contain his result. Any public page that assigns him a level, score, stage, strength, or weakness would invent evidence.
Yonavjak shares her own score in the interview and describes feedback about making her decision frameworks more visible to her team. That is her account of a developmental conversation. It is not an independent validation study.
The company reads structure in language
Readiness Engine's current methodology page says it looks for perspective reach, tension handling, evidence discipline, and the ability to coordinate scale and time. It says ratings are tied to verbatim evidence and a written rubric, with AI calibrated against expert human scoring and human review on edge cases or final candidates.
The current site presents six leadership dimensions: strategic complexity, relational and emotional intelligence, team climate, resilience under fire, purposeful agility, and coachability with identity flexibility.
flowchart TD
A["Consented interview or real-work language"] --> B["Evidence excerpts"]
B --> C["Rubric and AI-assisted pattern analysis"]
C --> D["Human calibration or review"]
D --> E["Developmental range and growth edge"]
E --> F["Human judgment and development plan"]
This is the company's public description, not an independent reconstruction of its proprietary instrument.
Vertical development supplies the theory
Yonavjak distinguishes learning more skills from changing how a person makes sense of complexity. The first is often called horizontal development. The second is often called vertical development.
The underlying literature includes constructive-developmental theory, ego development, action logics, hierarchical complexity, dynamic skill, and integrative complexity. These are related traditions, not one universally accepted scale.
Readiness Engine cites Robert Kegan, Susanne Cook-Greuter, Jane Loevinger, William Torbert, David Rooke, Michael Commons, Kurt Fischer, Peter Suedfeld, and Philip Tetlock. Its methodology says the proprietary contribution is the interview, scoring anchors, calibration, and reports.
Evidence that adults differ in meaning-making complexity does not automatically validate one vendor's inference from a transcript. The construct and the measurement method need separate support.
Coachability is not agreement
One of the strongest moments in the episode is the discussion of feedback without identity collapse. A founder may hear criticism of code, a pitch, or a process as criticism of the self. Development can involve seeing oneself as one part of a larger system.
That does not mean the coachable person accepts every recommendation. Good feedback can be rejected for good reasons. The better signal is whether the person understands the advice, examines its evidence, tests it where appropriate, observes the result, and updates the decision.
Recent workplace research treats coachability as a multi-part construct. A 2021 Coachability Scale study developed measures across four samples and called for more research across cultures, populations, behaviors, and outcomes. A 2024 situational judgment study followed participants for nine months and provided initial validation for a different assessment route.
The field has measures. It does not support treating one polite interview response as a permanent trait.
Standardization does not remove bias by itself
Yonavjak argues that a structured tool can add information to warm introductions, references, pedigree, charisma, and investor instinct. The interview also includes claims that current venture selection excludes people and that people problems drive company failure.
Those claims need exact datasets and methods. More important, a standardized process can reproduce bias through the construct, training data, language expectations, interview conditions, scoring rubric, population, threshold, and human use.
Readiness Engine's current methodology says accent, verbal polish, and storytelling style are excluded as evidence. Its Trust and Ethics page says models are audited for bias and assessed people have consent, access, and deletion rights.
Those are valuable commitments. A buyer still needs population-level results, subgroup definitions, uncertainty, sample sizes, audit methods, accommodations, error analysis, and ongoing monitoring.
The current company position is more bounded
The most important current disclosure appears on the methodology page. Readiness Engine says the instrument is early in development and initial validation. It says it is not validated for selection decisions and is intended for developmental use.
The site's FAQ says it should not decide who gets hired or promoted. The methodology says it is not designed or validated as the sole basis for hiring, promotion, termination, or other employment decisions.
The April 2026 privacy policy contains a three-tier model and says the human-reviewed tier is required when an output is used as a basis for consequential decisions, including investment selection.
These documents need to be read together. Human review does not convert an unvalidated measure into a validated selection tool. It can reduce automation risk and add context. It cannot supply missing evidence that the score predicts a decision-relevant outcome for the intended population.
The assessment handles sensitive inferences
The privacy policy says assessment inputs and outputs may reveal psychological and developmental characteristics. It describes video interviews, transcripts, scores, profiles, stage classifications, consent records, and audit trails. It names Google Cloud Platform, Willo, Vercel, and n8n as subprocessors.
The policy says identifiable data is not used for model training without separate consent. It also gives participants access, correction, deletion, contest, and human-review rights under described conditions.
That privacy record is unusually detailed for a young assessment company. Buyers still need to verify actual configuration, retention, contractual roles, security controls, client handling after the vendor returns a result, and what happens when consent is withdrawn.
The episode lands on the right role for the tool
Near the end, Yonavjak describes the company as providing another source of professional input rather than making the decision. Dalton calls it a leadership evaluation mediator.
That is the defensible starting point. A developmental assessment can help a leader name patterns, create a coaching agenda, or compare self-perception with structured evidence. It may still be unsuitable as a gate for employment, promotion, funding, admissions, or program access.
The burden is use-specific. The buyer must define the construct, population, decision, consequence, evidence, consent, fairness checks, appeal, and human authority before the first assessment.
The [[How to Evaluate an AI Leadership Assessment|AI leadership assessment buyer guide]] provides that review. The [[Can Coachability Be Measured|coachability analysis]] separates learning behavior from compliance.
AI assisted with research organization and drafting. Dalton Anderson remains responsible for the analysis, source boundaries, and publication decision.
Sources
Follow the evidence.
- multi-study workplace scaledoi.org
- Coachability Scale studydoi.org
- guidance on employment tests and selection procedureseeoc.gov
- NIST AI Risk Management Frameworknist.gov
- Leadership Quarterly review of constructive-developmental theorydoi.org
- situational judgment studydoi.org
- Readiness Enginereadinessengine.io
- media pagefounderready.io
- privacy policyreadinessengine.io
- termsreadinessengine.io
- recommendations for AI-based employee selection assessmentssiop.org
- Uniform Guidelines clarificationeeoc.gov
- methodology pagereadinessengine.io
- Trust and Ethics pagereadinessengine.io