---
name: emergent-task-planning
description: Use when asked to apply Emergent Task Planning (ETP) — Francis Seah's just-in-time, flexible-goal productivity framework for unpredictable environments — as distinct from a fixed, upfront-planned approach like a yearly-planning-meeting's annual cycle or a rigid work-breakdown-structure.
---

# Emergent Task Planning (ETP)

Emergent Task Planning (ETP), developed by Francis Seah, is a time-
management and productivity framework for effectively managing tasks and
maximizing productivity specifically in **dynamic, unpredictable**
environments — where a rigid, far-in-advance plan tends to break down
faster than it can be executed.

## Principles

- **Emergent goals** — focus on goals that are flexible and responsive to
  changing circumstances, rather than rigid adherence to a predefined
  objective set months in advance. Goals adapt in real time as needs and
  priorities actually evolve.
- **Dynamic prioritization** — traditional fixed task lists don't work
  well when priorities frequently shift or unexpected tasks arise; ETP
  emphasizes flexibility and adaptability in what gets worked on next,
  rather than mechanically working down a static list.
- **Task chunking** — break tasks into smaller, manageable pieces, making
  progress feel achievable and maintaining momentum, rather than facing
  one large, overwhelming task.
- **Just-in-time planning** — plan and execute tasks as needed, rather
  than far in advance; this minimizes time spent planning work that
  circumstances will likely change before it's reached anyway, freeing
  more time for actually taking action.
- **Feedback and reflection** — regularly reflect on progress, learn from
  experience, and adjust strategy accordingly (the same underlying
  discipline as [[agile-reflection]], applied to personal/task-
  level productivity rather than team process).

## When ETP fits, and when it doesn't

ETP is suited to environments where priorities genuinely shift often and
unpredictably — a rigid, far-upfront plan in such an environment spends
significant effort planning work that circumstances change before it's
reached. It's a poorer fit where genuine long-range commitments matter
(a [[yearly-planning-meeting]]'s annual budget and strategy, or a
[[work-breakdown-structure]]'s deliverable decomposition for a
contractually-scoped project) — those need a stable plan precisely
because other parties are depending on it holding.

## Common pitfalls

- **Applying ETP where genuine commitments require a stable plan** — a
  contractual deliverable or a dependency another team is relying on
  needs the reliability a fixed plan provides; ETP's flexibility can
  undermine that if applied indiscriminately.
- **"Just-in-time" becoming "no planning at all"** — the framework still
  involves real planning, just deferred to closer to execution time; skipping
  planning entirely isn't the same as planning just-in-time.
- **Skipping the reflection step** — without it, ETP's adaptability has
  no mechanism for actually improving over time; see
  [[agile-reflection]]'s identical warning about reflection without
  follow-through.
- **No task chunking, leaving tasks too large to start on** — large,
  unchunked tasks undermine the "maintain momentum" benefit ETP is
  specifically meant to provide.

## Learn more

- [[agile-reflection]] for the closely related reflection-and-adjustment discipline at team scale.
- [[yearly-planning-meeting]], [[work-breakdown-structure]] for the fixed-plan approaches ETP contrasts with.
