The No Strings Attached Apple Crisp

apple-crisp

A few months ago I made apple crisp for a team that I serve on at work. The apple crisp was partly to celebrate our accomplishment, partly because I love a good apple crisp, and partly because they totally guilted me into making it. (I made one for another team and this team got jealous, but that is another story.)

We consumed most of that crisp, with many having two or three helpings.

Some apple crisp remained.

In order to be able to clean the baking pan, I called another co-worker and offered the remaining apple crisp.

“Hey, I made this apple crisp, it is really good. Do you want some?”

Long pause…

“I guess so…but what do you need?”

I was a little stunned at the reply. I had to regroup.

“I don’t need anything, you see I made this for this particular team, and we had extra and I thought of you.”

Another long pause…

“Ok, but seriously, do you need something from me?”

Eventually the crisp was delivered. A cautious first bite, followed by a second and a third. As I left their office, the suspicion remained.

A few weeks later, I stopped by that office again (not because I needed anything). It was then that the real story came out.

At a company prior to this, if someone did something for you, it was not simply a gesture of goodwill. There were strings attached. Receiving from others created an obligation for you.

Nothing was free. Everything came with a price.

Maybe what we all need is a little more no strings attached apple crisp.

Try it out. Do something for others without expecting something in return. It may be awkward at first because of the expectation of strings from those around you.

Let us all know how it goes. Next time I may try cookies.

How Do You Define Teamwork?

Teamwork.  There is a seemingly endless list of how to define it, thousands of books written about it, and the notion that we should all strive to obtain it.  Teamwork has been rattling around in my head lately, and I was trying to remember a defining moment for any team where I was a member.  Nothing was coming to mind until I met recently with a member of this team for breakfast.

This particular team had been through some rough times together, but also celebrated well during successes.  The defining moment that I remember was during a meeting where we had been instructed to reduce our budget.  It wasn’t just a little reduction, the reduction was large enough that it would cause everyone in the room to take a hit.  I had instructed each of them to bring a list of what was important that needed to remain, and a list of what could be reduced.

One by one, each member of this team shared their list.  The items on the lists were important things that would have a significant impact on each person’s part of the operation, their ability to provide the right level of service.  After all the lists were read, it became quiet.  Part of me expected the real battle to begin, and each person around that table would start lobbying about why their department should be retained, and someone else should take the cut.

It was at this very moment that I witnessed teamwork, and what I heard had and still has an impact on me.

“After listening to the group, their lists seem more important to the overall operation.  I think I can reduce a little more.”

“I can take the hit, let’s make sure that other department has what it needs this year.”

“I don’t know how I am going to explain this to my employees, but I am withdrawing my list of needs, the other lists just seem more pressing.”

One by one, every member of that team saw the overall organization and operation as more important than their particular department, silo, or fiefdom.  Each member of that team knew that the only “win” was ensuring that the organization “won” not whether or not it was a “win” for them individually.

How should we define teamwork?  Maybe the definition is simple.  Teamwork is when everyone that is working together can look beyond themselves, see the larger picture, and “take the hit” for others.