Skip to content
Menu

Growth actions

An individual development plan built from concrete growth actions

Write down what someone will do to grow and by when, then keep the conversation about it in one thread instead of scattered chats.

Free plan · No credit card required

How it works

From a conversation to a finished action

  1. Raise it where the gap shows

    Add an action from a completed check-in, against the skill that needs work, or create one on its own at any time. Link it to a skill from the person's role, or keep it a broader goal.

  2. Both sides stay in the loop

    The other side is told when an action is added or its due date moves, and both the employee and the manager post progress notes in the action's thread as the work goes on.

  3. Close it with a result

    Only the employee marks an action complete, with a note on how it went. Open and overdue actions show on their profile, next to check-ins and feedback.

Permissions

Who does what

Employees
Add actions for themselves, edit them and move their due dates, post progress notes, mark actions complete, and reopen or cancel them.
Managers
Add actions for their direct reports, post notes, move due dates, reopen a completion they disagree with, or cancel what no longer makes sense. They cannot complete an action on someone's behalf.
Managers further up
Read the actions and full threads of everyone below them in the reporting line, without changing anything.
Admins
Choose when reminders go out ahead of a due date, for the whole organisation. They can delete an action, though they never open one.

Good to know

The details

Open, completed or cancelled
Every action is in one of three states. An open action past its due date is flagged as overdue, and the list can be filtered down to just those.
Reminders that know when to stop
Up to three reminders before the due date, on the days your organisation picks, and one the morning after it passes — never a daily stream.
It follows the reporting line
When someone moves to a new manager, the new manager takes over their actions and sees the whole thread. Earlier notes stay under their authors' names.
Notes stay as written
Notes cannot be edited or deleted one by one, so what was agreed stays readable for as long as the action exists.

See the whole product

Keep exploring

Templates to start from

  • Customer support

    Customer Support Specialist

    Five levels from Support Associate to Head of Support, across seven competencies from solving tickets to running the function.

    • 5 levels
    • 7 competencies
  • Engineering

    Software Engineer

    Five levels from Junior to Principal, across six competencies from shipping code to growing the team.

    • 5 levels
    • 6 competencies

Who it is for

  • For small businesses

    Small businesses

    For owner-run businesses where sales, support and operations need a career path as much as anyone — set up by the people who run the team.

  • For startups

    Startups

    For founders of 10–60-person startups setting up levels, their first managers and fair promotions.

Further reading

  • Development

    How to write an individual development plan (with examples)

    A short, practical IDP: start from one or two skill gaps, write concrete actions with dates and a clear finish line, and review them at every check-in. With a template and examples for four roles.

    Updated 1 October 2026

FAQ

Common questions

Can a manager mark a growth action as done?

No. Only the person doing the work can complete it. A manager who disagrees with a completion can reopen it, with a note saying why.

Do growth actions need a check-in?

No. An action can come from a completed check-in or be created on its own at any time. Actions raised from a check-in show which skill and conversation they came from.

Can we change when growth action reminders are sent?

Yes. An admin picks up to three reminder days before the due date, and the second and third can be switched off. The reminder after the due date is sent once.

Does every action have to be linked to a skill?

No. Linking an action to one of the skills the person's role requires is optional, so it can also be a broader goal.

What happens to an action that is no longer relevant?

Either side cancels it, with a note if they want one. It stays on record as cancelled and can be reopened later.

Give every development plan a due date

Start free and turn your next check-in into growth actions someone actually finishes.

Free plan · No credit card required