Developing Great Teams With Small Investments

Recently I was at a meeting where they brought in various teams from around our Company to showcase the work that they were performing.

Unexpectedly, I recognized someone who I hadn’t worked with or seen in 13 years running one of the booths. We immediately hugged hello and fell back into an old level of comfort with each other, laughing while talking about past stories, catching up on what we’re doing currently and what’s happened over the last few years.

After processing that encounter, I found myself wondering why I seemed to have a better and more authentic connection with a person I hadn’t seen in 13 years and only worked with for a shorter time compared to many others I have worked with either longer periods of time or more recently.

Many pieces play into group dynamics and connections, but looking at the traditional factors didn’t seem to uncover the answer. There had to be more. I really wanted to be able to find the answer so I could try and use that to continue to build great relationships with the teams I work on and people I work with.

That’s when I realized the difference between the strong bonds that had been formed more than 13 years ago versus some of the more tenuous bonds today.

When we were working together years ago, there were many more offsite and not-directly-work-related interactions. Our teams and colleagues spent more time doing things out of the office together and we had more support for little things like team lunches and offsite dinners.

Great relationships build great teams and great teams accomplish great things easier.

Since that’s the case, why do budget cuts first target the very things, like off sites and team meals, that can help build great teams?

So, the next time you hear about a startup or some smaller company hosting happy hours or buying everyone lunch realize that it’s not only a nice perk, it’s a strategic investment in accomplishing great things.

The next time someone asks you for budget for what may seem like fun vs. work related activities, realize it will pay off much more in terms of the work.

Using Urgent for Urgent’s Sake

One particular summer Friday a few years ago, I was fortunate enough to be working from a remote location at a beach town.  I wasn’t supposed to be working that day, but an “urgent” (in quotes because it was someone else’s definition of urgent) project meeting came up that was four hours long that I “had” to attend.  We were told to have the meeting urgently because it was described as a critical meeting to get something designed and moving that HAD to be completed immediately.

Beach towns aren’t always the greatest at WiFi connectivity (thankfully) so I had to ride my bike around town till I found a spot with internet connectivity. I sat on a rickety chair in the town library for the next five hours taking part in the meeting. Thankfully, because I was already at the beach, I could put the meeting out of my mind about ten minutes after it was over as next steps could wait till Monday.

Fast forward to that same weekend, one year later, and as I drove into that beach town again for the first time in the season I saw the library building and immediately had flash backs to that meeting–the meeting that had to get done on that particular day, because we had to get the project moving immediately.

Quickly my flash back turned into a great teaching moment as I realized that while it was now a year later, that particular project had still not started and was still having “urgent” meetings.

I just drove by that library again this season, and now every time I see it it becomes a great lesson in building trust with a team and how taking action to move a project forward is usually better than just talking about doing something.