There’s a huge disconnect between the business world and the engineering world that drives our software projects into the ground. We rewrite our software over and over again, not because we lack the engineering skills to build great software, but because we fail to communicate, make decisions in ignorance, and don’t adapt when the current strategy is obviously failing.
A friend of mine drew this picture on a napkin, describing “the problem to solve” which I thought captured our challenges perfectly. This is the biggest cause of failure in our industry:
Our problems are invisible. They’re hard to measure and explain. The pressure to deliver features doesn’t let up. The result? We fail to communicate, make decisions in ignorance, and can’t seem to take our foot off the accelerator pedal even when our project is headed for the wall.
But what if we could measure the indirect costs of pain building up on a software project? What if we could measure the loss of productivity, the escalating costs and risks, and could steer our projects with a data-driven feedback loop?
Visibility Changes Everything.
Once we can measure the indirect costs of pain building up on a software project, and we can see that over 50% of the team’s capacity is spent dealing with problems, suddenly spending 80 hours on a task that saves almost 700 hours a month, is an obviously important investment.
With visibility, we can bridge the gap between the business world and the engineering world, and get everyone pulling the same direction.