Range - Built for Distributed Teams
 

[Hacker Noon Hacks for Slack]

Turbo-charge your Distributed Team's Productivity with 3 Slack Hacks...

 
...and 11 Hacker Noon stories on Enhancing your Team's Productivity

 

 


One of the advantages of Slack is that when I tap on the app icon, it's just the people at my company and just the people I work with.


- Stewart Butterfield (co-founder Flickr & Slack)


Teams slack despite Slack

Distributed teams in tech are now a norm than the exception. But, the gains made in terms of flexible work hours and cheaper infrastructure costs face a trade-off due to poorer intra-team communication and unclear responsibilities.

This usually leads to heated discussions and passive-aggressive behavior which is even harder to resolve when all of you are not dining in the same cafeteria.


What are Slack Hacks and Why Should You Care?

From something as small as creating an off-topic channel for celebrating haikus made by team members to boost intra-team camaraderie, to, designing intricate Slack-Zapier-Google Sheets-Asana integration that automates multiple field entries across apps, everything is a Slack Hack.

This is the reason why we love Slack. The fact that there are tons of apps that are built upon the Slack interface to provide additional features. For example, the Stripe-integration app creates a new slack channel to send notifications as soon as a payment is received.


What Slack Hacks do Hackers at Hacker Noon use?

1. Use the Star to Create To-Do Lists - If you're a critical resource, your slack chimes every two seconds. As you start to get inundated with action items, it is natural to miss a few in the tens of channels. To overcome this, simply start adding important action items into your starred items list. This makes a hardly used feature into an easily accessible powerful to-do list sourced from all your channels.

At Hacker Noon, after we launched 2.0 (our inhouse developed CMS from scratch), our devs started getting inundated with change requests, feature requests, bug-fix requests, and a boatload of feedback. So, our devs started starring messages to create to-do lists and then made it trackable by migrating it to Asana via this Zap by Zapier.

2. Integrate Twitter to stay on top of Social Media Mentions - Modern companies are all over social media. Tracking mentions can be automated by connecting the company Twitter handle to Slack. This way, team members can engage customers/fans better by being able to notice and reply faster.

At Hacker Noon, the editors were at the frontlines during the migration process and bore the brunt of the barrage of communications sent over by our 8000+ writers and 2MM+ readers. While email is easier to manage, tweets were harder to be on top of due to the need to search for ‘hackernoon’ and answering messages one by one by scrolling. Twitter for Slack helped us collate all company related tweets on Slack and respond to them from within Slack itself.

 

3. Optimize Standups for Asynchronous Meetings - Standups have three components - what you did yesterday, what are you doing today, and what are the blockers you're facing. Unfortunately, doing your standup in Slack means that it’s hard to get context and information gets lost easily.

At Hacker Noon, we’re distributed all over the world. When it is noon for David and Linh in Colorado, it is 9PM for Arthur in Ukraine. So, we use Range to organize our standups without overwhelming the team. Range helped the Hacker Noon team quickly look up teammates’ availabilities and responsibilities and add items to their queues. We spoke to the good folks at Range and they’re giving away FREE 3 Month Trial Subscription to all Hacker Noon newsletter subscribers. Claim it here - FREE.

If you’re a part of a Distributed Team, you can share your story on Hacker Noon too. Simply click here to create an account, and share how you integrated team requirements and smashed constraints with technological innovation.

Maybe you'll be featured here next week.

Without further distractions, let's get to the best Hacker Noon stories on enhancing productivity of distributed teams, curated for your pleasure.

8 Mistakes We Made in our Company’s First 8 Years


This might sound a bit controversial. When we started out we were bootstrapped, so that forced us to move fast on product and make sales. I think that’s smart and fine.

Once we got something working, we gained breathing room on our runway, but instead of taking that room and investing deeper on product concepts, we spent further on revenue. We focused on driving sales and unit economics. Looking back, we were too early for that. Should have listened.

By focusing on bigger contracts, we needed a bigger scaled product. Then, pushing further, we were selling multi-year contracts to increase our LTV.

The problem was, it would then take us two to three years to truly find out if our product could retain a large customer. It took us years to truly find out if we did a good job.

 

Read full article or {TWEET THIS} by Brennan McEachran
 

How I Screwed up Myself Building my Dream Startup


Now, don’t get me wrong. I still believe that your passion is the number one ingredient for you to really start and grow a successful business. But there’s so much more you need to be prepared for before getting started.

I’ve been in the startup industry for so many years now, as a coach, accelerator director, program manager and finally a founder myself.

 I’ve heard it all, all the beautiful talks and all the challenges you might encounter, how hard it is…etc. And I always thought as long as I love what I do, I will pull through.

Read full article or {TWEET THIS} by Emna

 

Can You Resist Slack?


Indeed, when a workplace software such as e.g., Slack, being sold as the miracle tool of team productivity, glues employees on its interface giving them the illusion of free choice and interconnected ‘simplicity’, it should normally be difficult for an organization to adopt a solution that gradually becomes a continuous, dehumanized, hyperconnected coffee break that makes them unable to focus on their goals by pushing them to immediacy.

As early as 1995, XEROX PARC introduced in its guidelines for “Calm Technology” that technology “should require the smallest possible amount of attention” and communicate information “without taking the wearer out of their environment or task.” Or that technology “should respect social norms” not to “cause stress on” in particular. 24 years later and in today’s context, this hits home more than ever.

Read full article or {TWEET THIS} by Jeremy Leon

 

Episode 27: The Ways You Could be a Better Teammate


