Functional Field Notes
The 21 Functional Field Notes
Recurring conditions observed across organizations that surface early-warning signals of structural failure. Each names a pattern worth watching before it hardens into a failure mode.
FFN-01
Responsibility Compression at the Edge
The people closest to the work carry the most responsibility but have the least authority to change outcomes.
Functional Field Note
FFN-02
Interpretive Drift
The system has lost a shared way to interpret what it is seeing. Signals continue to flow, but shared meaning does not.
Functional Field Note
FFN-03
Authority Without Commitment
The system has authority on paper, but no mechanism that requires it to be exercised. Indecision is not neutral.
Functional Field Note
FFN-04
Escalation Inversion
Escalation paths formally exist but are functionally inverted — costly, discouraged, or reputationally dangerous. Problems get absorbed rather than surfaced.
Functional Field Note
FFN-05
Escalation Bounceback
Senior leaders frequently pass accountability down the chain rather than absorbing it at their level. Escalations circulate back to their origin.
Functional Field Note
FFN-06
Signal Misread
Incorrect tracking codes and linguistic gaps between customer language and system categories lead to misinterpreted escalation trends.
Functional Field Note
FFN-07
Orphaned Escalation
Escalation processes lack designated ownership for resolution. Handoffs multiply and resolution delays compound.
Functional Field Note
FFN-08
Authority Fog
Unclear processes for leave management, document submission, and policy updates create confusion about who holds decision authority.
Functional Field Note
FFN-09
Shadow Infrastructure
Teams navigate complex issues through informal mechanisms — creating tickets to bypass difficult problems, using homegrown tools for administrative functions.
Functional Field Note
FFN-10
Metric Displacement
Teams optimize against visible metrics while contextual factors remain unmeasured. The gap between what is scored and what matters widens without detection.
Functional Field Note
FFN-11
Context Gap
Results presented without supporting context — rate, volume, baseline comparisons — appear more significant than warranted.
Functional Field Note
FFN-12
Authority Without Permission
Decision-making stalls when teams conflate formal authority with required permission. Individuals with authority on paper still seek approval in practice.
Functional Field Note
FFN-13
Alignment Creep
Decisions accumulate alignment requirements that exceed what the decision actually needs. Each stakeholder consultation adds latency.
Functional Field Note
FFN-14
Frozen Recognition
Teams acknowledge the need for standardized decision-making protocols. Recognition of the problem persists without structural change to address it.
Functional Field Note
FFN-15
Permission Cascade
When decisions span teams, permission requirements multiply. Each boundary crossing introduces a new approval layer.
Functional Field Note
FFN-16
Defensive Escalation
When teams lack clarity on decision-making processes, decisions get pushed upward as a defensive measure. Escalation substitutes for communication.
Functional Field Note
FFN-17
Horizon Collapse
Aggressive focus on immediate results prevents visibility into second-order consequences. Strategy discussions collapse into reaction management.
Functional Field Note
FFN-18
Now Over Later
Long-term consequences are acknowledged but not weighted in decisions. Consistent prioritization of immediate results over strategic positioning.
Functional Field Note
FFN-19
Judgment Erosion
Sustained overwork leads to skill decay and weakened judgment. Leaders struggle to prioritize and delegate effectively.
Functional Field Note
FFN-20
Memory Scatter
Team members struggle to recall previous discussions and decisions. The shared narrative for why decisions were made becomes inconsistent.
Functional Field Note
FFN-21
Opaque Logic Drift
Users question AI logic and decisions when the reasoning is opaque. Initial trust depletes through repeated encounters with unexplained outputs.
Functional Field Note