The step that decides whether a new tool survives your first fifteen minutes is rarely the tool itself; it is the one step you end up doing twice.
I keep running into the same pattern when I time a first-run session: the total elapsed time tells you almost nothing useful, because a single clumsy step quietly pays for itself three or four times. You sign in, you get bounced, you sign in again, and now the clock has doubled while the step count barely moved. Wouldn't it be better to measure the rework instead of the wall clock, since rework is the part you can actually delete?
So that is what this teardown does. I am going to walk through a small friction log that records each step, its duration, its exit code, and whether you had to redo it, and then I will show the one fix that mattered in the walkthrough I use below.β¦