Skip to content

From approved to done

Approval is not the finish line. Approved ideas move to In implementation when work starts and to Implemented when it ships. Both transitions are admin actions.

  1. Approved → In implementation. When work has actually started, an admin opens the idea, clicks Override, picks In implementation, and writes a short note about who's running it and the rough timeline. Save.

  2. In implementation → Implemented. When the work is done, an admin opens the idea, clicks Override, picks Implemented, and writes a wrap-up note. Save.

Both transitions go through the override form, so both record feedback text. The submitter is notified at every transition.

  • The idea remains visible in the workspace at every stage. Approved and In implementation ideas appear in the Ideas list with their status pill.
  • The status timeline records every transition with the admin's name, the timestamp, and the new feedback text. The submitter and other reviewers can see the history.
  • The submitter's name is on the idea (unless they submitted anonymously, in which case peers continue to see "Anonymous").

While an idea is In implementation, the team usually wants:

  • An owner. Record who's accountable in the override note. There's no separate "owner" field at launch; the note is the source.
  • A target date. Record the rough timeline in the override note.
  • A discussion thread. Comments on the idea (Growth and Scale) are the lightweight option for ongoing updates.

Status timeline

The status timeline shows every change to an idea, including implementation steps.

Slack integration

Slack integration keeps the team posted on status changes in a shared channel.