// Blog

Insights & Perspectives

Thoughts on public sector technology, digital transformation, and building systems that serve communities.

Power BI for Public Sector Reporting: Beyond the Dashboard

Every government organization wants better reporting. Power BI has become the default choice for most Canadian provincial agencies, and for good reason — it’s cost-effective, integrates well with the Microsoft ecosystem most governments already use, and produces professional-looking dashboards.

But dashboards aren’t the hard part.

The Data Quality Problem

The real challenge in government BI isn’t visualization — it’s data quality and governance. Most provincial agencies have data spread across dozens of systems: legacy mainframes, SharePoint lists, Excel spreadsheets maintained by individual analysts, and enterprise systems that were never designed to talk to each other.

Why Government Digital Transformation Fails — And How to Fix It

Government technology projects have a reputation for failure. Multi-million dollar systems that never launch, platforms that nobody uses, modernization efforts that end up more complex than what they replaced.

After 15 years working inside these organizations — from crown corporations in Saskatchewan to provincial agencies in British Columbia — the patterns are predictable.

The Procurement Trap

Most government technology failures start in procurement. The RFP process, designed to ensure fairness and accountability, often produces the opposite outcome. Requirements are written so broadly that any vendor can claim compliance, or so narrowly that only the incumbent can respond.

M365 Migration in Government: Lessons from the Trenches

Migrating to Microsoft 365 sounds straightforward. Microsoft provides the tools, the documentation is extensive, and thousands of organizations have done it before.

Government migrations are different.

Why Government M365 is Different

Provincial agencies operate under privacy legislation that creates real constraints on how data can be stored, shared, and managed. FOIPPA in BC, LAFOIP in Saskatchewan — these aren’t abstract compliance requirements. They determine which M365 features you can actually use.

A Practical Guide to Privacy Impact Assessments in Canadian Government

Privacy Impact Assessments are one of the most misunderstood requirements in government technology projects. Done poorly, they become bureaucratic checkboxes that delay projects without improving privacy. Done well, they become design tools that produce better systems.

What a PIA Actually Is

A Privacy Impact Assessment evaluates how a proposed system or process will collect, use, disclose, and protect personal information. In Canadian provincial contexts, PIAs are typically required under provincial privacy legislation whenever a new system handles personal information.