When organizations say “VBA is not allowed” or restrict the use of Power Query and other advanced Excel features, it can be perceived as a barrier or, more optimistically, as an opportunity. The question is, how do we turn what seems like a negative into a massive positive? I’ve encountered this situation multiple times in my career, and each time, it’s opened the door to immense opportunities for growth, both for my clients and for myself. So, if you’re wondering how VBA restrictions can lead to profitable outcomes, stick around. I’m about to share my experience, which could reshape how you view this issue.
The VBA Dilemma: A Common Roadblock.
It’s not uncommon to hear that some organizations disallow VBA (Visual Basic for Applications). A colleague of mine, Tony Wong from Sydney, Australia, mentioned that VBA or macros aren’t allowed on Australian government spreadsheets. This isn’t unique. Throughout my career, I’ve encountered numerous organizations that shy away from VBA or other automation tools due to concerns about risk, support, and complexity.
However, rather than viewing this as a dead-end, I encourage you to see it as a golden opportunity. Let me explain why.
A Story from 1997: From Temp to Consultant.
Back in 1997, I was in a short-term temp job doing year-end account reconciliations for an organization. The work was tedious–printing accounts, highlighting discrepancies by hand, and then manually entering data into a spreadsheet. This was common practice back then, but to me, it was unnecessary.
We were using Excel 5 at the time, and it had a feature called “Get External Data” through a component called MS Query. The forerunner of the modern day Power Query. This tool allowed users to import data directly into Excel, saving time and reducing manual effort. Naturally, I tried to use it, but I hit a roadblock: the feature had been disabled across the company.
I called IT, and they told me, “It’s not part of the standard install.” The IT department had limited Excel’s functionality to prevent potential issues, much like some companies restrict VBA today. I could have let it go, but I knew how much faster and more efficient our work could be with that feature enabled. So, I made my case to my superiors.
The Outcome: What Happened Next.
The IT department eventually enabled “Get External Data” for me. What seemed like a minor technical change turned into a massive transformation in how we processed data. Over the next six years, I helped streamline processes, automate tasks, and save the company significant time and money. What began as a six-week temp contract with a £7,500 budget, grew into six years of continuous projects, totaling £1.4 million in consultancy fees.
This wasn’t because of VBA or Excel features alone; it was because I could show the organization how inefficient they were without these tools. By solving a real problem in a more efficient way, I became an indispensable resource.
The Real Lesson: Efficiency Over Tools.
The key takeaway from that experience is that management doesn’t care whether you’re using VBA, Power Query, or any other tool. What matters is the outcome. If you can demonstrate that a solution makes the organization more efficient, saves time, or reduces costs, management will back you. Whether you’re using VBA, Power Query, or even the latest Excel features like Office Scripts or Python integration, the principle remains the same.
When organizations ban VBA, it’s usually out of a fear of complexity, security risks, or support headaches. IT departments may feel that it’s easier to avoid issues by restricting tools that users could misuse. However, this mindset often leads to inefficiency across the business, creating a perfect opportunity for consultants and experts to step in and demonstrate massive added value.
Turning Restrictions Into Opportunity.
Here’s the critical point: when you hear “VBA is not allowed,” your first thought should be, “This organization is likely operating hugely inefficiently.” If you can demonstrate how they can improve their processes–whether it’s through VBA, Power Query, or other tools–you’ll likely win them over.
In my experience, clients often don’t realize the potential benefits of these tools until they see them in action. Once you show them the difference in efficiency, they are usually quick to change their minds. In not just one instance but four, after implementing a solution that utilized VBA to re-engineer and therefore simplify a complex process, my client tripled my pay because the productivity gains were so significant.
The Future: Beyond VBA, Power Query, and Excel.
As Excel evolves, new features like Office Scripts, Power Query, and Python integration bring even more power to the table. However, the same resistance that exists for VBA can also apply to these tools. Some organizations might say “Power Query is not allowed” for the same reasons they restrict VBA. But the principle remains unchanged: if you can show them the value of using these tools, they will come around.
Final Thoughts.
The next time you encounter resistance to VBA or any other Excel feature, don’t see it as a roadblock–see it as an opportunity. By demonstrating efficiency and solving real problems, you can turn that “no” into a resounding “yes.” It’s not about the tool; it’s about the result. And once you deliver, you’ll never look back.
So, when you hear “VBA is not allowed,” remember my story. It’s not the end of the conversation; it’s the beginning of a profitable opportunity.
You have been listening to a podcast by Hiran de Silva. Read by Bill
Add comment