Use case · product managers
MindWiki for product managers.
Specs, research, decisions, and shipping context — connected. The version of MindWiki that fits a PM workflow keeps each ticket close to the writing that justified it.
Where PM workflows leak today
- Spec docs live in Notion; research lives in another tool; decisions live in Slack threads. None of them link.
- Quarterly planning re-discovers conclusions from the last quarter.
- AI suggestions come from a blank slate — your team's actual context is invisible.
A PM-shaped setup
- specs/ folder — one page per feature/initiative. Frontmatter: status, owners, target release.
- research/ folder — interview notes, survey takeaways, competitive analysis pages.
- decisions/ folder — one page per real product decision. Each links to the research and spec(s) it impacts.
- AI: connect Claude or ChatGPT via MCP. Ask "summarize what we've learned about the activation funnel" — it reads research/ pages.
- Mirror tickets: pipe Linear/Jira tickets into MindWiki under a tickets/ folder via the REST API so they backlink to the spec.
Where it isn't the right tool
- Not a ticketing system. Keep Linear/Jira for tracker work.
- Not a real-time team workspace. Multi-user editing is not shipped.
- Not a roadmap board. Keep that elsewhere; link out.