Blog | David O'Grady Coaching

New Team Not Working? What the First Six Weeks Decide | David O'Grady

Written by David O'Grady | Sep 29, 2026, 6:33:13 AM

You put the team together carefully. Good people, a sensible mix of experience, a mandate everyone nodded along to. Six weeks in, the meetings are polite, everybody's busy, and somehow nothing important has been decided yet.

Key takeaways

  • Real project teams lock in their way of working in the first meeting or two, not through neat developmental stages.
  • Trust between new colleagues grows fastest in the first month, then levels off, according to an Irish study that tracked 193 new joiners weekly.
  • The best-evidenced team habit is the structured debrief: roughly 20 to 25 per cent better performance across a meta-analysis of 46 samples.
  • An effective team launch covers two halves: how we'll work together and how we'll deliver. Either half alone is not enough.
  • Six weeks in is a checkpoint, not a verdict. A deliberate launch conversation resets the pattern, even late.

If that's your team right now, you're far from the only one. When a leader or an HR director gets in touch about a team, this is usually the pattern underneath. And there's often a quiet worry attached: that it must be something they did, or failed to do.

To be honest with you, it almost never is. It's what happens when a team is left to form by accident rather than on purpose. And the research on team formation is clearer, and far more practical, than most of the advice leaders are given.

What does a stalled new team actually look like?

It looks polite, busy and stuck: meetings everyone attends, decisions nobody quite makes. What I've noticed across newly formed teams is how consistent the six-week mark is. The early energy of introductions has worn off. People have retreated into the work they already know how to do. Disagreements get parked rather than aired. Two capable people are quietly circling the same territory, and everyone can feel it, and nobody says it.

None of this looks like a crisis. That's exactly why it survives. A struggling team gets attention. A polite one gets left alone.

The standard advice at this point is patience. Teams go through stages, people say. Forming, storming, norming, performing. Give it time.

Is "forming, storming, norming" actually true?

Not in the way most people assume: the model was never derived from workplace teams. Bruce Tuckman's stages model is probably the most quoted idea in team development, but his 1965 paper in Psychological Bulletin was a review of 50 existing studies, and 26 of them were therapy groups. Tuckman himself was careful about this: he described the underlying data as highly anecdotal and warned that the model's generality "must be limited".

That doesn't make the model useless. It gives teams a shared vocabulary, and vocabulary matters. But it was never a law of nature. Later research on real project teams tells a rather different story about how teams actually develop.

Which brings us to the finding I most wish every leader of a new team knew.

When does a new team set its pattern?

In the first meeting, according to the best field research we have, and mostly without anyone deciding it. In a study I keep coming back to, Connie Gersick (1988, Academy of Management Journal) tracked eight real project teams from their first meeting to their deadline. None of them moved through tidy stages. Instead, each team locked in its way of working almost immediately, in the first meeting, and then largely stayed on that track until roughly the midpoint of its own timeline (halfway between its first meeting and its deadline, whenever that fell), when a genuine burst of change became possible.

Two things follow from that. The first meeting isn't a warm-up. It's where the team's habits get set, mostly without anyone deciding them. And if you miss it, your next natural opening for real change is a long way down the road.

From my own experience

I've sat on the other side of this. In a previous corporate role, a VP whose remit had just expanded opened her first meeting with our team by sharing her vision, then made it clear there was no room for disagreement: we were either on the bus or we weren't.

The disbelief never made it into the room. It went straight to the Slack backchannel. One meeting, and the rules on how honest anyone was going to be had been set.

There's a similar early window for trust. An Irish study is my favourite evidence here: van der Werff and Buckley (2017, Journal of Management) followed 193 new joiners at the Irish practice of a large professional services firm through their first three months. Willingness to rely on colleagues, and to open up to them, grew fastest in the first month and then levelled off. And people were reading each other's competence and warmth from the moment they met, not from month three.

8

real project teams tracked from first meeting to deadline

193

new joiners in Ireland: trust grew fastest in month one

20–25%

better performance from structured debriefs (46 samples)

So the comfortable idea that relationships will develop naturally, given time, has it backwards. The steepest part of the curve is at the start.

Time doesn't build a team. Early structure does.

What actually works in a team's first six weeks?

Two deliberate conversations and one habit. Where they happen matters far less than whether they happen, and how well they're run. They're conversations, held early, on purpose.

Mathieu and Rapp (2009, Journal of Applied Psychology) tracked 32 teams competing in a business strategy simulation over multiple performance periods. The teams that sustained the highest performance had invested their launch in two things, not one: a quality team charter (how we'll work together) and clear performance strategies (how we'll actually deliver). Either on its own wasn't enough. In fairness, these were MBA teams in a simulation rather than corporate teams, but the design lesson holds. A launch that only covers introductions and ground rules is doing half the job.

