Suggest edit — all-coders-no-communicator

Title

Name

Note

---
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. this is exactly why [[pitching-matters-as-much-as-product|pitching matters as much as the product itself]].

## 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 — make it an [[unclear-roles|explicit role assignment]]. even coders can present if they [[practice-presentation-once|run through it once]]. honestly, a [[solo-vs-bad-team|solo builder who can present]] beats four coders who can't.