In a large organization of any kind, your team will inevitably require input from other groups. You are dependent on others in ways you don’t have total control over, no matter how carefully you plan. While you slow down a bit every time you have to pick up the phone and get input, the bigger problem is that every roadblock increases the risk of getting stuck somewhere along the road.
You’re responsible for delivering an outcome. Yet, you can’t subvert the bureaucracy completely. If you need approvals or input, you can’t get to the finish line without them.
Or can you?
WASTE CAN WORK FOR YOU
One of my favorite ways to get past this no-win situation is to duplicate effort strategically. If you proactively design for a certain amount of this waste, you can plan in such a way that you can reach your goals even if other people don’t deliver.
While most people think of waste and inefficiency as inherently bad, when leveraged strategically, duplicated effort becomes a powerful tool you can use to guarantee outcomes.
You likely already build a buffer into your schedule to account for unknown delays. Using strategic waste goes beyond that common practice to cover the kinds of foreseeable situations that are very common in large organizations. This looks like deliberately duplicating suppliers, functionality, features, or even planning efforts as needed. (You’ll still want to add in margin for unknowns, over and above the allowance you’re considering here.)
In a worst-case scenario, how can you ensure your project reaches the finish line even if you don’t get the input you’re depending on?
STRATEGIC EFFORT DUPLICATION
Let’s say you’re building a software product. You know in advance that to take the software to market, you’ll have to be able to bill customers. (No matter how great your product is, if no one can pay you for it, you’ll fail.)
Your organization has a billing system they’ve spent the last 20 years developing. It handles all the complexity of billing in 82 countries. It’s a powerful tool, and your company has spent $200 million developing it. However, you’ve worked at this company for a long time. You know from experience that getting anything integrated into the company’s billing system will take a minimum of six months.
You also know that getting support for anything specific to your product—say, unit-based pricing—will be challenging, and you’ll have to advocate for any new features from week one to have any hope of getting them. So, start that process. Spend time filling out approval forms, advocating, and doing whatever it takes to shepherd that integration through the system.
However, it’s wise to be a realist. Going through the standard path might fail or take a year longer than the product does to launch. You’re still responsible for bringing that product to market, however. So, take other steps.
At the same time as you navigate the bureaucratic approval process, work on a full integration with a third-party payment API you can fully control, and start the process to advocate for a technical exception to the payment process.
HOLD ON, THAT’S WASTEFUL
This advice will result in two parallel efforts in your department working on the same task: the integration with your company’s core payment platform, and a separate effort building on a third-party solution.
A classic manager would pull the lever and stop the duplicative effort. If you know your company will make you integrate with the internal system, why would you duplicate that effort on a non-approved third-party billing system? One of the two paths will inevitably be waste, and waste is bad, right?
The reality is that nothing in your organization is carved in stone. The company’s billing system is not the natural law of gravity. Any policy inside your organization is more like a strong suggestion—it can be changed, if you find out who to talk to. Businesses are like dictatorships, and someone can change any policy for the right reason. I guarantee it.
PLAN ON POSITIVE WASTE
While a duplicative effort may appear to be wasteful, it’s actually positive waste. It acts as insurance. No matter what happens in your organization, at the end of the year, your product will be able to successfully bill customers and start bringing in cash.
My argument is that this duplication is not only acceptable waste, but necessary waste. If your product can’t die in its infancy, you must be able to bill. Therefore, if your company’s payment system will most likely fail at supporting your needs and timeline, you must have a secondary strategy in place that enables you to process a credit card from your paying customer.
Whenever your project or product is dependent on other groups for mission-critical tasks, you can use strategic waste as insurance. Carefully plan, and pay a premium in possibly wasted effort (perhaps 20% of your budget), so that your entire budget (100%) isn’t doomed.
Taking two paths to a single goal at the same time can help you to deliver success even when the odds are against it in your organization. To deliver the outcome no matter what, plan on waste.