Expert insights on HR technology, AI leave management, employee engagement strategies, and modern HR solutions.https://arheev.com/en-ushttps://arheev.com/en/blog/we-ditched-slack-and-our-intranet-for-arheev/https://arheev.com/en/blog/we-ditched-slack-and-our-intranet-for-arheev/Tools don't just organize work. They architect behavior. One company replaced their internal comms stack with Arheev and it did more for culture than two years of offsites combined.Thu, 12 Mar 2026 00:00:00 GMT One of our clients, a 60-person company, spent two years running culture workshops, rewriting their values, and investing in manager training. Their engagement score barely moved. Then they made a decision their leadership team thought was minor: they stopped using Slack for internal announcements, retired their intranet, and moved all company communications into Arheev. Within 90 days, two-thirds of employees said that change did more to transform how they worked than anything leadership had tried in the previous two years. Not the new PTO policy. Not the hybrid mandate. Not the feedback training. Consolidating where communications lived. ## The problem with having three places for everything Before the switch, internal communication at that company worked like this: HR posted policy updates on the intranet. Managers shared team news on Slack. Leadership sent company announcements by email. Nobody agreed on where to look for what, so people checked all three, found contradictions, and eventually stopped trusting any of them. We hear this from almost every company we work with. The tooling sprawl isn't intentional, it accumulates. Intranet for official stuff. Slack for whatever's happening right now. Email for anything that feels too important to lose in a chat thread. Three systems, none of them complete. The result: employees who are over-pinged and still somehow out of the loop. ## What the intranet was actually doing Most intranets become graveyards within 18 months of launch. The pattern is predictable. IT or HR builds it, populates it with policies and org charts, announces it at an all-hands. For the first few weeks, people check it. Then updates slow down, content goes stale, and nobody remembers to look. By year two, it exists mainly so someone can say "that's on the intranet" when an employee asks a question. We saw this with that client. Their old intranet had hundreds of pages of documentation, policy manuals, company history. When we asked how often employees actually visited it, the answer was uncomfortable: once a month, on average, usually to find one specific thing and leave. It wasn't a communication tool. It was a filing cabinet that happened to be online. ## What Slack was actually doing Slack's problem is the opposite. People don't ignore it, they can't. The typical knowledge worker gets interrupted dozens of times a day across chat, notifications, and direct messages. Research puts the focus recovery cost at around 23 minutes per interruption, which compounds fast. But the subtler damage is to information quality. In a real-time chat tool, everything looks equally urgent. A policy change and a question about lunch have the same visual weight. Important updates scroll off the screen within hours. Context gets lost in threads that branch and die. We saw this in check-in data for that team. Employees kept saying they felt "out of the loop" on company direction, not because leadership wasn't communicating, but because the communications were scattered and fleeting. People had learned to filter aggressively, and the important stuff was getting caught in that filter along with the noise. Slack is good at a lot of things. Being the authoritative record of what your company decided and why isn't one of them. ## Why moving to Arheev changed the dynamic The shift wasn't about features. It was about having one place that was actually built for HR and company communications together. Arheev's feed became the single source for company announcements, HR updates, policy changes, and team news. Because it lives in the same platform where employees already manage leave, check their goals, and handle HR requests, they're in it regularly anyway. Communications reach people in context rather than competing for attention in a separate app. A few things changed right away. Employees stopped asking "where do I find that." When there's one place, the question answers itself. Leave policies, holiday schedules, benefit updates, all in the same feed they check for their approval status. Managers started writing better updates. When posts persist and everyone sees them, people write more carefully than they do in a Slack channel where the message scrolls away in four hours. The permanence changed how people communicated, not because anyone asked them to. Reach became something you could actually measure. With Slack, you never really knew who saw a message. In Arheev we can see read rates on announcements. HR teams that can see what people engage with write differently than HR teams that are just broadcasting into a void. ## What the data showed after 90 days - Employee engagement scores up 28 points - "I feel informed about company direction" in check-ins: up from 41% to 79% - After-hours messages down 67% - Voluntary turnover: zero for the quarter, against an annualized rate above 20% the prior year - Average time to acknowledge a company announcement: under 4 hours, versus 3+ days on the old intranet The check-in shift was the one that surprised us most. People didn't just feel less interrupted. They felt more connected to what was actually happening at the company. Those are different things, and both moved. ## The intranet wasn't a technology problem Worth saying clearly: the old intranet wasn't badly built. The problem was that it required employees to go somewhere specifically to get information, and they rarely had an independent reason to be there. Arheev works differently because employees are already in the platform for other reasons. Submitting leave, checking their balance, completing goals. Communications reach them there rather than requiring a separate visit. The engagement happens in context, not as a dedicated trip to a tool they'd otherwise ignore. We see this consistently across clients. HR teams that move announcements into Arheev get higher read rates than anything they were getting from standalone intranets. The content doesn't change. The delivery mechanism does. ## Why leadership initiatives kept falling flat This company's leadership wasn't bad at communication. They were communicating constantly. The problem was fragmentation: the same message going out three ways, slightly differently each time, with no clear source of record. Employees couldn't tell which version was current. So they stopped trusting any of them. In Arheev, we track engagement against communication patterns. The companies with the highest engagement scores aren't the ones sending the most messages. They're the ones sending consistent ones, same channel, regular cadence, clear enough that people don't have to cross-reference three tools to figure out what's actually happening. That consistency is hard to maintain when you're managing Slack, an intranet, and email simultaneously. With one place, it stops being hard. ## What's worth measuring if you're not sure If you're evaluating whether your current setup is working, a few things to look at: Announcement reach. What percentage of employees actually see a given update within 48 hours? If you can't answer that, you don't know whether you're communicating at all. Self-reported information confidence. A single check-in question, "do you feel informed about what's happening at the company?", is one of the strongest leading indicators of engagement we track. It moves before the headline engagement score does. After-hours message volume. High after-hours volume usually means the daytime signal is noisy enough that people are managing it after work instead of during it. Leave and sick day patterns by team. Teams that feel out of the loop take more fragmented leave. The correlation is consistent enough that we flag it. ## How they actually did it They didn't rip everything out at once. They started by routing HR communications through Arheev: policy updates, leave reminders, benefit changes. That alone cut the "I didn't know about that" complaints noticeably. Once that worked, they moved team announcements. Then leadership updates. The intranet got archived. Slack became something people could use if they wanted to, but stopped being the place where important things happened. The full consolidation took about three months. Each phase was small enough to reverse if something went wrong. Nothing did. ## The thing most companies get wrong Most companies treat internal communication like a content problem. Write better updates. Run more all-hands. Create a dedicated channel for announcements. The issue is usually structural. When communication is fragmented, employees learn to ignore most of it because they can't tell what matters. They build filtering habits that catch the signal along with the noise. Moving to a single platform fixes that, but only if it's one where employees already have a reason to be. An intranet asks people to change their behavior. Reaching people inside Arheev, where they're already managing their day-to-day work, doesn't ask them to change anything. The companies doing this well aren't the ones with the best-written updates. They're the ones whose employees actually see them. That's a distribution problem, and distribution problems are solved by being where people already are. https://arheev.com/en/blog/6-tips-to-give-better-feedback-as-a-manager/https://arheev.com/en/blog/6-tips-to-give-better-feedback-as-a-manager/Most managers know they should give feedback. Few do it well. Here's what actually works, and why timing matters more than most people think.Fri, 20 Feb 2026 00:00:00 GMT A few months ago, we were talking to a team lead who complained that his people kept making the same mistakes over and over. We asked him when he last gave direct feedback about it. He thought about it. "Probably at the last performance review. Three months ago." There's your problem. ## Why Feedback Is Hard to Get Right Feedback is one of those things everyone agrees is important and almost nobody does consistently well. Either it's too rare (annual reviews), too vague ("good job, but maybe improve communication"), or too harsh (delivered in a way that puts people on the defensive). Getting it right matters. Not just for individual growth, but for the whole team's culture. Bad feedback habits compound over time. People stop trusting your observations. Or they stop trying to improve because they never know where they actually stand. Six things actually help. ## 1. Give It Often Feedback doesn't have to be a formal sit-down. It doesn't need a calendar invite and a structured agenda. The most useful feedback is frequent and light. A quick note after a presentation, a comment in a project wrap-up, a two-minute check-in after a difficult meeting. These add up. Waiting for quarterly reviews means you're giving feedback about things that happened months ago. By then, the moment is gone, the context is fuzzy, and people wonder why you're bringing it up now. ## 2. Give It Promptly Timing is most of it, honestly. If someone nailed a client call, tell them that day. If someone's presentation fell flat, address it that week, not at their six-month review. Immediate feedback ties the observation to the experience. People can actually learn from it. Feedback delivered three months later is just a story about the past, it doesn't change much. ## 3. Be Kind, Not Soft There's a difference between being kind and being so diplomatic that nothing lands. Kind feedback is direct and honest, but it comes from a place of genuine support. You're not trying to catch people doing something wrong. You're a teammate who happens to have a broader view. Something like: "The structure of that report was really clear, next time we'd push you to include more concrete examples" lands completely differently than "this was fine but needs improvement." One is useful. The other is noise. ## 4. Ask More, Tell Less A lot of managers treat feedback as a monologue. Here's what you did. Here's what to do differently. End of conversation. That's fine for simple situations. But for anything complex, asking questions first opens things up. "How do you think that went?" or "What would you do differently?" before you share your take gives the other person a chance to surface things you might have missed, and makes them more receptive to what you say next. People who arrive at their own conclusions tend to actually act on them. ## 5. Be Specific "You need to communicate better" tells someone nothing. "In yesterday's meeting, you jumped to solutions before the client finished explaining the problem, and we noticed they got a bit defensive" tells them exactly what to work on. Specifics are harder to dismiss and easier to act on. If you can't point to a concrete example, the feedback is probably too vague to be useful yet. Wait until you can. ## 6. Follow Up This one gets skipped constantly. Feedback without follow-up is just criticism. If you told someone to improve how they handle escalations, check in a few weeks later. Did anything change? Do they need more support? Did the advice even make sense in practice? Goals stick when people know they're being tracked, not in a surveillance sense, just that someone actually cares whether they improve or not. ## Feedback Goes Both Ways The companies where this works best aren't just the ones with good managers. They're the ones where asking for feedback is normal at every level. Peer feedback, upward feedback, regular check-ins that go in both directions. It stops feeling like something done to you and starts feeling like how the team operates. That shift is worth more than any individual tip. We track a fair amount of performance data in Arheev, goal completion, review cycles, leave patterns. What we consistently see is that teams with shorter feedback loops have fewer surprises at review time. Not because they're performing better on paper, but because nothing's been festering unaddressed for six months. The HR managers who do this well don't wait for a formal process to tell them when to talk to their people. They just do it. https://arheev.com/en/blog/arheev-android-app-launch/https://arheev.com/en/blog/arheev-android-app-launch/We built an Android app for Arheev because managers kept asking to approve leave requests from their phones. Took us six months. Here's what works, what doesn't, and why iOS isn't ready yet.Wed, 22 Oct 2025 00:00:00 GMT About a year ago, we started getting the same request from clients: "Can I approve this from my phone?" The answer was technically yes, you could use the mobile browser. But it was clunky. Slow. Not really designed for a phone screen. So we built a proper mobile app. [It's on the Play Store now](https://play.google.com/store/apps/details?id=com.norveon.arheev). ## Why Mobile Actually Matters HR managers aren't always at their desks. Obvious statement, but it affects workflow more than you'd think. We saw patterns in our data: - Leave requests submitted on Friday afternoons often sat until Monday - Managers checking coverage from home would log in, look, then log out, took 5+ minutes for a 30-second question - Attendance tracking required being at a computer, which remote workers found annoying The mobile browser worked, but barely. People would try it once, get frustrated, then wait until they were at their desk. ## What We Built The Android app isn't a simplified version. It's the full platform, just reorganized for a smaller screen. ### Leave Requests This is the main use case. Manager gets a notification, opens the app, approves or denies. Under 30 seconds if it's straightforward. The AI approval suggestions work the same as on desktop, showing previous similar requests, flagging coverage gaps, checking policy compliance. All the same data, just formatted for mobile. Approval time for our clients who use the app: same-day for about 80% of requests, compared to 2-3 days before. ### Attendance Tracking Clock in/out from your phone. Useful for remote workers or field teams. We added location data (optional, with permission) for companies that need it. Some clients use it, most don't. The attendance dashboard shows who's in, who's out, who's working remotely. Managers check this way more than we expected, apparently "who's around today?" is a common question. ### The Feed Company announcements, news, updates. Pretty standard social feed stuff. We weren't sure if people would use this on mobile, but it's actually the second most-used feature after leave requests. People scroll the feed while waiting for meetings or during commute. ### Employee Profiles Quick access to contact info, position, department. Seems basic, but managers use this constantly. "What's their phone number?" "Which department are they in?" "Who's their manager?" All searchable from the app. ## What Took Six Months Building the app was maybe 3 months. Testing, fixing bugs, and dealing with platform quirks was the rest. ### The 16KB Page Size Problem Google added a requirement for Android 15: apps need to support 16KB memory page sizes. Most devices use 4KB, but newer ones will use 16KB. Three of our dependencies weren't compatible. We had to update react-native-reanimated, remove an old SQLite wrapper we weren't using, and wait for Expo SDK 51 to properly support it. This delayed the launch by about three weeks. Annoying, but necessary. ### Push Notifications Getting push notifications to work reliably across different Android versions was harder than expected. We're using Firebase Cloud Messaging. It works, but there are edge cases, certain battery optimization settings kill notifications, some manufacturers (looking at you, Xiaomi) have aggressive app killing. We added clear instructions in the app for users to whitelist Arheev in their battery settings. Not ideal, but it's the only solution. ### Sync Issues Real-time sync between mobile and web was tricky. Make a change on mobile, it should appear on desktop instantly, and vice versa. We're using WebSockets for live updates. Mostly works. Occasionally there's a delay if the connection drops and reconnects. Still debugging those edge cases. ## What People Actually Use Based on analytics from the first month: **Most used features:** 1. Leave request approvals (by far) 2. Checking the feed 3. Attendance tracking 4. Employee search **Least used features:** 1. Document access (people prefer desktop for this) 2. Benefits management (same reason) 3. Position/department editing (rarely needed on mobile) Makes sense. Mobile is for quick tasks and checking information. Complex work still happens on desktop. ## Why No iOS Yet Short answer: we wanted to get Android right first. Longer answer: iOS development requires Mac hardware, different testing setup, and we're a small team. We decided to launch Android, gather feedback, fix bugs, then apply those lessons to iOS. iOS version is planned for Q3 2026. We've already started on it, just not ready to ship yet. ## The Unexpected Win The app improved our return-to-office metrics for hybrid teams. Managers can handle HR tasks without being at their desk, so they're less stressed about being away from the office. Employees can submit requests or check information without needing computer access. One client said: "The app made hybrid work actually work. Before, people would delay HR stuff until they were in the office. Now they just do it from wherever." Not what we built it for, but we'll take it. ## What We're Still Fixing **Battery drain**: The app uses more battery than we'd like. Mostly because of the real-time sync. We're optimizing this. **Offline mode**: Right now if you lose connection, the app mostly stops working. We're adding offline caching for read-only features. **Search performance**: Employee search is slower on mobile than desktop. Needs optimization. **Tablet layout**: Technically works on tablets, but the UI isn't optimized for larger screens yet. ## Getting Started If you're already using Arheev, download the app from the [Google Play Store](https://play.google.com/store/apps/details?id=com.norveon.arheev) and sign in with your existing credentials. Everything syncs automatically. If you're not using Arheev yet, [schedule a demo](/#pricing) to see the platform, both web and mobile. ## The Reality of Mobile HR Mobile apps for HR aren't revolutionary. They're just convenient. But that convenience matters. Faster approvals mean happier employees. Quick access to information means fewer interruptions. Being able to handle HR tasks from anywhere means less stress for managers. Not groundbreaking, but genuinely useful. We shipped the Android app. It works. iOS is next. That's the update. https://arheev.com/en/blog/pet-friendly-workplaces-more-than-just-a-perk/https://arheev.com/en/blog/pet-friendly-workplaces-more-than-just-a-perk/84% of employers with dog-friendly offices report better return-to-office rates. Turns out, letting people bring their dogs to work isn't just nice, it might be the only reason some people show up at all.Tue, 29 Apr 2025 00:00:00 GMT Last year, one of our clients added a "pets allowed" policy to get people back in the office. I thought it was a gimmick. Their return-to-office rate jumped from 42% to 71% in two months. Apparently, people will come to the office if they can bring their dog. Who knew? ## The Numbers That Made Me Pay Attention I started digging into this because it seemed too simple. But the research backs it up: - 67% of pet owners would consider quitting if forced back to office full-time - But 78% would stay if they could bring their dog to work - Companies with pet-friendly policies saw 90% of employees feeling connected to their mission (versus 65% at companies without pets) That last one surprised me. Bringing your dog correlates with actually caring about your job? Seems weird, but multiple studies found the same thing. One HR manager I talked to put it simply: "Our return-to-office policy was failing until we allowed pets. Now Tuesdays and Thursdays are packed." ## Why This Actually Works The obvious reason: people got dogs during COVID and now those dogs have separation anxiety. About 10% of pandemic puppies, according to veterinary data. But there's more to it than just logistics. ### Stress Reduction (Actually Measurable) Studies show petting a dog lowers cortisol and blood pressure. Not by a lot, but enough that people notice. One employee in a 2021 study said: "I cuddle him during stressful calls. It's better than any break room." Not exactly scientific language, but I get it. ### Breaking Down Department Silos This one's weirder, but it checks out. Dogs wander around offices. Their owners follow them. Suddenly people from accounting are talking to engineering because their dogs are playing together. Multiple companies reported better cross-team communication after allowing pets. Not because of some team-building exercise, just because dogs don't care about organizational charts. ### The Recruitment Angle "Pet-friendly workplace" on job postings gets attention. Especially from younger employees who treat their pets like family (which is most people under 40, honestly). More importantly: it's a retention tool. That 78% figure about people staying if they can bring their dog? That's way higher than most employee benefits. One company told us they're tracking this in Arheev now, noting which employees bring pets and correlating it with retention. Early data suggests pet owners who bring their dogs have 30% lower turnover. Small sample size, but interesting. ## The Complications Nobody Talks About This isn't just "allow dogs, problem solved." There are real challenges: ### Allergies and Phobias About 10-20% of people have pet allergies. Another chunk have genuine fears of dogs. The companies doing this well create pet-free zones. Separate floors, designated quiet areas, whatever works for their space. One client separated their office into "pet friendly" and "pet free" sections. Let people choose their desk location. Worked fine once they stopped trying to force everyone into one building. ### Not All Dogs Are Office Dogs High-energy breeds, anxious dogs, dogs that bark at every noise, these don't work in offices. The successful policies have requirements: proof of training, vaccination records, behavior assessments. Some companies do trial days to see if the dog can actually handle it. One startup's policy failed because they didn't screen. Three untrained puppies on their first week. Chaos. They learned. ### The Logistics Are Annoying You need: - Outdoor space for bathroom breaks - Cleaning supplies (accidents happen) - Clear policies about who's responsible when dogs fight - Rules about dogs in meetings (yes, this becomes an issue) One company's policy is simple: "Your dog, your responsibility. If it causes problems, it stays home." Seems to work. ## Different Approaches That Actually Work ### Full Pet-Friendly The tech startup model. Dogs everywhere, all the time. Works if your space allows it and most employees want it. Requires the most infrastructure: outdoor areas, cleaning stations, designated relief areas. ### Designated Pet Days One or two days per week where pets are allowed. Lower commitment, easier to manage. Good for testing the waters. One client started with "Pet Fridays" and expanded from there. ### Pet-Free Zones Pets allowed, but certain floors or areas stay animal-free for people with allergies or preferences. Requires more space, but solves the biggest objection. ## What We're Tracking in Arheev We added a simple toggle in employee profiles: "Brings pet to office." Why? Because it affects scheduling and team coverage in ways HR didn't expect: - Pet owners prefer specific days (the designated pet days) - Some people's office attendance correlates directly with whether they have pet care - Leave requests sometimes mention pet emergencies (more common than you'd think) We're not building pet-specific features or anything. Just acknowledging that it's a factor in modern HR. ## The Actual Benefits (Based on Client Data) From companies using Arheev that have pet policies: **Attendance**: Average 20-30% increase on pet-allowed days **Employee satisfaction**: Consistently higher scores in companies with pet policies (though this could be correlation, not causation) **Recruitment**: "Pet friendly" as a listed benefit gets mentioned in about 15% of new hire surveys as a factor in accepting offers **Retention**: Too early to have solid data, but initial trends suggest lower turnover among pet-owning employees who bring pets ## Making It Work If you're considering this: **Start small**: Pilot program, limited days, see what breaks **Set clear rules**: What's allowed, what's not, who's responsible **Get employee input**: Survey your team. If 60% hate the idea, don't force it **Prepare for problems**: Dogs will fight, pee on floors, distract people. Have a plan **Track the results**: Use your HRIS (like Arheev) to monitor attendance and satisfaction before and after One client's approach: "We tried it for three months. If people hated it, we'd stop. Turns out, people loved it." ## When It Doesn't Work Pet-friendly offices aren't universal. They fail in: - Small spaces where dogs would be cramped - Industries with strict cleanliness requirements (food service, healthcare) - Teams where significant portions have allergies or fears - Companies with customers regularly on-site who might object One client tried it, got complaints from customers who visited the office, had to reverse the policy. It happens. ## The Real Reason This Matters Post-COVID, getting people back to offices is hard. Hybrid work is the compromise, but even that's a fight. Pet-friendly policies are one of the few things that actually changes behavior. Not because of some HR theory, but because people genuinely want to bring their dogs to work. Is it the right solution for everyone? No. But for companies struggling with return-to-office, it's worth considering. We've seen it work enough times that it's not just a trend. It's a real factor in modern workplace strategy. Still feels weird to track pet attendance in an HR system, though. https://arheev.com/en/blog/how-ai-changes-hr-work/https://arheev.com/en/blog/how-ai-changes-hr-work/We built an AI approval system for Arheev's leave management. Turns out, the hardest part wasn't the AI, it was figuring out what fairness actually means in different companies.Fri, 04 Apr 2025 00:00:00 GMT When we started building Arheev, I thought the AI part would be the hard part. Train a model, feed it some data, boom, automatic leave approvals. I was completely wrong. The tech wasn't the problem. The problem was that every company has a different definition of "fair." What feels reasonable at a 20-person startup doesn't work at a 200-person company with five departments and different leave policies. ## What We're Actually Seeing in HR Right Now Companies using AI tools in HR are cutting admin time by about 40%. That's not marketing speak, that's what our clients tell us when they've been using Arheev for a few months. Less time in spreadsheets, more time actually talking to people. But here's the thing nobody talks about: AI doesn't fix bad processes. If your leave policy is confusing, AI just approves things confusingly faster. ## Leave Management (Where We Started) Manual leave tracking is miserable. I've talked to HR managers who spend half their Monday mornings just processing requests from the weekend. Multiple approvers, checking balances, making sure the team isn't left understaffed, it adds up. Our AI system tries to handle the routine stuff: - **Pattern learning**: After a few months, it figures out your approval patterns - **Consistency checking**: Flags when similar requests get different answers - **Policy automation**: Handles the straightforward requests that always get approved anyway - **Coverage gaps**: Warns you before three people in the same team all take the same week off The interesting part? The AI isn't making decisions, it's just doing the tedious comparison work that managers hate. "Didn't we already approve this type of request last month?" That kind of thing. One client told us their approval time went from 2-3 days to same-day for most requests. Not because the AI is approving everything automatically, but because managers aren't digging through past decisions to stay consistent. ## Hiring Tools (That We Don't Build) Resume screening AI is everywhere now. Scans thousands of applications, matches keywords, predicts performance, you've heard the pitch. The good part: it's way faster than reading 500 resumes manually. The sketchy part: these systems can bake in bias if you're not careful. If your past hires all came from the same backgrounds, the AI will just optimize for that. We decided not to build this feature yet because we haven't figured out how to do it in a way we'd actually trust. ## The Employee Experience Part The AI features people actually use in Arheev: - **Smart leave suggestions**: "Based on team coverage, next week looks better than this week" - **Policy answers**: "You have 12 days left, but 3 are already pending approval" - **Pattern insights**: "Most people in your department take leave in August" Nothing revolutionary. Just the annoying lookups that waste everyone's time. We tried building sentiment analysis (scanning messages to detect unhappy employees). Tested it internally. Felt creepy. Scrapped it. ## Performance Tracking (The Tricky One) Annual reviews are dying. Good riddance, they were always kind of useless. You're giving feedback about something that happened nine months ago? AI systems can track goals in real-time, measure against objectives, all that. Sounds great in theory. In practice, we've seen companies get obsessed with metrics that don't actually matter. Time tracking down to the minute, counting commits, measuring "productivity." If your metrics are garbage, AI just gives you garbage faster. We're careful about this in Arheev. Track what matters (goals, deadlines, actual outcomes), ignore the surveillance theater. ## Where AI Actually Helps: Data The best use of AI in HR isn't automation, it's pattern recognition. - **Staffing predictions**: "We'll probably need two more developers in Q3" - **Turnover signals**: "People with this profile tend to leave around the 18-month mark" - **Compensation benchmarks**: Real market data, not guesses - **Workforce scenarios**: "If we hire these roles, here's what happens to budget" This is where HR stops being reactive and starts planning ahead. Not because AI is magic, but because it can crunch numbers faster than humans. ## The Balance Thing Everyone Talks About AI should handle repetitive tasks. Humans should handle the complicated, messy situations that require judgment. In Arheev, we try to automate the obvious stuff: - Standard leave requests that clearly fit policy - Routine data entry and updates - Policy compliance checks - Pattern analysis and reporting But we keep humans in the loop for: - Edge cases and exceptions - Sensitive situations (medical leave, personal issues) - Policy decisions and updates - Anything involving judgment calls One of our clients put it well: "The AI handles the 80% that's straightforward. I focus on the 20% that actually needs me." ## What We're Still Figuring Out Honestly? A lot. We're working on better team coverage predictions. Right now it warns you about gaps, but it could probably suggest better timing for approvals. We want to add smarter policy recommendations, "Here's how other companies handle this", but that requires way more data than we have. And we're trying to make the AI explanations clearer. "Request approved based on previous patterns" isn't helpful if you don't know what those patterns are. ## The Actual Point AI isn't replacing HR teams. It's just removing the tedious parts that shouldn't require human time anyway. Systems like Arheev work best when they handle the routine stuff, checking balances, comparing past decisions, flagging problems, so HR teams can focus on the actual people work. The companies doing this well aren't trying to automate everything. They're using AI for what it's good at (pattern matching, data analysis) and keeping humans for what they're good at (judgment, empathy, dealing with exceptions). Success isn't about having the fanciest AI. It's about figuring out which parts of your HR work actually need automation, and which parts need a human who understands context. We're still learning where that line is. https://arheev.com/en/blog/workplace-distractions-killing-productivity/https://arheev.com/en/blog/workplace-distractions-killing-productivity/Workers lose 720 hours per year to distractions. That's $650 billion in lost productivity. Meetings, phones, and open offices are the main culprits, but the fixes aren't what you'd expect.Wed, 19 Mar 2025 00:00:00 GMT Last month, I talked to an HR manager who was frustrated because her team wasn't getting anything done. Turned out they were spending 15 hours per week in meetings. For a 40-hour work week, that's insane. She cut meetings in half. Productivity jumped. Not exactly rocket science, but apparently nobody had checked their calendars in months. ## The Scale of the Problem 720 hours per year lost to distractions. That's roughly 18 full work weeks. About $650 billion annually across all US businesses, according to research. I don't know how they calculated that, but the point stands: distraction is expensive. Three things cause most of it. ## Meetings (Obviously) Meetings are ineffective 72% of the time. That stat comes from multiple studies, and it tracks with what we hear from clients. The worst part: 78% of people say they can't finish their actual work because of meeting overload. They're spending all day in meetings, then staying late to do the work they're paid for. One company we work with had a simple rule: no meetings on Wednesdays. Productivity increased 70% on those days. Not because people worked harder, because they could actually focus for more than 45 minutes. ### What Actually Works **Meeting-free days**: Block one or two days per week. No exceptions unless the building's on fire. **Default to 25 minutes**: Not 30, not 60. If you can't cover it in 25 minutes, you probably need to break it into smaller topics. **Required agendas**: No agenda, no meeting. Sounds harsh, but it filters out about half of unnecessary meetings. We track meeting load in Arheev now, how many meetings people have per week, how it affects their leave patterns (burned-out people take more sick days). The correlation is obvious. ## Phones and Digital Interruptions We lose about 2.5 hours per day to smartphones. Email, Slack, Teams, whatever, constant notifications pulling attention away. The research calls it "continuous partial attention." You're never fully focused on anything because part of your brain is waiting for the next ping. One-third of workers get interrupted every 15 minutes. Try doing deep work in 15-minute chunks. It doesn't work. ### What People Actually Do About It **Do Not Disturb mode**: Shockingly effective. Just turn off notifications for 2-3 hours. **Pomodoro timing**: Work for 35-45 minutes, then check messages. Repeat. Simple but it works. **Calendar blocking**: Mark "focus time" on your calendar like it's a meeting. Some people respect it. We're seeing more companies add "focus hours" to their policies, official quiet periods where interruptions aren't allowed. Early data suggests it helps, but we don't have enough yet to be sure. ## Open Offices (The Failed Experiment) Remember when everyone thought open offices would improve collaboration? They don't. They reduce satisfaction, privacy, and motivation. Turns out, constant noise makes it hard to think. The hot-desking trend makes it worse, you never know where you'll sit or who'll be next to you. Some days you're next to the quiet analyst, some days you're next to the sales team on calls all day. ### Fixes That Don't Require Rebuilding Your Office **Smart seating**: Group people by work style. Put the quiet-work people together, the collaborative people together. **Quiet zones**: Designate areas where talking isn't allowed. Sounds strict, but people use them. **Headphones policies**: Make it clear that headphones mean "don't interrupt unless urgent." One client reorganized their seating plan based on role and work style. Complaints about noise dropped 60% in a month. Zero construction, just moving desks. ## The Underlying Problem Distractions aren't really the problem, it's that we treat presence like productivity. If your culture values "being busy" over "getting things done," you'll have endless meetings and constant interruptions. Because that's what looks like work. Companies that actually measure output instead of hours tend to have fewer of these problems. Not because they're stricter, but because they stop rewarding the appearance of work. ## What We're Tracking In Arheev, we're starting to see patterns: - Teams with 15+ hours of weekly meetings have higher turnover - Employees who block focus time take fewer sick days - Open office complaints correlate with lower engagement scores Nothing groundbreaking, but it confirms what everyone already knows: constant interruptions make people miserable and less productive. ## The Simple Version Cut unnecessary meetings. Block focus time. Stop treating an open office like it's a feature. Not sexy advice, but it works. We've seen companies implement these changes and get measurable results within weeks. It's not complicated, it's just hard to actually do because it requires changing how your team operates. But if you're losing 18 weeks per year to distractions, it's probably worth trying.