Steve Sanderson🚢
/stevesanderson

I love making important things better, while glimpsing at the patterns that connect
Steve Sanderson🚢
4y ago
reader beware: this is basically an opinion, even gut-feel, piece - backed up with personal experience and inspirational stories.
You're in a successful product company, and successful companies, with successful products, typically want to build new successful products.
In successful companies, you (hopefully) have a lot of data about customers & users. With that, you can find large opportunities, and jump straight to quickly building the features that best serve the largest number of that group.
However, there's likely one factor you completely missed - the path starts with innovating at the margins
Innovation is often path-dependent, i.e. it often works better to go from the margins to the mass market. Starting with targeting the solution to the mass-market (i.e. serving the "largest" group of people) is often a flawed path.
In startups, this is never a choice: most of them have to start at the margins, whether solving their own problems or solving problems for a small group of eager, early adopters. In my personal experience, this has been consistently true: a repeated pattern is that we started narrow before we went broad.
In disability tech, they've chosen the margins as their focus, and also follow the repeated pattern of starting narrow before going broad, e.g.
television subtitles for people with hearing difficulties "became widely adopted by a far wider group of able-bodied viewers". (from Disability tech goes mainstream by @AJack )
the original touchscreen technology in an iPhone came from creating "input devices for folks with compromised fine motor function" (from The Oxymoron of “Data-Driven Innovation” by @HeyChelseaTroy )
Solving problems for people in the margins not only lets you get early traction, and therefore more rapid learning, it appears to make the solutions more resilient - i.e. if they work for the people in the margins, then it's more likely to work for the mass-market.
Starting with the mass market and moving to the margins appears to be less effective, plus there's often pressure to move on to a new large opportunity instead of targeting the margins.
Follow a strategic path of innovation, from narrow to broad
In your product effort within a successful firm, identify the large opportunity, and start first with a segment of outliers.
Consider,
When you hear "this will work well for the vast majority of those users" flip the conversation and ask "what amount of this group are we willing to leave out?"; consider if this is an outlier segment to start with, and the impact if you left them out of the success.
When there's a demand for efficiency - reorient to make sure efficacy has come first.
When the objection to starting narrow is an assumed delay to delivery, remind yourself that in a context of uncertainty, speed of learning is a strong predictor of success.
Teams that attempt to jump past learning from the margins are making an expensive gamble that they will get it right on the first try.
Instead, start narrow (prove efficacy, build resilience), then go broad (prove efficiency and scale).
Steve Sanderson🚢
4y ago
As an unapologetic generalist working in Product, there's one go-to pattern when I'm trying to make sense of (and possibly help change) other people's product efforts: the perspective of supply and demand.
🧵👇
I've had the joy to work with, in, or on a significant number of product efforts across many domains, levels and industries for 30+ years. Through this, I get to continually identify, harvest, and use common patterns.
Frequently, I'm in the position to help make sense of other people's product efforts, usually towards some end (e.g. increase ability to grow revenue) and I've found it easiest to start by looking at their effort through the perspective of supply and demand.
While supply and demand is an economic model, I use it more generally: to understand how a team actually is trying to make an impact. While there are many ways to make sense of how product teams work, I start here because it is simple, quick, and often tells me quite a bit.
Through the lens of supply and demand, I want to understand two things:
how much do they actually spend on supply-side vs demand-side practices?
what's the actual meaning & motivation of their practices; does supply-side or demand-side motivate them?
As academic as this might sound, it's really a matter of getting to know the people - their actual stories and lived experiences - through this lens.
I'll follow up with some examples, and the practices I use to get this orientation on their work.
Steve Sanderson🚢
4y ago
Imagine you're a busy product manager of a successful product, and you're thinking about what's down the road... and you want to identify new opportunities.
You could focus on known, existing problems, and solve them with new features in your existing product... or you could try expanding your impact or even expanding your market.
The problem is, how can you explore this space quickly, and with low risk?
This pattern starts with the assumption that there are certain features in your current product that may be a sign of hidden demand.
Start by finding those features where users may be doing more with your results than you can see, e.g.
any features (now or in demand) that generate Excel or CSV files?
any features (now or in demand) for reports or dashboards?
Follow up by finding out what actions your users (want to) take with those results, e.g.
Excel / CSV - what actions do they take with the data?
Reports / dashboards - what actions do they take with the dashboard or report results?
Then get to deeper meaning of their actions, e.g.
pick those actions that include
any further processing or analysis, and/or
communicating the results to someone else
and ask your users some form of "what problem(s) do these actions solve, and who they are solving them for?"
Now you know there's a problem, that they're aware of having a problem, and that they've put together a solution out of pieces parts.
Congratulations, you've addressed 3 of the 5 levels of Steve Blanks' earlyvangelist Pyramid.
Steve Sanderson🚢
4y ago
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!