The bottleneck was never typing speed. We just found a more expensive way to prove it. That's the line we kept coming back to in the weeks after we shipped this, mostly because it kept being true in ways we hadn't fully clocked at the time.
Nobody on the team set out to learn this the hard way. We had a plan, a reasonable-sounding rationale, and a rollout timeline everyone nodded along to in the planning doc. It's the kind of thing that looks fine in a slide and falls apart the first time it meets a real workweek.
What actually changed things wasn't a new tool or a bigger budget: it was admitting, out loud, that the thing we'd been optimizing for wasn't the thing that mattered. That conversation was uncomfortable. It was also about two quarters overdue.
If you're in the middle of something similar right now, the advice we'd give ourselves six months ago is simple: the metric that's easiest to report on is rarely the one worth chasing. Figure out which one actually moves the business, and be honest about the gap between the two.
The bottleneck was never typing speed. We just found a more expensive way to prove it.