Project Management

Support to Develop

by
This blog addresses management-related topics and has three areas of focus: 1. Technical skills; 2. Competencies in the field of interpersonal relations and communication (including personal organization and delegation, leadership, teamwork, conflict resolution, conducting meetings, and negotiation); and 3. Strategy (including diagnosis, strategic guidelines, and implementation).4.Technology

About this Blog

RSS

Recent Posts

Does Integration Need an Integrator?

Before We Rebuild, What Must We Take Apart?

When Locally Valid Decisions Become Globally Incoherent

When Yesterday’s Solutions Become Today’s Constraints

PMBOK 8 Recognizes Integration. How Is Integrative Responsibility Allocated When Leadership Is Distributed?

Categories

Agile, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Career Development, Governance, Governance, Governance, Governance, Governance, Governance, In, Integration Management, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, Interpersonal Skills, le, lea, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, Leadership, or, Organizational Project Management, Program, Program Management, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Strategy, Sustainability, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management, Talent Management

Date

Constraint as a Strategic Capability

linkedin twitter facebook Request to reuse this  


Why Freedom Requires Boundaries

For decades, organizations have pursued a remarkably consistent objective.

Greater flexibility.

Greater autonomy.

Greater empowerment.

The underlying assumption has been equally straightforward.

The fewer the constraints, the greater the organization's ability to adapt.

This intuition is partly correct.

Organizations burdened by unnecessary bureaucracy become slower, less innovative and less responsive.
Removing obsolete constraints can therefore create genuine value.

But removing constraints does not automatically create adaptability.

Organizations become adaptive not because constraints disappear, but because the right constraints remain.

Every organization depends upon boundaries.

Authority must be distributed.

Responsibilities must be assigned.

Decision rights must be defined.

Some actions may be delegated.

Others require authorization.

Certain commitments must remain protected from ordinary operational discretion.

Without these conditions, freedom does not become autonomy.

It becomes ambiguity.

Coordination weakens.

Responsibility becomes difficult to attribute.

Local decisions gradually diverge from collective purpose.

The strategic question is therefore not whether constraints should exist, but whether they preserve or undermine the organizational capabilities required for coherent adaptation.

That question becomes increasingly important as organizations become more deeply AI-enabled.

Organizational action no longer develops exclusively through individual human decisions.

It increasingly emerges through continuous interactions between people, teams and computational capabilities.

Under these conditions, organizations cannot rely on continuous executive supervision to maintain direction.

Nor can they approve every operational decision without weakening the adaptability they seek to create.

Legitimately authorized institutional intent must therefore be translated into the organizational architecture within which action occurs.

That is where constraints acquire strategic significance.

Within many organizations, constraints are still understood primarily as mechanisms of control.

They define what people cannot do.

Their value is measured largely by the behaviour they prevent.

That understanding is becoming increasingly incomplete.

A poorly designed constraint limits capability. A well-designed constraint preserves it.

The difference lies not in whether a boundary exists, but in what that boundary protects.

A constraint designed merely to reduce discretion can become an obstacle to judgment and adaptation.

A constraint designed to protect legitimate authority, institutional purpose, accountability and critical dependencies can increase organizational autonomy because it reduces uncertainty without prescribing every decision.

The objective is therefore neither maximum freedom nor maximum control. It is to sustain the conditions through which freedom remains organizationally meaningful.

Seen from this perspective, constraints are no longer merely mechanisms of compliance.

They can become architectural capabilities.

A strategic constraint is an architectural capability because it preserves the organizational conditions through which autonomy, adaptation and judgment remain coherent, legitimate and strategically consequential across continuous organizational evolution.

This definition changes how strategic constraints should be evaluated.

Their value does not depend primarily on the behaviour they restrict. It depends on the organizational capability they sustain.

A strategic constraint does not prescribe every choice.

It establishes the conditions within which many different choices can remain legitimate.

Rather than concentrating intelligence, it allows intelligence to become distributed without fragmenting purpose.

Teams can adapt to local realities.

Managers can exercise delegated authority.

Computational capabilities can recommend, coordinate and execute actions within legitimate architectural boundaries.

Governance does not need to intervene in every action because legitimately authorized institutional intent has already been translated into the conditions through which organizational action emerges.

This explains why better boundaries often create greater autonomy.

When authority is clear, fewer decisions require escalation.

When critical outcomes are explicit, teams can experiment with greater confidence.

When unacceptable states are architecturally defined, computational capabilities can operate with greater independence.

When the conditions for intervention are protected, human judgment can be concentrated where interpretation, conflicting values and institutional responsibility create the greatest organizational value.

Strategic constraints therefore do not diminish judgment.

They protect the organizational space in which judgment remains necessary and consequential.

This reveals a form of capability that is often overlooked.

Capabilities are usually understood as resources, technologies, skills or processes that enable organizations to perform activities.

