The 15 Minutes Rule To IT Success

Are you puzzled by the ability of small tech startups like Frank and Oak to out-innovate their competition? What’s their secret?

These new leaders play by the 15 minutes rule!

If you are waiting more than 15 minutes for anything, someone broke your ability to turn cash into code, to productize this code into features, and to convert those features into value.

These newcomers are much quicker at improving their digital platforms, delivering new features almost daily. Many well-known brands, which have been in business for longer, are way more prominent and have more money, all seem stalled in a previous era.

We can confirm, from the technical audits we perform for our customers, that inertia is usually the primary cause of late or over budget projects. You can quickly get bogged down by accepted practices, which often introduce lead times in your delivery process.

friction diagram

Some of the most common causes of delays are:

  • Stampings from the architecture committee

  • Controlled access to restricted documents, VPNs, production servers

  • Provisioning of hardware and accounts by a dedicated team

  • The centralized release of core libraries by the framework team

  • Jim, the hero, who’s the only one on your squad who knows how to configure or build or deploy that critical microservice

  • Gatekeepers such as PR reviewers

  • Procurement authorization for licenses and tools

  • Corporate credit card numbers are necessary to create a new account somewhere

Lost velocity is terrible but delayed time to market is worst. It can kill your product if the competition gets there first. Your startup could also merely die from lack of cash flow.

A customer of ours, who had tenures as director, VP, and CTO of many high tech companies, including Amazon, once told us that his main focus has always been to reduce friction.

reduce the friction diagram

Delays are often introduced by middlemen with little-added value today, once they get replaced by automated processes such as continuous integration, configuration as code, automated testing or autonomous DevOps teams.

Be on the lookout for anyone saying that they have been waiting for something or someone for more than fifteen minutes. These are opportunities for change.

More often than not, this will require a cultural shift, even if processes or technologies are involved.

I’ll stop here. Someone has been waiting for me to finish this blog post for the past 15 minutes!

Be the Revolution!

Remy Gendron.jpeg


by Rémy Gendron, founder at INGENO

Learn more about us, how we build software and how we help companies deliver business value at