new file mode 100644
index 0000000..025a7dd
@@ -0,0 +1,24 @@
+---
+visibility: public-edit
+---
+
+# unclear roles
+
+## what happened
+
+discovered "are we all technical here?" as a simple first question that creates immediate clarity. without it, you end up with three people all trying to code the backend and nobody working on the frontend or the pitch.
+
+## 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.
+
+## 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