Origins of PRAGMAGILITY

From Personal Strategy to an Organizational Operating System

PRAGMAGILITY did not begin as an abstract management framework. Its earliest form emerged from lived experience: working under constraint, learning without formal advantage, speaking into uncertainty, entering unfamiliar systems, and allowing reality to correct both judgment and direction.

When I joined SGS in 1999 as a Trade Analyst, I entered with several apparent disadvantages. I did not have a degree. My typing speed was very slow, and I often operated a keyboard using only two alternating fingers. My salary was barely sufficient to cover rent, transportation, food, utilities, and basic obligations.

On conventional measures, I was not strongly positioned.

What I did possess was a wide range of practical experience. Before joining SGS, I had performed menial jobs, developed a product, participated in its manufacture, and managed its direct selling. Those experiences gave me exposure to realities that do not always appear in formal qualifications: how people respond to incentives, how products fail, how customers decide, how resources become constrained, and how survival forces adaptation.

I understood that merely asking for higher compensation would not substantially change my situation. I needed to become eligible for greater responsibility. My objective was therefore not to negotiate a better reward for my existing position, but to make myself increasingly selectable for the next one.

The method was simple.

I read whatever the organization allowed me to access about the business. I paid close attention during training. I listened carefully in meetings, particularly when leaders, specialists, and operational personnel explained how the organization functioned, what it valued, and where it struggled.

I was not only learning my assigned tasks. I was gradually constructing a broader model of the system around them.

Whenever an opportunity arose, I stated what I believed to be true. I did not always possess complete evidence, formal authority, or the vocabulary to express the issue perfectly. But when I saw something that appeared consequential, I placed it into the discussion.

My intention was not necessarily to win the argument immediately. I treated each observation as a seed. The people in authority might dismiss it, resist it, or become irritated by it. But if events later made the issue consequential, they might remember that someone had identified it early.

This approach created both recognition and friction.

I was sometimes called a “smart aleck” because I spoke directly in meetings and looked senior leaders in the eye while doing so. My manner signaled that I was willing to stand behind my interpretation, even when it challenged rank, habit, or prevailing opinion.

That directness was not always comfortable for others, and it was not always correct.

But it established that I was actively interpreting the organization rather than merely occupying a role within it.

The decisive change occurred when I was invited to participate in a project.

That opportunity opened the world of information technology to me. It exposed me to technical teams, systems, implementations, organizational dependencies, and the complex relationship between business requirements and technological execution.

I carried the same operating approach into that environment. I asked questions. I challenged assumptions. I raised concerns when I believed that technical decisions were separating from operational reality. This produced several intense encounters with technical personnel, particularly when specialist authority and practical consequences appeared misaligned.

Yet the overall result was positive. I continued to receive project assignments for almost ten consecutive years.

Projects became my real university.

They exposed me to incomplete information, competing priorities, functional boundaries, political sensitivities, time pressure, implementation risk, and measurable consequences. Each project expanded my understanding of how organizations actually change—not as a controlled sequence of plans, but as a moving system of relationships, decisions, constraints, and corrections.

There were also occasions when I was clearly wrong.

My survival in those moments did not come from defending every prior statement. It came from accepting the error and changing direction quickly. When reality contradicted my judgment, I learned to treat the correction not as personal defeat, but as a route toward a better answer.

Being wrong could still create value when it exposed what was right.

This became one of the most important operating principles behind PRAGMAGILITY: conviction must remain correctable.

Candid judgment without correction becomes arrogance. Adaptation without conviction becomes indecision. Productive action requires both: the willingness to act on one’s best current understanding and the willingness to revise that understanding when consequence proves it incomplete or mistaken.

Over time, this operating pattern contributed to nine role changes, including five promotions.

The progression was not produced by a single breakthrough, qualification, or act of sponsorship. It emerged from repeated selection for consequential work. Each assignment became evidence that I could enter unfamiliar conditions, acquire context, connect perspectives, surface problems, tolerate friction, accept correction, and continue moving.

PRAGMAGILITY later formalized this pattern.

Its foundations can be traced to several recurring movements.

The first is the movement from context to consequence.

Reading, listening, and observing created an internal understanding of the organization. But that understanding had limited value until it was brought into a meeting, project, decision, or implementation where reality could test it.

This eventually became the logic of COREDGE: establish sufficient coherence at the core, move an inference toward the edge, confront it with reality, and return the result to renew the core.

The second is the productive use of tension.

Disagreement was not always a failure of alignment. It was often evidence that different parts of the organization were carrying different truths. Business leaders, technical teams, users, and operational personnel each saw only part of the whole.

The challenge was not to remove disagreement immediately, but to preserve and route it until a more consequential resolution could emerge.

This became central to the Circles and Triangles Framework. The points represent positions, actors, or signals. The lines carry information, authority, dependency, and consequence. The triangle preserves the minimum tension required for a generative resolution. The circle defines the operating bound within which the tension can be managed.

The third is reality-based correction.

Errors cannot always be prevented, especially when decisions must be made under uncertainty. The more important capability is to distinguish what should be retained, calibrated, localized, revised, quarantined, or rebuilt.

This became VET: a disciplined method for tracing backward, testing forward, and refreshing understanding through consequence.

The fourth is relational and decisional alignment.

Projects repeatedly demonstrated that organizations can contain capable individuals while still producing incoherent collective action. Technical excellence, business knowledge, executive authority, and user experience do not automatically converge.

Someone—or some operating system—must connect the actors, decisions, and consequences while conditions continue to move.

This became the relational–decisional alignment kernel of PRAGMAGILITY:

PRAGMAGILITY aligns actors and decisions while conditions move.

The fifth is persistent differentiation.

My progression did not depend on being permanently better at one task. It depended on remaining useful as roles, technologies, projects, and organizational needs changed.

Persistent differentiation is therefore not a static advantage. It is the continuing ability to generate relevant value as context changes.

PRAGMAGILITY seeks to make that capacity reproducible at the organizational level.

It converts an individual operating method into a structured system:

• broad observation becomes contextual sensing;

• candid interpretation becomes edge inference;

• disagreement becomes managed generative tension;

• project opportunity becomes bounded permission;

• cross-functional conflict becomes relational alignment;

• visible error becomes structured correction;

• accumulated experience becomes reusable organizational knowledge;

• and repeated selection becomes persistent differentiation.

The purpose is not to produce employees who imitate the founder’s personality.

The original method depended partly on unusual personal characteristics: a high tolerance for confrontation, a willingness to operate without credential protection, low dependence on immediate approval, and the ability to recover quickly after being wrong.

An organizational system cannot require everyone to possess those traits.

It must instead create mechanisms that allow ordinary people to perform these functions safely and responsibly. That requires protected channels for dissent, bounded permission to experiment, traceable reasoning, explicit escalation routes, non-punitive correction, and clear accountability for consequences.

The institutional form must reduce dependence on personal heroics.

This is the deeper origin of PRAGMAGILITY.

It began as a way to survive and advance under constraint. It evolved through years of project work, organizational friction, technological change, and consequence-based learning. It was later compressed into frameworks, protocols, and operating primitives that could be applied beyond one person or one organization.

Its underlying proposition remains straightforward:

Organizations do not become adaptive merely by moving faster. They become adaptive when they can form coherent judgments, confront those judgments with reality, preserve useful tension, correct themselves without collapse, and continue generating value while conditions move.

PRAGMAGILITY is the attempt to make that capacity deliberate, teachable, repeatable, and institutionally durable.