Better Title Page Here

Description here

01. Discoverability

Tribal Knowledge

Invisible processes and hidden tribal knowledge that prevent teams from finding established workflows.

Understanding Discoverability

A Lack of Discoverability occurs when processes exist in silos, unindexed documentation, or purely within individual memory. Rather than leveraging verified existing paths, teams waste time recreating duplicate workflows or guessing correct procedures.

Key Indicators:

Heavy reliance on informal messaging channels to ask "how do I...?"
Redundant tools or workflows built independently by different teams.
Documented procedures buried in private drives without central indexing.

Sources:

Ackerman, M. S. (2000). The Intellectual Challenge of CSCW: The gap between social requirements and technical feasibility. Human-Computer Interaction, 15(2), 179–203. https://doi.org/10.1207/S15327051HCI1523_5

02. Distraction

Energy Vampires

Noise and administrative overhead that fracture focus and derail high-value execution.

Understanding Distraction

Distraction accumulates when fragmented processes, constant notifications, and repetitive status check-ins disrupt deep work. When processes force frequent context-switching, teams spend disproportionate effort re-orienting themselves to primary tasks rather than delivering core value.

Key Indicators:

Frequent interruptions requiring task re-entry.
High volume of administrative coordination relative to actual output.
Fragmented communication channels across multiple tools.

Sources:

Mark, G., Gudith, D., & Klocke, U. (2008). The cost of interrupted work: More speed and stress. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, 107–110. https://doi.org/10.1145/1357054.1357072

03. Dunning-Kruger Effect

Overconfidence

A cognitive bias where teams lack the metacognitive skill to recognize workflow inefficiencies, leading to misplaced confidence in broken processes.

Understanding Dunning-Kruger Effect

Dunning-Kruger process debt occurs when teams or leaders lack the operational perspective required to evaluate their own workflows objectively. Because the skills needed to design an optimal process are the exact same skills needed to evaluate one, low-competence process owners mistakenly believe inefficient, legacy workarounds represent peak performance.

Key Indicators:

Unwarranted high confidence in outdated, manual, or high-friction processes.
Immediate pushback or resistance toward objective efficiency audits and modern tooling.
Inability to recognize superior process design or operational benchmarks demonstrated by other teams.

Sources:

Kruger, J., & Dunning, D. (1999). Unskilled and Unaware of It: How Difficulties in Recognizing One's Own Incompetence Lead to Inflated Self-Assessments. Journal of Personality and Social Psychology, 77(6), 1121–1134. https://doi.org/10.1037/0022-3514.77.6.1121

04. Parkinson's Law

Procrastination

Parkinson's Law dictates that work expands to fill the time allotted for its completion, driving artificial complexity, bloated schedules, and structural inefficiency across organizational workflows

Understanding Parkinson's Law

When leadership allocates generous timelines under the assumption that extra time guarantees higher quality, teams unconsciously pace their execution to match the allotted window, over-polishing deliverables or delaying action until deadline urgency mounts. This temporal elasticity induces scope creep, administrative churn, and perfectionism, converting open capacity into low-value activities rather than raw throughput. Organizations routinely fall into this trap because padding time buffers is perceived as a risk-mitigation strategy; however, in the absence of hard constraints, teams normalize inefficient pacing and mistake the duration of effort for the value of the output.

Key Indicators:

Deliverables consistently finishing directly on the deadline date regardless of underlying task complexity or initial scope.
Proliferation of low-impact revisions, administrative check-ins, and excessive formatting polish as timelines drag on.
Unplanned scope additions and feature creep routinely emerging to occupy excess schedule capacity.

Sources:

Parkinson, C. N. (1955). Parkinson's law. The Economist, 177(5856), 635–637. https://www.economist.com/news/1955/11/19/parkinsons-law

05. Transferability

Knowledge Transfer

Rigid, highly contextual workflows that cannot easily adapt, scale, or hand off across different teams or tools.

Understanding Transferability

Transferability debt emerges when processes are hyper-tailored to specific individuals, legacy systems, or isolated departments. Because the workflow lacks abstraction and modularity, scaling the process or transferring execution responsibility creates extreme friction, high error rates, and steep learning curves.

Key Indicators:

Extended onboarding times before new team members can execute routine workflows.
Custom "workarounds" that fail immediately when attempted by another department or tool.
Critical reliance on specific individuals' tacit knowledge to complete standard operations.

Sources:

Szulanski, G. (1996). Exploring internal stickiness: Impediments to the transfer of best practice within the firm. Strategic Management Journal, 17(S2), 27–43. https://doi.org/10.1002/smj.4250171105