Practice : Explicit Workflow Policies

Purpose and Strategic Importance

Explicit Workflow Policies clarify how work moves through the delivery system, making expectations visible and reducing ambiguity. These team-owned agreements define what can be pulled, when, and under what conditions—improving flow and decision-making.

They support agility by creating shared understanding, reinforcing good behaviours, and building trust across team members and stakeholders. With clarity comes safety—people know what’s expected and how to act within the system.

Description of the Practice

  • Policies are visible rules that define how work flows through each stage of the process.
  • They often include pull criteria, WIP limits, blocker handling, and exit conditions.
  • Teams define and maintain these rules collectively as part of their working agreements.
  • Policies are lightweight guardrails, not bureaucratic gates, and should evolve with learning.

How to Practise It (Playbook)

1. Getting Started

  • Run a team workshop to draft initial workflow policies, starting with pull/exit criteria.
  • Make policies visible on the team board or digital tool (e.g. card headers, hover info).
  • Trial the policies for a few sprints and refine based on what causes friction or confusion.

2. Scaling and Maturing

  • Extend policies to address blocker handling, class of service, and high-risk work.
  • Use retrospectives to review the effectiveness of current policies.
  • Keep policies just-in-time and pragmatic—avoid gold-plating or over-documentation.
  • Share policy patterns with other teams to build consistency while allowing autonomy.

3. Team Behaviours to Encourage

  • Refer to policies during stand-ups and planning conversations.
  • Update policies whenever a new workflow behaviour emerges.
  • Use policy violations (e.g. pulling too much WIP) as learning moments, not reprimands.
  • Encourage questions and discussions when policies are unclear or unhelpful.

4. Watch Out For…

  • Policies becoming stale and unreviewed, losing their relevance.
  • Overly rigid rules that reduce flow or disempower the team.
  • Lack of team engagement in shaping or evolving the policies.
  • Policies that are hidden or implicit, leading to inconsistent interpretation.

5. Signals of Success

  • Team members make consistent decisions about work without escalation.
  • WIP, blockers, and flow metrics improve over time.
  • The team can explain how work moves and why things are structured that way.
  • Policies evolve regularly based on retrospectives and feedback.
  • Psychological safety increases as expectations become clear and shared.