Product workflow2 min readKeep one real product question in mind as you read.
A useful way through

Start with one real question and leave with a next step.

Start with the question in front of you, then use the guide to make the next decision easier.

Try saying

“I am trying to make this decision. What should I look at first?”

Start with context

Bring the smallest useful example.

Look for the signal

Separate what is known from what is assumed.

Take one step

Choose an action you can review.

Decision Log

Log a decision · 23 s video guideRead the transcript

What it does

The Decision Log keeps your product decisions in one list: what you decided, why, who made the call, and how it turned out. When someone asks "why did we build it this way?", the answer is one search away instead of lost in old chat threads.

In the sidebar it sits under Decide as Decisions. In ⌘K and the top bar it is called Decision log.

Three ways to add a decision

  • Log Decision: fill in the form yourself.
  • Extract from PRD: pick a document, and the AI pulls out up to 5 key decisions from it.
  • Log a decision with Specky: shown while the log is empty. The AI chat asks what you decided and why, then records it.

The form asks for:

  • What was decided? (required), e.g. "We will ship SSO before audit logs"
  • Rationale: why you chose this
  • Outcome: Expected, Confirmed, Revised or Reversed. A new decision is usually Expected.
  • Date and Decided by

Working with past decisions

  • Click Show rationale on a card to read the reasoning.
  • Link feature connects the decision to a feature in Prioritize work. Linked records show in the card's Evidence row.
  • Supersede marks a decision replaced by a newer one, Reverse marks it undone, and Reactivate makes it active again. Each change offers Undo for a few seconds.
  • Filter by All, Active, Superseded or Reversed, or type in Search decisions....

Decisions prepared from evidence (for example from research or the Opportunity map) carry a decision packet. Click Show decision packet to read the evidence and recommendation, then choose Agree, Request changes or Reject.

Did it work?

Every card has a Did it work? check. Write what happened and pick It worked, It didn't work or Too early to tell. "Too early" asks again in 30 days. An active decision is due for a check on its review date, or 90 days after its date if it has none. A banner at the top counts the decisions that are due.

Example

What was decided? Delay dark mode to next quarter

Rationale: Few customers asked for it, checkout problems came up far more often, and the team is fully booked.

Outcome: Expected

Decided by: Product team

Ninety days later the card asks "Did it work?". You write "No churn linked to dark mode; checkout tickets down by a third" and pick It worked.

Ready to apply this?

Start with your own product and keep the first read grounded. You'll create an account before the guided result so it can be saved to your workspace.

Try the guided start