Problem: It's challenging when multiple people collaborate on a draft of a Guru card. Without version history, it's difficult to track changes, identify the source of errors, and revert to previous versions. Someone might accidentally erase a really important part, or two people could change the same section without realizing it. Currently, in a draft, there is also no way to retrieve content that was accidentally overwritten/deleted by someone, and would also lead to rework. Without a clear record of who made changes and when, it becomes difficult to determine what was in the original draft and why the changes were made. 
 

How do you solve the problem today? Right now, we're trying to keep track of changes manually, but it's tough. Sometimes, Guru has glitches where a whole chunk of text gets deleted by accident. This makes it even harder to figure out what was changed and why.
 

How would you ideally solve the problem? It would be great if Guru had a feature like Google Docs, where we can see a history of changes. We could see who made a specific change and when, and even revert back to an earlier version if needed.

How big is the problem (business impact, frequency of impact etc.)? Not being able to track changes can cause a lot of problems. We might accidentally delete important information, or different people might make conflicting changes. It becomes diifficult to track changes, ensure consistency, and identify errors. It also increases the risk of unintentionally deploying inaccurate information. This can lead to mistakes, delays, and extra work (and may lead to potential compliance/regulatory issues). It would save us a lot of time and frustration if we could simply see a history of changes.