Effective 3 November 2026: shared priorities move to Enterprise Enablement

Low priority
What changes

In this fictional Northstar Group example, Enterprise Enablement coordinates priority decisions for customer requests that affect more than one business. Each business team still decides and delivers its own work.

The change in one minute

For employees whose work or decisions cross business-team boundaries

This page uses a fictional cross-business organization to show how a responsibility change can work. It is an illustrative example, not a real company policy.

Changed: one team coordinates the shared priority decision when a customer request affects multiple businesses. Unchanged: each business team decides its delivery scope and sequence. Coordination does not transfer delivery accountability.

Before and after

The change is about who coordinates shared priority—not who delivers each team's work.

Before and after
Work or decision Before 3 November From 3 November
Prioritize a request affecting multiple businesses Each business team prioritized its incoming requests independently. Enterprise Enablement coordinates a shared priority recommendation with the affected teams.
Decide a business team's delivery scope The business team decided its own scope. The business team continues to decide its own scope.
Set a team's work sequence The business team sequenced its own delivery work. The business team continues to sequence its own delivery work.

Responsibilities by role

Use the role that best matches the work you are doing.

Requesting teams
Own the request context
State the shared outcome, why it matters, the requested timing, and which business teams may be affected.
Bring useful evidence
Share relevant customer context and constraints. Do not assume a requested date is an agreed delivery commitment.
Do not reassign delivery
A request does not by itself change a business team's scope, sequence, or ownership.
Enterprise Enablement
Coordinate the shared priority
Bring the affected business teams together to compare the request's shared outcome, timing, and cross-business impact.
Make the recommendation visible
Summarize the proposed shared priority and the reasoning for the teams involved.
Do not take over delivery
Coordination does not authorize Enterprise Enablement to set a business team's delivery scope or sequence.
Business delivery teams
Confirm your delivery boundary
Identify what your team can own, what it needs from other teams, and any constraints on scope or sequence.
Contribute to shared prioritization
Explain the impact and trade-offs of your team's work so the shared recommendation reflects affected teams.
Retain delivery decisions
Your team remains accountable for deciding and delivering its own agreed scope and sequence.

Worked handoff: one request, two business teams

Illustrative example: a fictional customer request affects Northstar's Business A and Business B.

  1. 1

    Describe the shared outcome

    The requesting team explains the customer need, the requested timing, and why both businesses are involved.
  2. 2

    Coordinate the priority discussion

    Enterprise Enablement brings Business A and Business B together to compare impact, constraints, and the proposed shared priority.
  3. 3

    Confirm each delivery boundary

    Each business team states what it can deliver, its scope, and its sequence. For example, Business A may be able to provide one data feed while Business B decides whether and when to use it.
  4. 4

    Clarify unresolved ownership

    If the teams disagree about who owns a decision or handoff, the managers responsible for the affected teams clarify the boundary. Do not treat the shared priority recommendation as an automatic reassignment.

Which team owns this question?

Use the nature of the decision to find the right responsibility boundary.

A priority conflict across businesses

Bring the competing cross-business request priorities to Enterprise Enablement for shared coordination.
  • Name the affected businesses.
  • Describe the impact and requested timing.

A technical approach within one team's delivery

The business delivery team decides how to deliver its own agreed scope.
  • State the team's proposed approach.
  • Identify any dependency on another team.

A proposed change to the ownership boundary

Clarify the boundary before treating the work as reassigned.
  • Ask the managers responsible for the affected teams to resolve unclear ownership.

Where to take an unresolved question

Unclear ownership between affected teams: ask the managers responsible for those teams to clarify who owns the decision or handoff.

Unclear wording or scope in the operating-model description: ask Business Operations to clarify the description. Business Operations owns this fictional operating-model description.

When raising the question, name the work, the decision that is unclear, and the teams involved. Keep delivery moving only within responsibilities the affected teams have confirmed.