DEV Community

Cover image for Remove the step, don't speed it up
Pratyush Shivam
Pratyush Shivam

Posted on

Remove the step, don't speed it up

I'm Pratyush Shivam, CTO of Konfidio in Berlin, where I lead the technology behind TrustedTrucks. One rule I keep coming back to in product work is short enough to fit on a photo: remove the step, don't speed it up.

The pull towards faster

When a process feels slow, the request that reaches engineering is almost always "make this faster": a quicker form, fewer clicks, a shorter loading time. Those requests are reasonable, and sometimes they're exactly right. But they share an assumption: that the step should exist at all.

Ask why the step is there

Before optimising a step, I try to ask three questions:

  1. Who needs the output of this step, and what do they do with it?
  2. Is the same information already somewhere else?
  3. What would break if the step disappeared tomorrow?

Often the answer to the second question is yes. The information exists, but in another system, or in another company's system, so someone copies it across by hand.

A freight example

On a single shipment, several companies handle the same facts: the order, the delivery details, the proof of delivery, the invoice. Each keeps its own copy, so the same details get typed again at each hand-off, then checked against each other when something doesn't match.

You could make each of those forms faster. Or you could give everyone on the shipment one shared, verifiable record, so the details are entered once and everyone reads the same version. The second option doesn't speed up the retyping. It removes it, along with most of the reconciliation that came with it.

When speeding up is the right call

Not every step can go. Some exist for good reasons: a legal requirement, a real decision a person has to make, a safety check. Those deserve to be fast and clear. The point isn't to delete everything. It's to make sure the step you're optimising earns its place.

The takeaway

Next time someone asks for a faster version of a task, ask why the task exists first. The best improvement is often a step nobody has to do anymore.

More of my writing is at pratyushshivam.com.

Top comments (0)