This is not a consulting site. It's a working lab — a place where data governance ideas get built, broken, and rebuilt until they're actually useful.
Enter the sandboxes"Governance frameworks are written for the ideal state. The sandbox is where you meet the actual state."
Most organizations don't have a governance knowledge problem. They have a governance application problem. Frameworks get adopted before they're understood, and abandoned before they're useful. The lab exists to close that gap — deliberately, methodically, in public.
Each sandbox is a structured experiment — a real problem, a working approach, and honest findings. Nothing here is finished. That's the point.
Testing governance frameworks for AI-generated and AI-assisted data in real operating conditions. Who is accountable when the data source is a model? What breaks when AI outputs enter a governed pipeline without a defined owner? What does responsible AI data stewardship actually look like when the rubber meets the road? These are active experiments, not hypotheticals.
Organizations trust dashboards they can't explain. This sandbox applies the principle of lineage before launch — no metric reaches a decision-maker without a tested definition, a known owner, and a visible chain of custody. Experiments here expose the hidden assumptions embedded in reports and surface the governance gaps that make analytics unreliable at scale.
Architecture decisions are governance decisions — most organizations just don't realize it until migration. This sandbox stress-tests how structural choices in metadata layers, platform design, and domain modelling either enable governance or silently undermine it. The focus is on what breaks at the seams between systems, and how to build governance readiness into architecture from the start.
The catch-all for governance problems that resist clean categorization. Ownership disputes, policy design that nobody follows, stewardship without authority, working group dynamics that stall — the hard organizational friction that frameworks never account for. Experiments here focus on the human side of governance: what makes people actually adopt and sustain it.
I'm a data practitioner who works at the intersection of governance, engineering, and organizational reality. The lab is where I do the work before I talk about it.
Most governance advice skips the hardest part: figuring out why the last framework failed. The answer is almost never "we lacked a policy." It's that the policy didn't connect to how decisions actually get made — who touches the data, who gets blamed when it's wrong, and who has the standing to change it.
Every experiment in this lab starts with a clear-eyed read of the real problem, commits to a principle that addresses it, and takes deliberate actions that reinforce each other. If an experiment can't be explained in those three terms, it isn't ready.
Questions, collaborations, or just curious about something you saw in the lab — reach out.
// Message received.
Thanks for reaching out. I'll be in touch shortly.