Government does not fail at digital delivery because the technology is hard. It fails when legislation, policy intent, security obligation, and delivery reality are held by four different people who never share a document.
I hold all four. As Portfolio Digital Architect for the Government of Alberta, I set architectural direction across a six-ministry portfolio (Education and Childcare, Energy and Minerals, Indigenous Relations, Affordability and Utilities, Service Alberta and Red Tape Reduction, and Treasury Board and Finance) and translate statute and service need into architecture that teams can actually build against.
My work is deliberately close to delivery. I have taken an executive-priority system from requirements to production in six weeks, stood up new tribunal and case-management platforms on Alberta’s digital service platform, and shipped the AI playbooks and reference patterns that let other teams do the same thing without re-deriving the governance every time.
Portfolio and enterprise architecture, architecture review, decision records, trade-off analysis
AI delivery playbooks, RAG systems, Model Context Protocol knowledge services, AI-first governed delivery
Protected B & C hosting, OpenShift, identity, API contracts, information-protection patterns
Legislation-to-architecture translation, tribunal and case management, fixed-mandate launch dates
I work at the portfolio level, where the decisions are expensive to reverse.
Six ministries, one architectural direction. I am the primary architecture decision-maker for digital services across Education and Childcare, Energy and Minerals, Indigenous Relations, Affordability and Utilities, Service Alberta and Red Tape Reduction, and Treasury Board and Finance.
AI is only useful in government if it is governable. My work makes AI-assisted delivery repeatable, auditable, and aligned to enterprise standards.
High-sensitivity environments do not tolerate late security thinking. I define the hosting, identity, and information-protection patterns before the first sprint.
Governance earns its place when it makes delivery faster.
Key accomplishments and the value they delivered, measured rather than described.
Executive-priority meeting request system: From requirements to production, including architecture, API contracts, deployment, and production readiness.
Tribunal and case-management platforms: Established on the Alberta Digital Service Platform and running in production.
Consolidated architectural direction: Six ministries aligned under a single architectural direction.
Enterprise AI acceleration: Three reusable enterprise AI assets adopted by multiple delivery teams.
Highest-sensitivity secure hosting: Initiated on OpenShift, with integration patterns defined.
Critical system uptime after redesign: Legacy system overhauled with new high-availability and disaster-recovery patterns.
Recognized in year-end review for a rare blend of strategic thinking and hands-on technical prowess.
Architectural oversight for a Premier-mandate initiative working to a fixed launch date. Shaping solution architecture and sequencing to hold that date without trading away security or governance posture.
STACK ADSP · Case-management architecture · Secure integration · Reusable component libraries
Established the architecture from scratch on Alberta Digital Service Platform services, brought it to a stable state, and took it to production.
STACK ADSP · Case-management architecture · Cloud-native services · Platform-service integration · CI/CD
Led end-to-end architecture under a six-week executive timeline: refined requirements, drafted the implementation plan, defined API contracts, and oversaw deployment.
STACK Azure · API contract design · Azure DevOps · CI/CD
Built the assets that make AI-assisted delivery repeatable across government: a DDD AI Playbook, an AI Toolkit, and a Model Context Protocol architecture knowledge service deployed on ADSP.
STACK MCP · RAG · Agentic workflows · GitHub Copilot · ADSP
Architectural direction for systems that predate the current platform. Each engagement starts with a technical system overview and a pain-point analysis, then produces a recommended path and the architecture to execute it. Three run concurrently.
STACK ServiceNow App Engine / Dynamics 365 · AEM · GitHub Enterprise · Azure Boards · Azure Pipelines (YAML) · PowerShell automation
Principles I design by
| Credential | Issuer | Issued |
|---|---|---|
| Certified SAFe® 6 Advanced Scrum Master | Scaled Agile, Inc. | Dec 2022 |
| Certified SAFe® 6 Product Owner / Product Manager | Scaled Agile, Inc. | Dec 2022 |
| Certified SAFe® 6 Agilist | Scaled Agile, Inc. | Nov 2022 |
| New Models of Business in Society | UVA Darden School of Business | May 2020 |
| Machine Learning for Business Professionals | May 2020 | |
| ITIL® Foundation, IT Service Management | AXELOS | Jun 2017 |
| Alberta AI Academy, Levels 1 & 2 (Levels 3 & 4 in progress) | Government of Alberta | 2025 – 2026 |
consistently exceeding expectations across all performance goals
I am interested in the seam between systems that are designed and systems that are lived with.
Public services are the clearest example. A tribunal platform is architecture on one side of the screen and someone’s housing dispute on the other. That gap is where most digital government work quietly goes wrong, and it is the part I find genuinely worth doing well.
Outside the mandate work, I build the tooling that reduces the cognitive load of architecture itself: knowledge systems, playbooks, and AI agents that let a small practice behave like a large one. Some of that thinking ends up in writing.
If you are standing up an enterprise or portfolio architecture practice, modernizing a regulated platform, or trying to make AI adoption survive an audit, that is the conversation I am most useful in.