Field Autopsy #001: The $0 App That Couldn't Fix a Broken System

The Premise: A technology-first solution offered to a labor-intensive problem is often a reflection of the consultant's bias, not the client's operational reality. This autopsy dissects a failure—my own—to illustrate the core Enova11 principle: Criterion before technology. Reality before rhetoric.

1. The Presenting Symptom (The Visible Chaos)

A licensed cannabis producer in a remote area relied on a third-party labor provider to staff a high-turnover harvesting department. The provider managed everything through WhatsApp and Facebook groups.

Observed Chaos: A daily 70-person line to clock in on a single tablet, taking 3+ minutes per person. Zero formal training. High product waste. Minor injuries. A complete reliance on tribal knowledge ("the person with 4 days of experience trains the new person").

The Initial (and Flawed) Diagnosis: I, as the temporary laborer and a systems thinker, saw this as a "technology and communication gap." The solution seemed obvious: a custom mobile app for streamlined clock-in/out, scheduling, ridesharing, skills tracking, and training.

2. The Autopsy (The Uncomfortable Root Causes)

The proposed app was a symptom-treating tool, not a cure. The real failures were structural and human:

Failure of Accountability: The labor provider was a broker, not a manager. Their success metric was "bodies in the door," not "quality of work" or "systemic efficiency." An app would have made their scheduling slightly easier but done nothing for the grower's core issues of waste and safety.
Misaligned Incentives: The main company had outsourced a critical operational function (harvesting) without outsourcing the responsibility for quality. The two entities were connected by a transaction, not a shared system.
Complete Fluency Gap: The workforce was transient, untrained, and unmotivated. No app can force someone to read a training module. The problem wasn't the lack of a training library; it was the lack of a reason for the worker to care and a supervisor accountable for verifying competency.

The Real Problem: This was not a data management problem. It was a severely fractured human-operational system with no clear owner, no aligned incentives, and no mechanism for quality control. Technology poured into this gap would have been digitized confusion.

3. The Misalignment Cost

The cost wasn't the unsold app. The ongoing, unattended costs were:

Product Waste: High-value product damaged by poor technique.
Compliance & Safety Risk: Unreported minor injuries in a regulated industry.
Productivity Drain: 3+ hours of paid time lost daily just to clock in.
Strategic Blindness: The grower had no data on which temporary workers were effective, making improvement impossible.

4. The Intervention (Applying The Enova11 Method™ — D⁴™)

Had the Diagnose phase been conducted first, the approach would have been radically different:

DIAGNOSE: Map the handoff points between the grower, the labor provider, and the workers. Identify the single point of accountability for quality. Interview workers to understand real disincentives.
DESIGN:

A 3-Party Service-Level Agreement (SLA) defining quality metrics (waste %, injury rate) the labor provider is responsible for.
A 15-Minute Mandatory Onboarding & Safety Briefing for all workers, owned by the provider, verified by the grower.
A "Skills Passport"—a simple paper checklist for supervisors to sign off on a worker's competency for a single, specific task (e.g., "proper trimming technique").

DEPLOY: Implement the briefing and paper passport first. Only after this human system works would we ask: "What technology makes this checklist digital and this data visible to both companies?"
DRIVE: Review waste and injury data jointly in monthly meetings between the grower and provider, using the SLA as the scorecard.

5. The Outcome (Clarity Revealed)

The failed proposal was the greatest lesson. It revealed that without a shared structure of accountability, no tool—no matter how smart—can create alignment.

The takeaway is not that an app was wrong, but that it was premature. The foundational work of designing who is responsible for what outcome (The SYSTEMS and ALIGN pillars) was entirely missing. You cannot build INTELLIGENCE or FLUENCY on that foundation.

The Autopsy's Lesson:

The most elegant technical solution will fail if it is built for a system that does not exist. The first deliverable must always be clarity of ownership, responsibility, and consequence. Everything else is just features.

