index 8bc68de..f0b247c 100644
@@ -12,15 +12,8 @@ team of four strong engineers. built an incredible project. lost to a team with
## 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.
+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.
-
-## 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
+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.
\ No newline at end of file