Kind Disruptors
Challenge ideas openly without damaging trust or creative momentum
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 96%
Kind Disruptors is a team-culture model for producing stronger decisions through respectful dissent. Leaders first make it explicit that proposals, including their own, are open to challenge. Team members then examine an idea from multiple vantage points, identify weaknesses, and explain why they disagree without attacking its author. The leader demonstrates that criticism is safe by listening, stepping back, and changing direction when warranted. Core values provide behavioral boundaries so disruption remains constructive rather than combative. Used consistently, the model reduces founder-centered agreement, prevents processes from extinguishing creativity, and converts meetings into places where ideas are tested collectively before the organization invests in them.
Origin
Jasmine Star described the model during a Social Curator team meeting after hearing Reid Hoffman discuss the value of kind or nice disagreeers.
Core principles
- 01Treat ideas as shared hypotheses, not personal property
- 02Invite disagreement explicitly before consensus forms
- 03Challenge the proposal while respecting the person
- 04Preserve creativity while introducing useful systems
- 05Model openness to criticism from the top
How to run it
- 1
Define the cultural boundary
Clarify that respectful disagreement is expected and connect that expectation to the team's current core values.
Pro tip Revisit the values when the company's vision or stage changes.
Watch out Without shared behavioral boundaries, disruption can become personal or hostile.
- 2
Remove ownership from ideas
Frame every proposal as something the team can examine rather than a possession its originator must defend.
Pro tip Leaders should place their own ideas under scrutiny first.
Watch out Founder defensiveness will quickly teach the team that disagreement is unsafe.
- 3
Invite people to poke holes
Ask participants to identify assumptions, weaknesses, unintended effects, and reasons the idea may fail.
Pro tip Include perspectives from different departments or functions.
Watch out Do not mistake silence for agreement.
- 4
Disagree kindly and specifically
Explain what is weak and why while maintaining respect for the person who proposed it.
Pro tip Anchor objections in customer needs, evidence, or operational consequences.
Watch out Vague negativity does not improve an idea.
- 5
Adapt and reinforce
Change or discard ideas when criticism reveals a better path, then recognize contributors who challenged them constructively.
Pro tip Discuss examples of good disruption in recurring team meetings.
Watch out Inviting criticism but never acting on it makes the practice performative.
In the wild
A founder proposes a complicated launch campaign. Rather than approving it automatically, marketing identifies confusing messaging, customer success predicts support issues, and operations flags an unrealistic deadline. The founder thanks the team, removes two campaign elements, and adjusts the schedule.
→ The team launches a simpler campaign with fewer customer and operational risks.
A remote team reviews a proposed approval system. Designers explain that it would suppress rapid experimentation, while project managers explain where some structure is still necessary. They retain one approval gate and remove the rest.
→ The workflow adds accountability without eliminating creative autonomy.
Common mistakes
Protecting the founder's ideas
If the founder treats criticism as disloyalty, team members learn to agree rather than contribute their judgment.
Confusing disruption with aggression
Personal attacks and performative contrarianism damage trust instead of strengthening proposals.
Systemizing away the magic
Processes should support execution without eliminating the creativity that originally differentiated the business.
Is it for you?
Best for
It is best for growing teams that need candid debate while preserving trust and collaboration.
Not ideal for
It is not ideal for urgent incidents requiring immediate command decisions or teams without basic interpersonal safety.
From the transcript
“I want the team to poke as many holes in it as possible.”
“And so I want us to approach ideas in meetings with the ability for us to be kind disruptors.”
“I don't want us to be a bunch of people who say yes, Jasmine.”
From the episode
Pulling Back the Curtain: Day in the Life of a 7-Figure Business Owner