← Return to Field Notes Overview

Field Autopsy #002: The Phantom Implementation

The Premise: A failed system is rarely about the software. It is a symptom of missing foundational structure. This autopsy examines a "broken" HRIS platform where the real failure was the leadership's refusal to build the operational backbone the technology was meant to serve.

1. The Presenting Symptom (The Visible Chaos)

A rapidly scaling company had implemented a leading HRIS (Dayforce) amid a frenzy of acquisitions. The visible outcomes were catastrophic: 3 HR Directors, 2 Payroll Managers, and 1 HRIS Manager left in under a year. The universal verdict was "a bad implementation." The system was blamed for payroll errors, benefits chaos, and a complete lack of reliable headcount.

The Assumed Diagnosis: "The platform is broken. We need more experts to fix the configuration or consider a re-implementation."

2. The Autopsy (The Uncomfortable Root Causes)

The platform was not broken. It was orphaned. The real failures were upstream and human:

The Policy Vacuum: The company had no master HR policies or procedures. Each acquired entity brought its own rules into the system, creating a tangled web of conflicting compensation and benefits logic. The system was configured to automate chaos.
The Accountability Black Hole: No single leader owned the integrity of HR data. The CFO held the "super user" access but lacked operational HR knowledge. This created a bottleneck where critical fixes (like terminating benefits) required a gatekeeper who didn't understand the tickets in the queue.
The Integration Illusion: Acquired companies were not operationally integrated. Their data was dumped into the HRIS without aligning their people processes, making "one system" a technical mirage.
The Cost of Ghosts: A forensic glance revealed the company had been paying insurance premiums for terminated employees for over two years. This was not a system error; it was the material cost of having no process owner.

The Real Problem: This was not an implementation problem. It was a complete failure of operational design and governance before a single line of code was configured. The company attempted to use an aircraft cockpit to steer a ship that had no hull.

3. The Misalignment Cost

The cost was measured in more than software licenses:

Financial Leakage: Direct waste (e.g., two years of ghost benefit premiums).
Leadership Attrition: The repeated exit of senior HR talent, a clear signal of impossible working conditions.
Operational Paralysis: Inability to report accurate headcount or manage compensation, crippling strategic planning.
Tribal Workarounds: The proliferation of shadow systems (SharePoint lists, Teams approvals) that further fragmented the truth.

4. The Intervention (Applying The Enova11 Method™)

A true intervention would have required a ceasefire on "fixing Dayforce" to build the foundation it needed.

DIAGNOSE: Freeze all system changes. Map every HR policy variant from each acquired entity. Document every data entry point and its owner (finding there was none).
DESIGN:

Create a Minimal Viable Policy Set: Establish 5 non-negotiable master policies for hiring, pay, benefits, and termination.
Define the "First Team": Formally appoint a single Process Owner (ideally the CHRO or a Head of HR Ops) with the authority and accountability for data integrity.
Build a Clean Core: Design a single, clean company structure and job architecture in the HRIS to act as the source of truth.

DEPLOY: Implement the policy set and new governance in tandem. Then, and only then, cleanse the data against the new "clean core" and grant the Process Owner full system access.
DRIVE: Establish a weekly reconciliation ritual between Finance (payments) and HR (system status) to prevent future "ghost" costs.

5. The Outcome (Clarity Revealed)

The lesson is stark: You cannot automate a process that does not exist. A powerful system given contradictory commands and no clear pilot will fail predictably.

The company's choice to restrict access and work around the problem was a symptom of a deeper refusal: the refusal to do the hard, non-technical work of creating a single source of truth and assigning one person to defend it.

The Autopsy's Lesson:

A 'broken' system is often a perfectly functional mirror reflecting a broken organization. The first fix is never more configuration; it is the deliberate, often political, work of establishing clarity, ownership, and a single set of rules. Without this foundation, any platform will become a monument to the chaos it was meant to control.

← Return to Field Notes Overview