Mandates vs commitments vs tasks

Teams get stuck when everything looks like a task. A mandate isn't a big task. A commitment isn't a milestone on a Gantt chart. Each layer answers a different question.

Mandates: sustained outcomes

A mandate describes an outcome worth protecting over time. It's directional, not prescriptive: "Students graduate confident in engineering pathways" — not "run four workshops." Mandates have owners, revisit cadences, and health computed from what's underneath.

Commitments: owned promises

Commitments break mandates into deliverables someone is accountable for. They persist, have stakeholders, and carry context: notes, artifacts, blockers. When a commitment completes, the mandate moves — the mandate itself may never be "done."

Tasks: execution

Tasks are finite checklist items. They should always serve a commitment. Nested subtasks help with complex work — but the commitment is what you revisit in standups and board updates, not every checkbox.

Anti-patterns that flatten the stack

• Turning every mandate into a folder of tasks — you lose the why and the revisit
• Skipping commitments so leadership only sees checkboxes — nothing rolls up
• Writing mandates as project plans — they expire when the plan does
• Assigning "the team" as owner — silence has nowhere to land

Podz keeps all three layers linked so health and radar reflect real accountability — not a prettier task list.