Perfect taxonomies usually fail first
Most teams start with too many tags. Then everyone uses them differently. A month later, the system is technically organized and practically useless.
We are taking the opposite approach in Fiidbakk. Tags should start small, be easy to merge, and make the next review faster. If a tag does not help a teammate understand the feedback later, it should probably not exist.
The product now nudges teams toward reusable language, but still lets them move quickly when the right label is obvious. We want structure without turning feedback review into database maintenance.
The next version will suggest tag cleanup after repeated patterns appear, which should help teams keep their system fresh without a big admin pass.
