Program & Project Management

“Herding Cats” Is Not a People Problem. It Is Undeclared Authority.

Influence is a genuine skill and worth building. It is also, in most programs, being asked to carry weight that belongs to a decision nobody has made: who may commit this function's capacity to this outcome, and who resolves it when two commitments collide.

Steve Kopecky · 8 minute read

The position you are actually in

You are responsible for delivering something. The engineers report to an engineering director. The analysts answer to finance. The subject-matter experts have their own managers, their own priorities and their own performance reviews, none of which mention your dates. That is the ordinary condition of program work, and no amount of personal capability changes its structure.

The standard advice is to build relationships, pre-align before the meeting, create a coalition, trade favours. It works, and it is worth doing. But notice what it is: a set of private workarounds for a public gap. Each one has to be re-earned every quarter, with every new leader, on every new program.

The tell is how you spend your week. If most of your energy goes into securing capacity that was already committed on paper, you are not short of influence. The organization is short of a declared decision.

Influence is what a capable person does in place of a decision the organization has not made.

The four decisions that are usually missing

First, who commits capacity. When a function agrees to a program, what exactly was committed — named people, a number of hours, or a good intention — and who has the standing to change it.

Second, who resolves a collision. When the same person is promised to a program and to a quarter-end close, there must be one named place where that is settled quickly. Absent that, it is settled by whoever escalates hardest.

Third, what the program manager may decide alone. A real capability states it: re-sequencing inside the baseline, yes; moving a gate date, no. Without that line, every decision is either taken timidly or taken and then relitigated.

Fourth, what a gate actually gates. If a gate can be passed on optimism, then no authority exists anywhere in the program — the sponsor has authority over a formality.

Exercise

Write the authority line, then take it upward

In one page: the decisions you take alone, the decisions you bring to the sponsor with a priced recommendation, and the decisions that belong to the steering forum. Take it to your sponsor and ask them to correct it rather than approve it. The corrections are the real map — and once it is written, you are no longer negotiating authority in the middle of a crisis.

Why sponsors say yes to this

Program managers hesitate to raise authority because it sounds like a request for power. Framed as a decision map it is the opposite: it tells the sponsor precisely which decisions will arrive at their desk and which will not. Most sponsors are carrying a stream of small program decisions they never wanted, arriving late and without options.

The exchange that works is simple. You bring priced options instead of assertions — what pulling the date in costs per day bought, what fast-tracking exposes in rework, what descoping gives up in capability. In return you ask for the authority line to be written down. Sponsors accept that trade readily, because it converts their inbox of problems into a short list of choices.

Use it this week

  • Set the RACI at activity levelOne accountable name per activity, priced schedule options, and gates with binary pass criteria — the written form of the authority line.

What changes in about a month

Once authority is declared, the work does not become easier — it becomes ordinary. Decisions get made at the level they belong to. The weekly gets shorter because it holds decisions rather than status. Functional leaders stop being asked for favours and start being held to commitments they actually made.

The program manager stops being a person who chases and becomes a person who runs a record. That is not a promotion. It is the job, finally given the structure it needed.

Six signs authority was never declared

  • Capacity that was committed on paper has to be re-secured every month.
  • The same collision between program work and functional work recurs without ever being decided.
  • You do not know, in writing, which decisions are yours.
  • Gates have been passed with evidence outstanding.
  • Escalation depends on your personal relationship with one executive.
  • Two people believe they are accountable for the same outcome.

Write the one-page authority line this week and take it to your sponsor as a draft to be corrected. It is the least political version of the conversation, and it usually gets a yes. If you would rather think it through with somebody who has written a few of them, that is a conversation worth having and nothing more than that.

Share this

LinkedInX

Download this article

The French and Spanish sheets are translated at board register on request; the structure, exhibit and checklist are identical in all three.

Kept on this device — no address collected, nothing emailed.

The other side of the argument

Send a question or an insight

Nothing here is published. Your note goes directly to Steve Kopecky, who reads every one — reader questions decide what gets written next.

What kind of note is this?

0 of 4000 characters. Please leave out client names and confidential detail.

Or email directly

Aligned to FOUNDATION™

Present reality, leadership capability, purpose and organizational health.

Continue reading

Organization Design

Clean Sheet Organization Design: Building the Structure the Strategy Requires

A clean sheet design starts from the strategy and the vital few opportunities, not from the current org chart. This is the process, the ownership and the SIPOC that governs it.

Organizational Architecture

The Eight Culture Types Are Not Types. They Are Eight Reinforcement Patterns Your Design Is Already Running

