All updates

Week of July 13, 2026

Closing something now records why it closed: Status and Resolution split apart, Obsolete joined Completed and Rejected, and closure dialogs spell out what else gets affected. Evidence picked up inline coverage toggling, real-time search, and parents that close themselves when their children are done. Highlight: Status and Resolution are separate fields now, so every closure is auditable.

In this edition

Closing something now records why

"Closed" used to mean four different things depending on who closed it. Status and Resolution are separate fields now. Status is Open or Closed. Resolution is Completed, Rejected, or Obsolete, and it's the field that says whether the work got done, got turned down, or simply stopped mattering.

Read more

Obsolete (Retired) is the new one, for the pile of feedback that ages out rather than gets decided. "Won't Do" became Rejected, and both the Obsolete and Rejected labels are editable in Decision Vocabulary Settings if your team calls them something else. Closing now requires picking a resolution, through a Resolve Feedback dialog or a Closure Resolution modal, including from the board cards. Those dialogs warn you about linked work before anything cascades.

Filtering follows the same model. The inbox leads with status tabs, Open, Closed, All, and a secondary Resolution selector appears once you're looking at Closed items, so "what got rejected last month" is a two-click question instead of a query.

  • Status (Open / Closed) separated from Resolution (Completed / Rejected / Obsolete)
  • New Obsolete (Retired) resolution, and "Won't Do" renamed to Rejected
  • Both labels customizable in Decision Vocabulary Settings
  • Resolve Feedback dialog and Closure Resolution modal require an explicit resolution, board cards included
  • Closure dialogs warn about linked work before cascading changes
  • Status-first inbox filtering with a secondary Resolution selector for Closed items
  • Redesigned close and reject confirmations with a scrollable evidence list and three clear choices: cancel, this item only, or everything

Evidence keeps its own score

Evidence coverage is inline now. A clear check indicator marks a chunk as covered from either the Feedback or the Theme view, no drawer, no detour. Parent feedback closes itself when all of its child evidence is covered or closed, and reopens if any child comes back, so the inbox status matches the underlying evidence without anyone syncing it by hand.

Read more

The lists themselves grew up. Real-time search, filtering, and sorting landed in the Evidence lists inside Feedback and Theme drawers, with sorting as an explicit dropdown by Type, Severity, or Resolution instead of a guessing game. Cards show simplified counts like solved over total, and visually flag the states that don't add up, a closed parent still holding open children being the obvious one.

  • Mark evidence as covered inline from Feedback and Theme views
  • Parent feedback auto-closes when all children are covered, and reopens when a child reopens
  • Simplified evidence counts (solved / total) on inbox cards
  • Inconsistent states highlighted, for example a closed parent with open children
  • Real-time search, filter, and sort on Evidence lists in Feedback and Theme drawers
  • Sorting as an explicit dropdown: Type, Severity, Resolution
  • Type labels on evidence items with consistent icons for status, severity, and link actions

Right-click does the work

Quick actions got reliable. The right-click menu handles Mark as Solved and Unsolved, Change Severity, Change Type, and Resolve as Completed, Rejected, or Obsolete, without opening anything. Hover and toggle targets are limited to the indicator areas now, which cuts down on the accidental click that used to change a severity you never touched.

Read more
  • Right-click quick actions: solved state, severity, type, and resolution
  • Hover and toggle targets restricted to indicator areas to prevent accidental clicks
  • The Feedback detail panel keeps focus when an item's status changes, so you don't lose your place

Learnings move to where you already work

The standalone Learnings module is gone. Its content now lives inside Feedback Themes, where the insight sits next to the evidence that produced it and the action you'd take about it. One less tab to remember, and one less place for a learning to sit unread.

Read more
  • Learning content surfaced directly inside Feedback Themes
  • Standalone Learnings tab removed

Discovery shows the related pieces

AI-driven Capability Suggestions now appear reliably in the Change detail panel, so reviewing a change comes with the relevant capabilities and next steps attached. Related-entity sections around it, Work Items, Capabilities, Themes, Bets, and Hypotheses, are expandable and collapsible, which makes a densely linked change browsable instead of overwhelming.

Read more
  • Capability Suggestions render reliably in the Change detail panel
  • Expandable and collapsible sections for Work Items, Capabilities, Themes, Bets, and Hypotheses

Polish

  • Restored card exit animations on the Feedback Inbox
  • Fixed layout centering on the Feedback Inbox and User Profile pages
  • Delivery page KPI cards render reliably again

What this means for you this week

  • Every closure carries a reason, so a Closed item three months later still explains itself.
  • Retire feedback that aged out without pretending it was rejected on the merits.
  • Mark evidence covered where you're already reading, and let the parent close itself.
  • Find the learning next to the theme it came from, instead of in a separate module.
  • Answer "what got rejected, and what got retired" straight from the inbox filters.

If you want a walkthrough of the new resolution model, evidence coverage, or the Decision Vocabulary settings, reply here and I'll set up a quick demo.

See how Outcomet works.

Follow a customer problem from feedback to a product decision.

See how it works
Week of July 13, 2026 | Outcomet