Legal Strategy

What lawyers get wrong about Structuring

25 April 2026

Most legal structures fail quietly.

Not because they are invalid. Not because they fall outside the law. But because they were never truly designed to do what their creators believed they would do.

On paper, they appear sound. They read well. They pass scrutiny. They satisfy formal requirements and give the impression of control.

And yet, the moment pressure is applied, whether by investors, regulators, counterparties, or simply the passage of time, they begin to behave differently. Assumptions unravel. Outcomes diverge. The structure no longer reflects the intention behind it.

This is not a failure of law.

It is a failure of approach.

1. The Default Model: Structuring as Documentation

Most lawyers are trained to treat structuring as an exercise in documentation. The discipline is approached through the lens of drafting: define the parties, allocate the rights, record the obligations, and ensure that every scenario appears to be addressed within the four (4) corners of a document.

The process follows a familiar sequence. A company is incorporated. Shareholders’ agreements are prepared. Articles are adopted. Governance provisions are inserted. Control mechanisms are articulated through carefully drafted clauses. Each layer is added with the intention of capturing, in precise language, how the structure is meant to function.

The underlying assumption is rarely questioned. If the structure is clearly expressed, internally consistent, and legally valid, it should operate as intended. Clarity is equated with control. Precision is treated as predictability.

This model works in simple environments, where relationships are stable, jurisdictions are predictable, and the number of interacting variables remains limited. In such settings, documentation can approximate reality closely enough for the structure to behave as expected.

But complexity changes the equation.

As soon as a structure operates across multiple actors, institutions, or jurisdictions, the document becomes only one layer among many. The clauses no longer interact only with each other; they interact with external systems that interpret, filter, and sometimes override them. What is clear on paper becomes contingent in practice.

Because structures do not operate on paper.

They operate in systems, and systems rarely behave as cleanly as the documents that attempt to describe them.

2. Law Is Not Executed in Isolation

A legal document does not enforce itself. However precise its language may be, it remains inert until it interacts with the environment in which it is meant to operate.

That environment is not singular. It is a network of institutions, registries, banks, courts, regulators, counterparties, and administrative processes, each with its own logic, priorities, and interpretive process. A structure that appears coherent within a document is, in practice, filtered through all of these layers simultaneously.

Each of these actors reads the structure differently. Some focus on formal ownership. Others prioritize control. Some rely on documentation as presented. Others rely on observable behavior and historical patterns. What is decisive in one context may be secondary, or even irrelevant, in another.

This divergence creates friction.

A clause that appears definitive in a shareholders’ agreement may carry little weight when confronted with how a bank determines signatory authority in practice, how a regulator classifies effective control, or how a court reconstructs intent based on conduct rather than wording. The structure begins to fragment across interpretations.

This is where the limits of documentation become visible.

Structuring is not about writing a rule and assuming it will be applied uniformly. It is about anticipating how multiple systems will interpret, prioritize, and sometimes reshape that rule once it leaves the page.

3. The Overreliance on Templates

Templates are efficient. They reduce drafting time, standardize language, and create familiarity.

But templates encode assumptions.

They assume (i) predictable governance, (ii) balanced shareholder relationships, (iii) stable jurisdictions, and (iv) conventional use cases.

Most real structures violate these assumptions.

Founders want control without dilution. Investors want protection without responsibility. Groups operate across jurisdictions with conflicting rules. Assets are held separately from operations.

Templates stretch. But they do not adapt. And when stretched far enough, they stop reflecting reality.

4. The Confusion Between Ownership and Control

One of the most persistent errors in structuring is the assumption that ownership equals control. It is an intuitive assumption, reinforced by how companies are presented, negotiated, and even litigated. Equity percentages are visible. They are easy to measure, easy to communicate, and easy to document. As a result, they are often treated as the primary proxy for power.

But ownership and control operate on different planes.

Ownership is a legal position. It defines entitlement: to dividends, to proceeds, to certain formal rights attached to shares. Control, by contrast, is a functional outcome. It determines who actually directs decisions, influences outcomes, and shapes the behavior of the structure over time.

The two may overlap, but they are not the same.

Control can emerge through governance rights, board composition, veto mechanisms, operational dependencies, or even informational asymmetries. It may sit in the ability to appoint directors, to block key decisions, to control cash flows, or to influence day-to-day operations. In many cases, it is distributed across multiple layers rather than concentrated in ownership itself.

Because ownership is easier to document, it often becomes the focus of structuring. Percentages are negotiated, allocated, and formalized with precision. But real control frequently resides elsewhere, in mechanisms that are less visible, less standardized, and more dependent on context.

When structures are designed around ownership rather than control, the misalignment becomes apparent over time. Decision-making does not follow equity. Authority does not behave as expected. Disputes arise not from what is written, but from what actually happens.

And those failures are rarely surprising.

5. Designing for Approval, Not for Behavior

Many structures are designed with a singular objective: to be approved.

