RIDE Persuasion Model

Convince others to accept your proposal

Persuasion Topic: Request to add 2 Product Manager headcounts (HC)
Audience: Department Director + HRBP
My Proposal: Hire 2 Senior Product Managers in Q4 to share current team workload and support next year's business growth
Date: 2026-08-30

---

R — Risk

Open by explaining what risks come from NOT adopting your proposal (people are more sensitive to loss than to gain).

Amplify risks appropriately, but don't over-exaggerate.

Risks of not adopting the proposal:

Risk Factor	Impact Level	Likelihood	Notes
1. Current team overloaded, product quality declines	🔴 High	🔴 High	Currently 3 PMs cover 8 product lines, averaging 2.7 per person. Industry average is 1.5. Sustained overload inevitably leads to quality drops.
2. Core member burnout, turnover risk	🔴 High	🟡 Medium	Alex has been working overtime for 3 months straight. If we don't add staff and someone quits, the whole team becomes even harder to operate.
3. No one available for next year's new business lines	🟡 Medium	🔴 High	The company has already confirmed 2 new business lines for next year. If we don't hire now, no one will be ready in time, jeopardizing business goals.

Opening script reference:

Manager, I'd like to talk to you about team staffing. The current situation is — if we don't add PMs in Q4, I'm worried about several risks: First, everyone is running at overload, so product quality is hard to guarantee long-term. Second, if a core member burns out and leaves, the team becomes even more passive. Third, regarding next year's new business lines, if we don't build capacity now, we simply won't be able to deliver on time.

Notes:

• Risks must be real, not alarmist
• Amplify appropriately, but don't over-exaggerate
• Directly relevant to the other party's interests (team stability, business goals)

---

I — Interest

Explain what benefits come from accepting your proposal (having lowered the psychological threshold in the previous step, this step is easier to accept).

Don't present benefits as absolute certainties; just give the other party a clear comparison.

Benefits of adopting the proposal:

Benefit Point	Value	Time to Impact	Notes
1. Improved product quality, fewer production issues	🔴 High	Medium term	With enough staffing, each PM can focus more, requirements research and solution design get more thorough, and production bugs decrease.
2. Improved team stability, lower recruitment costs	🟡 Medium	Medium term	Avoid core member turnover. Hiring a senior PM costs ~¥50-100K (headhunter fee + time cost) — better to add staff earlier.
3. Build talent reserve for next year's business growth	🔴 High	Long term	Position new business lines ahead of time, so next year won't be a scramble. Business goal achievement becomes more assured.

Transition script reference:

By contrast, if we can hire 2 senior PMs in Q4, the benefits are pretty clear: First, product quality improves, production issues decrease, and people don't have to firefight every day. Second, team pressure eases and core members are more stable. Most importantly, next year's new business lines have people ready, so we hit our business goals with more confidence.

Notes:

• Benefits need to be concrete, not vague
• Don't state them too definitively; leave some room
• Form a clear contrast with the earlier risks

---

D — Differences

What makes your proposal different and unique (everyone likes something distinctive).

Your differences need to be relevant to the other party, not just self-serving uniqueness.

What makes my proposal unique:

Differentiator	Difference from Standard Approach	Value to the Other Party
1. Not "just add people", but "add people + restructure"	Usually adding staff just means more headcount. I propose optimizing product line allocation at the same time, so each PM focuses more.	Not only solves the understaffing problem, but also improves per-person efficiency — 1+1 > 2.
2. Phased hiring, hire 1 first to test the waters	Usually people ask for 2 hires upfront. I suggest hiring 1 senior PM first, then the 2nd after validating results.	Reduces hiring risk and cost pressure, leaves you decision-making buffer space.
3. Internal development + external hiring combined	Usually only external hiring is considered. I suggest simultaneously opening an internal promotion path, giving existing team growth opportunities.	External injection + internal activation — both bring in fresh blood and motivate the existing team.

Comparison script reference:

Unlike the usual "just ask for HC directly", my approach this time is: First, not just adding people, but simultaneously optimizing product line allocation so everyone is more focused and efficiency is higher. Second, take two steps — hire one first to see results, then decide on the second, so you don't feel too much pressure. Third, combine external and internal: hire a senior externally and develop someone internally too, giving the team room to grow.

Notes:

• Differences must be relevant to the other party, not self-indulgent
• Highlight uniqueness without disparaging other solutions
• Describe differences in language the other party understands

---

E — Effect

Mention some flaws of your proposal appropriately to increase credibility (things that are too perfect seem unreal; small shortcomings are fine as long as they don't mar the overall quality).

Don't be overly modest and list a ton of problems, which would backfire.

Shortcomings of the proposal:

Flaw	Impact Level	Mitigation
1. New hires need 2-3 months to fully onboard	🟢 Minor	Prepare onboarding docs in advance, assign a mentor to guide them, speed up integration.
2. Labor cost increases in the short term	🟡 Moderate	Phased hiring: hire 1 first, the 2nd in Q1, spreading the cost pressure.
3. Internal promotion may trigger feelings of unfairness	🟢 Minor	Define clear promotion standards and processes, keep them open and transparent so everyone is convinced.

Honest script reference:

Of course, this plan isn't perfect. New hires need time to ramp up, roughly 2-3 months to fully catch up. Labor costs will also increase in the short term. But both can be mitigated through a solid onboarding mechanism and phased hiring. Overall, the benefits still far outweigh the costs.

Notes:

• Only mention small flaws, not deal-breakers
• Don't be overly modest and list a pile of problems
• Every flaw should have a corresponding mitigation approach

---

📝 Complete Persuasion Script

Step	Content
R Risk	No hires → product quality declines + core member turnover risk + can't deliver next year's new business
I Interest	Add hires → product quality improves + team stability + talent reserve for next year
D Differences	Not just adding people, but "add people + restructure", phased hiring, combined internal/external approach
E Effect	New hires take time, short-term cost increases, but both have mitigations — flaws don't outweigh benefits

Closing script:

All things considered, I think adding 2 PMs in Q4 is worth it. Of course, the final decision is yours. Do you think this approach is feasible?

---

💡 Usage Tips

Persuasion order matters:

Risk (loss aversion) → Interest (benefit comparison) → Differences (unique appeal) → Effect (honesty builds trust)

Applicable scenarios:

• Proposing solutions to superiors
• Selling products/services to customers
• Cross-department coordination and resource negotiation
• Persuading colleagues to accept your ideas

Key principles:

1. Loss before gain — Talk about risks first, then benefits, leveraging loss aversion
2. Sharp contrast — Risks and benefits form a strong comparison
3. Highlight uniqueness — What others don't have I have; what others have I do better
4. Modest self-critique — Proactively mention small flaws to increase credibility
5. Return the decision — Persuasion isn't coercion; give the other party choice

---

📌 Quick Reference Card

Letter	Chinese	English	Purpose	Core Logic
R	风险	Risk	Create a sense of crisis	People are more sensitive to loss than to gain
I	利益	Interest	Show the benefits	Easier to accept after lowering the psychological threshold
D	差异	Differences	Highlight uniqueness	Everyone likes something distinctive
E	影响	Effect	Increase credibility	Too-perfect things feel unreal