What Group Projects Taught Us… and What They Didn’t

I was coaching a leader recently when she laughed and said, “This feels like another school group project."

I immediately knew what she meant!

One person was carrying the team. Deadlines were slipping. The person who cared the most had become responsible for keeping everything on track while others contributed far less than they should have.

We've all experienced some version of that dynamic.

For years, I thought the lesson from group projects was that some people simply didn't pull their weight. Looking back after coaching hundreds of coaching calls, I think they taught us something much more important.

They required us to work together, set expectations, navigate conflict, and… hold one another accountable. The thing is, almost none of us were ever taught how to do those things well. We were simply expected to figure it out… and those expectations don't change when you get to the real world.

We Were Assigned the Project. We Were Never Taught How to Lead It.

Get your Trapper Keepers ready; I’m going to transport you back to middle school, high school or even college for a moment.

You were assigned a group, given a topic, handed a due date, then told to “work together.”

But did anyone ever teach you how to:

• Have a difficult conversation when someone missed a deadline?

• Clarify expectations before the work started?

• Address conflict before resentment built?

• Hold a peer accountable without damaging the relationship?

• Reset priorities when circumstances changed?

  
  

Probably not.

We learned the basics of algebra, chemistry, history, and grammar, but one of the most important life skills, navigating accountability with another human being, was never part of the curriculum.

Then We Became Managers

Put away the gel pens (or not!) and let’s fast forward ten years.

The classroom became a conference room, and the group project with fellow students became a work project with fellow coworkers. Only this time, the outcome affected clients, budgets, timelines, and the people sitting around you. Missing a deadline didn't mean a lower grade. It meant someone else had to pick up the slack, a customer had to wait, or an important opportunity slipped by.

The stakes changed, but our approach often didn't.

Many leaders still assume everyone shares the same understanding of the project and its priorities. When things fall behind, the conversation quickly turns to accountability. More often than not, the real issue started much earlier. Expectations were never fully aligned, priorities were interpreted differently, and no one realized it until the work was already off track.

The Project Management Institute has found that ineffective communication is one of the biggest contributors to project failure, with more than half of project failure risk tied to poor communication. That points to a much different conclusion than many leaders reach. 

Accountability matters, but clarity comes before accountability.

Crystal Balls and Rubber Balls

During that same coaching conversation, my client used the familiar crystal ball and rubber ball analogy to describe her team’s work.

"Some responsibilities are crystal balls. If someone drops them, they shatter. The problem is, I think my team sees those same responsibilities as rubber balls."

A project deadline might feel flexible to one team member because pushing it back a day doesn't seem like a big deal. To them, that ball is rubber. It will bounce. Everyone will be fine.

To the manager, that same ball is crystal. Missing it could delay a client launch, create extra work for another department, damage trust with a customer, or push back revenue. Once that ball hits the floor, the cleanup is difficult, and the project is never quite the same.

Everyone is looking at the same responsibility; they're just seeing different consequences.

Leaders often assume their teams know which priorities can't slip. More often than not, those priorities have never been discussed explicitly. People make decisions based on the information they have, and when that understanding isn't shared, accountability starts to break down before the work even begins.

Accountability Must Be Built Before It's Needed

By the time a leader is having an accountability conversation, they're often managing the consequences of a problem instead of preventing one.

The strongest leaders create accountability long before performance slips. They use the beginning of a project to align expectations, discuss tradeoffs, explain why priorities matter, and make sure the team understands the impact of their work on everyone around them.

Those conversations don't eliminate every challenge, but they give people a shared foundation for making better decisions when priorities compete and circumstances change.

The Accountability Test

Most of us still cringe when someone mentions a group project.

We don't remember the high school assignments nearly as much as we remember the frustration of feeling like everyone was working from a different set of priorities. Years later, many leaders are facing that same challenge.

So here's the first question I'd encourage every leader to ask themselves:

What are the crystal balls in my organization?

That question is usually the easy one. The second question might be a wake-up call.

Would my team call those same responsibilities crystal balls... or rubber balls?

The answer says a great deal about how well your team understands what matters most. When leaders create that shared understanding, accountability becomes far easier because people are making decisions from the same perspective.

-

If your organization is ready to strengthen accountability through greater clarity and alignment, contact us today. Learn how E Leader Experience helps organizations build leaders who create clarity, strengthen accountability, and keep teams aligned long before projects start to go off track.