Managing the Communication Chaos of Collecting Employee Feedback for Remote Workers
December 4th 2018
A few years back, the Weirdly team went 100% remote. Since then, we’ve grown (literally and figuratively), our
needs have changed and we’ve found a kind of equilibrium – a balance between remote and not-remote, that works
(so far) for the job functions and personalities we have onboard. Finding that sweet spot has been tricky at
times and by far the biggest of all the challenges has been around communication.
Internal comms in a remote team gets…noisy. Especially in a fast growing startup, where our lives are a
constant barrage of sprints, pivots, urgent requests, deadline changes and never ending feature tweaks. It’s
really easy for important messages to get lost or overlooked. We’ve had decisions get forgotten (and endlessly
discussed and re-made), leave requests go missing, and “productive conflict” turn in to actual conflict as we
juggle the mess of communication platforms. Creating order from a confusion of emails, internal chat tools,
collaboration apps and hangouts is a real work in progress for us.
But over the past few years of testing, we’ve developed guidelines that work for our crew to keep
communicating efficient and useful.
Step 1. Define the purpose of each tool.
Seems obvious, but think about how many different ways and places you communicate with your colleagues – in
the lunch-room, at your desks, over email, in a meeting room, during your electric-bike club meetup. In the
real world, our comms move organically from place to place – just like in the digital world – but there are
safety nets. We can read body language to spot misinterpretation before it becomes a problem, other people can
pop up with a helpful “Hey looks like you and Dale were getting some good stuff down on the whiteboard earlier
– any decisions I need to know about?”.
In a remote team, we don’t always have these safety nets and the number of places we can meet and chat and
collaborate are almost infinite. It gets very messy, very fast.
We found putting simple guidelines in place that broadly describe the kinds of conversation that should happen
in each place has helped heaps. Of course, there’s a bit of flexibility around this, but as long as everyone’s
aware of comms expectations, we’ve found it works pretty well.
Here are a few of our favourites:
Slack (public channels) – this is our most casual place. It’s for talking about any work in progress that the
whole team needs to know about (new sales, key feature updates, user issues) and giving heads-up around
decisions or actions being taken somewhere else. It’s also our place for relationship and culture building –
#chuffies, jokes, pictures of dogs – the usual “office banter”.
DirectSuggest – Getting suggestions from the employees of your business is something that has been found
invaluable. DirectSuggest connects your decision makers directly to your employees and makes it simple for an
employee to make suggestions with the assurance that they arrive where they are needed.
Slack (DM’s and private channels) – these are for more in-depth discussions – information that isn’t critical
or interesting for anyone else to weigh in on. This keeps the noise down in the public channels and means we’re
not all wading through thousands of notifications. It also give people the chance to get down REAL deep into
detail without someone (ok, me) jumping in every 5mins to ask what a “dimensionality reduction algorithm” is.
Video hangouts (Google and Slack) – nothing beats face-to-face sometimes and this gets us pretty close to the
real deal. Team discussions, standups and meetings are done using video – with SnapCam filters optional.
Email – for confirming decisions, requesting leave or any formal admin stuff.
Jira – task allocation and briefing. This is also where very technical decisions are recorded like, “Hey Malcolm, you’re good to go ahead and design a novel fuzzy clustering algorithm that operates on relational input data as discussed”.
Google docs – for collaborating on content, spreadsheets, roadmapping – anything that you’d traditionally do around a whiteboard or a piece of paper.
Step 2. Put basic rules in place for each tool
This is a deceptively tricky one. Communication is a fluid, evolving thing and the tools people feel most
comfortable using change over time. New apps get introduced, new people join the team, the types of challenges
change and people get closer. Still, we’ve found there are some universal laws that really helped create order
in the comms chaos.
Formalise decisions: Any decisions made in chat, collab or messaging tools get formalised in
email. This means they’re clearly dated and easily searchable. It also allows everyone to double-check
they’re on the same page with the detail of each decision.
Pick up the phone: Working through complicated issues is a recipe for frustration. So we
implemented “two strikes then get out (of slack)” rule. Basically, if people have gone back and forth
on the same issue more than twice, they step away from the text-chat and pick up the phone or move to
a video call.
All leave requests get sent through on email: We originally set up a #leave channel in our team slack
that collected these, but found they were too easily overlooked or forgotten. Also since our admin
person is the one processing these requests, she gets to dictate the format they arrive in and she
loves her inbox!
Protect the outages channel: Alerts and notifications related to critical app stability all go
through to one Slack channel. Any discussion related to those issues happen in that channel but
absolutely no other chat happens there. It’s the product team’s most fiercely adhered to rule – it
keeps a sense of urgency over any notifications you see coming from that channel.
More heads-ups are better than none: Anytime anyone makes a change to a spreadsheet, adds a comment to
a google doc or drops a new resource in dropbox, we chuck a heads-up in Slack. Usually, this is a DM
to the person or people concerned, but sometimes it’s a more general announcement to the team.
Use @here or @channel alerts rarely: Another self explanatory Slack rule – we all get enough
notifications without having a “@here” message go out everytime someone loses their EarPods.
This is all a work in progress of course. People have a way of ignoring communication rules that don’t feel
natural to them, so we’re regularly checking and adjusting as our remote teams grow. That’s our own golden rule
we’ve discovered over the past 4 years: Work with people’s natural behaviour, not against it.
This article was originally published at Weirdly Blog
Keren Phillips (Co-founder of Weirdly)
Co-founder of Weirdly, a customisable screening tool that helps in-house recruiters find
candidates who’ll drive culture forward (while providing a world-leading candidate experience). In the Weirdly
team, she heads up marketing and vision. Which really means she spends all day digging through trend research,
telling people about the awesome work Weirdly does with their customers and ATS partners, and dreaming about a
day when HR, Talent Acquisition and Marketing will work together in perfect, harmonious unity.