Who owns governance?
In a cross-domain approval meeting, every domain signs off on its own area, yet no one in the room owns the enterprise decision itself. A stack of approvals isn't a decision — so who owns it?
The complete library
Govern the decisions that shape delivery and AI.
Browse every field note on one page. Search by a decision, operating problem, or topic, or move directly to the chapter closest to the work in front of you.
Showing all 34 field notes.
Portfolio & delivery governance
14 field notesMake commitments, capacity, and value easier to steer.
Decide what can move, what must wait, what is truly ready, and how expected value remains owned after approval.
Separate the decision from the outcome
Capital reallocation is the real portfolio decision
Decision rights are a system-design choice
Standardize the Component, Not the Project
A portfolio needs scenarios, not a single annual plan
Decision friction is a portfolio risk
A PMO dashboard should show investment health
The EPMO's job is capacity, not calendars
Stage gates work only when they can kill projects
A project is not ready because a plan exists
Portfolio governance is a funding-discipline problem, not a reporting problem
Documentation is cross-functional leverage, not clerical output
Benefits realization is where transformations quietly fail
AI operating governance
13 field notesPut AI inside accountable work.
Connect AI access, autonomy, evaluation, and investment to the workflow, evidence, oversight capacity, and human ownership that make reliance possible.
AI Deployment Is a Jurisdiction Decision Before It Is a Model Decision
Set the operating boundary first; confirm it against the candidate before commitment.
An AI evaluation is a production operating control
Local AI versus cloud AI is a governance decision
The demo-to-production gap
Confident and wrong
Oversight capacity, not model capability, is the ceiling on AI scale
Governing AI as operational change, not software activity
Every agent needs a human operating model
Enterprise AI trust is built through operating evidence, not tool novelty
The AI value test: automate, build, buy, hire, or wait
AI usage belongs in workflow governance, not blank-check access
AI knowledge bases are operating infrastructure, not “second brains”
AI adoption starts with the constraint, not the tool
Work, adoption & judgment
7 field notesDesign work that preserves learning and accountability.
Use AI to improve judgment, reduce coordination burden, and strengthen evidence without eroding the people and operating knowledge the work depends on.
Felt productivity is not measured productivity
Govern AI on evidence of the work — a baseline, a work-output signal, and a review that separates felt speed from delivered outcome — because self-reported speedup is not operating evidence.
The exception path is the real automated workflow
The coordination tax
The prove-it economy is coming for careers and AI programs
Business imagination is the scarce asset now
AI should make people better thinkers, not just faster producers
The AI replacement boomerang is a governance failure
Related proof
Move from principles to examples.
The library explains the operating logic. The portfolio’s methods and workflow systems show how that logic becomes review paths, artifacts, and inspectable examples.