September 27, 2026

Feedback Dates & Evidence Order

In this edition

Set an optional historical source date when submitting Feedback, or edit that date later in Feedback details. The system's original ingestion timestamp remains unchanged.
Problem evidence is ordered by the Feedback source date, with timestamp fallbacks when that date is missing, so backfilled evidence follows the customer's chronology.

Extraction Recovery

Newly created Feedback awaiting classification starts background processing across source channels, including team entries, interviews, widgets and tickets.
Opening an item already beyond the five-minute processing window makes Restart Extraction available without waiting another five minutes in the detail view.
Stalled items beyond that window no longer display an active analyzing indicator in the Inbox.

Move an Initiative through guided phase transitions from Kanban, the card menu or the full-page brief. Moving from Clarify goal to Decide approach asks you to confirm a measurable goal and success criterion.
Save a title-only draft without a goal. Initiatives with an agreed goal can reach Decide approach even before Problems are linked.
Reopen a closed Initiative or move back through earlier phases. Historical closure receipts remain available for inspection after reopening.
Searching without an explicit status filter includes open and closed Initiatives. Kanban supports horizontal scrolling and keyboard-accessible Move to phase actions.
The decision brief exposes What it impacts for capability exploration/linking and Delivered work & Changes for connected execution context.
During closure, select which connected Problems to resolve with the Initiative's conclusion. Problem resolution is an explicit choice; it is not implied by closing the Initiative.

Capability exploration can consider the complete workspace taxonomy, including capabilities outside its initial shortlist, and prioritizes explicit capability references in a Change.
The Delivery graph marks a capability's first chronological appearance with a New badge; later appearances do not repeat it.
Empty capability suggestion results remain empty instead of being filled with an arbitrary fallback. Documentation-only changes do not receive a guessed owning capability when there is no supported match.
Supported capability suggestions for documentation changes are retained even when the capability is outside the initial heuristic shortlist.