Soma Kiran Gonella
Back to all frameworks
Decision Architecture

The STEP Framework: Structural, Transactional, Exceptional, and Process

A taxonomy of organizational decisions and their interrelationships

Core Proposition

"Not all decisions are created equal. Organizations break down when they treat structural boundaries as transactional choices, or allow exceptional decisions to alter policy without governance."

Taxonomy

The STEP Decision Hierarchy

Continuous Organizational Telemetry
StructuralProcessTransactionalExceptional (Precedent loop)

Exceptional Decisions

Variable / Critical Trigger Points

Deliberate departures from established rules to resolve unforeseen emergencies, capture strategic opportunities, or solve novel problems.

Real-World Corporate Context
Granting a 35% compensation exception to secure a specialized AI researcher, or waiving Net 30 billing for a key account.
SigmaGo TelemetryDeviation Factor & Precedent Velocity
Organizational Failure RiskDangerously hardens into unmonitored shadow policy if rationale is not systematically governed.

Theoretical Foundation & Operational Mechanics

Organizations are constantly flooded with choices. Without a shared taxonomy, teams apply the same ad-hoc committee meetings to routine transactional questions as they do to irrevocable structural changes. The STEP Framework categorizes every organizational decision into one of four interconnected layers: - **Structural Decisions**: Foundational decisions that set boundaries, risk tolerances, core values, and governance architecture. These are slow-moving, high-stakes, and deliberate. - **Process Decisions**: Rules, workflows, approval hierarchies, and playbooks that determine how structural boundaries operate day-to-day. - **Transactional Decisions**: High-frequency operational applications of process rules (e.g., standard expense approvals, routine requisitions, standard customer refunds). - **Exceptional Decisions**: Deliberate or forced deviations where circumstances warrant stepping outside the standard process. Exceptional decisions are the most consequential because they test the boundaries of the organization. When an exceptional decision is made repeatedly without being recognized, it quietly creates shadow policy. SigmaGo tracks the interplay across these four layers.
Applied Scenario

Real-World Corporate Application

Context & Challenge:

A company policy mandates that all customer contracts must use standard billing terms (Net 30).

Conventional Approach

Sales leadership routinely approves Net 60 terms for large enterprise prospects as "urgent exceptions." No one tracks the aggregate frequency, leading to unexpected cash-flow compression and friction with Finance.

Decision Intelligence Approach

Every Net 60 exception is logged in the Exceptional layer connected to the Process layer. When exception frequency exceeds 18% of deals, an alert flags that the process rule is decoupled from market reality.

Resulting Organizational Outcome:

Leadership deliberately updates the Structural and Process policies to offer tiered terms, eliminating manual exception bottlenecks.

SigmaGo Product Architecture

How SigmaGo Implements This Concept

SigmaGo uses the STEP taxonomy to map organizational graphs. It measures the Deviation Factor when Exceptional decisions collide with Process boundaries and calculates Policy Health over time.

Related Intellectual Frameworks