An action plan converts an agreed goal or decision into concrete work. It should show the desired outcome, tasks, sequence, owner, deadline, dependencies, resources and evidence of completion. A task such as ‘improve onboarding’ is not actionable until the team knows which change will be delivered, by whom, by when and how it will be checked.

Use a decision record, project review, audit finding, strategy map or personal goal as the source. AI can suggest a hierarchy, but it cannot commit another person’s time or know hidden dependencies. Confirm capacity and dates with owners. Keep outcomes separate from activities, and keep optional ideas outside the committed action list.

Use workstreams to preserve context without creating an artificial department list. A workstream should represent a coherent contribution to the outcome, such as simplifying a process, training users or changing a system. Under it, order tasks by dependency and decision point. Add a milestone only when several actions combine to produce a reviewable change, not merely because a date appears on the calendar.