Strategic constraints represent something fundamentally different.

This is not primarily a capability to perform more activity.

It is a capability to maintain organizational integrity while activity evolves.

That capability becomes increasingly valuable as complexity grows.

Different teams pursue different objectives.

Different technologies operate at different speeds.

Different stakeholders hold different expectations.

Computational capabilities continually create new opportunities for optimization and adaptation.

Each local decision may appear entirely reasonable within its own context.

Collectively, however, those same decisions can gradually weaken the organization if nothing maintains their relationship with institutional purpose.

Strategic constraints do not resolve this tension by eliminating diversity or imposing uniformity.

They resolve it by defining what must remain coherent while allowing everything else to adapt.

Purpose.

Legitimate authority.

Critical dependencies.

Risk boundaries.

Accountability relationships.

Constitutional commitments.

Within those conditions, considerable diversity remains possible.

Different teams may solve problems differently.

Different business units may pursue different operating models.

Different computational capabilities may optimize different processes.

Adaptation can therefore become distributed without becoming fragmented.

This is freedom within coherence, not freedom from coherence.

Its strategic significance extends well beyond governance.

It enables organizations to delegate authority without dissolving responsibility.

To decentralize decisions without fragmenting direction.

To automate operational activity without abandoning accountability.

To innovate and adapt without making every institutional commitment provisional or repeatedly reconstructing the foundations of legitimate action.

The capability does not lie in possessing more constraints.

Every organization already operates within numerous formal, technological, economic and cultural conditions.

At the organizational level, the capability is expressed through the ability to distinguish between constraints that preserve organizational capacity and those that merely preserve the past.

Some should remain stable because trust, predictability and institutional continuity depend upon them.

Others should evolve because strategy, technologies and operating conditions change.

Still others should disappear because the assumptions that originally justified them no longer exist.

Organizations that cannot make these distinctions often oscillate between two equally damaging extremes.

One is rigidity.

Constraints remain long after they have ceased to protect anything of strategic value.

The other is volatility.

Boundaries change so frequently that authority, accountability and organizational expectations gradually lose coherence.

Strategic capability lies between these extremes.

It protects continuity without defending obsolescence.

It enables evolution without allowing adaptation itself to become institutionally arbitrary.

Artificial intelligence makes the significance of this capability especially visible.

Computational capabilities increasingly observe, recommend, coordinate and execute organizational activity at a scale and speed that human supervision alone cannot match.

They can analyse alternatives.

Simulate consequences.

Identify patterns.

Support learning.

Improve efficiency.

But they cannot independently determine which institutional commitments should remain protected, which distributions of authority remain legitimate or which organizational values should never become variables for optimization.

Those remain institutional determinations.

Technology may support them.

It cannot legitimately replace them.

Strategic constraints allow computational capabilities to exercise increasing autonomy without separating organizational action from organizational purpose.

The advantage therefore does not arise because an organization possesses fewer constraints than others.

It arises because the organization can intentionally design, preserve and legitimately evolve better ones.

That capability influences how effectively strategy is translated into distributed organizational action and how confidently authority can be delegated.

It also affects how safely computational capabilities can be integrated and how rapidly adaptation can occur without weakening organizational integrity.

Strategy is concerned not only with where an organization intends to compete or what value it seeks to create.

It must also address the architectural conditions through which people and computational capabilities can continue pursuing that strategy coherently as the organization evolves.

Strategic constraints belong to strategy because they preserve the organizational capability through which strategy remains executable under conditions of continuous adaptation.

Organizations do not become strategically adaptive by eliminating boundaries.

They become strategically adaptive by preserving the boundaries that allow autonomy, adaptation and judgment to remain coherent, legitimate and strategically consequential.

Freedom, therefore, is not created by the absence of constraints. It is sustained by the presence of the right ones.

Yet this conclusion leads naturally to another question.

If strategic constraints protect the conditions that make coherent organizational action possible, what happens when organizations begin optimizing everything that can be measured, accelerated or improved?

Optimization always requires an objective.

But not everything an organization must preserve can safely be reduced to an optimization objective.

Some institutional conditions derive their value precisely from remaining protected from optimization itself.

That is where the next article begins.

The Limits of Optimization
What Architecture Must Protect
Posted on: August 19, 2026 07:45 AM | Permalink | Comments (0)

Constitutional Stewardship

linkedin twitter facebook Request to reuse this  


Who Preserves Institutional Legitimacy When Authority Becomes Distributed?

Organizations do not preserve their legitimacy automatically.

Policies may be documented.

Governance structures may be established.

Decision authorities may be clearly defined.

Constitutional commitments may be formally articulated.

None of these, however, is self-executing, self-interpreting or self-renewing.

Organizations evolve.

Markets change.

Technologies mature.

Leadership changes.

Structures are redesigned.

New computational capabilities emerge.

