The Exchanges

Every argument clarity score on this site is built from rows on this page. Each question and answer was assessed with names hidden, the host's own answers included, on four things from 1 to 5: directness (does it answer the question asked), coherence (do the ideas follow), precision (concrete details and clear references), compression (says a lot per word). The weighted mix (30/30/25/15) is the exchange score. A person's published score averages their exchange scores on raw tape only, at least 8 of them, shrunk toward the cohort mean. Full method →

Alexander Taubman no published score: only 1 usable exchange on raw tape, and a fair score needs 8+ record → ← everyone

Every exchange below was scored with names hidden, four dimensions each from 1 to 5. An exchange's score is 0.30·directness + 0.30·coherence + 0.25·precision + 0.15·compression. The published score averages the raw tape exchange scores and shrinks small samples toward the cohort mean, so five great answers can't beat twenty good ones. Produced feed rows count only toward coarse estimates, never toward a full score.

clear all ✕
1exchanges match
1on raw tape
0redirected or not addressed
Answered raw tape D 5 · C 5 · P 5 · Cm 4 4.85

Q And your engineers are just viewing your employees as their customers in some sense then. Is that correct?

A That's right. Our, our team views our employees and our team members in the field as the customer and that feedback loop internally. That's the, the other point is we have a much tighter feedback loop. So, you know, the, the old skunk works thing of you want the engineers and the factory to be co-located so you can have more innovation. That's what we have at Long Lake. So our team members and our engineers are together in the field all the time. I think there's our engineering team. They're probably in 20 different states right now, sitting with team members across our architecture business, across our HOA business, across our HR services, or You know, specialty tax business. And so they're sort of, um, and there's a deep amount of change management that's involved. So this is a lot of, you know, sitting with the team members, understanding their pain points. And so there's a real like solutions orientation of how do we take the pain point? We, and then we build a tool within Nexus to solve it. And that feedback loop is really important. So you get to better outcomes this way.

AI assessment note: “That's right. Our, our team views our employees and our team members in the field”

page 1
Made with StarZero

Turn any episode into a week of clips.

This entire site, over 100 episodes transcribed, diarized, checked and made playable, runs on the StarZero media pipeline. Drop in your own episode and the podcast clipper finds the moments worth sharing, cuts them, captions them, and reframes them for every feed.