Principles Library / Explicit Constraints

Explicit Constraints

Explicit Constraints Clarify Priorities

Act

Showing all 6 practices. Answer the Diagnose questions and the most relevant come first.

Name the constraints that shape the outcome

Identify the constraints that materially shape the delivery outcome, such as customer commitments, regulatory obligations, funding and capacity.

Start by asking your team: What constraints genuinely shape this outcome?

Avoid · You’ll know it’s working when

Avoid

Assuming more constraints automatically improve prioritization

You’ll know it’s working when

Regulatory, technology and capacity limits are known before commitments are made, and teams read priorities the same way.

Separate real constraints from assumptions and preferences

Check each stated constraint and separate the real ones from assumptions, preferences and artificial deadlines.

Start by asking your team: Are we treating an assumption or preference as a real constraint?

Avoid · You’ll know it’s working when

Avoid

Treating every leadership preference as a constraint
Imposing arbitrary deadlines without a meaningful business reason

You’ll know it’s working when

Assumptions get questioned before anyone treats them as fixed, and trade-offs get settled where they arise.

Mark which boundaries are fixed and which flex

Make it explicit which boundaries are fixed and which are negotiable, so people know where a trade-off can be made.

Start by asking your team: Which constraints are fixed, and which are negotiable?

Avoid · You’ll know it’s working when

Avoid

Fixing time, scope, funding and quality all at once without acknowledging the trade-offs

You’ll know it’s working when

Everyone can say which of dates, scope, funding and quality is fixed, and those expectations no longer conflict.

Settle trade-offs against constraints before work starts

Use the agreed constraints to resolve trade-offs before work begins, and drop the options they rule out.

Start by asking your team: What trade-off should this constraint force us to make?

Avoid · You’ll know it’s working when

Avoid

Using constraints primarily to control teams

You’ll know it’s working when

Trade-offs are decided before work starts, and only a few things carry the high-priority label.

Revisit constraints when business conditions change

Revisit constraints when business conditions materially change, and retire the ones whose purpose has gone.

Avoid · You’ll know it’s working when

Avoid

Keeping outdated constraints after their original purpose has disappeared

You’ll know it’s working when

Priorities hold through new demand and move only when business conditions change materially.

Set clear decision boundaries for agents

In AI-enabled delivery, define boundaries for agent authority, cost, risk, data access and human review.

Start by asking your team: As AI increases execution capacity, what boundaries must remain explicit?

Avoid · You’ll know it’s working when

Avoid

Allowing agents broad authority without clear boundaries on risk, cost or human oversight

You’ll know it’s working when

Agents work inside clear decision boundaries, and their calls fit business, regulatory and architecture constraints.

Overview

Principle intent

Make the real boundaries affecting an outcome explicit so that trade-offs can be resolved and priorities can be set with confidence.

Read the full intent

Relevant constraints may include customer commitments, regulatory obligations, funding limits, technology boundaries, capacity, security, quality, or risk tolerance. When constraints remain implicit, teams make different assumptions and priorities become unstable.

When it holds: what it does for you

Priorities that hold

Teams read priorities the same way, and they don't move every time new demand arrives.

Trade-offs settled early

Decisions get made against agreed boundaries before work starts, so fewer of them climb the escalation chain.

Commitments people believe

Hard limits show up early, so the dates and scope you commit to stand up.

When it is ignored: from early signs to a lasting condition

Early warning signs · Visible now, cheap to fix

Dates, scope, funding and quality expectations conflict with each other.
Assumptions are treated as non-negotiable constraints.
Important regulatory, technology or capacity limits turn up late.

What happens over time · Accumulates, costly to reverse

With no agreed constraints, priorities feel subjective and keep changing.
Trade-offs stay unresolved and decisions slow through repeated escalation.
Delivery commitments have lost their credibility.

The condition it becomes

Strategic Volatility · Primary

Every quarter starts over. Nothing compounds.

How this principle feeds it

priorities that change often enough stop commitments from being kept, which is the condition itself.

Workload Saturation · Primary

Everything is in progress. Nothing is finishing.

How this principle feeds it

more objectives and growing scope with fixed capacity is more work in progress than the system can finish.

Oversight Erosion · Secondary

The review process still runs. It stopped meaning anything.

How this principle feeds it

review sized for earlier agent volume checks less of what agents do as activity grows.

Local Optimization Bias · Secondary

Every team hits its targets. The product still misses.

How this principle feeds it

without named constraints, teams and agents optimize their own reading of priority and the end-to-end outcome falls.

Where is your system on this path?

Diagnose

AI signs are on by default. Use the AI switch to exclude them.

1. Which of these early warning signs are you seeing?

Everything is labeled high priority.
Teams read the same priorities differently.
Dates, scope, funding and quality expectations conflict with each other.
Trade-offs keep getting deferred or escalated.
Assumptions are treated as non-negotiable constraints.
Priorities shift whenever new demand shows up.
Important regulatory, technology or capacity limits turn up late.
Agents work toward broad objectives with no clear decision boundaries. (AI)
AI activity keeps rising while business priority stays unclear. (AI)
Reviewers spend more time filtering agent output that serves no stated priority. (AI)
Agents make technically valid calls that clash with business, regulatory or architecture constraints. (AI)

2. Over the last few months, have you noticed…

For each consequence: Not seen / Sometimes / Persistently / Not sure.

With no agreed constraints, priorities feel subjective and keep changing.
Trade-offs stay unresolved and decisions slow through repeated escalation.
Teams chase too many competing objectives while scope and workload keep growing.
Delivery commitments have lost their credibility.
AI activity outgrows governance because nobody set its decision boundaries. (AI)
Teams and agents optimize their own reading of priority, and system outcomes slip.

3. The condition it becomes

Based on your answers, recognize at most two conditions: No / Partly / Yes, that is us.

Strategic Volatility: Every quarter starts over. Nothing compounds.

Workload Saturation: Everything is in progress. Nothing is finishing.

Oversight Erosion: The review process still runs. It stopped meaning anything.

Local Optimization Bias: Every team hits its targets. The product still misses.

Take your Diagnosis to the next level by invoking AI Diagnostic Coaching tool.

What else have you observed? Optional. Shared only if you choose to start coaching.

Start a Diagnosis session: review and edit a draft containing your note, conditions you recognized in Step 3 (including whether they match partly), warning signs and consequence ratings before sending it. No scores or principle files are sent.

See what practices will help you