Decision formation, recommendation and execution become increasingly distributed across people, teams and computational capabilities.

The constitutional challenge therefore extends beyond defining which institutional commitments deserve deliberate preservation.

It also requires preserving, interpreting and legitimately evolving those commitments as the organization itself changes.

This is the challenge of Constitutional Stewardship.

The previous article argued that constitutional organizations intentionally preserve, interpret and legitimately evolve institutional commitments that remain more stable than the ordinary decisions, practices and arrangements they govern.

That naturally raises another question.

Who preserves those commitments as authority itself becomes increasingly distributed?

The answer cannot simply be "everyone."

Shared responsibility becomes institutionally weak when it is not accompanied by identifiable authority, differentiated duties and answerability for preservation.

Nor should institutional legitimacy depend exclusively on a single constitutional authority acting on behalf of the entire organization.

A central body may perform an important stewardship role.

But no individual, committee or office should become the exclusive source of constitutional meaning.

Constitutional Stewardship therefore begins with a simple observation.

Institutional legitimacy requires stewardship. It does not preserve itself.

Many organizations possess governance.

Fewer consciously develop stewardship.

The distinction is fundamental.

Governance structures, distributes and constrains authority.
Stewardship preserves the institutional legitimacy through which that authority remains recognizable, contestable and worthy of trust.

Governance asks:

Who may decide, within which boundaries and under what forms of accountability?

Stewardship asks:

How does the organization preserve, interpret and legitimately evolve the institutional foundations through which that authority continues to deserve recognition?

These are different questions.

Both are necessary.

Neither replaces the other.

Governance structures how authority is exercised.

Stewardship preserves the institutional conditions through which that exercise of authority remains legitimate across time.

Distributed authority can expand organizational capability.

Decisions can be made closer to operational reality.

Relevant expertise can influence action more directly.

Adaptation may become faster and more context-sensitive.

Computational capabilities can support analysis, coordination and execution at increasing scale.

Yet distribution also introduces an institutional risk.

Authority is often easier to distribute than the institutional legitimacy required to sustain its exercise.

Responsibility is easier to diffuse than answerability.

Interpretation is easier to fragment than coherence is to preserve.

Organizations may succeed in distributing decisions while weakening the institutional continuity that allows those decisions to remain collectively legitimate.

This is where governance alone becomes insufficient.

The organization also requires stewardship.

Constitutional Stewardship should not be confused with ownership.

Institutional commitments are not the property of any particular organizational actor.

They express obligations that extend beyond the tenure, preferences and authority of those temporarily responsible for interpreting them.

Stewardship is therefore not ownership or sovereign control.
It is an institutionally authorized responsibility for preserving, interpreting and enabling the legitimate evolution of constitutional commitments.

The distinction lies not in the absence of authority, but in its purpose.

Ownership claims control.

Stewardship exercises authority conditionally, on behalf of commitments that no steward may redefine unilaterally.

Constitutional Stewardship may be distributed across multiple roles, bodies and relationships.

But distribution must not become diffusion.

The organization must remain able to identify who is responsible for preserving institutional memory.

Who may interpret constitutional commitments.

Who can contest those interpretations.

Who can require reconsideration.

Who may authorize legitimate revision.

Authority may be distributed.

Stewardship may be shared.

Responsibility for preservation must nevertheless remain institutionally traceable.

Distributed stewardship therefore requires answerability, countervailing authority and institutional traceability.

Answerability ensures that those exercising stewardship can explain and justify how constitutional commitments have been interpreted, protected or revised.

Countervailing authority prevents any individual or body from becoming the exclusive source of constitutional meaning.

Institutional traceability allows the organization to reconstruct how commitments were interpreted, challenged and revised across time.

These conditions prevent distributed stewardship from becoming anonymous, insulated or structurally unaccountable.

Constitutional Stewardship also depends on several interdependent institutional capabilities.

Institutional memory preserves the reasons, precedents and commitments required to connect past decisions with present interpretation.

Institutional interpretation keeps constitutional commitments intelligible and relevant as organizational contexts evolve.

Contestability preserves the organization's ability to challenge constitutional interpretations before and after they become embedded in institutional practice.

Contestability must, however, be effective rather than merely formal.
A constitutional commitment may remain formally open to revision while becoming practically immune to learning if those who surface materially relevant dissent, adverse evidence or alternative interpretations incur personal or professional cost.
Constitutional Stewardship must therefore preserve legitimate channels through which such challenges can reach the competent authority, with protection against retaliation, appropriate confidentiality, traceability of how they are handled and an obligation to consider them.

Protected dissent is necessary, but it is not self-authorizing.
The ability to challenge a commitment does not confer authority to revise it.
Revision must remain subject to bounded authority, proportionate deliberation and the legitimacy requirements appropriate to the institutional significance of the commitment.
Protected dissent preserves the organization's capacity to recognize when revision may have become legitimate.
It does not predetermine whether revision is justified.

