fenbs for product managers: the list behind the roadmap
A board for the features, improvements and bugs a product actually has, that engineers, designers and an AI assistant all work, with a role for everyone else that can look and comment but not change.
Last checked
What it is
A backlog with three kinds of thing in it — features, enhancements, bugs — and four lanes that say what is committed and what is being built. No epics, sprints, story points or roadmap views: fenbs is the list, and the roadmap is the Next Up lane in priority order. That sounds thin until you notice how much of a product tool’s surface is spent restating the same list five ways.
The AI assistant triages
Connect Claude or ChatGPT over MCP and give it a role. Paste a week of customer emails and ask it to file each request as a task of the right kind, dedupe against what is already on the kanban board, and comment where it merged two. Everything it does is signed with its name and can be reviewed in the history; its first call is always fenbs_whoami, so it knows what it may do before it does anything.
Stakeholders get a role
Sales, support and the founder can each be on the board with a role that lets them report and comment and nothing else. For everyone else there is the Client role: they see the board, live, and can comment, but cannot change anything. Client and Reporter are suggested roles, one press each to add.
What you give up
Cycles, story points, dependencies, roadmap timelines, OKRs, and integrations with your analytics. If your product organization runs on those, Linear or Jira is the tool and this page will not argue.
How to try it
Paste in the real list you are working from this week using Add many, add the one person who most often tells you about problems with a small role, connect the AI assistant you already use, and work from the board for a week. At the end ask one question: is the board still true? Your own board is free, so the trial costs nothing but the week.