Same Destination,
Different Maps

Full framework · 69 questions

Four areas, seen through four lenses

You don’t need to ask every question. Choose the ones most likely to expose assumptions at the stage you’re in, or let the Question Builder choose for you.

The four lenses

DestinationAre we heading to the same place?
Routes & RolesWho navigates, who decides, who’s accountable?
Signals & CheckpointsHow do we know when the landscape is changing?
Arrival & SuccessHow will we know we’re getting where we intended?

Codes like O·D1 are map references: area, lens, and item. Recurring questions come up in more than one area. New marks questions added from panel feedback.

Area 1

Outcomes and what good looks like

Align on the problem, the value of solving it, and the evidence that the work was worthwhile.

Destination

Are we heading to the same place?

  • O·D1
    What problem are we solving right now, not eventually?
  • O·D2
    What are we optimizing for?
    speed, quality, adoption, risk reduction, cost, learning
  • O·D3
    What does “worth it” look like for the institution? For the partner?
  • O·D4
    What does success look like 30, 60, and 90 days after delivery?
  • O·D5
    What must still be true a year after this project is delivered?
    New

Routes & Roles

Who navigates, who decides, who’s accountable?

  • O·R1
    Who defines success metrics and acceptance criteria?
  • O·R2
    Who owns adoption and change management, and who owns delivery?
  • O·R3
    What stays internal by design?
    Recurringcommunications, governance decisions, content ownership
  • O·R4
    Where are we assuming capacity?
    SMEs, approvals, analytics, training

Signals & Checkpoints

How do we know when the landscape is changing?

  • O·S1
    What will tell us we’re off track?
    adoption lag, stakeholder pushback, technical blockers
  • O·S2
    What does silence mean?
    Recurringapproval, confusion, overload, or avoidance
  • O·S3
    How do we surface uncertainty early, and make it safe to do so?
  • O·S4
    Who speaks for the institution?
    Recurringwhen feedback is mixed

Arrival & Success

How will we know we’re getting where we intended?

  • O·A1
    What does “good enough” mean, and who decides?
  • O·A2
    How do we evaluate progress before launch?
    prototypes, pilots, QA gates, usability checks
  • O·A3
    What can change midstream without renegotiating “success”?
  • O·A4
    What triggers a reset or re-baseline of outcomes?
  • O·A5
    What are your internal success measures for whether you nailed this engagement?
    Newask the partner, and answer it yourself
Area 2

Decision rights, governance, and escalation

Align on who can decide, what needs approval, and how to move when decisions stall.

Destination

Are we heading to the same place?

  • D·D1
    What decisions are open, and what’s already decided?
  • D·D2
    What decisions must be made in the next 2–3 weeks to keep momentum?
  • D·D3
    What does delaying a key decision cost?
    time, money, stakeholder trust
  • D·D4
    What are the institution’s non-negotiables?
    brand, security, accessibility, policy

Routes & Roles

Who navigates, who decides, who’s accountable?

  • D·R1
    Who has decision authority?
    scope, timeline, budget, design, technical choices
  • D·R2
    What needs explicit approval, and at what stage?
  • D·R3
    What stays internal by design?
    Recurringprocurement, HR, labor relations, internal politics
  • D·R4
    What tradeoffs are implicit?
    speed vs. consensus, flexibility vs. compliance

Signals & Checkpoints

How do we know when the landscape is changing?

  • D·S1
    What are the early signs decision-making is breaking down?
    late reversals, vetoes, conflicting feedback
  • D·S2
    What does silence mean?
    Recurringon approvals and reviews
  • D·S3
    How do we document decisions so they don’t get relitigated?
  • D·S4
    What’s the escalation path, and what triggers it?

Arrival & Success

How will we know we’re getting where we intended?

  • D·A1
    How will we know governance is working?
    fewer reversals, predictable approvals, faster decisions
  • D·A2
    What does a healthy escalation look like?
    clarity, not blame
  • D·A3
    What triggers a reset of decision rights?
    new stakeholder, leadership shift, risk discovery
  • D·A4
    If we have to choose, which decisions can wait and which must be made now?
