The why above your features, with a prediction written first.
A prediction written before you build, and one timeline across every initiative. Mind fills in the metric; the number is yours.
14 days free. No card needed.
Write what you expect before you build.
Before an initiative goes into build, its owner writes what they expect it to change. Mind fills in the metric, today's value and the check date, and never suggests the number.
- A time budget reads "Day 4 of 21": a limit, never an estimate.
- Cards count what is done, never an estimated percentage.
- Each morning, Now initiatives show On track, Watch or Off track, with the reason.
Three questions, then a pre-mortem grounded in your records.
Shape an initiative in three questions and get a pre-mortem grounded in what you know. Mind imagines the check date has come and the number didn't move, and asks why.
Up to three causes come back, each with a guard and how likely it is. Each names its source: a feature, a belief, a test, or something a user said. A cause it can't ground is left out, and the owner accepts, edits or declines the draft.
One page from why to what to build.
One page from why to what to build: the evidence, who asked, Ready to build?, and the docs. Every feature shows its evidence strength, decided by rule from its linked feedback.
- Acceptance criteria you can tick. A story is Ready only when it has them.
- The spec interview: seven plain questions, then Mind writes the PRD and stories.
- Copy for Claude Code copies the picked stories as one brief.
Every document in one list, and which went stale.
Every document across your product, in one list, each saying whether feedback has arrived since it was last edited. The list opens on what needs attention.
- Mind can suggest an edit to one section; nothing changes until an editor accepts.
- New from evidence starts a document that quotes only its sources.
- Export as Word or Markdown, or Copy for an agent.
Working as a team, sharing outside
Each feature carries a Build Pack with the initiative's goal and prediction inside. The problems behind it come from Problems ranked by your users, and Results checks the prediction on its date. For a small product team, start with the page for product teams.
Questions about Initiatives, Features and Documents
Something else? Search the help center or email us.
Does Mind predict the number?
No. Mind fills in the metric, today's value and the check date. The number you expect is always yours. Only the initiative's owner or a product admin writes or edits the prediction, and an edit keeps the first words.
Can an initiative go into build without a prediction?
Yes, with a reason. The skip is logged as a decision. An initiative without a written prediction gets no outcome review on Results.
Why is there no percentage on a card?
Cards count what is done: "Features 1 of 4 shipped", "3 of 15 stories done". Mind never estimates a percentage. A time budget reads "Day 4 of 21": a limit you chose, never an estimate.
What does "stale" mean on a document?
Feedback counted on its feature has arrived since the document was last edited. The row says how many pieces. It does not mean the document is wrong: read the new feedback, edit if it matters, or ask Mind about it.
What makes a story Ready?
At least one acceptance check you can tick, and an approved spec. A story that moved on before checks existed says "Needs criteria" and keeps its status.
Put the why above your features.
Write one prediction before the next build. Mind fills in the metric and the date. The number stays yours.
- 14 days free
- No card needed
- Viewers are free
