Paradox Lens Approach
Turn conflicting demands into complementary actions and feedback loops.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 7
- Confidence
- 99%
The Paradox Lens Approach reframes conflicting demands as complementary components of a stronger operating system. A leader first names the contradiction, such as being decisive while remaining open to feedback. The leader then identifies what each side protects: decisive action creates momentum, while feedback exposes risks and improves adaptation. Rather than choosing one, the leader designs a sequence that preserves both—for example, key stakeholders form a proposed decision, explain the factors considered, solicit asynchronous input, and revise when useful evidence appears. This avoids both unilateral blindness and slow decision-by-committee. The mechanism works because responsibility remains clear while learning continues after the initial choice. Over time, repeated feedback loops make the organization faster, more inclusive, and more adaptable.
Origin
Extracted from The Jasmine Star Show. Jasmine Star described developing the approach after her team wanted more input into decisions without adding meetings or forcing every decision to be made by a tribunal.
Core principles
- 01Treat paradoxes as opportunities rather than roadblocks.
- 02Preserve the valuable function of each opposing demand.
- 03Act decisively while creating a mechanism for adaptation.
- 04Invite relevant feedback without requiring consensus from everyone.
- 05Use key stakeholders to protect speed and accountability.
How to run it
- 1
Name the paradox
Express the competing demands in one sentence, such as needing to decide quickly while remaining open to feedback.
Pro tip Use “both” language so the problem is not framed as a forced choice.
Watch out Do not label ordinary preferences as a strategic paradox.
- 2
Identify each side's value
Clarify the benefit or risk-control function supplied by each demand. This reveals why simply eliminating one side would weaken the decision.
Pro tip Ask what would be lost if either side disappeared entirely.
Watch out Do not preserve a side merely because it reflects habit or hierarchy.
- 3
Design a complementary sequence
Arrange the demands so they reinforce one another, such as making a proposed decision first and collecting targeted feedback before final implementation.
Pro tip Separate proposal, feedback, final decision, and review into explicit stages.
Watch out Trying to satisfy every demand simultaneously can create confusion.
- 4
Assign key stakeholders
Give the people closest to the project responsibility for analyzing the decision and preparing the recommendation.
Pro tip Keep the decision group small while allowing broader asynchronous input.
Watch out Do not turn stakeholder inclusion into universal veto power.
- 5
Explain the proposed decision
Share the key points, factors considered, and reasoning through a concise written, video, or audio update.
Pro tip Use a reusable decision-brief template to reduce preparation time.
Watch out Feedback quality will suffer if the proposal and decision criteria are vague.
- 6
Run the feedback loop
Invite concerns, evidence, and insights, then adjust the proposal where the input materially improves it.
Pro tip Set a response deadline and ask contributors to identify risks or missing information.
Watch out Do not treat feedback as a ceremonial step after the decision is already irreversible.
- 7
Review the outcome
Monitor the decision after implementation and revise it when results reveal a better path.
Pro tip Choose a review date and success measures before implementation.
Watch out Adaptability should respond to evidence, not every passing opinion.
In the wild
Jasmine Star's team wanted more influence over decisions, but involving everyone in repeated meetings would slow execution. Key stakeholders instead discussed the issue, and a leader recorded a video or audio message explaining the factors and proposed decision. The wider team could then contribute feedback asynchronously before the final call.
→ The process preserved decision speed, allowed useful concerns to surface, and reduced unnecessary meetings and groupthink.
When team members proposed a YouTube community, they were asked to itemize the proposal, identify the key stakeholders, clarify the actual decision, and specify who was involved. The material was distributed for advance review before a focused meeting.
→ The team converted an uncertain idea into a reviewable decision with clearer ownership and better preparation.
Common mistakes
Confusing participation with consensus
Stakeholders can provide valuable evidence without jointly owning the final call. Requiring universal agreement can erase accountability and slow action.
Collecting feedback too late
Input cannot improve a decision once execution is effectively irreversible. Place the feedback loop before commitment and retain a later review point.
Inviting unstructured reactions
Broad requests for opinions produce noise. Explain the proposal and ask for specific risks, missing evidence, or implementation concerns.
Is it for you?
Best for
It is best for leaders navigating complex decisions where two legitimate demands appear incompatible.
Not ideal for
It is not ideal when a legal, ethical, or safety constraint leaves no valid room for balancing alternatives.
From the transcript
“I want you to try the paradox lens approach.”
“This strategy involves viewing paradoxes as opportunities instead of roadblocks.”
“For example, you might make a decision but then set up some kind of like feedback loop to monitor how effective it is, and then…”
From the episode
Make Better Business Decisions with This One Mindset Shift