The eight culture descriptors in circulation describe what an organization rewards, tolerates and discourages. Read that way they stop being labels to pick and become findings to trace back to the mechanism producing them.

Personal Effectiveness

A Message on Personal Habits: The Private Architecture Behind Every Executive Result

Architecture determines performance — and that is as true of a person as it is of an enterprise. A long-form message on habit design, 80/20 daily management, and the self-talk that governs behavior.

Organizational Architecture

The Engagement Layer: Why Slack Sits at the Center of Every Compass Partnership

Most advisory relationships depend on quarterly meetings and email chains. Compass designs the engagement as an operating layer — and Slack is where it lives.

Growth & Value Creation

The Second Curve Begins Before the First One Ends

The right moment to build what comes next is while the current business is still strong — which is precisely when no one feels the need to.

Simplification

Complexity Quietly Consumes Margin, Capacity and Leadership Attention

No one approves complexity. It accumulates one reasonable decision at a time, and it is paid for in margin, speed, and executive attention.

Simplification

FOCUS: The Vital Few Constraints That Create Economic Value

FOCUS is not doing less. It is concentrating effort on the customers, products, and markets that produce disproportionate value — and removing the complexity mirror they cast inside the organization.

Organizational Architecture

What Is Enterprise Business Architecture — and Why Does It Determine Performance?

Enterprise business architecture is the deliberate design of how an organization decides, aligns, and executes. It sets the ceiling on performance long before effort does.

Organizational Architecture

The Ten Elements of an Enterprise Architecture — and Why They Only Hold Together

Strategic intent, simplification, leadership, governance, planning, cadence, decision rights, performance, enabling systems, and renewal. Designed together, or not designed at all.

Strategy & Execution

Architecture vs. Improvement: Why Better Execution Cannot Fix a Flawed Design

Improvement makes the current system perform closer to its limit. Architecture changes the limit. Confusing the two is the most expensive mistake in the mid-market.

Organizational Architecture

Every Organization Is Producing Exactly What Its Design Allows

Decision rights, cadence, reporting lines, incentives and leadership habits are not background. Together they are the machine producing the number on the books.

Organizational Architecture

Effort Cannot Solve a Design Problem

Pressure produces a short improvement, then the system pulls the result back to where the architecture says it belongs.

Organizational Architecture

Architecture Is Designed, Not Discovered

The work is concrete: name the few outcomes that matter, place each decision where it is properly made, remove the complexity consuming margin, and rebuild the cadence so commitments close.

The CEO / Owner Lens

The Chief Executive Is Not Supposed to Be the Integration Mechanism

When strategy only reaches the work through the chief executive, growth adds volume to an unresolved design. The fix is structural, not personal.

The CHRO / People Lens

Turnover Is Usually a Structural Reading, Not a Hiring Result

When roles, capability, managers and recognition point in different directions, capable people leave — and the organization reads it as a recruiting problem.

The Operations Lens

Performance That Depends on Who Is on Shift Is Not Performance

Where the process is undefined, capable people carry it. The result looks like variable performance and is read as a discipline problem.

The ERP / Systems Lens

An ERP Program Is a Process Decision Wearing a Technology Budget

Systems enable the management system; they never replace it. Configuring before the process is designed automates the current mess at scale.

The Exit / Succession Lens

A Buyer Discounts Precisely What the Owner Cannot Hand Over

Transferable value is documented processes, governed data, named successors and results that hold when the founder is not in the room.

The Leadership Team Lens

A Team That Meets Often and Decides Rarely Is Compensating for a System

When reviews end in discussion rather than dated commitments, the same root cause is rediscovered every quarter.

The AI & Data Lens

Pilots Demonstrate Capability. Designed Processes Produce Results.

AI moves a measure inside a process. Where the process is undesigned and the data ungoverned, there is nothing for it to move.

The Transformation Lens

Exhaustion Is Routinely Misread as Resistance

Change fails at the point of absorption far more often than at the point of design. Capacity, honesty about recent change, and reinforcement decide the outcome.

The Strategic Program Lens

Becoming Efficient at Work You Never Chose

Portfolios fail at intake far more often than in delivery. Unranked work consumes the capacity that strategy was supposed to direct.

The Next-Curve Lens

The Next Curve Is Absorbed by the People Already at Capacity

A next curve is designed on paper and delivered by an organization that must also run the current one. Readiness is whether the system can carry both.

The next step

See this in your own organization.

Reading about the operating system is one thing. Seeing yours clearly is another. Start with where you actually are.

Not sure where to start?

Three questions, and we point you to the right instrument.

Under a minute. From this page, most leaders begin with The organization.