The operating problem
Leadership teams often need to decide before every dependency, cost, risk, or delivery condition is fully known. Reporting more status does not resolve that; it usually just moves the same uncertainty later.
Executive governance guide
Executive Decision Support
Reporting more status does not necessarily improve a decision. The key is signal quality: what is known, what is uncertain, what decision is needed, and what each option implies.
Decision clarityEvidence qualityOwner follow-through
The useful move
Translate operational complexity into clear choices. Make the decision visible instead of burying it inside status language, and name who actually owns saying yes, no, or not yet.
What good looks like
Shorter decision cycles, better escalation quality, less rework from misunderstood approvals, clearer accountability, and an executive cadence people prepare for instead of sit through.
A working model
Four moves from status to a closed decision.
A decision forum should not be a status meeting with more senior people in the room. The work is to isolate the choice, name the evidence, show the consequences, and make the follow-through owner visible.
01IsolateState the decision being requested in one sentence, separated from general status or discussion.
02AttributeName the decision owner, the affected stakeholders, and who only needs to be informed.
03ComparePresent options with consequences — what each one delays, protects, risks, or makes irreversible.
04RecordClose the loop with a decision record: choice, owner, rationale, and the signal that would trigger reconsideration.
Practical interventions
How leadership choices get clearer.
Most decision forums fail before the meeting starts, because the pack was built to report status rather than request a choice.
Isolate the ask
If a reader cannot find the one sentence describing the decision being requested, there probably isn't one yet — just a well-organized status update looking for validation.
Separate status from decision
Status, issue, risk, dependency, assumption, and tradeoff are different things. Flattening them into a single red/yellow/green rating hides exactly the information a decision-maker needs.
Track decisions like open items, not meeting minutes
An open decision should have the same visibility as an open risk: an owner, an age, and a date by which it closes, ages out, or returns with new evidence.
What I would look for
Executives being asked to approve work without seeing opportunity cost, teams escalating issues without a decision request, and meeting notes that record discussion but not ownership.
How this plays out
A dotted-line cadence that replaced status with sequencing.
In one CTO-sponsored environment, I operated as the dotted-line planning and delivery layer between the CTO and eight department heads across R&D, software, test, commissioning, and cybersecurity. The forum's job was never to collect status; it was to surface the specific tradeoffs, capacity conflicts, and schedule risks that needed an executive decision.
In a separate revenue-technology environment, the same discipline ran through a dotted-line layer of product managers chairing cross-team governance forums, shifting the executive conversation from status reconciliation to change-based discussion focused on risk and sequencing.
Doosan GridTech · 2024–20268Department heads connected to the CTO through one dotted-line planning and decision layer.Read case study →Doosan GridTech · 2024–2026~$125MCapital-coupled deployment streams brought under one sequencing and decision view.Read case study →Doosan GridTech · 2024–20261,000–1,300Tasks per stream integrated into a single schedule without added bureaucracy.Read case study →Doosan GridTech · 2024–20263+Parallel workstreams competing for the same constrained engineering capacity and decision bandwidth.Read case study →T-Mobile · 2021–20247Dotted-line product managers chairing cross-team governance forums reaching 100+ contributors.Read case study →
Doosan GridTech
An essential partner in managing multiple cross-functional complex projects concurrently … always able to quickly help me morph complex plans into forms more easily digestible by executives and corporate audiences.
Marco’s measured approach contributed to much improved outcomes and provided certainty where there had previously been none. His strategic direction made us better and will make any team he joins better, too.
I watched him walk into contentious meetings between engineering, field operations, and C-suite executives — groups that had been talking past each other for months — and within two sessions, have everyone aligned on priorities and next steps.
A great combination of being easy to work with, precise in how he approaches timelines and deliverables, and communicates well with executive management both internally and at our customers.
His diplomatic and often democratic approach brought right-sized levels of structure to our processes exactly when they were needed, enabling short, medium, and long-term successes.
Marco brings a calm, but firm, analytical approach to complex problems, steers the attendees back onto the path and moving forward, asks the hard but necessary questions, and then helps turn those conversations into concrete plans and artifacts.
T‑Mobile
He navigated a complex portfolio of initiatives with ease and became a central resource for my whole team to go to with questions.
He excels at PMO leadership, balancing innovation with analytical precision … a solutions-oriented critical thinker who can quickly analyze complex situations and determine the best path forward.
He successfully managed a complex portfolio of initiatives, provided invaluable insights to leadership, drove process improvements, and encouraged technology adoption.
Where this breaks
Common ways decision support quietly fails.
Status dressed as decision
The pack implies a decision is needed but never states it, so the room discusses without anyone realizing a choice was on the table.
No owner, all informed
Everyone is copied, no one is accountable, and the decision drifts until it is overtaken by events instead of made on purpose.
False consensus
The meeting ends with apparent agreement that unravels the moment someone acts on a different understanding of what was decided.
Green dashboards, open questions
Status reads green while real, unresolved decisions sit underneath it, invisible until they surface as a late escalation.
Decisions that never close
The same question gets re-raised every cycle because no record exists of what was already decided and why.
Decision test
The meeting is useful when the choice survives the room.
Before
The pack names what is known, what is uncertain, what decision is needed, and what happens if no decision is made.
During
The discussion stays anchored on options, consequences, assumptions, and decision rights instead of drifting into broad status review.
After
The decision record names the choice, owner, rationale, follow-up date, and signals that would cause reconsideration.
Questions this raises
What leaders usually ask next.
Isn't this just better meeting hygiene?
Meeting hygiene helps, but the real fix is structural: a decision log that survives past the meeting, not a better agenda template.
What if the decision owner keeps deferring?
Deferral is a legitimate answer, but it needs its own date and consequence attached, or it becomes a quiet way to avoid ever deciding.
How should irreversible decisions be handled differently?
Name them explicitly as hard-to-reverse and require a higher evidence bar and a named sponsor before they close, not just a nod in a status meeting.
Continue