Zero trust for mid-market businesses: practical first steps
Full zero-trust implementation is a multi-year programme most mid-market businesses don't need yet. A handful of its principles, applied now, deliver most of the benefit.
Read perspectiveTechnical perspectives
Better questions. Better engineering.
Notes on the decisions beneath a working system. Written for the people responsible for building, changing and operating complex environments.
How to recover a stalled cloud migration
A stalled migration usually doesn't need a restart. It needs a diagnosis of which specific decision is blocked, and who actually has the authority to unblock it.
Read perspectiveNetwork segmentation basics for hybrid environments
A flat network means one compromised device is one step away from everything. Segmentation buys the time a security team needs to actually respond.
Read perspectiveWhat infrastructure as code actually buys a mid-sized business
The real early return on IaC is speed and consistency, not the cost savings it gets sold on — and it needs an owner, not just a repository, to keep paying off.
Read perspectiveWhen public cloud isn't the right answer
Public cloud wins on elasticity and managed services. It loses on egress cost, data-gravity constraints and latency-sensitive workloads — and pretending otherwise gets expensive.
Read perspectiveWhy restore testing matters more than backups
A completed backup job only proves data was written. Industry research puts real restore failure rates high enough that an untested backup should be treated as unverified, not safe.
Read perspectiveWhat a dependency map should include before a migration
A server list tells you what exists. A dependency map tells you what breaks if you move it — and it's the document most stalled migrations were missing from the start.
Read perspectiveAzure cost optimisation: the checks that actually save money
Reserved capacity, right-sizing and auto-shutdown of non-production environments account for most realistic Azure savings — in that rough order of effort versus return.
Read perspectiveHow to scope a cloud migration project properly
Dependency mapping and a wave plan before implementation — the sequence that prevents a migration from becoming a more expensive datacentre.
Read perspectiveThe failure modes of the IT generalist who does everything
The person who single-handedly keeps a business's technology running is a genuine asset and a structural risk at the same time — recognising both is the first step to managing it.
Read perspectiveBuilding an internal-external IT relationship that lasts
The co-managed arrangements that hold up over years share a few habits — regular communication, clear ownership, and treating the internal team as a client, not a client's IT department.
Read perspectiveWhat a change and architecture review actually catches
A second set of experienced eyes before a change ships catches the class of mistake that's cheap to fix in review and expensive to unwind in production.
Read perspectiveKeeping internal IT morale high when adding co-managed support
Bringing in outside help can read as a vote of no confidence if it's handled badly — the framing that avoids that is specific about what's being added, not replaced.
Read perspectiveHire internally or bring in co-managed support?
The decision usually isn't about cost per hour — it's about whether the need is ongoing and generalist, or specialist and intermittent.
Read perspectiveThe hidden cost of a single IT generalist
A $70k salary commonly becomes $95k–$115k in fully-loaded cost — for coverage that still has no redundancy, no after-hours capacity, and no deep specialist expertise in any one discipline.
Read perspectiveWhat senior escalation should actually look like
A defined escalation path specifies who gets contacted, how fast, and what happens next — response and resolution are not the same commitment, and treating them as one hides the real number.
Read perspectiveSplitting responsibility between internal and external IT
The most common source of co-managed IT friction is an undefined boundary. Here's how to draw one that survives contact with a real incident.
Read perspectiveSigns your internal IT team needs backup, not replacement
Delayed projects, unworked alerts and a growing backlog usually mean the team is stretched, not underperforming — and the fix is capacity, not a new hire or a full outsourcing decision.
Read perspectivePatch management: what good actually looks like
The gap between vendor patch release and exploitation is measured in days. Most environments take months to close it — here's what closes it faster.
Read perspective"Unlimited support" pricing: what to check before you sign
Unlimited-ticket pricing usually means the limits moved somewhere else in the contract — after-hours rates, on-site charges, or a narrower definition of what's included.
Read perspectiveRolling out MFA without killing productivity
Employee resistance to multi-factor authentication is almost always a rollout problem, not a security objection — and a staged approach fixes most of it.
Read perspectiveBackup vs disaster recovery: what gets confused
Backup protects your data. Disaster recovery protects your uptime. Most businesses have bought one and assumed it covers the other.
Read perspectiveWhat good IT onboarding actually looks like
The difference between a new starter who's productive on day one and one who spends their first week waiting on access requests — and what that says about the environment.
Read perspectiveEndpoint security basics every business needs
The layer of protection that actually stops most incidents — device encryption, managed patching, endpoint detection and least-privilege access — before anything more advanced.
Read perspectiveHow to evaluate a managed IT provider before signing
The questions that separate a genuine capability from a sales pitch — response versus resolution, scope boundaries, and what a reference call actually reveals.
Read perspectiveWhat "24/7 monitoring" actually means
The difference between an alert firing at 2am and someone actually being accountable for acting on it — and why the two get sold as the same thing.
Read perspectiveThe Microsoft 365 licence audit checklist
What to check 60–90 days before renewal — unused seats, duplicate SKUs and the licence tiers nobody re-evaluated since onboarding.
Read perspectiveThe cost of a deferred security backlog
Why technical debt and deferred security work compound quietly, what it costs organisations that let it, and what a managed backlog actually looks like in practice.
Read perspectiveWhy IT escalation takes too long
What actually happens inside a support tier structure when a problem is too complex for tier one — and what a defined escalation path should guarantee instead.
Read perspectiveSigns your IT provider is out of its depth
The gap between a help desk that closes tickets and a provider that can actually own infrastructure risk — and how to tell which one you have.
Read perspectiveHow to prepare infrastructure for AI-driven operations
Telemetry, identity, change records and environment access — the unfashionable prerequisites before AI can operate on your estate.
Read perspectiveAI agents vs traditional automation for IT operations
Where agents help IT operations, where scheduled automation and runbooks still win, and how to keep a human on the approval path.
Read perspectiveHow RAG can be used safely with internal data
Retrieval-augmented generation against SharePoint, file shares and ticketing data — with access control, logging and failure modes made explicit.
Read perspectiveWhat platform engineering means for traditional infrastructure teams
Platform engineering without the hype: golden paths, paved roads and what changes for people who currently run servers and tickets.
Read perspectiveTroubleshooting hybrid Azure network problems
A method for hybrid Azure network incidents: DNS, routing, NSGs, firewalls and ExpressRoute — in the order that actually finds the fault.
Read perspectiveAzure Virtual Desktop vs Citrix
A practical comparison of AVD and Citrix for Australian estates that already have identity, profiles and application delivery constraints.
Read perspectiveWhy infrastructure automation projects fail
The usual reasons Terraform, Ansible and pipeline programmes stall — and how to scope automation so it survives contact with operations.
Read perspectiveAzure Landing Zones: what they actually need
What belongs in an Azure landing zone that an operations team can run — and what to leave out of the first release.
Read perspectiveWhen to migrate VMware workloads to Azure
A decision sequence for moving VMware workloads to Azure — and the cases where staying put, or using Azure Local, is the better engineering answer.
Read perspectiveVMware vs Azure Local for Australian IT teams
How to compare VMware on-premises, Azure Local, and public Azure when licence, skills, latency and data residency actually matter.
Read perspectiveStart a conversation
Ready for technology that’s managed, not just supported?
Tell us how your environment is managed today and what isn’t getting done. We’ll work out the right starting point together.
Talk to an experienced engineer