Area 3

Capacity, roles, and ownership

Align on the work each side actually has to do, especially the work between meetings.

Destination

Are we heading to the same place?

  • C·D1
    What else must be true for the deliverable to matter?
    content readiness, training, support, communications
  • C·D2
    What are we optimizing for, given real capacity limits?
    MVP vs. full scope, phased rollout
  • C·D3
    What’s the highest-value slice we can deliver if time or people shrink?
  • C·D4
    What is explicitly not being solved in this engagement?

Routes & Roles

Who navigates, who decides, who’s accountable?

  • C·R1
    Where are we assuming capacity on the institution side?
    SMEs, reviewers, technical access, content owners
  • C·R2
    Who owns the work between meetings?
    inputs, decisions, artifact updates
  • C·R3
    What stays internal by design?
    Recurringpolitical alignment, internal communications, stakeholder management
  • C·R4
    What’s the tradeoff between the partner doing more and the institution building its own capability?
  • C·R5
    What’s your interpretation of your role in this project?
    New
  • C·R6
    Where will the work be managed, and who is the point person for each area?
    Newwhose project management system; one wrangler, never a single point of failure
  • C·R7
    Who owns the work after the engagement ends?
    New

Signals & Checkpoints

How do we know when the landscape is changing?

  • C·S1
    What are the early signs capacity is failing?
    missed reviews, long feedback cycles, partial inputs
  • C·S2
    What does silence mean?
    Recurringapproval, bandwidth issues, or missing context
  • C·S3
    How can either side say “we can’t meet this commitment” early, without stigma?
  • C·S4
    Who speaks for the institution?
    Recurringon availability, when people rotate or leave

Arrival & Success

How will we know we’re getting where we intended?

  • C·A1
    What does “good enough” look like for institutional inputs?
    content completeness, QA coverage
  • C·A2
    How do we evaluate readiness early?
    content readiness gates, access checks, review turnaround
  • C·A3
    What can change midstream without derailing the work?
    roles, review cadence, deliverable sequencing
  • C·A4
    What capacity change should trigger a reset?
    lost resources, denied access, dependency delays
Area 4

Change, risk, and map updates

Align on how you spot drift, make tradeoffs, and update the plan without calling it failure.

Destination

Are we heading to the same place?

  • C·D1
    Given what we know now, what problem are we solving this month?
  • C·D2
    What risks are we optimizing against?
    reputational, legal and compliance, security, accessibility, continuity
  • C·D3
    What does “worth it” look like if conditions change?
    re-scoping without calling it failure
  • C·D4
    What is our shared definition of a material change?

Routes & Roles

Who navigates, who decides, who’s accountable?

  • C·R1
    Who can approve a re-baseline of scope, timeline, or budget, and how fast?
  • C·R2
    Who owns risk mitigation in each category?
    security, privacy, accessibility, communications, governance
  • C·R3
    What stays internal by design?
    Recurringsensitive constraints, procurement limits, institutional politics
  • C·R4
    What tradeoffs become explicit when change happens?
    pay more, cut scope, extend timeline, accept risk

Signals & Checkpoints

How do we know when the landscape is changing?

  • C·S1
    What are the leading indicators of drift?
    new stakeholder demands, scope creep, dependency surprises
  • C·S2
    What does silence mean?
    Recurringwhen a risk is raised
  • C·S3
    How will we make uncertainty visible early?
    risk register, assumptions log, decision log
  • C·S4
    Who speaks for the institution?
    Recurringwhen priorities shift

Arrival & Success

How will we know we’re getting where we intended?

  • C·A1
    What does an acceptable risk posture look like?
    what we can accept vs. what we must mitigate
  • C·A2
    How will we evaluate progress against risk before the end?
    security reviews, accessibility checks, compliance sign-offs
  • C·A3
    What can change without forcing a full renegotiation?
  • C·A4
    What triggers a formal reset?
    change order, re-baseline meeting, or pause-and-replan