Tuckman, Teams, and Bruce Lee
Working as a software engineer in today’s world often requires working with others. The top tech companies, fintechs, and even up-and-coming disruptors organize their engineers into teams with specific missions, goals, and ownership. It might be the fabled two-pizza team, or it might be a team of ten or more.
Learning to work well within a team is critical to your success as an engineer. The notion of the hero programmer or the lone ranger won’t get you far. The top engineers are ones that accomplish through others by mentoring, teaching, and shaping the organizational culture. And it’s hard to do any of those things if no one wants to work with you.
But the thing about teams is that they change. New members join, old members leave, reorgs create brand-new ones, etc. And when this happens, it can be hard to understand what to do next.
But it’s paramount that when these changes happen that you do adapt. Otherwise, you will get stuck in the past.
This begs the question: how do you adapt? How do teams change?
Much research has gone into how teams form, perform, and find their roles on their team (which we’ll get into it soon). But before we get there, whenever I think about adapting, I think about Bruce Lee.
