Problem-First Product Expansion
Let each solved customer problem expose the next product to build
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 90%
Problem-First Product Expansion grows a portfolio by following the customer's chain of constraints. After one product solves a useful problem, observe what still prevents the customer from completing the broader job, then decide whether the company can contribute a meaningful solution. Blackmagic Design moved from capture cards to monitoring, colour correction, and cameras as each area exposed another limitation in affordable television and film work. The rule is not to fill a market segment merely because it exists or to retaliate against a competitor. Each expansion must add something interesting and useful, begin with a credible narrow product, and earn acceptance over time. The resulting portfolio is connected by a customer mission rather than by a spreadsheet of attractive categories.
Origin
Petty described Blackmagic Design's progression from a capture card into monitoring, DaVinci colour correction, and cameras as one solved problem exposed another. Extracted from The Foundr Podcast.
Core principles
- 01Expand from observed problems rather than market segments
- 02Use one product to reveal adjacent constraints
- 03Build only where the company can add something meaningful
- 04Expect each new product line to earn trust separately
How to run it
- 1
Trace the remaining job
Watch what customers still cannot do after using the current product. Frame the limitation as a problem in their broader workflow.
Pro tip Look beyond requests for features to the creative outcome the customer is trying to achieve.
Watch out Do not infer a portfolio opportunity from an isolated complaint.
- 2
Test for meaningful contribution
Ask whether the company can add something useful and distinctive to the adjacent problem. Reject expansion whose only rationale is occupying a segment.
Watch out Competitor hostility or industry gossip is not a customer reason to build.
- 3
Define a narrow first step
Choose the smallest credible product that removes part of the constraint. Accept that the first one or two products in a line may serve a niche task.
Pro tip Use existing capabilities where possible, while identifying what the new line must teach the team.
Watch out Do not expect to jump from no capability to a mature product line instantly.
- 4
Launch and earn trust
Put the product into use, address weaknesses, and allow customers to judge whether the company delivered what it promised.
Pro tip Measure acceptance over years for important product lines, not only at launch.
Watch out Credibility from an existing line does not eliminate resistance in a new category.
- 5
Follow the next constraint
Use the product's real operation to reveal the next obstacle in the customer workflow. Repeat only when the next move remains consistent with the customer mission.
Watch out Expansion can dilute focus if it is disconnected from the chain of customer problems.
In the wild
Blackmagic Design began with a low-cost capture card. Monitoring problems led to further products; acquiring DaVinci supported wider access to colour correction; limitations in affordable cameras then pointed toward digital film cameras that preserved images suitable for that work.
→ The company assembled connected product lines around making television and film creation more accessible.
Common mistakes
Filling a segment for its own sake
Petty explicitly rejects making a product merely to battle inside an existing market segment; the company should have something useful to add.
Assuming trust transfers instantly
A new product line can face its own resistance even when the company is accepted elsewhere.
Trying to leap to maturity
Early products may need to solve a narrow task while the team learns enough to build the fuller line.
Is it for you?
Best for
It is best for companies with deep customer and technical knowledge whose products expose adjacent workflow constraints.
Not ideal for
It is not ideal when an adjacent problem falls outside the company's ability to add distinctive value.
From the transcript
“one product breeds another”
“you start with the capture card and then you said I've got monitoring problems so well let's solve that”
“unless it's really you know we can add something to it there's no point doing”
From the episode
236: Bootstrapping a $300M Cinema Company, With Grant Petty of Blackmagic Design
Grant Petty