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.

Common mistake: flattening the stack

When mandates become folders of tasks, you lose the why. When commitments are skipped, nothing rolls up to leadership. Podz keeps all three layers linked so health and radar reflect real accountability.