Articles for category: Drive

Loss of Flow

Three years ago, all you could find were blogs and blogs, books, podcasts, everything and anything that would help you achieve Flow. The zen state where you are in full-throttle mode, accomplishing anything and everything. Now, today, we couldn’t care less – AI will do it for me if I don’t get into Flow or someone else on my team. Interrupt me 17 times a day, pile on more and more interactions, as many as you want, because in between I’ll send out a prompt for AI to do some more stuff for me. And what you’ll end up with

2 weeks ago

Greg Thomas

The Perfect Update

It’s simple. It’s to the point. It answers the contextual questions you know are coming. It can be digested quickly and easily, allowing people to ask the real questions. If your update is bloated, uses lots of cool words (I’m looking at you, AI), and requires loads of clarifications, you’re not giving a good update – you’re throwing spaghetti on the wall and hoping something sticks.

Onboarding Quickly is a Skill

On any project, there is a point where adding more people will slow down the project as you seek to onboard them to the work everyone else is doing. It takes time to bring a new person up to speed – sometimes estimated in months when it needs to be a few days or weeks. If you are someone who comes up with a toolbox, learns in advance where the project is at and where the team is having trouble, and knows the tech stack (or is early learning it), your onboarding can drop to those mythical days and low-cost

The Dying Seconds

The dying seconds are the most exciting because they are the finality of what everyone is counting down to. There is no interpretation of what is dying and what are seconds – they are constants reducing in uniform fashion down to 0. At the end, you either feel amazing, sad, perhaps hoodwinked, but if done right, you know that you gave everything to be there, in that moment.

Learning for the Team

When leading a team, there are things you need to learn so your team can have someone to talk to and bounce ideas off of. You don’t need to have all the answers. You are not meant to be an expert. You are meant to be there for your team. You are meant to take that “new” thing you learned, apply everything that you know, and provide an opinion on how they could solve a problem. Sometimes, that’s why you might need to do some learning for your team, even if you’re not the one doing the actual work. Queue