You Own the Outcome. The Work Crosses Every Boundary.

You are accountable for results that depend on decisions, resources, and capabilities beyond your function. The org chart shows who leads each function. It does not show how the work moves between them—or how people will decide when priorities, capacity, and dependencies collide.

The result lives in the value stream, not in one function

Most consequential outcomes—serving a customer, launching a product, filling a critical capability—travel across functions. Finance depends on operating data. A workforce plan depends on decisions in operations, finance, and HR. A new way of serving customers touches process, systems, roles, and habits across the enterprise.

When that shared work is not designed, accountability outruns authority. A project waits for a decision. Two teams plan around different assumptions. Leaders add meetings because ownership is uncertain. These are signs the work has not been designed for cross-functional execution—not a judgment about the people doing it.

Decision rights before delegation

Clarifying RASCI—Responsible, Accountable, Support, Consulted, Informed—is a start, not the answer. A role chart alone does not resolve a cross-functional problem. The process, handoffs, decision rights, capacity, and evidence around the work must be clear too. Each critical decision needs a named owner, and everyone needs to know who decides when priorities collide.

Capability ready when needed—not merely requisitions filled

Consider a hypothetical manufacturer planning a model factory. Recruiting is already competing for TIG and MIG welders in a tight labor market. If the organization designs the factory first and hires later, the capability arrives after it is needed. If it hires against today's job descriptions, it may staff for work that automation is about to change.

Automation will reshape welding, material handling, and feeder roles—shifting demand toward maintenance and quality assurance. The question is not only "how many people?" but "which capabilities, ready when, shaped by which design decisions?" Capability planning is a cross-functional design question, not a requisition count. This example is hypothetical; its point is that workforce decisions made inside one function can commit the whole enterprise.

Systems shape the signals people see

In the Beer Game, capable people playing retailer, wholesaler, and factory roles produce boom-and-bust ordering—not because they are careless, but because delayed signals and local information shape rational local decisions into system-wide oscillation. Deming's Red Bead experiment makes the same point differently: workers measured on defects produced by the system itself cannot improve results through effort alone.

The lesson for a functional executive is direct: when outcomes disappoint, examine the design of the work and the signals people receive before concluding the people are the problem. Accountability works through clear owners and useful evidence—not through pressure applied to a system that produces the result.

A working rhythm: Analyze, Refine, Commit

Cross-functional work drifts without a deliberate review rhythm. The Compass ARC discipline—Analyze, Refine, Commit—gives owners a way to review evidence, resolve the decisions that block progress, and renew commitments at a cadence suited to the work. Each cycle asks: What result? What next work? What dependencies? Who owns each decision? What evidence? What changed?

Start with one priority

Choose one priority that crosses functional boundaries. Define the result, map the work and dependencies, clarify RASCI and decision rights, identify the adoption change, and agree the evidence and review cycle. You own the leadership of your function. You can also help the enterprise make shared work workable—so the result does not depend on one person carrying it alone.

You set the outcome. Compass works alongside you to design the work, decision rights, and execution rhythm that deliver it.