This common idea (search it) that sometimes you need to “slow down to go faster” has come up many times throughout my career. What it essentially means in the web development context is that we sometimes need to slow down releasing customer facing features in the short-term to focus on internal processes that will eventually make our velocity much greater in the longer-term. This may include increasing unit test coverage, automating builds, deployments, and other pure DevOps measures to increase the overall flow of work through the product team.

The easiest way to tell when you need to slow down…

Zachary Keeton

A 12th-year web dev building products and leading teams at Plus One Robotics in San Antonio, Texas, USA

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store