Recognize the decision before choosing the service.

Renew, renegotiate, replace, or defer?

Frame: Does current fit, responsibility, cost, and transition risk still support the incumbent?

Bring: Terms, usage context, service boundaries, alternatives, switching effort, decision deadline.

Fund the platform or the prerequisite first?

Frame: Which dependency makes the intended outcome credible?

Bring: Outcome, base case, dependency, adoption need, capacity, operating owner.

Reduce, accept, transfer, or investigate?

Frame: Who has authority to choose based on consequence and available options?

Bring: Exposure, affected operation, existing controls, options, cost, residual responsibility.

Which initiative moves with limited capacity?

Frame: Which sequence satisfies obligations and unlocks value without overloading shared owners?

Bring: Deadlines, dependencies, people, readiness, displacement, review trigger.

Who owns the condition after launch?

Frame: Where do delivery responsibility and continuing operation transfer?

Bring: Acceptance criteria, administrator, support route, vendor boundary, review cadence.

Is recurring IT ownership missing?

Frame: Does the pattern require ongoing context across decisions or one bounded intervention?

Bring: Decision frequency, executive access, internal ownership, vendor mix, change load.

What should wait, and under what condition?

Frame: Can leadership explain the consequence and trigger for every meaningful deferral?

Bring: Priority logic, dependency, capacity, exposure, owner, next review point.

What exactly needs executive authority?

Frame: Is the escalation a decision request, an exception, or status without an ask?

Bring: Decision, options, recommendation, consequence, deadline, required authority.