Coherence examines whether everyday decisions, practices and arrangements remain consistent with constitutional commitments.

Legitimate evolution allows constitutional commitments to be revised through processes proportionate to their institutional significance and supported by broader deliberation, justification and authority than ordinary operational change.

None of these capabilities exists independently.

Together, they allow constitutional evolution without reducing institutional legitimacy to either rigidity or constant revision.

Constitutional Stewardship must guard against both excessive rigidity and institutional drift.

The less visible of these risks is often drift.

Organizations rarely abandon their constitutional commitments through a single deliberate decision.

More often, legitimacy weakens through the cumulative effects of successive operational adaptations.

Exceptions become precedents.

Temporary practices become permanent routines.

Optimizations become institutional assumptions.

Over time, organizations may discover that they have not consciously revised their constitutional commitments.

They may continue to invoke those commitments while no longer preserving the conditions that give them practical meaning.

Institutional erosion is rarely dramatic.
It is usually incremental.

This is precisely why stewardship cannot be understood as occasional constitutional review.

It requires sustained institutional attention.

Stewardship should not prevent organizational evolution.

Its purpose is exactly the opposite.

Organizations must remain capable of learning, adapting, innovating and transforming when their purpose and context require it.

Constitutional Stewardship preserves the conditions through which that evolution can remain institutionally legitimate.

Not every constitutional commitment should remain unchanged.

Neither should every commitment evolve with equal ease.

Stewardship therefore preserves neither rigidity nor permanent stability.
It preserves institutional continuity through legitimately governed evolution.

This distinction defines its constitutional role.

As organizations increasingly integrate human judgment, computational capabilities and distributed authority, stewardship itself becomes an organizational capability.

It is not necessarily a single role, office or governance body.

Nor can it depend exclusively on individual leaders.

Constitutional Stewardship is not defined by any single organizational form.

It becomes organizationally real through identifiable arrangements, practices and relationships that preserve constitutional legitimacy across time.

Those arrangements may include differentiated responsibilities, interpretive practices, institutional memory, channels of contestation, countervailing authority and legitimate processes of revision.

Their form may vary.

Their institutional function cannot disappear.

Constitutional commitments cannot remain more stable than ordinary organizational change unless responsibility for their preservation remains identifiable, answerable, contestable and institutionally traceable.

Constitutional Stewardship therefore does not determine who governs the organization.
It determines how the legitimacy of governance is preserved when authority, interpretation and action become distributed.

That legitimacy is not preserved by everyone in general.

Nor is it preserved by one authority alone.

It is preserved through identifiable stewardship arrangements whose responsibilities remain institutionally visible and whose exercise of authority remains open to justification, contestation and legitimate revision.

Yet stewardship cannot depend on intention alone.

Those entrusted with preserving constitutional legitimacy must themselves operate within boundaries that prevent interpretation from becoming discretion without limit, preservation from becoming rigidity and authority from becoming capture.

This reveals a broader organizational principle.

Freedom does not become sustainable through the absence of constraints.

It becomes sustainable through constraints that preserve the conditions for legitimate action.

That is the question explored in the next article:

Constraint as a Strategic Capability: Why Freedom Requires Boundaries.
Posted on: August 17, 2026 05:35 AM | Permalink | Comments (1)

The True Gap in Organizational Transformation

linkedin twitter facebook Request to reuse this  


In the previous two articles, I sought to show that Project Management has evolved far beyond the discussion of methodologies.

Over the past few decades, the discipline progressively shifted its focus from a concern with methods to an increasing attention toward adaptation, outcomes, products, and context.

Subsequently, we saw that this evolution cannot be limited to teams.
True adaptive capacity also depends on how the organization distributes authority, structures work, funds priorities, exercises leadership, and preserves strategic coherence.

Yet this conclusion inevitably leads to a new question.

If today we better understand what characterizes an adaptive organization, why do so many transformation initiatives continue to produce results below expectations?

The Closing the Change-Readiness Gap report offers a particularly interesting answer.

Its primary contribution does not consist in identifying new methodologies or new organizational models.

It consists in showing that many organizations already know, to a large extent, what ought to change.

The problem lies elsewhere.

It lies in the difficulty of preserving the conditions that allow that intention to be transformed into effective change.

It is precisely here that what I consider to be the true gap in organizational transformation resides.

The problem is not understanding change

For many years, it was relatively common to attribute the failure of organizational transformations to people's resistance.

Whenever an initiative encountered difficulties, the explanation emerged almost automatically:
People resist change.

Although such resistance exists in certain circumstances, this explanation proves insufficient today.

Organizations invest increasingly in training, methodologies, technologies, communication, consulting, and transformation programs.

Professionals today possess far more knowledge about change management than they did twenty years ago.

Despite this, many organizations continue to face similar difficulties.

The problem, therefore, appears deeper.

