Notes for product teams.
Short, practical pieces on product knowledge, decisions, and the questions every product manager keeps getting asked. One a week, no filler.
Explainer
Tribal knowledge: what it is, why product teams cannot document their way out, and what works
Tribal knowledge is what a team knows but never wrote down. In product teams, most of it was said out loud in a recorded meeting. Here is what it is, with examples, why "document it" fails, and how to capture it from the conversations you already have.
Read the post
How-to
Product decision log: what to record, a template, and how to keep it current
A product decision log is only useful if it records why, not just what. Here are the five fields a decision needs, a template you can copy, and the reason most logs die within a quarter.
Read the post
Comparison
Meeting notes tools vs product knowledge platforms: which one does your team need?
Meeting notes tools record what happened in a meeting. Product knowledge platforms keep what is true about the product. Here is the difference, when you need each, and why most teams end up with both.
Read the post
Buyer's guide
AI assistant for product teams: what it should do, and how to test one in ten minutes
Four different products are sold as an "AI assistant for product teams". Here is what the phrase should mean, five tests you can run before you buy, and where Wisibl lands on each.
Read the post
Behind the scenes
Half the loop is deciding the same thing twice
Product building is not six steps. It is a loop of ten, and three of the ten are the same decision made again. Here is where the repeats come from, and what "kept once" means.
Read the post
Product knowledge
Why meeting summaries are not enough for product teams
A summary records one meeting. Product teams need what is true across all of them. Where recaps break, what to keep instead, and where an AI assistant fits.
Read the post