I can admit this for myself and claim for many, that we all have been guilty for at least one of the things below:

  • You’ve let your emotions of stress, worry, frustration, sadness lash out to the team as you’re struggling to keep up somehow.
     
  • You’ve gone a bit ahead, or not taken the time to help your team mates. This means you are not considered your team mates who are struggling
     
  • You’ve let yourself get impatient and either lashed out or done something aside from the team
     
  • Because your group is behind schedule, you have found something small to blame that isn’t the only reason, or perhaps is never the case (I.e your team-mate is ill or has a personal issue and is not there for one day)


Read full article or {TWEET THISby Dania Mah
 

When Doing Your Best Is The Worst Option


For me, all of agile boils down to the following 4 points -

  1. Work in Small Batches
  2. Limit Work in Progress
  3. Get Feedback
  4. Do Not Sabotage Your Ability to Do the First Three Points

The unfortunate part is that everything we are taught, everything that we have learned to do in the name of individual excellence runs counter to all of these. When it comes to working in an agile manner, doing your best(in the traditional sense of individual excellence) is the worst thing you can do.

Read full article or {TWEET THIS} by
Prateek Singh
 

[Insights for CEOs] Starting and Managing A Remote-first and Multicultural-first Company


In a remote-first company, communication is paramount. We often hear that engineering-focused companies are better candidates for remote working. I'm not sure; have you considered, for instance, if:

  • Communication is an engineer’s strongest suit?
  • Writing is an engineer’s best skill?
Communication, for us, meant setting up processes and tools, then finally, writing down and recording everything! Add to that the fact that 70% of our team has to do all of this in a foreign language and we have a serious challenge to tackle 💪.

We've set up some processes and rituals to help communication flow well between everyone and to make sure we can all give our best.


Read full article or {TWEET THIS} by Guillaume Montard
 

10 Life Lessons from 8 Startups


Secondly, some attention is totally worthless.

My first hand experience: We did a viral video together with two Youtube influencers, which now has over 7M views on Youtube. I think only in the first week, it had like 1M views and brought us hundreds of thousands of visitors. Do you know how many conversions we have actually made? De nada. Jackshit. Zero. I mean ok, some people did convert, but none of them became loyal customers. And it had absolutely zero impact on the business.

We wanted to charge a % commission (on rent) instead of a regular SaaS fee. Now, this looks fantastic in a pitch deck. But in reality every commission business which has some real life component (except a very few cases) will have a pretty unscalable operational part. And this part will cost you a fortune to scale.


Read full article or {TWEET THIS} by Dominik Vacikar
 

Why I Chose to Build a Fully Remote Company Before it Was Cool


We had to be very intentional about how we communicated, and we experimented with it constantly. In the early days, we found that talking things through live via Skype worked better than simply emailing questions or deliverables.

We’d sometimes augment communication between calls with screen recordings, and even developed our own screencasting tool to make it easier. For quick questions, we used Skype instant messaging. The communication flowed constantly, easily, and deliberately. It had to for people to stay unblocked and productive.

Today, we’re heavy users of Slack messaging, Zoom video conferencing, and our own screencasting (Peek) and feedback (Articulate Review) apps.


Read full article or {TWEET THIS} by Adam Schwartz
 

Growth Hacking for Remote and International Developers – Part 1


That was one major difference being a virtual team and then the other part dealing with non-US developers. I’ve had some experience with that, but more tangentially, like I said. I worked with a couple company positions. I worked for a mobile software development company and it was on the larger side for me.

It was probably about 600-700 people when I joined, it did recently go public. They were still a pretty young company but kind of growing quickly. Engineering team was probably 20-30 people big when I joined at their offices that I was at, but it turns out that we actually had a whole offshore development team in India and actually growing that but for me it was a bit of black box.

It was always a mystery.


Read full article or {TWEET THIS} by mobycast
 

Keeping Our Ducks Aligned With Slack

 

A lot of people view Slack as a distraction that just gets in the way of real work from getting done. It certainly can have that effect if you aren't careful. Slack can also be a tool that reinforces silos and discourages collaboration.

Slack can also be an invaluable tool that helps people work together to bring ideas to life. It's just not possible to get the same level of communication through emails, meetings, and other traditional means.

A little organization along with a little discipline can go a long way.


Read full article or {TWEET THIS} by Dane Lyons
 

Moving Everybody into the Bay Area Doesn’t Scale


“Moving everybody into the Bay Area doesn’t scale. The Bay Area is way too expensive, and taxes are high. It’s not even the nicest quality of living for what you’re paying, and people have lives and families in other countries and other parts of the country.

“The idea of remote work as a separate category will be gone within a decade or two. The tools still aren’t quite good enough, but they’re getting better by the day.

“We’re going to see an era of everyone employing remote tech workers, and it’s not too far away. In fact, now’s the time to prepare for it. But I think in the meantime, the companies that are going to do the best job at it are the ones that are remote companies or that have divisions internally that are remote.

It’s going to be done through lengthy trials. It’s going to be done through new forms of evaluating whether someone can work remotely effectively.”

Read full article or {TWEET THIS} by 
Angel List
 

Have a great weekend,
Utsav from Hacker Noon 👨‍💻
Range - Built for Distributed Teams
 
Want to customise what kind of emails you get from us? 

Manage your topic preferences
Twitter
Facebook
Website
Copyright © 2019 Hacker Noon. All rights reserved.

Our mailing address is:
PO Box 2206, Edwards CO, 81632, U.S.A.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.
Twitter
Facebook
Website