Then there's the habit with the strongest evidence I know of in team research. Tannenbaum and Cerasoli (2013, Human Factors) meta-analysed 46 samples of debriefs, those short structured reviews of what just happened, and found that properly conducted debriefs improved performance by around 20 to 25 per cent over comparison groups. It isn't a one-off event. It's a short, regular conversation about what worked, what didn't and what to change, and the evidence for it is stronger than for almost anything else in team research.

A practical tool

The first three conversations a new team should have

If I could give a newly formed team just three meetings' worth of structure, it would be these.

1

How we'll work together. Roles and who owns what. How decisions get made, and by whom. How we disagree (out loud, and early). What "done" looks like. This is the charter conversation, and the research suggests its quality matters far more than the document it produces.

2

How we'll deliver. What this team exists to produce, what good looks like in six months, and the first concrete plan for getting there. This is the half most launches skip.

3

How we'll learn. Agree the debrief rhythm now: a short, structured review after every significant piece of work. Twenty minutes, three questions, no blame. Build it in from week one, before there's anything to be defensive about.

A leader can run all three. For the first one, though, a skilled facilitator and a behavioural assessment such as Everything DiSC® or Insights Discovery® will usually get a team further, faster. They give everyone a shared, non-judgemental language for how each person prefers to work, which is exactly what “how we'll work together” needs. A well-run off-site is often the best place to have that conversation properly.

Is six weeks too late to fix it?

No. Six weeks is a checkpoint, not a verdict. If your team is past its first meeting, past its first month, even well past the six-week mark, the moment isn't gone. Gersick's midpoint finding cuts the other way too. Each of her teams became genuinely open to changing how it worked at roughly the halfway point of its own timeline. For a team with a six-month mandate, that's around month three. And in my experience, the reset can start sooner, the moment someone names what everyone's already feeling. It becomes a lovely conversation to have, once somebody starts it.

From a client room

An HR lead asked me to facilitate a reset for a team of experienced professionals who had been working together for six months. During the session it became clear that trust between members simply wasn't there. Some wanted meetings to be direct and focused on the task. Others led with care for the people involved. Each side had been quietly reading the other's style as the problem. Insights Discovery gave them a shared, non-judgemental language for those differences.

By the end of the half day, the whole team could see the value in both lenses, and they built both into their new team charter and the way they make decisions. A lot of passive resentment came to the surface and was finally dealt with.

A new team that isn't working yet is not a verdict on the leader. And the first six weeks don't decide whether a team will succeed. That part belongs to the team. What those weeks decide is how much friction the team carries into everything it does next.

Three-minute check

Where does your new team actually stand?

I built the New Team Scorecard for exactly this moment. It takes about three minutes, and you receive an insightful report on where your team stands.

Take the New Team Scorecard

And if this way of looking at teams is useful, I write a monthly letter for HR and people leaders in the same spirit. One pattern from real work, one practical tip, one honest use of AI. Sign up for the HR as Coach letter.

Questions I'm often asked about new teams

How long should a new team take to gel?

Longer than the first week and less time than most teams are given. The research points to the very start: working patterns tend to set in the first meeting, and trust between new colleagues grows fastest in the first month. A team can feel settled within a month if the forming was deliberate, or still be circling at six months if it wasn't.

Is an off-site a good way to reset a new team?

It can be one of the best, if it's built around the right conversations. The evidence favours two questions: how will we work together, and how exactly will we deliver. A facilitated off-site, often with a behavioural assessment such as Everything DiSC or Insights Discovery, gives a team the time and a shared language to answer both properly. An off-site without those two answers written down tends to produce the same meeting the following Monday.

What is a team launch conversation?

A structured session, usually 90 minutes to half a day, where a new team agrees roles, decision rights, ways of working and its first concrete delivery plan. In the research, launch quality on both halves (teamwork and taskwork) is what separated the consistently high-performing teams.

Is it too late if the team formed months ago?

Rarely. Teams become genuinely open to change around the midpoint of their own timeline, and naming the stuck pattern out loud can open that window earlier. The reset conversation works late; it just works better early.

About the author

David O'Grady

David O'Grady, executive and team coach in Ireland, helps new teams form faster. He is Ireland's only dual Everything DiSC® and Insights Discovery® Authorised Partner, Chartered MCIPD, with an MSc in Work and Organisational Behaviour from Kemmy Business School, University of Limerick, and more than 20 years in HR and L&D.