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.
6 min read
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.
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.
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.
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.
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.
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.
"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.
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.
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.
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.
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.
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.
Take the first step toward better human resource management