Update goal status labels and descriptions for better clarity

[markoa]

Our current goal status system has a label that doesn't clearly communicate intended meaning:

• "Needs attention" with description "There are emerging risks. $(REVIEWER) should be aware."
• Work map badge shows "Attention" which doesn't make sense for goals (unlike projects where daily attention matters).
• The word "attention" implies the problem is about focus or awareness. But in reality, this status typically means "we're making progress but not fast enough to hit our timeline".
• Closed projects are represented with a green 'Completed' badge while goals can have both green and red statuses based on the yes/no question before closing - Accomplished / Missed.

[markoa]

Edited issue description to only contain problem definition.

Reposting first solution proposal which we do NOT consider our best yet since it adds too much variance to UI:

---

• "Needs attention" → "Lagging"
• "At risk" → "Off track"

New descriptions:

• For 'Lagging': Progress slower than expected.
• For 'Off track': Current approach won't reach target.

Here I also propose dropping the second sentences from red and yellow descriptions. This will make check-ins more scannable. I don't feel like we're in a place to give an interpretation of what every goal status means to people. (For projects it's more straightforward.)

---

For perspective, this creates a logical progression that matches how goals evolve:

• Pending → hasn't started yet
• On track → following expected trajectory
• Lagging → moving toward target but velocity is insufficient
• Off track → current approach won't reach the goal
• Achieved → target(s) achieved
• Missed → allocated time ended without success

[markoa]

Part 1: Streamline WIP statuses

We need a simplification - same words for green - yellow - red that work for any resource (projects, goals, KPIs, etc).

Proposal:

• 🟢 On track
  • Progressing as planned. No blockers.
• 🟡 Caution
  • Emerging risks or delays. Reviewer should be aware.
• 🔴 Off track
  • Significant problems affecting success. Reviewer's help is needed.

[markoa]

Part 2: Streamline finished statuses

Currently:

• Projects
  • don't have a mark as success/failure option
  • have 3 text areas for retrospective notes
  • always represented with a green 'Completed' badge in work maps (misleading)
• Goals
  • have a mark as accomplished / not accomplished option
  • have 1 text area for retrospective notes
  • represented with either 'Achieved' green badge or 'Missed' red badge
  • display 'Marked as accomplished' / 'Marked as not accomplished' on retrospective

Proposal:

• Projects
  • Add an outcome assessment Yes/No question: "Did this project achieve its intended outcomes?"
  • have 1 text area for retrospective notes
  • when closed, represent with either green 'Achieved' or red 'Missed' badges
• Goals
  • change the outcome question to "Was this goal achieved?" (options are Yes or No)
  • rest stays the same
  • apply the same 'Achieved' / Missed words on retrospective page

[markoa]

Part 3: sync up activity items

activity items for both projects and goals should start with a colored circle - status word - followed by text below

currently activity items for projects behave like this (but should pull new words)

see discrepancy we have rn:

[markoa]

Part 4: email copy

Atm goals and projects behave differently in this area too.

Projects show the status option from drop down. Goals give a worded update.

For example:

The goal is ==at risk== due to blockers or significant delays. Frank's help is needed. [...timeline part...]

This should become

The project/goal is ==on track== and progressing as planned.
The project/goal ==needs attention== due to emerging risks or delays. Frank should be aware.
The project/goal is ==off track== due to significant problems affecting success. Frank's help is needed.

The above sentence should be added to project check-in email.

[shiroyasha]

Let's define migration steps for to avoid data loss:

have 1 text area for retrospective notes

Proposal: Unify the content into one + inject titles.

prev:

{
  what went well: <message>
  what could be better: <message>
  what did you learn: <message>
}

The migration would create a new unified message with H2 titles:

# What went well

<message>

# What could be ..

<message>

# What did you lea...

<message>