It does not result merely from people's capacity to accept change.

It results from the organization's own capacity to preserve the conditions that make that change possible.

This is a fundamental distinction.

When strategy loses meaning

The first obstacle identified by the report concerns the progressive loss of context.

Organizations invest significant time defining strategy.

They clarify objectives.

They define priorities.

They produce plans.

They communicate intentions.

However, as those decisions cascade through the organization, part of their meaning is gradually lost.

What began as a strategic intention gradually transforms into:

  • Objectives;
  • Metrics;
  • Projects;
  • Tasks;
  • Instructions.
When it finally reaches the teams, what needs to be done often remains clear, but why it needs to be done is no longer evident.

This distinction is decisive.

Without understanding context, teams can execute.

However, they face far greater difficulty in adapting.

Adaptation requires understanding intention—not merely following instructions.

When context disappears, part of the capacity to make coherent decisions in the face of unexpected situations also disappears.

Strategy then ceases to guide work.

It merely describes it.

Responsibility without authority remains dependency

Another recurring obstacle relates to how decision-making power remains distributed in organizations.

In recent years, it has become common to speak of autonomous teams.

However, autonomy does not result simply from assigning responsibilities.

A team can be responsible for project outcomes and yet remain entirely dependent on successive authorizations to alter priorities, mobilize resources, resolve dependencies, or respond rapidly to new circumstances.

In these cases, the organization transfers responsibility.

However, it does not transfer effective decision-making capacity.

The consequence becomes predictable.

Teams remain waiting.

Decisions continue to ascend the hierarchy.

Priorities shift faster than the organization can respond.

Adaptation becomes slow not because teams are incapable, but because the decision architecture remains essentially unchanged.

Barriers created by the organization itself

The report also calls attention to a particularly relevant phenomenon.

Many organizations seek to become more adaptive while simultaneously maintaining structures designed to maximize stability, efficiency, and control.

This combination produces permanent tension.

  • Speed is desired; multiple approval layers are maintained.
  • Experimentation is desired; error-penalizing mechanisms are maintained.
  • Cross-functional collaboration is desired; functional silos are maintained.
  • Continuous adaptation is desired; processes designed for relatively stable environments are maintained.
There is no contradiction between people here.

There is a contradiction between objectives and organizational architecture.

Organizations begin demanding behaviors that their own structures continue to impede.

Psychological safety is also an operational issue

The report also addresses a topic that, for a long time, was treated primarily as a cultural issue:
Psychological safety.

Naturally, an important human dimension remains.

However, there is also an organizational dimension that is frequently undervalued.

Without psychological safety, information degrades.

Risks cease to be communicated in a timely manner.

Errors remain hidden.

Assumptions cease to be questioned.

Bad news ascends more slowly.

Decisions come to rely on an incomplete representation of reality.

From this perspective, psychological safety ceases to be merely a well-being factor.

It becomes an essential condition for the quality of organizational decision-making.

The greater the complexity, the greater the importance of this condition.

Because adaptive organizations depend on the continuous flow of credible information.

Without that flow, adaptive capacity is inevitably reduced.

Trust accelerates adaptation

There is another element running throughout the entire report:
Trust.

When trust exists:

  • People share information.
  • They question assumptions.
  • They experiment with new approaches.
  • They take responsibility.
  • They learn faster.
When that trust does not exist, precisely the opposite happens.

  • People avoid exposing problems.
  • They protect themselves.
  • They wait for instructions.
  • They postpone decisions.
  • They escalate situations they could resolve locally.
The organization slows down precisely when it needs speed the most.

Trust, therefore, ceases to be merely a characteristic of interpersonal relationships.

It comes to represent an invisible infrastructure of adaptive capacity.

The true problem is inconsistency

Observing these different obstacles, a common pattern emerges.

  • None of them results from the absence of methodologies.
  • None results from the nonexistence of processes.
  • None stems from a lack of technology.
The common element is different:
The organization seeks to adapt without preserving the conditions necessary for that adaptation to occur.
  • It wants speed; it maintains slow structures.
  • It wants autonomy; it maintains centralized authority.
  • It wants innovation; it maintains risk aversion.
  • It wants learning; it maintains cultures where error continues to be penalized.
  • It wants collaboration; it maintains local incentives.
Inconsistency thus becomes one of the greatest obstacles to organizational transformation.

Not because organizations do not know the path, but because they frequently remain organized according to assumptions incompatible with the outcomes they intend to achieve.

The true gap

Perhaps this is the main message of the report.

The true gap in organizational transformation does not separate strategy and execution.

Nor does it separate leadership and teams.

Much less technology and people.

The true gap separates what the organization intends to achieve from the conditions it preserves to make that intention possible.

This distinction profoundly alters how we interpret transformation.

Transforming ceases to mean merely altering structures, processes, or methodologies.

