Respectful Change Adoption Path
Learn the system, recruit allies, and separate your identity from the idea
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 99%
The Respectful Change Adoption Path converts raw frustration into an organization-ready proposal. Begin by learning how decisions and change actually move through the institution, including why the current practice became standard. Ask curious questions before prescribing a replacement; this demonstrates respect and may reveal constraints invisible to a newcomer. Next, find early adopters who already believe improvement is needed and can contribute history, credibility, and support. Present the idea consistently, but detach your identity from its reception. A rejected proposal may reflect resistance to change or weaknesses in the idea, not dislike of you. This emotional separation makes iteration possible and prevents one setback from ending the effort. The mechanism combines context, coalition, persistence, and depersonalized feedback.
Origin
Bosché developed programs that teach young employees to provide effective, respectful feedback to leadership. She says these programs have helped organizations capture ideas that saved millions of dollars.
Core principles
- 01Change proposals need context before advocacy
- 02Questions signal curiosity where blunt challenges signal disrespect
- 03Early adopters provide credibility and support
- 04Rejection of an idea is not rejection of its author
How to run it
- 1
Learn the adoption system
Find out how ideas are evaluated, approved, funded, and implemented in the organization.
Pro tip Ask experienced colleagues how previous changes succeeded or failed.
Watch out Do not assume an illogical-looking practice has no history or constraint behind it.
- 2
Ask before prescribing
Use curious questions to understand why the current best practice is considered best.
Watch out Repeated 'why isn't it this way?' challenges can sound disrespectful.
- 3
Recruit early adopters
Partner with people who support change and possess institutional credibility or knowledge.
Pro tip Look for veterans who agree with the need but are tired of pushing alone.
- 4
Depersonalize the proposal
Treat criticism as information about change or the idea rather than a verdict on you.
Watch out Personalizing rejection makes useful iteration much harder.
- 5
Persist and improve
Refine the proposal with feedback and continue demonstrating its value respectfully.
Pro tip Use resistance as an opportunity to strengthen the evidence.
In the wild
A new analyst sees a repetitive manual report and first asks why it exists, learns the audit constraints, and partners with a veteran who previously attempted automation. Together they propose a compliant pilot instead of criticizing the team.
→ The idea receives a fair test because it incorporates context and internal support.
Common mistakes
Challenging before learning
Declaring the current system irrational without understanding it makes a useful idea sound disrespectful.
Taking rejection personally
Equating a declined proposal with personal dislike turns feedback into an identity threat.
Is it for you?
Best for
It is best for employees with useful ideas who lack organizational tenure or formal authority.
Not ideal for
It is not ideal for urgent safety or compliance failures that require immediate escalation rather than gradual adoption.
From the transcript
“number one finding out how change is adopted in the organization is really important”
“number two find early adopters”
“removing your personality from the proposal i think is such an incredible way to make sure that you push through some of that that um…”
From the episode
Gabrielle Bosche: The Misunderstood Millennial
Gabrielle Bosche