Executive Mandate Check · General Framework

Do not let the
deadline
become the
product.

A pre-PD/PDM field manual for VP and director rooms. Use it before scope turns into theatre, before AI becomes a shortcut word, and before a target date means seven different things.

The seven gates

01 / 06
00/

Decision

"What decision changes if this MVP works?"

  • Vendor decision, customer pilot, funding, delay, replacement, or coexistence
  • Named decision-maker and decision date
  • Explicit consequence of doing nothing
Kill criterion - no decision = no mandate
01/

Sponsor

"Who can approve access, team, and scope?"

  • Executive sponsor named
  • Customer or business-unit access authority named
  • Scope tradeoff owner named
Kill criterion - interested senior people are not ownership
02/

Scope

"What is in, what is out, and what is only vision?"

  • One bounded product surface
  • OOS list with trigger conditions
  • POC, demo, operational pilot, and production separated
Kill criterion - everything is in = nothing is deliverable
03/

Use Cases

"Which user or customer pain points are inside this scope?"

  • Top 3 validated workflows
  • Named customer, user group, or business unit
  • Current pain, frequency, and business impact
Kill criterion - invented use cases do not count
04/

Architecture

"Who owns the technical shape and integration boundary?"

  • Architect or tech lead named
  • Read-only vs writeback defined
  • Real, mocked, data-ready, and vision separated
Kill criterion - no architect = no credible MVP
05/

Team

"Who is committed to deliver, not just supportive?"

  • Product owner
  • UX, data, frontend, backend/API roles
  • Protected capacity or explicit spare-time scope
Kill criterion - spare time cannot support strategic commitments
06/

Proof

"What evidence proves the MVP mattered?"

  • Sponsor or customer accepts workflow value
  • 3 demos over real or representative data
  • Existing commitment delayed, reduced, challenged, or complemented
Kill criterion - shipped page with no decision impact = theatre

The correct order

02 / 06
First
Define scope
Then
Get use cases
Then
Derive features
Then
Set architecture
Then
Assign team
Only then
Commit date

Executive disqualifiers

03 / 06
DQ 01

The date is doing product work.

A target date sounds aligned, but each person may imagine a different product.

Ask: "What exactly must exist by the target date for the decision to change?"
DQ 02

AI is used as a confidence amplifier.

AI can accelerate implementation, but not replace scope, data contracts, permissions, or ownership.

Ask: "What is the grounded evidence and next action?"
DQ 03

Stakeholder support is confused with commitment.

Senior interest is not the same as team capacity, architecture ownership, or customer access.

Ask: "Who can say yes, no, and out of scope?"
DQ 04

The comparison is against a stronger incumbent's polish.

That is the wrong fight. The stronger fight is owned context, workflow depth, and speed of adaptation.

Ask: "Which workflow can we prove faster than the incumbent can roadmap?"

Readiness matrix

04 / 06
Dimension Pass Fail
Decision One named decision changes if the MVP works. General excitement, no clear decision.
Sponsor One person can unlock customer access and capacity. Many senior people are interested.
Scope In, out, mocked, real, and vision are separated. The mandate means portal, BI, AI, workflow automation, reporting, and more.
Use cases Top 3 workflows from a named customer or user group. Internal assumptions about what users want.
Architecture Architect defines data, API, permissions, and writeback boundaries. The demo implies production without a migration path.
Team Named roles with protected capacity. "We can probably do it with AI."
Success Evidence changes vendor, funding, scope, or pilot decisions. MVP exists but nobody knows whether it mattered.

Anti-patterns

05 / 06
Noise
"We need this by the target date."
Check
What exact decision happens on that date, and what proof must exist before then?
Noise
"We already have the data."
Check
Which data sources are available, legally usable, joined, fresh enough, and owned by whom?
Noise
"AI lets us move fast."
Check
Which workflows are accelerated by AI after scope, permissions, and data contracts are clear?
Noise
"Users want this."
Check
Which named customer or user group gave which top use cases, and who agreed to validate the demo?
Noise
"This can replace current tools."
Check
Which current tools or processes are replaced, complemented, hidden, or still source-of-truth?
Noise
"We can tailor it however they want."
Check
What is configurable by design, and what becomes custom build debt per customer or unit?

Output brief

06 / 06

Mandate readiness brief

  • Problem: Teams are forced to stitch fragmented tools, data, and decisions manually.
  • Decision: What will the sponsor, customer, or business unit decide if the MVP works?
  • Sponsor: Who can unlock customer access and team capacity?
  • Scope: One bounded workflow surface, with explicit OOS.
  • Use cases: Top 3 validated customer or user workflows.

Delivery truth

  • Architecture: What is real, mocked, read-only, writeback, or only vision?
  • Team: Named product, architecture, data, UX, frontend, and backend roles.
  • Proof: 3 workflows over real or representative data that change a vendor, funding, scope, or pilot decision.
  • Date: A constraint after scope, not the definition of the product.
  • Next gate: Only then move into PD/PDM feature checks.