index 025a7dd..3da3128 100644
@@ -10,15 +10,8 @@ discovered "are we all technical here?" as a simple first question that creates
## why it's a gotcha
-in a group of strangers, nobody wants to be the one to say "so what do you actually do?" but without that conversation, work gets duplicated, gaps go unfilled, and the team runs inefficiently for the entire event.
+in a group of strangers, nobody wants to be the one to say "so what do you actually do?" but without that conversation, work gets duplicated, gaps go unfilled, and the team runs inefficiently for the entire event. roles are part of [[teams-without-shared-understanding|shared understanding]], and the most common gap is [[all-coders-no-communicator|having no communicator on the team]].
## the fix
-ask it directly in the first 5 minutes. "are we all technical?" "who's strongest at frontend?" "who wants to own the presentation?" assign lanes early. it feels awkward for 30 seconds and saves hours of confusion.
-
-## see also
-
-- [[teams-without-shared-understanding]] — roles are part of shared understanding
-- [[all-coders-no-communicator]] — the specific role gap that kills hackathon teams
-- [[figure-out-what-you-want-before-partners]] — know your own role first
-- [[solo-vs-bad-team]] — when role confusion makes the team worse than solo
\ No newline at end of file
+ask it directly in the first 5 minutes. "are we all technical?" "who's strongest at frontend?" "who wants to own the presentation?" assign lanes early. it feels awkward for 30 seconds and saves hours of confusion. [[figure-out-what-you-want-before-partners|know your own role first]], and when role confusion makes the team actively worse than working alone, remember that [[solo-vs-bad-team|solo is a valid option]].
\ No newline at end of file