When different teams in an organization review requests to sign off on new investments in technology, some are quicker to convince than others. While sales teams might green-light new tech right away if they are looking to close a deal, a legal team may have a slower approval process.
“Teams incentivized by growth, speed, and experimentation — such as product, R&D, marketing and sales — are generally the easiest to convince because they readily adopt tools that remove bottlenecks and help them hit targets faster,” says Rob Enderle, principal analyst at the Enderle Group. “Conversely, gatekeeper teams like information security, legal, compliance, finance, and IT operations are much harder to win over because they are measured on stability, budget discipline, and risk mitigation.”
Lukas Alexander, vice president of customer success at ChurnZero, an AI-powered customer growth platform, says a department may begin developing a tech application without obstacles, but when they need approval from legal or input from the cybersecurity team, that’s when they get stuck.
Other challenges occur when a key champion or decision-maker for a tech tool leaves the company, and the application sometimes leaves with them, according to Alexander.
“A tool with one champion is a single point of failure,” he says.
Here, experts provide some guidance on how to win over multiple teams on new tech.
Clearly Address a Business Problem
More stakeholders are likely to approve a new tech tool if it clearly addresses a business challenge, explains Russell Jukes, chief digital information officer at DXC Technology, an IT services provider.
“Teams struggling with a clear problem are usually the most receptive to new tech because they are already looking for help and can see how new technology might relieve that pressure,” Jukes says. “It is harder to gain buy-in from teams that believe their current approach is working well, since the change can feel imposed without an obvious benefit.”
Factor Governance and Security Into Application Design
When getting cross-functional buy-in, organizations should incorporate enterprise governance and interoperability considerations from the start so they can win over compliance and security, Enderle advises.
He adds that incorporating retrieval-augmented generation, Okta single sign-on and automated personally identifiable information (PII) redaction can boost chances of getting approval from compliance and security.
Companies should also incorporate security engineers into the demo process of new software to catch compliance blockers before the product launches, Enderle adds.
Build Financial Literacy
Tech professionals should become financially literate and master stakeholder management so they’ll be able to close enterprise deals rather than relying on technical skills alone, Enderle advises.
“For example, an engineering lead who knows the difference between capital and operating expenses can structure a hardware-plus-software pitch to fit cleanly into an existing cloud OpEx budget rather than triggering a freeze on new CapEx equipment purchases,” he explains.
Tech professionals should be sure to get sign-off from the executive sponsor as well as the finance and procurement teams. Alexander cited HR tech as an example. A winning strategy would be to get multiple departments to pay the bill for that product rather than just HR, he explains.
Coauthor Projects
Find a finance analyst to coauthor a return-on-investment spreadsheet for an upcoming server migration, Enderle advises. They can also sit in with product managers during quarterly budget prioritization meetings and listen in on InfoSec threat-modeling reviews so they learn what questions they need to ask executives when seeking approval for funding projects, he says.
Create Interoperability With Existing Systems
If you’re looking to get approval for new IoT sensor data, route the data directly into enterprise systems the company already uses, like SAP or Salesforce. This strategy bypasses compliance blockers because the flagship platforms have already passed security, auditing and regulatory reviews, according to Enderle.
“When an engineering team tries to spin up a brand-new, stand-alone database or custom cloud dashboard to collect factory sensor data, IT operations and compliance have to halt the project to audit how that new system handles user passwords, data backups, cybersecurity patches, and regulatory reporting,” he says.
If engineers roll out the design of a new warehouse temperature sensor and feed the data right into an SAP environment through a standard interface, the data acquires SAP’s preapproved access control settings, encryption and audit logs. Therefore, security and IT can approve deployment in days instead of months, Enderle notes.
Reduce Risk for Tech Projects
When seeking buy-in on new technology, tech professionals must show how they can reduce risk for business leaders while also increasing margins and growing revenue, according to Jukes.
Enderle explained how tech professions must “derisk” new technology.
“De-risking with a proof of concept means removing the fear of a costly, irreversible mistake by testing the technology in a small, controlled sandbox before asking for a company-wide commitment,” Enderle explains. “In an enterprise setting, leaders often reject new tools simply because they fear a rollout will break existing workflows, go over budget, or fail to deliver on vendor promises. You eliminate this anxiety by setting strict boundaries around time, budget, and data exposure, alongside pre-agreed success metrics and a one-click exit strategy.”
Tech professionals can request $10,000 for a 30-day period to run a new tool for a single 10-person team rather than asking for $500,000 to replace an analytics platform across a company, he says.
“If it does not reduce reporting time by at least 20% by day 30, you unplug it with zero disruption to the daily business,” Enderle adds.
Tech professionals can get buy-in on new projects with the right mix of low-risk strategy and an eye on compliance and security.