Aug 8, 2017 · 1 min read
In contrast with Charles Miller below, I find that a cute team code names both:
(a) make it radically harder to tell what people are actually working on , making people’s work opaque to other teams and to new employees… and
(b) cause people on the team to have a slightly less meaningful sense of connection to the thing they are actually working on. Practitioners develop a greater sense of connection with (say) “Kung Foo Ants” than with (say) “first-time mobile customers”.
Basically, code names increase the distance between us and our users, and make it harder for teams to collaborate between teams because people don’t even know what the other teams actually do.
