Sound familiar? You’re standing in the boardroom. Your presentation is over. You’ve presented a technically sound plan for a new data platform or a crucial project to improve data quality. In your view, the business case is airtight. And then there’s silence. The executives nod politely, but their expressions are hesitant. There’s no “yes.” Instead, they say, “We’ll take it into consideration.”

You leave the room feeling frustrated. Why can't they see it? The plan is technically flawless, and the need for it is crystal clear.

The hard truth is that management rarely says “no” to a good plan. They say “no” to a plan they don’t understand in the language they speak: the language of business value, risk, and return. You didn’t “sell” the project because you used the wrong arguments.

Step 1: Stop selling data technology; start solving business problems

The biggest mistake an IT or data manager can make is selling the “drill” when senior management wants to buy a “hole in the wall.” You’re talking about the architecture of the data warehouse, while the CEO wants to know how it will help him make better decisions.

The first step toward gaining support is the translation process. Translate each technical data component into a concrete business value:

• Don’t sell a “data platform”; instead, sell “the ability to steer the sustainability effort with factual insight into the condition of our real estate.”
• Don’t sell “master data management”; instead, sell “preventing lost rental income by ensuring that new construction is entered correctly into the systems right away.”
• Don't sell a "central data warehouse"; instead, sell "an end to the endless debates about whose numbers are correct, so that meetings can focus on the content again."

By prioritizing business value, you shift the discussion from a technical data expenditure to a strategic information investment.