Why Workflows Resist Standardization

Context: Across every operational improvement project, we encounter the same pattern: workflows that seem similar are actually deeply different. Here's why standardization often fails and what works instead.

The Standardization Paradox

The more you understand a workflow, the less standard it appears. What looks like the same process performed by different people is actually:

• Different mental models achieving similar outcomes
• Accumulated workarounds that became the process
• Personal optimizations that were never documented
• Hidden dependencies that only certain people know

The Four Workflow Personalities

We've observed four distinct patterns in how people approach the same work:

The Builder

Starts from scratch each time, deriving the solution from first principles. Slower but handles edge cases naturally.

The Adapter

Begins with a template and modifies it. Fast for normal cases, struggles with exceptions.

The Intuiter

Can't explain their process but gets consistent results. Their workflow is embodied, not documented.

The Systematizer

Has a rigid process that works perfectly for their subset of cases, breaks for others.

The Accommodation Pattern

Instead of standardizing, we build systems that accommodate all patterns:

1. Multiple Entry Points: Let builders build, let adapters adapt
2. Flexible Sequencing: Steps can happen in different orders
3. Progressive Disclosure: Complex options only appear when needed
4. Pattern Recognition: System learns each user's approach

Real Example: Estimation Workflows

In a recent project, three estimators all produced accurate quotes but through completely different paths:

• Estimator A: Started with total price, worked backwards
• Estimator B: Built up from materials, added labor
• Estimator C: Copied similar past job, adjusted

Forcing them into one workflow would have reduced accuracy and increased time.

The Solution: Descriptive, Not Prescriptive

Rather than enforcing how work should be done, we build systems that:

• Observe how work actually gets done
• Support the patterns that emerge
• Connect different approaches to the same outcome
• Learn from variations to improve the whole

Implementation Principles

1. Start with Reality

Document actual workflows, not idealized ones. Use shadowing, not interviews.

2. Find the Invariants

What must happen regardless of approach? These become your system's constraints.

3. Support the Variants

Everything else becomes configurable, optional, or adaptive.

4. Measure Outcomes, Not Process

Judge success by results, not adherence to process.

The Lesson

Workflows resist standardization because they encode individual expertise. The goal shouldn't be uniformity - it should be transparency and support for the patterns that already exist.

Sometimes the best standard is no standard at all.

---

Next: Building systems that learn from usage patterns