As we think about audacious goals for next year and how to organize teams for success, we’re thinking about the skills required for team flow. If you’re familiar with Shape Up, you’re also familiar with the Hill Chart analogy of progress. You begin with a large space of optionality; you start by figuring things out, discovering unknowns, and feeling around the edges. Then the work transitions into getting things done, putting the pieces into place, and getting everything to work together.
Can you share anything you've learned with regards to how to train people up on this skill or spot those who have it so that you can add them to the team? I agree with what you've written here - this isn't taught in school and dedicating years of your life to building software (becoming 'senior') doesn't automatically teach you these skills.
I have a few techniques I've used to interview engineers with decent success. I'll write something up this week. I'm also thinking through the training part now. Had some decent success with a few engineers at Medidata, so will be cool to share and compare notes.
Can you share anything you've learned with regards to how to train people up on this skill or spot those who have it so that you can add them to the team? I agree with what you've written here - this isn't taught in school and dedicating years of your life to building software (becoming 'senior') doesn't automatically teach you these skills.
I have a few techniques I've used to interview engineers with decent success. I'll write something up this week. I'm also thinking through the training part now. Had some decent success with a few engineers at Medidata, so will be cool to share and compare notes.