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)
“Also struggling with the exact same issue here! It's hard to get buy-in from team. I like some of the advice here though so far..”
“Tasks are just a record of a request for somebody to perform an action. Unless there is a conversation that ends with a commitment, then no system on earth will help. The commitment doesn’t have to be heavy. It can be as simple as “yes, I will do this by Friday,” after which the system is simply where commitments are recorded.”
“You can't make people use a tool they're not intrinsically motivated to use or extrinsically forced to use as a part of their performance. The first builds ownership and consistency, the second way leads to employee burnout, distrust and grudging baseline compliance. If teams aren't invested in the systems from day 1, the likelihood of persistence is almost zero.”
“Start doing performance and merit reviews based on what is in notion, that fixes things fast.”
“We used to have it every morning. Some of those mornings it turns into an hr+ long argument between two people that doesnt need to involve the 10 of us that's just waiting there. We got rid of it. We have a main chat where everyone posts what they're doing, plus a kanban on progress throughout the day.”
“my standups took over an hour every day, just reading the tickets on the jira board out loud, then PM asking a million pointless questions dragging each persons topic on and on when it had nothing to do with the other 20+ people. always ended with "let's take this offline". thank God I quit that job”
“Agreed, automation is key to minimise the effort in updating any visuals and thus increase the probability that they'll stay current. Interestingly I've found that automating a roadmap can allow you to spot errors in the underlying data/plan which are hard to spot when dealing with the detail. "What's that doing over there in the plan on a page" is usually a sign that the underlying plan has a mistake :)”
“We’re a smaller MSP with a handfull of techs but only two senior engineers, and we have a handfull of small projects that we either can’t get into the schedule but need to get done sooner, and a few for larger clients that, if I’m being honest, should probably be done by more specialized / higher qualified people. Where do you go to find labor and skills your trust while protecting the business interest? submitted by /u/GhostNode [link] [comments]”
“This sounds like a human problem not a Notion problem. Why are tasks being created nobody picks up, what do they actually do if not the tasks? Are there any meetings to go over the status of the tasks and see if there are any blockers etc? The tool isn't an issue here.”
“Yep, this is exactly the issue I keep coming back to, once external people are involved, the permission system starts feeling much less comfortable. Have you found any setup you actually trust now, or are you still basically double-checking every link before sending?”
“We ran into this too, having a visual layer for dependencies and risks helped a lot without adding another task tracker. For QA heavy teams, practitest can also be useful for keeping test coverage, risks, and progreas visible in one place. I think the key is making sure it fits into the workflow you already have rather than creating another system everyone has to constantly update.”
“I’d rather have individual tools that are fully functional. The real pain point for me is having multiple tools that do the same thing! We have docs in share point, NAS’s, self-hosted wikis, azure wiki, teams chats, git repos. It’s a mess”
“The problem, as you described, is a missing connection between information. A visual layer helps because it makes those connections clear. Dependencies and priorities become things people can point to and debate, which is very useful in a remote setting. Maintenance is also a different problem when the visual links to the work it describes. Updating it becomes part of the work instead of a separate task, which is why visuals that exist in isolation are usually abandoned.”
“Do you have a problem statement? do you have system, user and workflow requirements? Because that is what you need to map to a product or system not taking a stab in the dark and thinking of what product might do the job. You run a very real risk of having a system that doesn't do what it needs to do because people will either not use it as deployed because it doesn't help them in their job or worse case scenario it could lead to outright system abandonment because it doesn't do what”
“Any tool is fine. Use whatever you have and identify the gaps you have with your process and the tool itself. then make a list of the ideal process for your needs, and the list of requirements you have is sitting in front of you. Plug this into chatgpt and it will recommend something for you.”
“Tried moving from spreadsheets to actual tools last year and the rabbit hole is deep. Airtable works if you want something halfway between a spreadsheet and a database without the learning curve of Jira. The agent-based ones still feel like they're 80% hype and 20% actually saving you time, but if you just need something that won't fight you on dependencies and timeline views, that's where I'd start.”
“Wondering if someone has additional information - My org currently uses CodeTwo. I really like it, and I believe it does it's job well for our size. We're a 200 person org. I have a few different templates that I assigned by groups to different departments where additional information may be required in their signatures. We're currently using server side to apply the signatures, but more and more people are complaining that their signatures don't append when using the default MS”
“I've installed as test. Is there a way to group clients (invited end-users)? We service business clients and a single client may have 3 or 4 people that needs to see all tickets for their business...not just tickets they themselves enter. Would sponsor an advanced tier if so....that looks like one of the only outstanding feature for our use case.”
ah well mgmt hopefully is paying for inference in that case
“You already have several recurring complaints, but they may belong to different buyers and workflows. I would avoid treating “manual updates” as one problem. Pick one role and ask them to walk you through the last time an update was missed or repeated. Where did the information originate, where was it copied, who asked for it, and what happened when it was late or wrong? Then test the workflow manually with three teams. For example, generate one weekly report from their existing Jira, GitHub, or”
“here is the context: Mid size (1000 users) company that has been trying to do in-house software dev (outsourced to south east Asia) with poor results. Company IT side is fairly mature, heavily virtualized, hybrid on prem/cloud, but a bit weak on the Azure side. Existing sysadmins are pretty solid. The dev is, well a shitshow. We are presented with projects with no infrastructure requirements, the devs dont really seem to know what they need. Currently they are doing everything in Blazor after we”
+1 for Fibery. Very flexible, but takes some set up. Feel free to send me a message if you need a hand with it.
“I think the bigger issue may be less about finding another planning tool and more about making the priorities and dependencies clear enough that everyone sees how the pieces connect. A simple view of the few priorities that matter most, what depends on what, and who owns each piece can make planning calls much more focused. Otherwise, the team just ends up organizing more information.”
“before picking anything, figure out if the real gap is visibility or alignment. if people cant see how things connect thats a tooling problem. if they see it but disagree on priorities thats a process problem, and no visual layer fixes that”
“Famous Run2525, Please provide additional information to better understand your challenges. What tool or PMIS are you using to track your tasks, risks, meeting notes, etc? Based on your answer you may either be missing a tool to link all priority projects, roadmap and risks or you may be underusing your current tool.”
“tried a bunch of visual tools and most end up as ghost towns if they're not dead simple to update, whiteboard style stuff with sticky notes and arrows seems to stick better than gantt charts or kanban boards nobody touches”
“Looks really good! Thanks for all your hard work? Some architectural questions: - Why is your system to identify (sub)tasks ID based instead of link based? Are you thinking about an option to change it or is there some reason behind that decision? - Is there / will there be a way to change frontmatter properties in the settings to align with existing task and project management systems users build themselves? - could it be possible to open tasks / projects just in obsidian's native md view (”
“We sync approved leave/sickness from Workday into Kimble (Salesforce-based PSA), and over the last month around 90 support tickets came in, more than half tracing back to Workday-Kimble sync or calendar issues, affecting dozens of people, not just a couple. Main patterns: absence approved in Workday not showing up in Kimble at all, some coming through as half days instead of full, UK bank holidays not being recognised, and several people unable to submit any time entry for the last day of the mo”
“Wonder if other PMs deal with this same daily pain point. My company’s data team is always buried under requests. Anytime I need cohort breakdowns, retention curves or basic product metrics for roadmap planning and feature work, I have to file an official request and wait ages. By the time I get the report, the data is already stale. User behavior has changed, we’ve moved on with product iterations, and those insights barely help for quick decision‑making. These data bottlenecks are so annoying”
“Yeah the search clutter is the one thing that never fully goes away with this approach, but its a fair tradeoff for keeping relations intact”
“Needed to vent to a group that would understand (and please, join in with your own stories). Why ask me (and my team) to build you tools, workflows, solutions that you just ignore and stop using?! What an absolute waste of my team's hard work and valuable time. What blatant disrespect, knowing how busy we are. We built you reports and a dashboard, cool work queue visuals/tools, and then I see you using a homegrown XLS in the meeting to track customer engagements?! Or a messy word doc with no”
“Building internal is the right call at your size, and your eval method (same use cases across every system) is the part most teams skip. One layer worth planning from day one, because retrofitting hurts: what goes INTO the model. Intake notes, medical records, discovery docs all carry client PII and privilege, and once your internal tool sends them to an LLM API they're in prompts, logs, and provider retention policies. The pattern that's worked for teams I know: a redaction step in fron”
“Harvey employee here. Which DMS and project management tool do you use? We can look into integration.”
“The one-dashboard approach sounds useful. How do you keep it from turning into another backlog when several clients hit Review at the same time? Do you cap what’s visible, or split it into “needs me now” and “waiting on client” views?”
“While this is dope. I have a couple of questions and doubts one is whether you have done a long term feasibility study on maintaining it in-house. The second is, does this mean your firm and other firms are all out on external software. I don't mean Harvey, Legora but rather specialised tools like lets say Clio. Because while its fairly easy to replicate Harvey & Legora's functionality with a few API calls, at least the bare bones of it and then customize on top of that. Its not real”
“Makes sense. Separating the tasks is a great strategy to show completed work and monitoring new requirements/ revisions that keep the project moving.”
“Worth separating two problems here. One is the firm workflow, one is the software. On workflow: most "not paying attention" mistakes come from asking someone to type what a rule should have coded. Tighten your vendor rules so the admin is reviewing, not entering, and see what is left. On software: Dext for receipts and bills, and testing Xero on your side business is the right way to build the case with your partner. Desktop pricing will make the argument for you soon enough. One ask,”
“One useful pattern is not letting assistants write straight into whatever you consider canonical. Have them propose changes into a separate “pending updates” view, then promote them to the canonical record after a quick review. Otherwise corrections, restatements and genuinely new information can easily end up mixed together. I'd also separate what was decided from why it was decided . The reasoning gives the next assistant a much better chance of recognizing whether a decision is still vali”
“before adding more software, map where the admin is making mistakes. automate those specific steps first then keep human review for expectations. that usually works better than trying to automate everything.”
“"Impressive-to-build and useful-to-receive are not the same thing" is going on my wall. Engineers love building complex dashboards, but users just want actionable clarity in 3 seconds. Ripping out the noise to deliver a single plain-text answer takes guts, but it's always the right move.”
“I struggle with having no idea how long it will take. Either the LLM will finish it in an hour, or it will take me 3 days because it just can't do it right, and it ends up taking longer than if I just did it myself because of all the flailing. But it is less on average.”
“Backlog, post MVP. Companion to 390, which takes the rest day setting out of Settings for MVP scope — this is where it comes back. Nothing to design here yet beyond restating what already shipped and was pulled: a single weekday nothing is expected on, subtracted from the week's division ( RestWindow , 73) and excluded from the dead rep arithmetic ( WeekSpans 's actionable , 100). docs/week marks.md 's "Deferred, on purpose" section already flags three unresolved interactions worth reading befor”
“I think the bigger question is why are you getting multiple revisions? Are the requirements not clear? Can you do more work up front with the client to prevent this? Maybe mockup stories?”
“I’d avoid one giant context page. Store decisions, constraints, sources, and open questions as separate records with an owner, status, effective date, last review, and “supersedes” relationship. Assistants should retrieve a filtered current view while people retain the complete history. Conflicting updates should create an exception instead of silently replacing the old record. We use SIGNLD internally to connect decisions with documents, conversations, tasks, systems, and later outcomes so an a”
“Solo founder here, running one small product plus the usual pile of docs, roadmap, and half-baked ideas. For a couple of years everything lived in one big all-in-one workspace. It was fine early on, but lately opening it feels like work. Nested pages I forget exist, templates I set up once and never touched, and it's gotten slow enough that I avoid it, which defeats the point. I'm looking for a lighter notion alternative for a one-person operation. My actual needs are small: - fast plain”
“Thank you. It makes sense to use different phases/ statuses. There are so many reports, will it really be helpful to have a new Jira story created every time a revision is completed?”
“Yes. I can help. Have done it many times before. Where is the compliance team? The ISSO? The system owner? Do you have any of those people at your company?”
“You can interact with GitHub issues via email, iirc they come through as one email thread per issue, and replying to the email thread adds a comment. You can get a solution that works for both of you; PM gets to use email and the rest of the team get to use an actual, functional, searchable, linkable, fucking issue tracker”