How do you maintain the Knowledge Graph for writing software

Question

Lately there has been a slurry of new (and pretty good) note taking applications like Notion, Roam, Obsidian, Slite etc. I have found Roam and Obsidian great for maintaining a graph of connected notes easily.But they don't scale very well for a team - specifically a Software Product Team.The use case is a bit different for software. You need to map everything to a feature - or a feature set. And soon you need to prioritise a collection of features - a super critical decision.How do you manage it? How would you improve it?

brettkromkamp · Accepted Answer

I use topic maps to model these kind of things. So, both a feature and a feature set would be (separate) topics with appropriate (semantically meaningful) relationships between them.I am the author or Contextualise, a topic maps-based (personal and collaborative) knowledge management application, so I am biased :)