📝 Blog Post 2

Part 2 of the Real IT Superpower

The Request That Sounded Simple

“We just need a way to upload this Excel report into the system with a live refresh.”

Sounds easy, right?
This request came from a regional sales team during target-setting season. Their goal? To speed things up by pulling their spreadsheets into our reporting platform, so they could share numbers alongside historical sales during alignment calls with different markets.

They were emailing Excel files back and forth, adjusting figures live, then manually updating versions — all while trying to hit deadlines. From their side, uploading the file into our reporting system seemed like a small, but powerful solution.

But here’s the problem: that solution clashed with the core design of our system.

When You Know Something’s Off

I’d already set clear rules for our reporting tools: no manually entered data. Our platform was built for combining data from trusted sources — not for becoming yet another input or workflow tool.

At first, I felt that familiar tug — just say yes and get it done. Keep everybody happy. You have so many other requested let this be a quick-win and move on.

But I’d already learned the cost of unchecked yeses (see Post 1). So instead, I slowed down and asked more questions:

• Why do you need to upload the Excel file?

• Who adjusts the values, and when?

• Is this a report… or part of a planning process?

The more I listened, the more I realized this wasn’t about reporting at all.
They didn’t need a dashboard.
They needed a live, internal target-setting tool — something they could adjust collaboratively during strategy calls.

From “Quick Fix” to Long-Term Solution

That changed everything.

Instead of adding manual uploads to our reporting system (which would have created long-term tech debt), we designed a lightweight input tool. It was built specifically for target-setting — flexible, real-time, and aligned with how the teams worked.

We even made it generic enough that other teams could configure their own inputs and workflows later on. Making it add continue to add value beyond the original idea.

Yes, before you ask, this did cost more and take more effort than manually uploading an excel file. Once I had framed it to the business that the new solution would be better than the excel file and solve many more use cases in the future without the need for development, each time the file or process changed, we got the funding really easily.

What started as a small request became a really powerful internal solution — and the team was even happier with the outcome than what they originally asked for. This system is now being used by multiple teams across the organisation.

Why This Matters

When you take the request at face value, you risk solving the wrong problem.

But when you pause and dig a little deeper, you unlock:

• More impactful solutions — ones that actually meet the need

• Simpler systems — by keeping the right work in the right place

• Happier teams — who feel seen and supported, not just patched

And most importantly:
You protect your core systems while delivering real value.

What to Watch Out For

In my experience, these are signs that a request might need a deeper look:

• It starts with “can’t we just…”

• It’s asking for manual input into a downstream system

• It feels like a reporting request but involves changing numbers

• It’s a workaround for a missing workflow elsewhere

• It sounds fast, but your gut says “hey! this doesn’t belong here”

What I Love About IT

This is the part I love most:
Taking a messy request and turning it into something clean, valuable, and future-proof. It’s not just about saying no — it’s about offering something better.

It’s why I believe IT isn’t just a service team — it’s a strategic partner in building smarter businesses.

👉 Next up:  How to Say “No” Without Damaging Relationships
I give you real examples and words you can use to push back, reframe requests, and still keep your business partners on your side.