> I don't care if the body of the ticket is empty and as the Engineer you prefer to write it in a notebook. > I don't care where the conversation gets recorded

> I don't care if the body of the ticket is empty and as the Engineer you prefer to write it in a notebook. > I don't care where the conversation gets recorded, or at all (provided the people are capable of remembering it). That -"provided the people are capable of remembering it"- is quite a restriction you got there. If some engineer writes it in their own notebook, some other one simply goes by their own memories, etc, then I'm willing to bet there will be different memories of how it went and at least some of those will be fragmented or lost. And every time you need that information, you'll find yourself having to re-search it, re-compile it, and reconcile it again. And then someone leaves and that perspective of the conversation history is lost forever. I mean, sure, don't put the tool over the actual conversation. But then again, please, do use a tool to register history, key arguments, accepted limitations, relevant decisions, actions taken. > This is strong evidence of a team working with extremely shared context. Not really, no. It may be a reflection of that... or it may be a reflection of something else entirely. Like some people making small notes so they will remember and nobody else reacting to them. Ideas that come up but are never discussed afterwards. The visible result of this can be exactly the same as what you describe and yet the situation is totally different.