Create wiki/all-coders-no-communicator.md
5fd24784a7a7 harrisonqian 2026-04-12 1 file
new file mode 100644
index 0000000..8bc68de
@@ -0,0 +1,26 @@
+---
+visibility: public-edit
+---
+
+# all coders, no communicator
+
+*(common gotcha)*
+
+## what happened
+
+team of four strong engineers. built an incredible project. lost to a team with a worse product but a designer and a presenter. nobody on the engineering team could explain what they built in a way that excited the judges.
+
+## why it's a gotcha
+
+a balanced team needs someone who can present, not just code. if everyone on your team wants to be in the IDE, nobody's working on the pitch, the slides, or the demo narrative. technical skill wins buildathons; communication wins hackathons.
+
+## the fix
+
+actively recruit for complementary skills. one great presenter is worth more than a fourth backend developer. if your whole team is technical, assign one person to own the presentation and protect their time from getting pulled into code.
+
+## see also
+
+- [[pitching-matters-as-much-as-product]] — why communication wins
+- [[unclear-roles]] — assign the communicator role explicitly
+- [[practice-presentation-once]] — even coders can present if they practice
+- [[solo-vs-bad-team]] — a solo builder who can present beats 4 coders who can't
\ No newline at end of file