Initiatives and the timeline
The why above your features, with predictions and time budgets
On this page
An initiative is the why above your features: a problem worth solving, how much time it is worth, and what you expect it to change. Objectives are initiatives now. Each kept its text, key results, date and status, and gained a key (I-1, I-2, …) and a lane.
The board
Build › Initiatives shows four lanes:
- Later (needs evidence): ideas that wait until there is evidence. Mind may suggest one from a problem many people raise; Make it an initiative or Not now.
- Next (shaped, waiting).
- Now (in build). If your product sets a limit on how many run at once, going over it asks for a reason.
- Closed (delivered or stopped).
Each card counts what is done: "Features 1 of 4 shipped", "3 of 15 stories done". Nothing shows an estimated percentage. A feature can serve several initiatives; it counts once in each, and once in the product's totals.
An initiative's page
Click a card to open the initiative (key I-1, I-2, …). Its tabs:
- Overview: the success metric and today's value, the prediction, the time budget, features shipped ("N of M"), the plan inside the time budget and the stories.
- Features: the features it serves, with Order by dependency and the pre-mortem.
- Evidence: the problems behind it, its tests and competitors' moves on its features; the beliefs it depends on, each with its strongest evidence, and its open questions; and quotes from the feedback kept on its problems, word for word.
- Results: its predictions, checked (see Build › Results).
- Discussion: comments with @mentions.
- History: what happened to it and the decisions taken on it, newest first.
The prediction
Before an initiative goes into build, its owner writes what they expect it to change: "I expect {metric} to reach [your number] by {date}". Mind fills in the metric, today's value and where it came from, and the check date. Mind never suggests the number. You can skip the prediction to start anyway, with a reason; the skip is logged as a decision. Only the initiative's owner or a product admin writes or edits the prediction; an edit keeps the first words.
The time budget
A time budget is how long you are willing to spend before you stop: a limit you choose, never an estimate. The card reads "Day 4 of 21". Changing it moves the end date and is logged.
Health
Each morning Mind reads the initiatives in Now: done stories against the share of the time budget used. On track, Watch or Off track, always with the reason and its source. If you set the health yourself, Mind leaves it for 7 days.
The timeline
Initiatives › Timeline shows every initiative with its features as rows, the checks and deadlines across the top and a line for today. Group it by team, area or owner; zoom by month or quarter. A feature under two initiatives shows under both and says "also in I-n". Dates are edited in a bar's quick look, never by dragging.
Launch days on the timeline
The timeline's Checks and deadlines row also shows each planned launch's day (an outlined diamond, "{launch} launches"), beside prediction checks, tests' deadlines, decisions due for review and outcome reviews.
More places a prediction can be measured from
Besides a value you enter, Stripe totals, feedback on a problem and a test, a prediction can be measured from PostHog (sign-ups, or activated sign-ups, a week) once PostHog is connected and has read a day, and from Stripe customers (paying accounts on the day) once Stripe customer data is connected. Mind still never suggests the number.
Closed initiatives
The board's Closed lane shows the latest four. Show N more lists every closed initiative; All results opens Build › Results, where each one's outcome is checked.
Shape an initiative
On an initiative in Later or Next, Shape this initiative asks three plain questions, one at a time:
- How long are you willing to spend before you stop? Its time budget. If one is set, "Already known" offers it.
- What is the smallest slice that would still move the number? Say it in your words, or press Suggest one (1 credit): Mind names one of the initiative's features and the smallest part of it. It is only a suggestion: Use it, change it, or ignore it.
- What would make this initiative fail? Your words. They show on the Overview next to the prediction.
Nothing is saved until the last step. Save to the initiative saves all three as one change you can undo for a day, and Mind starts drafting the pre-mortem.
The pre-mortem
Mind imagines it is the check date and the number didn't move, and asks why. You get up to three causes, each with a guard (what would prevent it, naming the feature it would change) and how likely it is. Each cause names what it was drafted from: a feature, a PRD, a belief, a test, something a user said, a competitor's public change, or your own words. Mind never invents a number or a quote; a cause it can't ground is left out, and a guard that names nothing real reads "No guard yet".
It arrives as a draft on the Features tab. The initiative's owner or a product admin accepts it, edits it, or says Not now; until then it is a draft. Drafting costs 2 credits; if Mind finds nothing it can ground, the credits come back. You can draft it again later.
The order its dependencies set
When an initiative's features wait on each other, the Features tab shows the order that follows ("pay page → schedule editor → templates"). Order by dependency proposes it as a plan: the features take that order, and a feature that starts before what it waits on ends moves to the day after. If two features wait on each other, the page says so; Mind never picks which dependency to change.
Tidy
On the board and on Build › Features, "Mind found N things to tidy" appears when there is something: two very similar features (merge the newer into the older), a feature whose problem was decided No, an idea with no new feedback and no change for a month, a feature whose feedback is mostly from outside your ICP (left unticked: your call), a late or out-of-order date, a feature with no initiative that belongs to one. Review shows them as one plan: untick what should stay, apply the rest, undo for a day. Nothing is deleted: a merged feature is archived with its documents, and its stories, feedback and dependencies move to the other. What you untick isn't suggested again for 30 days. Tidy uses rules, not AI, and costs nothing. Ask Mind "tidy up" and it reads the same list.
Who can do what
Editors create initiatives, move them between lanes, edit their details, link features, shape them, draft the pre-mortem, tidy, re-order and comment. The initiative's owner or a product admin writes the prediction, decides the pre-mortem, closes, archives and restores it. Viewers read everything.
FAQ
Are initiatives the same as objectives? Yes. Every objective kept its text, key results, date and status, and gained a key and a lane.
Why does going over the Now limit ask for a reason? Your product sets how many initiatives may be in build at once. Going over it asks for a reason.
Why is there no percentage? Cards count what is done ("3 of 15 stories done"). Mind never estimates one.
I can't write the prediction. Only the initiative's owner or a product admin does.