Skip to main content

About Beau Dean

Beau Dean

I'm Beau Dean, an IT professional based in Albury–Wodonga, on the New South Wales–Victoria border. For more than a decade I've worked in IT across several industries — moving from frontline support to service management and cybersecurity.

My focus today is the behind-the-scenes work that keeps a business running safely: security, sensible governance, and clear communication with the people who rely on it.

Why Shadow IT exists​

Shadow IT grew out of a simple goal — better outcomes, and a higher standard of IT work. Rather than start my own business, I chose to build a public, open repository of what I've learned across Microsoft 365, cybersecurity, and IT professionalism.

The name is a deliberate play on words. In the industry, "Shadow IT" means the tools and systems that run outside formal oversight — the hidden layer most organisations only notice when something breaks.

This site turns that idea around. It drags the hidden layer into the light: documenting what good looks like, holding my own work to a clear standard, and sharing the reasoning, not just the result.

It isn't a sales pitch. It's an open, evolving record of how I think about and practise IT.

My background​

My experience covers the full arc of IT delivery — from the service desk through to coordination, management, and security — across a range of industries:

  • Managed services (MSP) — delivering IT to many client businesses at once
  • Education — embedded IT support and management inside schools
  • Healthcare & diagnostics — IT service management at a national scale
  • Community & disability services — IT coordination and digital uplift
  • Professional services — frontline support for a busy advisory firm

Working across regional managed services, schools, and national healthcare has shaped how I work. I've seen what happens when IT is treated as a cost to be trimmed — and how much changes when it's run as a proper discipline, with standards.

Ongoing professional development​

Professional development isn't a box I've ticked once; it's part of treating IT as a discipline. I'm currently studying a Master of Business Administration with a focus on cybersecurity at Charles Sturt University, deliberately pairing the technical side of security with how those decisions land as business ones — risk, cost, and continuity.

Alongside study, I keep an active focus on industry certification. That means Microsoft certifications across the Microsoft 365, security, and identity stack, and working toward the Australian Signals Directorate's Essential Eight Assessment Course — the formal pathway for learning to assess an organisation's maturity against the Essential Eight. Keeping these current is how I make sure the guidance on this site reflects real, up-to-date practice rather than yesterday's habits.

How I approach IT​

Everything here is grounded in the ACS Code of Professional Conduct — the ethical standard the Australian Computer Society sets for IT professionals. Its first and highest value is the Primacy of the Public Interest: when interests conflict, the public's come before any personal, business, or sectional interest. That principle sits above everything else I do.

Primacy of the Public Interest — security that protects people. The reason to secure a system isn't compliance or a sale; it's the people whose data and livelihoods depend on it. Good security for a smaller organisation isn't about buying the most tools — it's a few well-chosen protections over who can log in, the devices they use, and where the data lives, matched to the real risk. I'd rather get the basics right than add complexity no one will keep up. When a commercial shortcut and the public interest pull in different directions, the public interest wins.

Competence and professionalism — write things down. Honest, competent work is work that can be checked and handed over. How a system is set up, who can access it, and what has changed should all be recorded — not because an auditor is watching, but so the system still makes sense, and stays safe, a year from now. The guides and runbooks on this site come from that habit.

Honesty — plain language, no surprises. The Code asks for honesty, and the quickest way to break someone's trust is to leave them in the dark. I explain the why in everyday terms, show the work going on in the background, and avoid surprises. "Managing the unseen" only works if the people relying on you can see that it's handled.

What you'll find here​

The Docs hold service deep-dives, onboarding guides, and runbooks written to be useful to small-business readers, not just technicians — where I work through what I'm learning across Microsoft 365, cybersecurity, and IT professionalism.

If something here is useful, wrong, or worth a conversation, I'd like to hear it — get in touch.