The board meeting is next week. You need to present an update on SAP.
You prepare slides about system uptime, tickets resolved, projects delivered, and milestones achieved. You explain the migration timeline, the go-live success, and the current backlog.
The board listens politely. Then someone asks: "So when do we see the return on this investment?"
The room goes quiet. Not because you don't have an answer. But because the answer isn't in your slides.
The gap between what SAP teams report and what the board wants to hear
Most SAP updates to the board focus on activity. What was done. What was delivered. What's in progress.
The board thinks in outcomes. What changed for the business? What's faster, cheaper, or less risky than before? When will the investment pay for itself?
These are different conversations. And the disconnect creates friction.
The SAP team feels undervalued. They delivered a complex migration on time. They keep the lights on. They solve problems every day. And the board doesn't seem to appreciate it.
The board feels uncertain. They approved a significant investment. They were promised efficiency, speed, and better data. And the update they receive tells them about system uptime and open tickets.
Neither side is wrong. They're just measuring different things.
What the board actually cares about
Board members, regardless of industry, consistently care about three things when it comes to technology investments.
Financial impact. Did the investment reduce cost? Did it increase efficiency? Can you quantify the savings? The board wants numbers, not stories. If month-end close went from eight days to five, that's a number. If the team eliminated 40 hours of manual reconciliation per month, that's a number. If error rates dropped 60%, that's a number.
Risk reduction. Did the investment make the organisation more resilient? Are there fewer audit findings? Are there fewer production incidents? Is the organisation less dependent on key individuals? Risk isn't abstract for the board. It translates directly to cost, reputation, and regulatory exposure.
Strategic readiness. Is the organisation in a better position for what comes next? Can it scale? Can it adopt new technology? Can it respond to market changes faster? The board doesn't care about technical architecture. They care about whether the platform enables or constrains the business.
How to build the right update
The shift isn't complicated. It requires tracking different metrics and presenting them differently.
Define outcome metrics that matter to the business. Not system metrics. Business metrics. Processing time for key processes. Error rates in critical workflows. Time spent on manual work versus value-adding work. Number and severity of audit findings. Hours saved per month through automation.
Baseline before you optimise. Before you automate a process or implement an improvement, measure the current state. How long does it take? How many errors occur? How many people are involved? Without a baseline, you can't show improvement. And without showing improvement, you can't demonstrate ROI.
Show trends, not snapshots. A single number is a data point. A trend is a story. The board wants to see direction. Month-end close was eight days in January, six in March, five in May. That trend tells a story of continuous improvement. It builds confidence that the investment is paying off.
Connect automation results to business language. Don't say "we automated the reconciliation process." Say "monthly reconciliation now takes four hours instead of three days, freeing finance to focus on analysis instead of data chasing." The result is the same. The language makes it land.
Be honest about what's left. The board respects transparency. If there's a gap between the promised ROI and current reality, acknowledge it. Explain what's being done to close it. Show the plan. A credible roadmap with early results is more convincing than over-optimistic projections.
The conversation you want to have
Imagine walking into the boardroom with this:
"Since go-live, we've reduced month-end close by three days. Manual reconciliation that used to take 120 hours per month now takes 15. We had zero audit findings on automated controls last quarter, compared to four findings the year before. The team has capacity to focus on the next round of improvements, and we expect to deliver another 30% efficiency gain in Q3."
Nobody asks about system uptime after that. They ask what's next.
That's the conversation every SAP team should be having with their board. Not defending the investment. Demonstrating the return.
At Boundaryless, we help SAP teams build the automation results that make these conversations possible. Not slides. Outcomes.