It comes to mean preserving a set of organizational conditions that make it possible to learn, decide, adapt, and create value continuously.

When those conditions do not exist, any transformation initiative will inevitably hit a limit.

  • Regardless of the quality of the methodology used.
  • Regardless of the competence of the teams.
  • Regardless of the available technology.
A new perspective on transformation

Perhaps the greatest contribution of Closing the Change-Readiness Gap is precisely this:

To remind us that transforming an organization does not consist merely in defining a new direction.

It consists in ensuring that this direction can cascade throughout the entire organization without losing meaning, decision capacity, trust, and coherence.

True readiness for change does not depend solely on strategic intention.

It depends on the conditions that allow that intention to be transformed into action.

And that distinction profoundly alters how we understand Project Management itself.

Because projects are, increasingly, one of the primary mechanisms through which organizations materialize their strategy.

If these conditions are not preserved, projects will also inevitably encounter limits that no methodology will be able to resolve.

The problem, after all, does not consist merely in changing the organization.

The true challenge consists in preserving the conditions that allow that change to happen.

In the next article, I will analyze the implications of this evolution for the role of the Project Manager and discuss why this professional is assuming an increasingly important role as an integrator between strategy, execution, people, technology, and organizational transformation
Posted on: August 16, 2026 04:49 AM | Permalink | Comments (2)

The Constitutional Organization

linkedin twitter facebook Request to reuse this  


Why AI-Native Organizations Need Institutional Guardrails
Every organization must adapt.

Markets change.

Technologies evolve.

Customer expectations shift.

New risks emerge.

Competitive advantage rarely lasts.

For decades, adaptability has therefore been recognized as an important capability for organizations seeking to remain viable and relevant over time.
More recently, artificial intelligence has reinforced this imperative by expanding the speed and scale at which organizations can analyse information, generate alternatives and coordinate action.

The ability to change has become a strategic capability.

Yet this creates an important question.

If organizations become increasingly capable of changing more of how they operate, what should intentionally remain more difficult to change?

This is not merely a philosophical question.

It has become an organizational one.

The more adaptive an organization becomes, the more important it becomes to distinguish between what should evolve continuously and what should evolve more deliberately.

This is the constitutional challenge of AI-native organizations.

The previous article argued that governance creates its greatest value not only by reviewing important decisions, but by designing and preserving the organizational conditions within which those decisions are formed.

That argument naturally leads to a further question.

If governance increasingly shapes organizational architecture, should every element of that architecture remain equally open to revision?

Intuition often suggests that adaptability requires maximum flexibility.

In practice, sustained adaptability also depends on deliberate stability.

Organizations capable of sustained adaptation are rarely those in which everything changes.

They are those in which change occurs around institutional commitments that remain sufficiently stable to preserve organizational coherence.

Without such commitments, adaptability can gradually become volatility.

Local optimization may displace organizational purpose.

Distributed autonomy may fragment collective action.

Continuous change may slowly lose direction.

Adaptability therefore depends not only on the capacity to change.

It also depends on preserving the conditions that give change coherence.

This distinction becomes increasingly important as organizations distribute authority across people and computational capabilities.

Artificial intelligence can optimize schedules, generate recommendations, detect patterns, coordinate workflows and support resource allocation.

As computational capabilities evolve, they are likely to perform many of these activities with increasing effectiveness.

Computational capabilities may inform questions about what an organization should preserve.

They cannot, by themselves, determine which institutional commitments should evolve more cautiously than ordinary operational arrangements, because that determination requires institutional legitimacy rather than computational performance.

Optimization answers different questions.

It identifies preferable choices within a defined objective, model and set of constraints.

It does not determine which objectives, constraints or institutional commitments deserve deliberate preservation.

That determination remains an institutional responsibility rather than a computational one.

This distinction reveals that organizations evolve at more than one level.

Operational adaptation concerns how the organization changes the way it performs its work.

Constitutional evolution concerns how the organization preserves, interprets and legitimately revises the institutional conditions within which that adaptation occurs.

Confusing these two forms of change can produce organizations that become increasingly responsive operationally while progressively weakening their institutional coherence.

For this reason, constitutional commitments should not be confused with operational rules.

Operational rules govern how work is performed within established institutional boundaries.

They should remain open to revision when evidence, context or improved methods justify change.

Constitutional commitments serve a different purpose.

They express the institutional conditions that the organization considers sufficiently important to preserve across ordinary adaptation.

Their revision requires broader legitimacy because those conditions shape how future decisions will be formed and how organizational authority will be exercised.

Protecting those commitments requires constitutional guardrails.

Constitutional commitments express what the organization intends to preserve.

Constitutional guardrails are the principles, structures, authorities and practices through which those commitments are protected and legitimately revised.

The distinction is fundamental.

The commitment identifies what should remain more stable than ordinary organizational change.

