This is the fourth post in a 4-Part series. To get the scoop in why recognition is important, see Part 1. To understand some of the myths about recognition, see Part 2. To learn about the 4-level framework for a recognition program, see Part 3.

The Manager who approached me in Part 1 of this series had used his original question of 'Sal, why do I have to give people recognition for doing their job?' to set me up.

He was persistent and continued, "I don't give people recognition for just doing their jobs. That's what they get paid for."

The conversation went on, and he justified his position of not giving people recognition by saying that he had high standards. Hmmm. High standards, I thought. What does that have to do with it?

In my last two posts, we tackled a few challenges that remote teams face. Part 1 was focused on getting your remote team aligned. Part 2 on building cohesion.

In this post we'll focus on process.

For remote teams to maximize their effectiveness, they need to have disciplined processes in place. Here are some ideas you might consider:

In Part 1 of this series, we discussed some of the challenges of working on remote teams and ideas for getting your remote team aligned. But, to truly be effective, your remote team has to find a way to build cohesion. After all, only when people are working together on the right things can we gain efficiencies.

Here are a few ideas:

Working on teams where some or all team members are remote is becoming the norm rather than the exception. And frankly, having remote team members adds complexity that often times accelerates and amplifies communication breakdowns.

For example,

One of the fastest ways to get a new team member "up to speed" is to make the process intentional.

In many companies, HR plays a key role in "onboarding" new employees. But more must be done at the team level (from senior leadership teams to functional teams) to help new team members get acclimated to the culture and its unwritten rules (that aren't documented in employee handbooks), and to truly understand roles and accountabilities (that aren't usually accurately captured in a position description).

When teams formally spend time orienting new team members it...

With the economy recovering and business picking up, I have been asked the following question several times by clients and potential clients in the past few weeks...

"How do we keep growing and maintain our culture at the same time?"

That is a great question.

Things seemed to be changing quickly. In just a matter of three months, Ben was unexpectedly promoted from Consultant to Manager, Angela was hired and then quit, and now Henry was coming on board.

“So, how’s it going?” Ben's Manager Steve asked.

“Swamped,” Ben replied. “Henry’s started as of last Tuesday and so far seems to be working out pretty well.”

“Great,” Steve responded without knowing that Ben was about to continue.

“It’s nice having another resource around.”

“What?” Steve asked as he looked sharply back at Ben.

One of the challenges that senior leadership teams face is what I call an "interesting duality."

On on hand, a senior leader is often responsible for a functional unit or team within an organization. On the other hand, they are asked to be on a team with other leaders - usually headed by a Director, VP, or CEO.

My clients often ask me,"How big should our team be?"

My answer is typically...it depends.

It depends on the purpose of the team.

The challenge on many teams is a lack of clarity about a team's true purpose. In most cases, team's don't even know that they don't know their purpose.

This is usually a bigger issue at the senior leadership team level, where a CEO, VP, or Director leads a
team of other leaders.