Definition
The diagnostic that separates a team from a group doing teamwork: can the individuals in this group achieve individual wins and losses regardless of what their partners do? If yes, it’s teamwork, not a team, no matter what anyone calls it. If no, it’s a team — the outcome is shared whether the group wants it to be or not. The test is binary. There is no third tier.
Explanation
Applied to the building, the leadership layer — the operator, the kitchen manager, the front lead — passes the test as a real team. None of them can post an individual win: the operator can’t call it a great quarter because the front of house crushed it while the kitchen bled money. The P&L is one number and the Guest Experience is one verdict, so all three are bound at the outcome whether they like it or not.
Front of house and back of house cast fail the test — they’re teamwork, not a team. A server can have a great shift on a night the kitchen runs sideways; a cook can execute a station perfectly while servers drop tables. They share goals and coordinate constantly, but their individual outcomes stay genuinely separate. Shift-level leads land on the teamwork side too, despite carrying more responsibility than line cast — they can still post an individual win or loss independent of their peers.
The failure this test diagnoses: operators import leadership frameworks built for small, mutually-accountable teams and bolt them onto large, role-distributed teamwork groups, then blame the cast when the framework doesn’t take. Running [The Win/Loss Test] first tells the operator which structure they’re actually building for before they borrow a framework built for the wrong one.



