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 →

Laura Behrens-Wu 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 5 · P 4 · Cm 4 4.60

Q Right. But that's still the part that is aimed towards developers. And then you're saying that you build dashboards on top of that for everybody else in the business who needs to get what they need. So talk to me about that, because I'm actually very interested in the design And UI aspects of APIs and everything around it?

A Yeah. So we've built a dashboard that just reflects everything that happens through the API in the dashboard as well. It's not meant as the primary way to access Shippo, but you're able to see whatever's going on through the API. And it's for operations people to access the shipping data, for finance people to access the shipping costs and all that stuff. And then also for customer support people to know what's going on with the packages, where they are. Because when people start writing in about my package is lost, it's damaged, whatever. Customer support people need to be able to go into the dashboard and figure out the tracking information. So that's very Shippo specific. On a high level, I'd say, like, it's just important to figure out what are the other stakeholders in the company that need to interact with the data, and how can we make it available to them without the developers having to build custom dashboards for that company.

AI assessment note: “we've built a dashboard that just reflects everything that happens through the API”

page 1
Made with StarZero

Turn any episode into a week of clips.

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