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 →

Ralph Goody no published score: no usable exchanges 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
0on raw tape
0redirected or not addressed
Answered produced feed D 5 · C 4 · P 4 · Cm 4 4.30

Q change topics to the right way to work with non-technical co-founders. Um, and I think the topic that came up most commonly in the Startup School Forum was the one that Ralph alluded to, which is how to deal with deadlines and timeframes, particularly with non-technical co-founders. Um, and I, I think particularly in the, in the early days. So does anyone have thoughts on that? Any, any orders? Good.

A I'll volunteer for this since my, my technical, non-technical co-founder is staring at me over there. Um, a few, a few ideas here. If you've got someone that's really non-technical, and I'm not saying my co-founder is really non-technical. I'm sure she can use a computer. Um, but you know, if it's really non-technical, this is an amazing testing opportunity for you. I mean, I remember I would write this software and I'd be so happy about it and I'd hand it to her. And as soon as she touched it, it would break. I mean, I don't know what she did. She shook the iPad, she rotated it three times, but she had a way to break the stuff I wrote, and, um, that was amazing for testing in the beginning, so that's one way to engage your non-technical co-founder. Um, you eventually have to learn how to start pouting your deadlines. That's really hard to do. I never got very good at this. I'm always optimistic. Even to this day, I'm like, oh yeah, it's gonna take me a week. So I never really got good at this. I'm just aware that I'm Optimistic about it, and then I'm always kind of off by a week, and she's aware of that as well. Um, so eventually I've talked to other engineering leaders that keep two books. They keep, like, a separate set of books they talk to their technical co-founders, non-technical co-founders about. Say, okay, here's the deadlines here, and then you have another set of bo…

AI assessment note: “You eventually have to learn how to start pouting your deadlines.”

page 1
Made with StarZero

Turn any episode into a week of clips.

This entire site, over 300 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.