It’s a global world out there, and for many companies, a single office location just doesn’t cut it anymore. But success takes more than setting up desks in a new city. Whether your coworkers are across the world or across the country, there’s a right way and wrong way to approach distributed teams. I’ve rounded up four avoidable mistakes that’ll cost you serious productivity, plus four solutions that helped us performance hack our way to improvement.
Practice makes perfect, right? Well that may not be the case with feedback, even though many of us dish it out all day long.
I learned that the hard way after completing a software demo for a new product. Everything worked like a charm, and I went back to my desk proud of my team’s success. Then, an email with the subject line “Feedback on Demo” caught my eye.
It contained a bold-faced, bulleted list filled with phrases like “this does not yet look great” and “I think we can improve this much more” and “was this intentional?”
I was shocked at first, but ultimately realized I make some of the same mistakes. There’s no shortage of advice out there, but I started jotting down my own list of what it means to give good feedback and came to the conclusion that giving better fetter feedback is easy if you follow these five rules.
If you’ve read this blog more than once, you probably realized we have a lot to say about something we call “performance hacking”. We’ve been doing it long before this blog launched in late July, and the creative workarounds and lessons learned just keep coming. In case you missed an update or two (or you’re just getting started here), we’ve rounded up our best performance hacking posts so far.
Have something you’d love to see our team cover? Let us know in the comments!