Skip to content

Commit

Permalink
Edit team building post
Browse files Browse the repository at this point in the history
  • Loading branch information
ryanspletzer committed Feb 23, 2025
1 parent 7604ee6 commit 96de012
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions _posts/2025-02-22-how-to-build-a-team-from-scratch.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,11 @@ I often see avoidable missteps when people try to build a brand-new engineering
are a few rules of thumb that can help. I work in the software engineering field, so I approach this mostly from that
perspective; however, this advice likely applies to other professional domains as well.

Opportunities to start a brand-new team from scratch can be exceedingly rare. More often, a manager inherits an existing
team or joins a new company where the team is already established. (As an aside: I believe breaking up well-functioning,
"jelled" teams should be a last resort —- unless the team's success and growth require splitting it to accommodate
another manager for ideal team sizes. More on that below.)
Opportunities to start a brand-new team from scratch can be rare. More often, a manager inherits an existing team
through various means like joining a new company where the team is already established, or perhaps even experiences a
reorg where folks from multiple teams are split off and merged together. (As an aside: I believe breaking up
well-functioning, "jelled" teams should be a last resort —- unless the team's success and growth require splitting it to
accommodate another manager for ideal team sizes. More on that below.)

However, if you do have the golden opportunity to build a team from the ground up, this advice is for you.

Expand Down

0 comments on commit 96de012

Please sign in to comment.