Team Member — The Engine

Leads: Sustain (locking in gains)

Team Members are the force behind execution and continuous improvement. They hold the knowledge that the other two roles need but rarely ask for — the intimate understanding of how work actually gets done.

Key Responsibilities

• Execute tasks assigned during Briefing
• Identify improvement opportunities during Circle and estimate potential value capture
• Implement improvements using Stories (A3-inspired)
• Verify results and establish new standards

The Tension

The Team Member knows the most about the work but has the least formal authority to change it. Their challenge is to surface problems and ideas in a system that historically punished both.

Anti-pattern: The Passive Operator

When the Team Member executes without thinking — completing tasks without questioning, following instructions without observing waste — the team loses its most powerful sensor. Improvement dies at the source.

How to detect: The Circle produces no new Stories. The Board's Check column is empty. The same problems recur cycle after cycle without anyone naming them.

How to recover: The Leader must create space for observation and questioning. The Circle must be protected as a time for thinking, not just doing. Often the root cause is psychological safety — members do not surface problems because they have been punished for doing so in the past.

PDCA Participation

Step	PDCA	Event	Role
T2.1	Plan	Briefing	Receives objectives and priorities from Team Leader
T2.2	Do	Briefing	Takes ownership of assigned tasks
T2.3	Check	Debriefing	Detects and presents improvement opportunities from execution
T3.1	Plan	Circle	Identifies improvement opportunity and estimates potential value capture
T3.2	Do	Circle	Implements improvements periodically using Stories
T3.3	Check	Circle	Verifies results against expected value and identifies new opportunities
T3.4	Act	Circle	Adjusts action plans and/or realizes captured value into new standards