May 21, 2019
If you don’t have one, you need one. It’s a set of words, a song, a video, a poem, whatever you want it to be. But it brings you back from the brink, back from exhaustion, back from fear, picks you up when you are down, gives you the kick to get started. When everyone else has given you up, it’s the one little thing that forces you back into the driver seat to do what we’ve been needing you to do since Day One. Take the Initiative and Lead.
May 20, 2019
Yes, not Complaints, but Complains. Can you go a whole day without complaining? Are you complaining day in and day out about the same thing? Are you willing to do anything about it or just keep complaining about it? If you want to keep complaining about it, no need to share with everyone, you made the choice, find a room, vent away. But if you want to do something about it, start tracking what it is and what you can do to erase it from your daily view. Who wants to waste their time complaining about the same thing over
May 16, 2019
What sets you apart from everyone else? What drives you? What gets you up in the morning? What will you stand for? What will you lead? Who will you lead? What matters most? What matters least? Where do you stand when the chips are down? These are some, there are more, but what matters is that you ask them, write down the answers and be what defines you.
May 15, 2019
Humour. Appreciation. Comfort. Understanding. Consideration. Wrapped up into one word, Empathy. If the goal of your chat bot is to collect information to route to an agent, save yourself the time and money and add a front-end form to your chat application collecting this data and then route that customer to an agent. Bots aren’t time stallers, waiting for an agent to become available, they are collectors of information. But if your customers are looking for any of the above based on your business model and how you project yourself to interact with them, then they are probably not for
May 14, 2019
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