The guardrail preserves that differentiation by preventing the commitment from being altered accidentally, silently or through the cumulative effects of routine decisions.

Constitutional guardrails should not be equated with bureaucracy.

Bureaucratic arrangements can preserve consistency, due process and institutional memory.
They can also perpetuate procedures after their original purpose has weakened.

Constitutional guardrails are distinguished not by resistance to change, but by the institutional commitments they protect and by the legitimacy required to revise them.

Organizations frequently remove constraints in the name of agility.

Sometimes they should.

Some operational constraints outlive their purpose and slow execution without creating commensurate value.

Constitutional guardrails are different.

They exist because not every capability should automatically become organizational authority.

Not every optimization should become organizational policy.

Not every efficient solution should become an acceptable one.

Without constitutional guardrails, organizations risk confusing what is technically possible with what remains organizationally legitimate.

One of the deeper dangers is therefore not simply that artificial intelligence becomes increasingly capable.

It is that organizations may gradually lose the institutional reference points required to exercise those capabilities responsibly.

This does not imply that constitutional commitments are immutable.

Organizations must remain capable of evolution.

Markets change.

Technologies mature.

Social, legal and ethical expectations evolve.

Constitutional arrangements that cannot evolve may eventually obstruct the organizations they are intended to protect.

The constitutional challenge is therefore not preserving permanence.

It is preserving continuity.

Institutional commitments do not all require the same pace or process of evolution.

Some may be revised through ordinary governance.

Others should require broader deliberation, stronger justification and wider institutional legitimacy.

The defining characteristic of a constitutional commitment is not that it never changes.
It is that it must not be allowed to change accidentally.

Its revision requires broader institutional legitimacy than ordinary operational change because it modifies the conditions within which future decisions will be formed.

This distinction separates constitutional evolution from operational adaptation.

Viewed in this way, the Constitutional Organization is not defined by the existence of a written constitutional document.

Nor is it defined by any particular governance model.

It is defined by the intentional preservation, interpretation and legitimate evolution of institutional commitments that remain more stable than the ordinary decisions, practices and arrangements they govern.

Those commitments provide continuity while allowing adaptation.

They help preserve legitimacy while enabling innovation.

They create coherence without preventing learning.

Most importantly, they protect against organizational evolution gradually removing the conditions that make responsible evolution possible.

Constitutional commitments therefore do more than preserve organizational continuity.

They define the conditions under which organizational evolution itself remains legitimate.

As organizations become increasingly AI-enabled, the strategic challenge extends beyond deciding faster, optimizing better or adapting more frequently.

It also involves preserving the institutional foundations that allow adaptation itself to remain coherent, legitimate and sustainable.

Architectural Governance concerns the organizational conditions that shape how decisions emerge.
The Constitutional Organization distinguishes the institutional conditions that may evolve through ordinary adaptation from those whose revision requires broader legitimacy because they shape the legitimacy of future organizational action.

Yet one fundamental question remains.

If constitutional commitments must be preserved, interpreted and legitimately revised across time, who carries that responsibility?

Not who owns the constitution.

Not who originally designed it.

But who preserves its legitimacy through continuous organizational evolution.

That is the question explored in the next article:
Constitutional Stewardship - Preserving Legitimacy Across Organizational Evolution.
Posted on: August 14, 2026 03:57 AM | Permalink | Comments (0)

Architectural Governance

linkedin twitter facebook Request to reuse this  


Designing Boundaries Before Decisions Happen
Organizations often make governance most visible when an important decision reaches the boardroom.

A strategy is presented.
An investment is approved.
A project receives authorization.
A policy is reviewed.
Governance is expected to examine the proposal, exercise judgment, authorize a course of action and ensure accountability before a final decision is made.

For decades, this understanding remained workable because consequential decisions could still be treated, for governance purposes, as identifiable moments of review, authorization and accountability.

That understanding remains necessary.

It is no longer sufficient.

In AI-enabled organizations, important organizational outcomes rarely originate from a single decision.
They emerge through continuous interactions between people, computational capabilities, organizational processes, delegated authority and operating conditions that evolve continuously.

By the time a proposal reaches a governance body, much of the decision has already been shaped.
Information has been selected.

Alternatives have been filtered.

Priorities have influenced the analysis.

Recommendations have been generated.

Certain courses of action have become more visible, more credible and therefore more likely than others.

The formal decision still matters.

But it is no longer where organizational behaviour truly begins.

This changes a fundamental assumption about governance.

If decisions are increasingly shaped before they are formally made, governance cannot concern itself only with the decisions organizations make.

It must also concern itself with the organizational conditions that shape how those decisions are formed.
That shift represents far more than a procedural adjustment.

It changes the very object of governance.

Organizations often treat decisions as beginning when someone consciously chooses between competing alternatives.

In reality, they usually begin much earlier.

A procurement committee evaluates suppliers that have already passed qualification criteria.

