Best practices

Getting the most out of MindBacklog

Updated 1 Nov 2026 · 2 min read

Give Mind your product first. Your site, help center, pricing page and a deck or two: in onboarding, or later from What Mind knows › Add a link or a document. Mind reads them into the master summary (Market › Positioning) that every draft and answer starts from. Check What Mind doesn't know there now and then: each gap links to its fix.

Say who it's for. Confirm your main segment on Market › Positioning and build it out on Learn › Who it's for. Problems rank by how much of their feedback comes from your main customers, so a missing segment weakens every ranking.

Connect where your users already talk. The feedback widget, a web form, email forwarding, app store reviews, Slack, your support desk: every source on Market › Sources adds evidence. Competitors' reviews and public threads are welcome too: they are labelled public and never count toward a problem, so they can't drown out your own users.

Confirm what Mind filed, once a week. Learn › Feedback › To confirm shows what Mind filed and nobody has checked: Confirm the N in one go, and use Wrong? Correct it when it misread something. Mind reads the next pieces with your correction.

Talk to people, and ask about the past. Ask what they did, not what they would do: "When did you last…?" beats "Would you…?". Prepare the call from Learn › Questions, capture it in Conversations, and let Mind's read move your beliefs up the evidence ladder.

Make a call on every problem. Build, Test first, Not now or No, each with a one-line reason. A Not now comes back on its review date; a No stays findable. Your decisions, and the evidence as it stood, are kept in Learn › Decisions.

Test before you build when you're unsure. Set a test's pass line before it starts (Learn › Tests), so the result can't be argued after.

Put the why above the work. Group features under an initiative with a goal, a time budget and a prediction you write yourself (Build › Initiatives); Build › Results checks the prediction when it falls due.

Approve the spec, then hand it over. A story is ready only with acceptance checks and an approved spec. Your coding agent then builds from the feature's Build Pack and reports back (see Build Pack).

Close the loop. When a feature ships, Tell the N who asked drafts a note to each of them; you send it yourself.

Read the weekly review. It is ready every Friday on Today: what moved, your calls checked against what you predicted, and an update you can send.

Read Mind's drafts before you apply them. They are first drafts, from your data; your judgement and domain knowledge make them right.

Bring your team in at the right level. Editors for the people who shape and build; viewers, who are free, for everyone who should see the evidence and ask Mind. Discuss on the item itself and @mention whoever needs to see it.