Field Notes · Boring-First IT
Short, generous write-ups from inside production systems — anatomy-of-a-system teardowns and governance lessons. The point of view is calm and boring on purpose: restraint over reach, governance over heroics, shipped over shiny. Each note shows the decision that was actually load-bearing, and why the dull choice was the right one.
// No hot takes. No tooling fashion. Just the systems thinking that keeps a thing running after the launch buzz is gone.
Architecture
Most teams bolt audit on as logging, then panic when someone asks “what did this look like the day it was approved?” The boring-first move: bake auditability into the data model — frozen snapshots, append-only history, guarded transitions — so the answer is a SELECT.
Architecture
Most scoring systems assume each subject can be scored on its own. This one couldn’t — a third of its formulas scale across the whole cohort, so you can’t finalize one score until enough others report. How a two-pass engine turned an impossible problem into two boring ones.
Patterns
Mid-size mission-driven orgs don’t hit a ceiling because their people aren’t capable — they hit it because no one’s job is the whole picture. The pattern, the economics of the gap, and the boring-first way to fill it without a big hire.
Governance
The day you switch on Power Platform, makers start building. If the guardrails aren’t already there, you get an ungoverned sprawl of apps, flows, and connectors leaking data — with no owner and no audit trail. Boring-first means the guardrails come first.
Governance
The five questions an auditor actually asks about your Microsoft 365 and Power Platform environment — and the boring-first governance that answers each one before they do.