The "So What?" Test:
Proving Technical ROI to Non-Technical Executives
You’ve been there. (Or if you haven’t, you can be sure you will be in the future).
You walk into your one-to-one with your director, proud of what your team has accomplished. “It was a great week,” you report. “We deployed the new CI/CD pipeline, resolved 50 high-priority customer issues, or cleared the entire backlog of P2 tickets.”
It doesn’t matter what the specific tasks were—customer issues, demos delivered, onboarding completed—they are the time-consuming, necessary lifeblood of your team. It’s important work. Right?
You wait for the praise. You wait for the validation. Instead, you get a polite nod, a quick subject change, or worse—a simple, off-putting question:
“So what?”
That question can feel like a punch to the gut. It feels dismissive of your team’s hard work. After all, these are the things your team does to keep the wheels on the bus. But what if it isn’t intended to be a punch to the gut? What if it’s an invitation?
For new leaders in tech, this is the defining moment where you realize that the skills that got you promoted are not the skills that will make you successful. Your technical expertise got you the job. Learning how to communicate technical outputs to non-technical stakeholders is what will get you influence, a bigger budget …and your move towards the next promotion.
It’s time to stop working harder, and start translating smarter.
The API Between Brilliance and Business
In many tech cultures, there’s a healthy scepticism of “corporate speak.” The idea of applying business acumen for tech leaders can feel uncomfortable—like you are translating your team’s elegant, complex work into bland metrics that miss the point. It can feel like selling out.
Let’s reframe that.
Think of yourself as building a powerful API. Your team produces brilliant, high-performance code, provides world-class support, delivers high-quality demos, or builds resilient infrastructure. That’s one side of the system. On the other side is the business, which runs on the language of strategic goals: revenue growth, risk mitigation, and market share.
You are the API.
Your job is not to shield your team from the business, nor the business from the tech. Your job is to create a clean, efficient, and reliable translation layer. You are responsible for translating technical outputs to business outcomes, much like the DORA research program has statistically proven that software delivery performance drives organisational performance.
When you do this, developing business acumen stops being a chore. It becomes your most powerful tool to protect and empower your team. It’s how you turn your department from a misunderstood “cost center” into a recognized “value creation engine.”
The Three Words That Will Change Your Career:
Outputs, Outcomes, and Impact
The “So What?” question is simply a request for translation. The reason it’s so hard to answer on the spot is that most of us are trained to report on Outputs.
To master strategic thinking for technical leaders, you must distinguish between three distinct levels of communication:
1. Outputs (The "What")
An Output is what you did. It’s the tangible result of your team’s work.
- “We deployed a new feature.”
- “We refactored the legacy authentication module.”
These statements are accurate, but they carry no inherent business value. As Martin Fowler explains, unless you frame this as paying down the ‘financial interest’ on your code to speed up future delivery, executives will only see the cost, not the investment.
2. Outcomes (The "So What?")
Your director, however, likely thinks in terms of Outcomes. An outcome is what changed as a result of your output. It’s the direct functional consequence.
- “Because we deployed the new feature, users can now complete the checkout process in half the time.”
- “Because we refactored the auth module, login errors have dropped by 90%.”
This is better. It shows improvement. But to truly secure resources, you need to go one step further.
3. Impact (The "Why It Matters")
Truly indispensable leaders speak the language of Impact. Impact connects the outcome to a strategic goal. It is the ultimate method for proving technical ROI.
- “By making the checkout process faster, we reduced cart abandonment by 15%, which is projected to increase Q4 revenue by $50,000.”
- “By fixing the auth module, we eliminated a top churn risk for enterprise clients, safeguarding $1M in annual recurring revenue.”
See the difference?
- Output: We did a thing.
- Outcome: The thing we did made something better.
- Impact: The thing that got better is driving a key business objective.
Once you master this translation, you’ll never fear the “So What?” question again. You’ll welcome it.
Strategies for Aligning Technical Teams with Business Outcomes
Developing this skill requires practice. It requires you to look at your Jira board, your CRM or your demo pipeline not just as a list of tasks, but as a portfolio of investments. Here are three strategies to start building this muscle:
1. Start with the "Why" in Team Meetings
Don’t just assign tickets or delegate tasks. Explain the business context. Make that part of how your team interacts together. This is one of the early steps of transformational leadership. When your team understands the desired business impact they often find better solutions to achieve it. This embeds strategic thinking for technical leaders directly into the daily stand-up or team meetings.
2. Stop Reporting Activity, Start Reporting Progress
Review your weekly status emails. Are they lists of “Done” tickets? Try grouping them under business objectives. Instead of “Front-end updates,” try “Initiatives to Improve User Retention. Instead of “Delivered 15 customer demos,” try “Onboarded 5% more upsell pipeline opportunities”.
3. Use the Right Framework
You need reliable tools for translating technical outputs into actionable business insights. You shouldn’t have to invent a narrative from scratch every time you enter a meeting.
Make It Your Superpower
This mindset shift is the one of the most important steps in your transition from a technical expert to a business leader – a strategic business leader. It’s how you stop talking about being busy and start talking about being valuable.
It’s how you justify headcount, fight for a bigger budget, and ensure your team’s incredible work gets the visibility and credit it deserves.
Ready to build your API?
I’ve created a simple but powerful template to help you practice this translation. You’re welcome to download it free.
It includes a one-page worksheet and a 3-part email mini-course designed to help you turn your team’s weekly wins into powerful narratives that resonate with executives.
Stop reporting on your work. Start communicating its impact.
Related Topics
Check Out More Insights from the Leadership Ethos Substack
Real-world leadership is nuanced. On the Leadership Ethos Substack, I share regular insights, practical frameworks and reflections on the challenges facing modern tech leaders.
- Navigating External Uncertainty With Inner Clarity
by Damien Mulligan on August 22, 2025 at 9:55 amLearn to navigate uncertainty by building team adaptability and cultivating your emotional intelligence. A practical guide for new leaders to thrive in a VUCA world.
How I Support Leadership Development
If you are a new or recently promoted tech manager, you don’t have to navigate this transition alone. Many generic online leadership development courses for professionals lack the personal touch required for true growth. They focus too much on theory or worse, they focus on the management tools and techniques – the fundamentals, not how to apply them in a broader context.
The Leadership Ethos program is different. It’s designed as a 12-month journey to accelerate your growth from technical expert to authentic leader, including:
- On-Demand Training Courses: A series of 12 monthly, themed online modules with micro-courses and practical worksheets to contextualise learning to your unique circumstances. Participants should expect to invest 1.5 to 3 hours per month.
- Monthly 1:1 Coaching & Mentoring: Twelve confidential, one-hour monthly calls to review progress, cement learning, and provide expert guidance on specific challenges and opportunities – effectively tailoring the program to your unique needs
- Professional Leadership Assessment: Participants in our Growth and Mastery tiers gain access to a third-party leadership strengths assessment from a recognised industry leader, which is then used to leverage your particular strengths throughout the lifetime of the engagement engagement.
- Comprehensive Support Resources: Continuous development is supported through a curated, evergreen library of productivity resources, academic papers, and leadership articles, alongside a detailed monthly action plan summarising discussions and guiding next steps.
I’ve searched and I don’t think you’ll find a program like this offering learning based outcomes alongside one-to-one time with an experienced mentor.
I help you understand how to create a leadership development plan tailored to your specific needs and develop your Impactful Intangibles of Vision, Authenticity, and Collaboration. This ensures you have the confidence to lead your team and master modern performance management to deliver real results.
Book a complimentary call with me to discuss how you can accelerate your development as a transformational, strategic leader, delivering results for your team and your company.