When things go wrong, when a requirement has been missed, a bug delayed, a feature bigger than we thought it’s because everyone was working remotely, because we were not in the office.

So the default response is to have everyone get back in the office so we can fix the problem.

But the problem wasn’t an “in the office” problem, it was a communication problem, or a complexity problem, or a new person problem.

It had nothing with people being in or out of the office.

If you’re going to run a remote team, this can’t be your default response when something goes wrong.

We’re past being elbows apart from each other, it’s time to find a better answer.

Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).  I’m also the co-host of the Remotely Prepared podcast.


Write A Comment