HR Buried in Repetitive Employee Questions
Small companies struggle as HR and operations teams spend excessive time answering repetitive employee questions from scattered documents like handbooks and policies. This manual process is inefficient and prevents these teams from focusing on more strategic initiatives. A solution is needed to automate answers and streamline internal knowledge access.
SOURCES (60)
“The documentation exists but it covers the what, not the reasoning behind it. Why not? I started keeping a lightweight decision log outside of our main PM tool, just a running doc with the date, the context, who was in the room, and what the…”
“I'm in the the middle of a project to replace Chatter with Slack Channels for Records at my company and hit a handful of product gaps along the way that I wanted to share, because I couldn't find much out there when I was looking for lessons learned. From my perspective, the Slack Channels for Records product is solid and I'm excited about where it's headed, but there are some rough edges that will affect you depending on how complex your org is. We're running this across Cas”
“So it's a bit of yes and a bit of no. I think Kanban would only be useful if I breakdown more, and my boss feels attacked whenever anyone suggests we breakdown more (and while he's the main barrier, some individual project team members also push back hard). So I could, but only at the feature level, and a number of people are involved within each step. And at that point I don't see any value in it, that's kind of a portfolio-at-a-glance view.”
“having filters and automations to hide stuff once it’s done from my main view to keep an overview somehow”
“The ping-the-author loop is the real problem. Our docs are usually stale so everyone scrambles in the ops channel anyway.”
“Confluence or SharePoint, but i'll be honest the real knowledge lives in Teams channels (or other communicating tools) and a few people's heads. Equally important the process of documentating should be maintable and scalable because i have seen well structured documentation not up to date. The docs exist but you don't trust it's current, so you ping the author anyway. Update the docs during postmortem while it's fresh. Docs written only when someone has time are already outda”
“How difficult is it to start? I have seen some people use it and it looks cool but also lots to learn”
“PS - Can you transfer full ownership of a page or database to another person? For example if I have ownership of page A and it appears only in my workspace, can I transfer main ownership to another person where it only appears in their workspace?”
“The multi-source consolidation is a real problem, but the harder question is usually: which source's signal is most underrepresented in your current roadmap decisions? Most teams over-index on sales and enterprise requests (loudest voices) and under-capture the patterns in customer calls that dont make it into written tickets. A customer who says "it takes us 3 steps to do what used to take 1" isn't filing a ticket - that insight lives in the call. For surfacing patterns from c”
“We are small agency of 8. I make the final call as the owner. There isn't someone specifically responsible for change management”
“yeah that's kind of where i landed too but it feels weird calling something current when you know it's already 5 days old by the time it hits the dashboard. the data is real but the timing makes it look like we're always behind. not sure there's a clean fix honestly, might just be the nature of how this comes in”
“Agreed here. If there isn’t buy in around the content and capacity to achieve the layers of verbal comms to monitor it then no amount of calls, docs or software is adequate.”
“Came here to say exactly this. I completely agree with you. We use the mint out framework and it really works. First version is definitely better. Reading the revised version isn’t necessarily rocket science, but I had a harder time understanding it and it’s too many words. First version did the job.”
“You can have any system in the world but it comes down to the quality of input which will determine the quality of the output.”
“Visual project management docs help but only if the information stays current. The tool doesn’t reduce meetings on its own. What actually does is people being able to answer their own questions without needing to tack someone down. For that to work, the visual layer has to reflect reality in close to real time, which means whoever owns the work has to actually update it rather than treating it as a reporting tool they fill in before the sync. Where I’ve actually seen this cut meeting load is whe”
“In my opinion this is a company culture and ways of working issue. If basic work and project document we think isn't part of the culture, then the sources won't stay updated. If self serving information isn't part of the culture, no one will read them. If asynchronous, independent work isn't part of the culture, neither matters at all and you probably won't make much progress. Imo you have to fix the underlying issue through long, boring, leadership supported change managemen”
“lean teams usually land on either a lightweight CLM like Ironclad or Juro, both low-overhead, or something like Irys One if the workflow bleeds into drafting and redlining too, less pure CLM but fewer vendor handoffs. implementation lift is the real differentiator to pressure-test in your next round.”
“That's the key. The moment people stop trusting the board, they go back to asking each other. After that, every update becomes "Can you just confirm...?"”
“Same post under r/projectmanagement https://www.reddit.com/r/projectmanagement/s/f5IGyWvIBN”
“I'm at the very start of scoping a master's thesis, which will be some type of cloud based application that solves a particular issue, and want to ground it in something real rather than picking a topic in a vacuum. My thesis needs a cloud component, so I'd like to build a prototype with some cloud capacity, but beyond that I have no fixed idea yet. I know it seems there's a SaaS or tool for nearly everything already, so I'm not asking "does X exist." I'm trying”
“what you've built is fragile for exactly the reason you named: it runs on everyone already knowing each other, not on anything documented. that's fine at 5 people and breaks hard the moment someone new joins, because they have no way to learn who's good at what except by trial and error over months. the fix isn't switching to corporate hierarchy, it's writing down the thing that currently lives in your heads. a simple map of who owns what and why, even informally, lets a new”
“Find a dev on the team that you can pull with you into leadership meetings, and make them give brief updates on the technicals. A "SME". You want the most knowledgeable individual who is also articulate, so that they can catch any bullshit other developers might be giving you. In my experience, as soon as you start holding them directly accountable, shit stops slipping to the right. JIRA is free I believe, you need tickets for each piece of development, with developers actively comment”
“Yes, there is a very small pilot group. We have MCPs for JIRA, Confluence, and Slack.”
“Interesting, thank you. Could I ask which type of company and size you work in? Sorry for asking too many questions”
“For PM - Engineering use Jira+Git, rest of the company use Briefmatic + Claude Google workspace apps for email, docs, Drive. Slack for internal chat, Whatsapp for external chat”
“We are doing the same, documenting decisions in Git. And the nice thing with this and design repos is that AI tooling also has that decision context.”
“We ran into this on long projects with staff turnover. We found that documenting what was decided wasn't enough. The missing piece was why it was decided. A decision log with the rationale, assumptions, alternatives considered and who approved it proved much more valuable than another set of meeting minutes. Six months later, new team members could understand the context instead of reopening decisions because they looked arbitrary.”
That is a very, very important piece of feedback. I am really glad you looked at it :) I am noting it down. Thanks !!
“The Google Doc graveyard is a universal problem. Documentation fails because it gets treated as a project instead of a habit. The only thing that actually sticks is recording people doing the work, not writing about it. Have your team do a screen share or Loom video the next time they do any recurring process and just narrate what they're doing. Takes five minutes, captures the nuance, and doesn't require anyone to sit down and write a manual. Store everything in one place, Notion works”
“The playbooks-as-team-memory angle is the right moat, but the hard part won't be saving them, it'll be making them survive a different machine, since desktop automation is brutally sensitive to UI changes, timing, and each person's setup, and a playbook you recorded on your Mac silently breaking on a teammate's is what will erode trust fastest. If you can make replay resilient (anchor steps on element semantics and verify each one actually happened instead of blindly firing click”
“Two things. A process map should show current state aka what the team is actually doing. You can make a future state that addresses the bottlenecks and pain points the team is circumventing and train on it. Then it becomes current state. Future state processes are for vetting and training. Your shared process map should show show what is actually happening. I map using BPMN as my process language, build in Visio (draw.io is a good starting point) and document it in our quality management system”
“We started writing short decision records in the repo right next to the feature code. When someone inevitably asks why we went with option B, you just link the record and move on.”
“It’s always hard to come up with a systematic approach in a grown organization without bothering anyone with additional work. Documentation is always lacking behind. I assume you have some sort of documentation, but it’s not up to date. Some easy hacks (and proceed from there): - build an AI skill with your favorite AI that knows and updates the documentation and one that tracks decisions and creates reports. You can also hook them up with your Jira or sth. Let it keep track of decisions, gaps,”
Our internal docs are kind of a mess right now. A lot of our workflows jump between 5 or 6 different apps, so documenting one simple process turns into a bunch of…
“Slack, Outlook, airtable, enterprise search (I believe they use coveo), my obsidian vault, Google docs (yes we use outlook and gsuite, I have no idea why), Jira, GitHub, figma, a couple of internally developed data querying MCPs, Zoom (ugh), and Lucid off the top of my head. All company approved connections. Google Workspace CLI, which heads up is kind of unofficial (it's a grey area).”
“I feel like this is a bit of a bell curve situation. - At a small scale a couple scripts without much central configuration management or monitoring works fine. - At a medium scale there's a benefit to paying someone else for an all in one solution to maintain the scripts/monitoring for you. - At a large scale the cost of outsourcing the solution is more than building your own internal solution. The exact numbers on the tipping points are going to depend on how heterogeneous your environment”
“yeah, this is pretty common imo. sometimes just having a clear, centralized way to trace back requirements to specific customer feedback makes a big difference.”
“You called out the part most wikis miss: the system works for a week, then nobody updates it. We built our solution around that exact failure mode: it connects to meetings, Slack, Gmail, and documents, then keeps a cited team memory current without a documentation owner. If you're still comparing options, would you like to run a short test using one real workflow? I would also like to hear about your daily workflows and see if we can adjust what we have now to better fit your needs. lmk”
What methods do you use to document and plan/prioritize the work?
“The hard part usually isn’t choosing the knowledge base—it’s getting people to contribute consistently. We’ve had better results when the important context is captured from the conversation itself instead of asking someone to rewrite it later.”
“We switched to Notion a year ago. The biggest lesson was that the tool wasn't the problem, it was making documentation part of the workflow. If updating docs is optional, nobody does it.”
“For meetings you can create a database in confluence. Each entry a meeting. Sort by date (database field) and keep most recent meetings up. You can also categorize by customer or project. In jira I just track delivery. PRD -> Refinement -> Jira Epic ->Jira Tasks. From then on that belongs to engineering and I use it to keep track of delivery at the Epic level. Execpt the PRD, the rest are short lived artifacts. The Epics may bit long lived but in my case it is a slice of a feature. The”
“Thanks, this is really helpful. I like the distinction between documenting meetings and documenting what was actually agreed, and that's a subtle but important difference. I also hadn't thought about accountability as the bigger issue rather than documentation itself. Out of curiosity, have you found Confluence and Jira sufficient for maintaining that history on larger or longer-running projects, or do they start to become difficult to keep in sync?”
“Document meetings, specially what was agreed: end a meeting, write meeting notes in confluence, share page with participants. Make people accountable for their decissions. Call out those who are not adhering to previous commitments, require evidence or strong justification to accept change, reject or just defer to next iteration of the feature. Reduce scope of features so the oppty window to change requirements during delivery is narrower and you can also rely on earlier feedback to guide next s”
“Maybe it's time to switch to an open-source alternative like r/xwiki . Also, with the OpenProject Integration (Pro) we developed, you can now have both knowledge and project management in one single source of truth.”
“If these people are working in a company then company needs to enforce some rules around how knowledge is shared. People are not allowed to use any tool willy nilly in a company when it comes to downloading application. Same should be applied for documentation tool. As a company choose a tool and stick with it. I built NeetoKB since all other tools were charging per user basis and that's how we document how we run our company.”
Honestly you can have the most elaborate documentation system but it heavily relies on people putting time and energy into updating it and actually using it (people dont like reading FYI). Having…
“our biggest improvement came from making documentation part of the task itself instead of something people do later”
“Curious what everyone is using. Obsidian? Docusaurus? MkDocs? Mintlify? GitBook? Notion? Confluence? What do you like and hate about it? submitted by /u/insertion-dynamics [link] [comments]”