A project steering committee reviews options that have already been analysed, prioritised and framed.

An executive approves recommendations that have already been influenced by available information, organizational priorities, established processes and computational capabilities.

None of these conditions determines the final decision.

Together, however, they shape the decision environment within which judgment is exercised.

Organizations have always operated within structures that influence behaviour.

What has changed is the speed, scale, continuity and embeddedness of that influence.

Computational capabilities continuously process information, identify relationships, generate recommendations and coordinate activities across organizational boundaries.

Increasingly, organizational behaviour develops between formal moments of executive intervention rather than simply because of them.

If the architecture shaping decisions becomes more influential than the decision moments themselves, governing decisions alone can no longer be sufficient.

This does not diminish the importance of leadership.

Boards remain responsible for strategy.

Executives remain accountable for organizational performance.

Human judgment remains indispensable.

What changes is where governance creates its greatest value.

Traditional governance asks who is authorized to decide.

Architectural Governance retains that question, but asks an earlier one.

Under what organizational conditions will that decision be formed?

The distinction appears subtle.

Its implications are profound.

Authority determines who decides.

Architecture shapes the conditions within which every decision becomes possible.

Organizations do not repeatedly produce coherent decisions by accident.

They are more likely to do so when their architecture consistently supports coherent judgment and responsible action.

Governance therefore creates value long before any proposal reaches a governance meeting.

Its contribution lies not only in reviewing important decisions, but in designing and preserving the organizational conditions that continuously influence how decisions are formed.

This perspective also changes the meaning of organizational boundaries.

Boundaries are often interpreted as restrictions on autonomy.

In reality, well-designed boundaries are among the strongest enablers of responsible autonomy.

An experienced project manager does not require executive approval for every operational adjustment because the organization has already established delegated authority, budget tolerances, escalation criteria and acceptable levels of risk.

Those boundaries do not eliminate judgment.

They make judgment possible without constant supervision.

The same principle increasingly applies to computational capabilities.

Artificial intelligence may analyse scenarios, optimise schedules and generate recommendations at unprecedented speed.

Its effectiveness depends not only on computational capability, but also on the organizational architecture within which that capability operates.

Which information may be used?

Which recommendations require human validation?

When must authority be escalated?

Which decisions require human judgment, accountability or authorization?

These questions cannot be answered after a recommendation has been produced.

They must be addressed before the recommendation becomes possible.

Governance therefore extends beyond supervising decisions.

It increasingly includes designing and preserving the architecture that shapes them.

Architecture is never neutral.

Every workflow, delegation mechanism, decision rule and computational model influences how authority is exercised, how information flows and how responsibility is distributed.

Over time, organizational performance depends not only on the quality of individual decisions, but also on the quality of the architecture that repeatedly shapes them.

No architecture guarantees perfect decisions.

No organization can eliminate uncertainty.

What architecture can do is considerably more important.

It can preserve the organizational conditions within which responsible decisions become consistently more likely.

This may ultimately become one of governance's most important responsibilities.

Good governance is concerned not only with making legitimate decisions.

It is equally concerned with preserving the organizational conditions that make legitimate decisions possible.

As organizations increasingly distribute work across human and computational capabilities, that distinction becomes progressively more important.

Without coherent architecture, accountability gradually weakens.

Authority becomes ambiguous.

Responsibility becomes increasingly difficult to attribute.

Adaptability eventually loses coherence.

Conversely, when organizational conditions are intentionally designed and continuously preserved, autonomy becomes more responsible, coordination becomes more consistent and adaptation becomes more sustainable.

Governance, therefore, is not the opposite of organizational freedom.

It is one of the conditions that makes responsible freedom possible.

As organizations become increasingly adaptive and AI-enabled, governance can no longer be understood solely as the oversight of important decisions.

The decisions that matter most are increasingly shaped long before they reach a boardroom, an executive committee or a steering committee.

Governance therefore creates its greatest value not by supervising more decisions, but by designing and preserving the organizational conditions that make responsible decisions more likely across the organization.

Architectural Governance is not about replacing leadership with structure.

Nor is it about constraining organizational adaptability.

It is about ensuring that authority, autonomy, accountability and organizational purpose remain coherently connected before decisions are made, rather than attempting to reconnect them afterwards.

Yet this immediately raises a deeper question.

If governance increasingly shapes the architecture through which organizations adapt, should every element of that architecture remain equally open to change?

Or are there certain institutional commitments that must remain intentionally more stable because they preserve the legitimacy of everything that follows?

That question leads naturally to the next step in this series:

The Constitutional Organization — Why AI-Native Systems Need Institutional Guardrails.
Posted on: August 12, 2026 05:46 AM | Permalink | Comments (0)
ADVERTISEMENTS

"Love your enemies just in case your friends turn out to be a bunch of bastards."

- R.A. Dickson

ADVERTISEMENT

Sponsors