new file mode 100644
index 0000000..bfe8618
@@ -0,0 +1,25 @@
+---
+visibility: public-edit
+---
+
+# solo > bad team
+
+## what happened
+
+solo tbh very strong. benefits: no comms issues, no dependency issues, no presentation disagreements, when you win you actually feel it.
+
+## why it's a gotcha
+
+there's pressure to team up at hackathons. "you need a team to win" is conventional wisdom. but a bad team is actively worse than solo — you spend more time coordinating than building, you make compromises that make the project worse, and if things go wrong, it feels worse because you gave up control.
+
+## the fix
+
+if you don't find a team you're genuinely excited about, go solo. a focused solo builder who ships a working demo beats a dysfunctional team every time. the best teams are small and aligned; the worst teams are big and confused.
+
+## see also
+
+- [[teams-without-shared-understanding]] — what makes a team bad
+- [[unclear-roles]] — role confusion is a team-killer
+- [[figure-out-what-you-want-before-partners]] — find the right team or go alone
+- [[personality-mismatch-under-pressure]] — another way teams fail
+- [[all-coders-no-communicator]] — unbalanced teams lose
\ No newline at end of file