They are built to satisfy registries, regulators, investors, or internal stakeholders. The focus is on meeting formal requirements, aligning with expectations, and presenting a clean, coherent process that can pass review without resistance. Approval becomes the benchmark of success.

But approval is a moment.

It reflects a point in time when the structure is examined against a set of criteria and deemed acceptable. It does not guarantee that the structure will function effectively once it begins to operate. It does not account for how the structure will behave under pressure, across different scenarios, or over extended periods.

Behavior, by contrast, is a lifecycle.

A structure that is easy to approve may be difficult to operate. One that appears elegant and efficient on paper may produce friction in practice. Governance provisions that seem balanced may become sources of conflict. Mechanisms designed to protect may end up constraining. The clarity that facilitated approval may mask the complexity that emerges in execution.

This is where the gap between design and reality becomes visible.

The question is not whether a structure can be accepted at the outset. It is whether it can sustain its intended function over time, across situations that were never explicitly drafted, interpreted by actors who were never directly contemplated, and tested under conditions that cannot be fully predicted.

6. Ignoring Jurisdictional Gravity

One of the most subtle, and most consequential, mistakes in structuring is the assumption that jurisdictions are interchangeable.

If a rule exists, it can be implemented anywhere. If a structure is valid, it should behave consistently across borders.

In theory, this is correct.

In practice, it is not.

Every jurisdiction imposes its own form of gravity. Not through statutes alone, but through administrative density, institutional culture, enforcement patterns, and interpretive habits. These forces shape how structures behave once they leave the document and enter reality.

A provision that functions predictably in one jurisdiction may produce entirely different outcomes in another. The divergence is not necessarily legal; it is behavioral.

Some environments accelerate. Others formalize. Some refine. Others absorb.

Structuring without considering jurisdictional gravity is incomplete.

7. The Difference Between Lugano and Lanzo d’Intelvi

Consider two places that exist within close geographic proximity: Lugano and Lanzo d’Intelvi.

On paper, both operate within stable, developed European legal systems. Both offer predictability. Both are capable of hosting sophisticated structures.

And yet, their behavior is fundamentally different.

Lugano represents precision.

Its legal and administrative environment is calibrated, disciplined, and reputationally anchored. Structures placed there inherit credibility. They are read through a lens of coherence, alignment, and systemic integration. Documentation is expected to be exact. Governance must be justifiable. The structure must make sense not only internally, but externally.

Lugano does not tolerate ambiguity easily. It rewards clarity, but it also demands it.

Lanzo d’Intelvi operates differently.

It is not a center of visibility. It is not built around reputational signaling. It does not impose the same level of systemic expectation.

Its administrative environment is quieter. Interpretation outweighs automation. Context matters more than scale. Structures are not immediately classified as strategic or complex; they are first read as local, proportionate, and contextual.

This difference is not about strength or weakness. It is about behavior.

In Lugano, a structure is evaluated. In Lanzo, it is experienced.

8. Designing With Environment, Not Against It

Most structures are designed in abstraction.

The focus is on internal coherence: ensuring that rights align, obligations are clear, and mechanisms are enforceable. The external environment is considered only to the extent necessary for compliance.

But durable structures are not designed in isolation.

They are designed with their environment.

A structure placed in Lugano must respect precision. It must align with expectations of clarity, justification, and reputational coherence. Complexity must be explained. Control must be defensible.

A structure placed in Lanzo d’Intelvi must respect proportion. It must align with context, pacing, and administrative quiet. Complexity must not overwhelm its environment. Control must not appear excessive relative to purpose.

In both cases, the same structure, on paper, would behave differently.

Designing without this awareness creates friction.

Designing with it creates alignment.

9. The Cost of Misalignment

When structure and environment are misaligned, the consequences are rarely immediate.

They emerge over time.

A structure that is too complex for its jurisdiction attracts attention. A structure that is too visible for its environment invites scrutiny. A structure that is too rigid for its context begins to fracture.

These failures do not occur because the structure is invalid.

They occur because it behaves differently than expected once exposed to real conditions.

The cost is not always legal. It is operational.

Decisions become harder to execute. Control becomes harder to exercise. Disputes become harder to resolve.

And gradually, the structure drifts away from its intended purpose.

10. Structuring as Architecture

At its core, structuring is not drafting.

It is architecture.

It requires understanding not only the elements of the structure itself, but the environment in which those elements will interact. It requires anticipating behavior, not merely defining rights.

A well-drafted document can fail in the wrong environment.

A modest structure can endure in the right one.

The distinction is not technical.

It is architectural.

Beyond the Document

The legal profession tends to focus on what can be written. But structures do not live in documents. They live in systems, in institutions, in jurisdictions, and in time.

They are shaped by how they are interpreted, how they are operated, and how they are experienced by those who interact with them.

This is why many structures fail quietly. Not because they were poorly drafted. But because they were never fully designed.

Because in the end, structuring is not about capturing intent on paper. It is about making sure that intent survives contact with reality.

Originally published on my LinkedIn newsletter, The Quiet Advantage.