Sign in or create a free account to save this Card to your Deck.

Principle Card · A rule to test

Keep judgment and approval with responsible leaders

A MODEL CAN ADVISE. THE LEADER MUST DECIDE.

A project assistant can propose a changed sequence or deadline, but authorized leaders must weigh commitments, resource effects and customer consequences. Approval should be traceable. Use this principle to sharpen a concrete leadership decision while preserving context, exceptions, human dignity, and accountable authority.

Expanded teaching

Expanded teaching

The governing distinction

A project assistant can propose a changed sequence or deadline, but authorized leaders must weigh commitments, resource effects and customer consequences. Approval should be traceable. The Card is useful when this distinction changes a live leadership decision rather than becoming another slogan.

Why the distinction matters

Projects fail when activity is mistaken for progress, parallel work ignores dependencies, ownership is diffused, milestones do not correspond to usable value, or risks become visible only near the deadline. A leader can follow a superficially reasonable practice and still produce a weak result when the underlying distinction is ignored.

How to inspect it

Who may change scope, accept delay or revise a contractual promise? Compare the stated principle with several recent decisions or conversations. Record exceptions and the evidence supporting them.

Where the principle can be misused

Avoid turning a leadership principle into a universal formula. Stakes, role, capability, relationship history, decision rights, urgency, and uncertainty can change the appropriate response.

Human and AI responsibilities

AI can draft plans, map dependencies, summarize status, detect schedule anomalies from authorized data, and prepare risk briefs. Project truth still requires current evidence, accountable owners, and human approval at consequential gates.

Decision rule and next action

Record decision rights and require explicit approval before consequential changes are made. Then review whether applying the principle improved understanding, commitment, direction, performance, or delivery in the intended way.

Diagnostic inquiry

Questions to ask, not conclusions

For “Keep judgment and approval with responsible leaders,” where would applying this principle materially change a current leadership decision, and what context could justify an exception?

Questions that distinguish possible explanations

  • Who may change scope, accept delay or revise a contractual promise?
  • What adjacent competency could be mistaken for this issue? Project Implementation executes bounded initiatives. Organizational Steering chooses priorities; Performance Management manages ongoing individual and team expectations; Operations Process governs recurring delivery work.
  • What observable result would tell you the proposed next action helped? Proposed action: Record decision rights and require explicit approval before consequential changes are made.

Practical application

Practical application

Apply “Keep judgment and approval with responsible leaders” to one current leadership issue. Record decision rights and require explicit approval before consequential changes are made. Document one case where the principle applies clearly and one case where context could justify a different response.

Ask Atria

Talk through this Card

Talk it through with us

If this Card describes your week, a free conversation is the fastest way to see what it means for your company and what to do next.

Book a free conversation