Fast Oscillation

Part of

Dynamic Work Design Patterns

Key Points

Switch between Factory Mode and Studio Mode – depending on what the work needs. This is the core of Dynamic Work Design.

The Pattern: Problem occurs → Studio Mode (collaboration) → Problem solved → Factory Mode (efficiency)

The Benefit: Efficiency AND flexibility simultaneously.

Details

Fast Oscillation is the central pattern of Dynamic Work Design. Instead of staying statically in one mode, an organization quickly switches between Factory Mode (efficiency) and Studio Mode (collaboration) – depending on what the current state of work requires.

The Basic Pattern

Normal State: Factory Mode

Standard process running
People work according to defined workflows
Minimal coordination needed
Highest efficiency

Problem Occurs: Shift to Studio Mode

Something doesn't fit the routine
People meet, discuss, solve problem
Fast, intensive collaboration
Problem is clarified

Back to Factory Mode

Problem is resolved
Back to standardized process
Normal operations continue

Duration of switch: Minutes to hours, not days or weeks.

The Toyota Andon Cord Example

The best example of fast oscillation is the Toyota Production System with the Andon Cord:

Normal State (Factory Mode):

Worker performs precise, well-defined tasks
Cycle time: e.g., 90 seconds per step
Line runs continuously

Problem Occurs:

Worker can't complete task in the allocated time
Worker pulls a cord or presses a button (Trigger)
Alarm: Line signals problem

Shift to Studio Mode:

Supervisor arrives immediately
Together they analyze the problem
Together they find the solution
Typically lasts: < 1 minute

Back to Factory Mode:

Problem is clarified
Worker can continue
Line continues running
Supervisor moves to other tasks

Result: Fast problem-solving, high quality, continuous improvement.

Why Does Fast Oscillation Work?

It combines the advantages of both modes:

Factory Mode Advantages:

Efficiency through specialization
Predictability and planning
Continuous, smooth operations

Studio Mode Advantages:

Quick adaptation to problems
Creative solutions for unexpected situations
Learning and continuous improvement

Fast Oscillation:

→ You get the best of both worlds

Prerequisites for Fast Oscillation

For fast oscillation to work, you need four things:

1. Clear Separation: Distinguish well-defined from ambiguous work

2. Frequent Checks: Monitor status regularly

Triggers: What shows something is wrong?
Checks: Scheduled evaluation points (e.g., daily standup)

3. Help Chain: Who helps when?

Concrete names, not abstract roles
Clear escalation paths

4. Quick Response: When trigger is activated, react immediately

Not "let's talk tomorrow"
Bring people together and clarify immediately

Practical Examples

Example 1 – Agile Software Development:

Normal: Developers work on features (Factory Mode)
Daily Standup: Checks at start of day
Problem detected: "I'm stuck" → Immediately pair-coding with senior dev (Studio Mode)
Resolved: Continue working alone
Sprint Review: Check with customer, feedback

Example 2 – Customer Service:

Normal: Frequent queries handled by script (Factory Mode)
New query type comes in: Shift to team discussion (Studio Mode)
Solution approach is developed, documented
From next time on: Can be handled by new script (Factory Mode)

Common Mistakes

Mistake 1: No trigger for switching

Problem: People don't know when to ask for help
Result: Improvisations, workarounds, poor quality

Mistake 2: Too rigid – no flexibility

Problem: "We can't deviate from routine"
Result: Problems accumulate and worsen

Mistake 3: Permanently in Studio Mode

Problem: "We're agile now!" → constant meetings
Result: Wasted Attention, no real efficiency

Mistake 4: Slow reaction

Problem: Trigger is pulled, but nobody comes
Result: Frustrated teams, people give up escalating

Better: Switch quickly, targeted, time-limited

Fast Oscillation in Practice

Checklist for Organization with Fast Oscillation:

Are the two modes clearly defined?
Are there explicit triggers for switching?
Are there regular checks?
Is the help chain clear?
Can teams react quickly when trigger is activated?
Do we learn from studio sessions and improve factory mode?

If oscillation isn't working well, organizations often fall into the Axis of Frustration instead.

More about this

Dynamic Work Design was developed by Nelson P. Repenning and Donald C. Kieffer at MIT Sloan. Start with the foundational article "A New Approach to Designing Work" (2018) and watch "Unlock Your Organization's Full Potential with Dynamic Work Design" by Don Kieffer to see practical applications.