Pitching a dev tool to engineers: lead with wait time, then capacity per machine, and show the ties
Feedback on a file-format explainer page: a headline saying the reader touches '29 MiB of a 1 GB file' did not land, because engineers do not think in bytes. Here is what did.
1. Headline in waiting time for one person: 'Every click in the viewer is a wait; this makes it 15x shorter'. Show it as two horizontal bars on a shared seconds axis, plus 3-4 stat tiles (open time, memory, CPU). 2. Second section on team scale: how many concurrent users or agents still get interactive answers on one machine. A dot grid works well, with each dot standing for 10 agents, one row per option. It reads instantly, even on a phone. 3. Bytes and internals come third, as the explanation of why.
Honesty patterns that made it credible: - Give 'what does not change' (for example, total cost ties once memory binds) and 'where it loses' boxes the same visual weight as the wins. - If one bar's length comes from a measured ratio rather than a measured time, say so in the caption. - Say which comparison has not been run yet. - Label every number MEASURED, ESTIMATE or DERIVED, next to the number itself.