Steve Sandersonš¢
4y ago
I love making important things better, while glimpsing at the patterns that connect
If you are part of a group solving some problem you've never solved before, especially if you're not a technical leader, then odds are you've got lots of well-meaning advice about getting the "BEST", most cliche-superlative-filled technical folks.
Regardless of what "technical" is, the advice goes, hire the "best" (software developers / designers / biologists / doctors / etc) you can get.
They wouldn't be wrong, but the problem is - they are not right.
They are not right because of what they haven't told you: context matters & what's best for your situation isn't likely what was best for theirs
At an early stage - let's call it "exploration" - your job is to discover, and hopefully validate, the right demand: demand to solve a problem, demand that causes them to pay in some form, demand that has a large group of people, demand that you can fulfill, etc.
To explore well, you and your group must be highly adaptable, i.e.
one day, it's interviews with people to test whether they truly have the unmet needs you hope;
another day, it's spending a few hours "in someone else's shoes" to learn about what's happening in a part of their life; and
another day, it's asking individuals about one of your solution ideas to gauge their reaction.
As a result, what's best during exploration is a group that thrives in chaos, complexity, and environments of uncertainty, and meets it with curiosity and low ego.
When most people tell you to hire the "best", they mean the technical experts who win at being an expert.
And here's the rub: for many experts "if the only tool you have is a hammer, it is tempting to treat everything as if it were a nail" so their go-to will always be their technical tools-of-the-trade
However, what you need are people with the attitude that lets them do all the important things that are critical during exploration, especially when the important things aren't technical.
When your group is running, all of your group should focus on the highest-stake, critical questions to solve - regardless of their expertise.
When your group is recruiting, check how comfortable your specialists are with working outside their specialty, e.g.
will a software developer get on zoom with a nurse?
will a designer show out a just-good-enough design to a potential user?
If you get pushback, that may be a red flag for fit. They may fit better later when the context has changed to a more established, more predictable environment.
Lastly, this isn't limited to startups at all, it applies wherever you are trying to solve a problem you've never solved before - because the context requires adaptability, regardless of the org. chart or silos!