Hi folks, I've been struggling a bit in different orgs with intel & progress mgmt. Motivating folks to keep data up to date was always a challenge.
Recently started experimenting with some ideas in this space but I'm not great at gathering eyeballs and am in need of critical input. It may very well be that I'm being unreasonable and should just go through therapy to get rid of my tooling/process rage. 😅
📌 Asking the Emacs community because of our focus on FLOSS, data ownership and the ability for end-users to control how to consume/produce information which are ideas we want to prioritize and believe align well with this communicate. I'm well aware that we can't ask teams to all use Emacs so we're thinking of ways how we allow folks to collaborate better without ripping them away from the tools they feel comfortable in to think and create. Considering how passionate Emacs users are, I reckoned this place would be a good place to quickly get called out on a ludicrous premise -- that would be highly appreciated tough-love.
🙏🏿 Ask: if you work in a technical team, please walk through this [3min survey (on Typeform)](https://h8d701bcme8.typeform.com/to/z4DjWYjQ) to provide us a glimpse of your situation. I'd love to spar with folks about tooling hacks that I've learned about through multiple chats over the past months if you leave an email address in the form. Leaving such data is entirely optional, just FYI, so anonymous submissions also work.
# TL;DR:
All the teams we've spoken to are either using Confluence+Jira, or Notion (often solo or in combination with some progress mgmt tooling like Trello, Linear, etc.). The tools "kinda" work but folks are very unhappy about them especially in engineering/research functions. From our chats it seems that the tools are heavily designed for managers and pay less attention to the needs of engineers and scientist. We're scouting out what a solution better tailored to eng/sci functions looks like.
Within larger orgs, some resorted to having dedicated roles to keep knowledge/progress data up-to-date. In smaller teams this documentation function is largely an afterthought and a bit of a nuisance as folks just want to get on with their "work". This often results to pain when folks realise that they need some write-up of decisions or designs that were never recorded or were recorded but are no longer findable.
We're curious to understand how other folks deal with this problem (or keeping knowledge and progress data up-to-date) and learn to which extend this problem is "made up" on our end.