The Audit

The episode introduces the Kolbe Index framework with clear explanations of how conative strengths differ from cognitive and affective dimensions, and provides concrete team examples showing how different Kolbe scores interact (e.g., Eric's quick-start vs. others' fact-finding). However, significant portions consist of definitions, repetitive explanations of the same concepts across different dimensions, and extended tangential stories (the furniture-building attorney, the CFO's 100-story building) that don't add operational insight. A B2B operator would learn the framework and how to apply it, but much of the content is expansive without being dense.

“The thinking cognitive, you know, how smart you are, what you've learned. Uh it's not about the what you feel, your emotions, your preferences. Um, and there are a lot of affective assessments...But the this cognitive part of the mind, the doing part, is the way we take action.”

“All things being equal, the teams that have a blend of Colby results of cognitive strengths do better than teams where there's just they kind of clone each other.”

The Kolbe Index itself is a proprietary framework with some differentiation from Myers-Briggs and other personality assessments, but the conversation relies heavily on repeating its core taxonomy rather than developing novel applications or challenging assumptions. The practical insights - that diverse teams outperform homogeneous ones, that hiring managers replicate themselves, that you must align work with strengths - are well-established leadership truths. The AI application discussion is forward-looking but underdeveloped. No significant contrarian or first-principles thinking emerges.

“We need these differences. All things being equal, the teams that have a blend of Colby results of cognitive strengths do better than teams where there's just they kind of clone each other.”

“a lot of leaders you see, they hire themselves over and over and over again, right? Their team is very homogenous.”

David Kolbe is the CEO of Kolbe Corp and grandson of the founder (his mother invented the Wonder Lick test), giving him deep domain expertise and organizational authority. However, he is primarily a thought-leader and assessment vendor rather than an operator who built something at scale in a different domain. His experience is narrow to his own product. The hosts (Eric, Josh, Nick, Jen) are IT security practitioners, which is more relevant to the audience, but they are secondary voices here. Kolbe's credibility is strong within his domain but limited beyond it.

“I co-wrote with Amy Brewski, the president of the company, uh Do More More Naturally.”

“Yeah, and that's part of why she got into what she got into...your grandfather started the wonder lick.”

The episode lacks hard data: no metrics, timelines, or financial figures are provided. Examples are mostly anecdotal (the CFO building a physical 100-story model, the attorney who builds furniture, a security engineer named Cam who likes cable management). While these bring color, they don't provide operators with measurable benchmarks. The team's own Kolbe scores are mentioned (e.g., 'Josh with a six, Nick also with a four') but never tied to specific outcomes or ROI. AI development is discussed conceptually without timelines, accuracy metrics, or concrete use cases.

“Our team, we are very diverse. We have very different interests and and our defaults are very different, but it's what makes us like push.”

“His presentation, he literally built a 100-story tall building to show where each percent of financing was gonna come for that project.”

The hosts ask reasonably targeted questions (e.g., 'Does this work fill your cup?', questions about hiring and team dynamics, the Johari window reference) and demonstrate genuine curiosity about Kolbe applications. However, few questions are sharp or probing; most are softballs that invite Kolbe Corp messaging. The hosts don't challenge Kolbe's claims - no one asks about failure rates, when Kolbe predictions are wrong, or evidence that the tool actually improves business outcomes. Follow-ups are absent; a question is asked, answered at length, and the next topic begins. Eric and Josh show some chemistry and call out observations, but these don't push back.

“Eric will always ask the question, like, but does this work fill your cup?”

“Have you thought about writing a book with with some of these things?”