The 7 conditions
Every person experiences work differently. But when we bring those perspectives together, we can begin to see patterns in how the team works. Momentum Quest focuses on these team-level patterns: how people experience communication, workload, trust, recognition, and the other conditions shaping their work together.
The Momentum Scan looks at each condition from three perspectives: your own experience, how the team works, and the team’s environment.
Our seven conditions give teams a practical way to explore those patterns and decide what they want to improve.
Each condition shapes the others. Choose one to read more.
Each teammate brings a different perspective. The Momentum Scan brings those perspectives together to reveal team-level patterns, not to assess individual employees.
We’re interested in what the team’s responses collectively tell us about how work happens. That’s where the conversation begins.
Decades of research on team effectiveness have shown that team performance depends on more than the people involved.
Researchers such as Richard Hackman and Ruth Wageman have studied the conditions that help teams succeed. Google’s Project Aristotle also highlighted the importance of psychological safety, dependability and clarity in effective teamwork.
Momentum Quest draws on these insights to help teams explore seven practical conditions in their own work environment.
Google’s Project Aristotle research ↗A note on method: our seven conditions are a practical framework informed by research, not a scientifically validated model of team effectiveness.
Each condition below comes with an everyday example. Examples, not diagnoses: the same signal can come from different conditions, and your team decides what it means.
Condition 1 of 7
How clear work feels.
People understand priorities, roles and how work gets done.
When Organization is working well, people know what matters, where to find what they need and how work moves from one person to another.
When it’s stretched, priorities can compete, information gets scattered, ownership becomes unclear and people spend energy figuring out the work around the work.
Three perspectives
Sounds familiar?
“Important information keeps living in DMs.”
A Trail to explore: Smooth the Path
All seven conditions ↑Condition 2 of 7
How sustainable work feels.
Work doesn’t stop affecting us when the workday ends. Workload, pace, expectations, recovery time, and boundaries between work and personal life all influence how sustainable work feels.
Some of these pressures come from outside the team. Others are shaped by everyday habits, such as when people send requests, how they share urgent work, and whether teammates feel able to disconnect.
When it’s stretched, urgent beats important, work spills into evenings and people run on fumes until the next break.
Three perspectives
Sounds familiar?
“New work keeps getting added, but nothing seems to come off the team’s plate.”
A Trail to explore: Make Room
All seven conditions ↑Condition 3 of 7
How safe honesty feels.
People can say what they see without worrying about the consequences.
When Openness is working well, problems surface early, disagreement is useful and people say the hard thing in the room.
When it’s stretched, people agree in meetings and disagree afterward, and problems arrive late, already bigger.
Three perspectives
Sounds familiar?
“People talk about a problem after the meeting, but not during it.”
A Trail to explore: Say What’s Unsaid
All seven conditions ↑Condition 4 of 7
How reliable teamwork feels.
People can count on each other, and decisions match what the team says it values.
When Trust is working well, people ask for help early, hand work over without worry and believe what they hear.
When it’s stretched, people double-check each other, hold on to work and wait until they’re stuck before asking.
Three perspectives
Sounds familiar?
“People hesitate to ask for help until they’re already stuck.”
A Trail to explore: Ask for Help
All seven conditions ↑Condition 5 of 7
How shared effort feels.
Responsibilities, opportunities and workload are shared in a way that feels fair.
When Fairness is working well, the load moves around the team and the good opportunities do too.
When it’s stretched, the same few people absorb the extra work, and resentment builds quietly.
Three perspectives
Sounds familiar?
“The same people keep picking up the extra work.”
A Trail to explore: Share the Load
All seven conditions ↑Condition 6 of 7
How valued people feel.
Effort and contribution get noticed and returned.
When Recognition is working well, people see each other’s work, including the quiet work that keeps things running.
When it’s stretched, results get noticed but the effort behind them doesn’t, and people start doing less of the invisible work.
Three perspectives
Sounds familiar?
“Important work gets done, but much of the effort behind it goes unseen.”
A Trail to explore: What Went Unseen
All seven conditions ↑Condition 7 of 7
How connected we feel.
People feel part of one team, not people working alone.
When Connection is working well, information and support move through the team, and people feel like they’re moving together.
When it’s stretched, people work well side by side but interact mainly when they need something.
Three perspectives
Sounds familiar?
“People work well side by side, but mostly interact when they need something.”
A Trail to explore: Beyond the Work
All seven conditions ↑Every team has strengths and challenges. A lower score doesn’t mean the team is failing, and a higher score doesn’t mean there’s nothing to improve. Some conditions are within the team’s influence. Others depend on the wider organization.
The goal isn’t a perfect score.
It’s a clearer understanding of the team’s experience and what can be improved together.
From the Momentum Scan
Your Momentum Scan helps identify two starting points.
Momentum Source
The condition your team rates highest right now.
Something already working in your team’s favor, worth understanding and protecting.
Momentum Drain
The condition your team rates lowest right now.
Not a sign your team is failing, or a problem it must solve alone. Some Drains need support from leadership; the Quest helps the team find a realistic step and say what it needs.
These aren’t labels or judgments. They’re a way to start a conversation about what’s helping your team and what might need attention.
A system, not a scorecard
Conditions don’t exist in isolation. When responsibilities are unclear, for example, workload can feel less fair. When teammates trust one another, asking for help may become easier.
Understanding these connections can help a team choose a practical place to start.
The goal is to understand the pattern, then decide together what matters now.