Principle-Aligned Competitive Response
Filter competitors’ successful tactics through your product principles
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 97%
Competitive pressure creates a temptation to copy whatever appears to be working, but successful tactics may embody assumptions that conflict with the product’s purpose. The team first states the principles it believes create durable value for its users. It then decomposes a competitor’s success into specific insights, mechanisms, and surface features. Insights consistent with the principles can improve the product; those that conflict require a more fundamental decision about whether new evidence justifies changing the principles. A bounded experiment can resolve uncertainty, but the team must judge the result against strategic coherence as well as engagement. If a feature splinters the product’s message, it should be removed even after substantial investment.
Origin
Scott Belsky derived the approach after Behance spent roughly a year building a snapshot-sharing response to Dribbble, then killed it because it conflicted with Behance’s portfolio-first principles.
Core principles
- 01Let competition reveal opportunities without dictating strategy
- 02Adopt tactics that reinforce the product’s purpose
- 03Treat conflicting tactics as a test of principles
- 04Change a principle only after examining the underlying evidence
How to run it
- 1
State the enduring principles
Write down what the product must consistently deliver and what it refuses to optimize away. Make each principle specific enough to guide feature decisions.
Pro tip Use principles grounded in observed customer needs rather than brand slogans.
Watch out Vague principles can be retrofitted to justify any decision.
- 2
Decompose the competitive signal
Identify precisely what is working for the competitor, including the user behavior, incentive, and social dynamic behind it.
Pro tip Distinguish the underlying mechanism from its visible implementation.
Watch out Do not infer durable value from attention or growth alone.
- 3
Test alignment
Compare each competitive insight with the product principles. Adopt aligned insights while escalating conflicts into an explicit strategic discussion.
Pro tip Ask whether the tactic helps users achieve the outcome for which they trust the product.
Watch out Silently violating a principle can splinter the product’s identity.
- 4
Experiment without surrendering direction
When evidence is ambiguous, test a constrained version with clear success and coherence criteria.
Pro tip Define in advance what result would justify changing a principle.
Watch out A large implementation can create sunk-cost pressure to retain the wrong feature.
- 5
Keep or kill decisively
Retain the feature if it strengthens the product’s purpose; otherwise remove it and record the lesson.
Pro tip Evaluate whether users now understand the product more clearly, not only whether engagement increased.
Watch out Leaving a conflicting feature in place can permanently blur positioning.
In the wild
Dribbble made lightweight design snapshots easy to post and socially rewarding. Behance built its own snapshot-sharing tool under competitive pressure, but the feature conflicted with its belief that designers should be judged through complete projects shown in context. The team ultimately killed the feature and recommitted to truthful, portfolio-first presentation.
→ Behance preserved its differentiated professional portfolio model while Dribbble continued serving a complementary niche.
Common mistakes
Copying the surface feature
Teams imitate a competitor’s interface without understanding the behavior or incentive producing its success.
Treating principles as immutable dogma
Principles should resist short-term pressure, but strong contrary evidence may justify changing them deliberately.
Keeping a conflicting experiment
Sunk costs can persuade teams to retain a feature even after it visibly weakens the product narrative.
Is it for you?
Best for
It is best for product teams facing pressure from a fast-growing direct competitor.
Not ideal for
It is not ideal when the team has not yet developed evidence-backed product principles.
From the transcript
“when you have principles for what you believe is best for your community and your product, the insights that you gain from competitors that are…”
“But when you see competitors doing things that are not in line with your principles but seem to be working, you have to really determine…”
“it has taught me about for for an approach for dealing with competitive pressure, uh, which is channeling it for us to spend more energy…”
From the episode
Behance (with Scott Belsky)
Scott Belsky