【部下のやる気を出す方法】マネジメントができない人はコレを考えていない｜やる気を高めるマネジメント　（元リクルート　全国営業一位　研修講師直伝）

Business-focused summary (motivating low-initiative subordinates)

The speaker argues that low motivation/initiative is usually a management design problem, not an employee capability problem. When subordinates don’t react to new methods or policies, managers often fail to:

1. Set expectations with context first
2. Create structured opportunities for employees to share opinions—turning employees from “being forced” into “volunteering/implementing.”

---

Core diagnosis: why motivation drops

• Low initiative is not due to incompetence or low potential.
• The real cause is that employees are making risk-averse choices based on the information and conditions the manager provides.
• If management assumes people “will volunteer,” it backfires—because employees will avoid danger/uncertainty unless leadership reduces risk and increases ownership.

Practical implication: If the team atmosphere is heavy (“nobody raises a hand”), check what the manager did before the communication and how involvement is structured.

---

Management playbook / framework (action sequence)

1) Open-book management (pre-empt uncertainty with information)

• Raise expectations by first providing information—the “what’s happening / what’s at stake / what might happen next.”
• Disclose relevant metrics and context, such as:
  • Sales figures and departmental performance
  • Participation plans
  • Rival company sales figures and competitor strategy
  • Company perspective on risks/opportunities (including changes driven by digital transformation and AI)

Goal: Make employees feel they are part of the “implementing side,” not merely complying with orders.

Example given: If new hires/young talent can’t explain the sales numbers and participation plans, they likely experience the work as coerced rather than owned.

• Framework term used: “open-book management” (disclosing information to drive involvement)

---

2) Create structured opportunities to solicit opinions (in the right format)

After sharing information, ask for input:

• “What do you think?”
• “What should we do?”

Recommended structure:

• Start with one-on-one conversations with key members first to avoid a trap where group discussion produces only self-centered opinions or generic agreement.
• Then hold a forum for everyone to exchange opinions.

Proposed approach:

• Divide participants into key members (more ownership/self-sufficiency) and non-key members
• The manager consolidates and clarifies policy based on feedback

---

3) Decide roles explicitly—voluntary ownership beats sudden “top-down” policy drops

After gathering input, the manager should:

• Clearly assign roles
• Ask individuals to “volunteer” for responsibilities

The speaker emphasizes that even if someone hesitates, the manager can request them to take the role with context, so the team understands the “why,” not just the “what.”

---

Key “mistakes” to avoid (what causes backlash / no reaction)

• Announcing new policy without preparation (“suddenly presented a clear policy”) leads to backlash and rebellion.
• Increasing difficulty without increasing incentives/support creates resentment.
• The manager’s described failure mode:
  • Giving policy first, then discovering employees don’t understand the “why.”
  • Under-communicating so employees feel they must comply with no autonomy—this increases conformity pressure and kills intrinsic buy-in.

---

Concrete example (personal story) with an operational lesson

The speaker recalls being an inexperienced manager:

• They announced a new policy abruptly.
• Employees challenged the rationale: “Why is the difficulty level so high?”

They later learned the company’s system linked pay/grade to mission difficulty, meaning the incentive was mismatched with perceived unfairness (“same grade, but higher difficulty” / location already taken).

Outcome lesson:

• The speaker now recognizes the need to look ahead, align incentives and rationale, and build involvement so employees understand the purpose.
• After applying the new approach, employees actually worked harder—used as proof-of-concept.

---

Promotion / organizational tactic: roles and accountability

Promotion criteria are framed as:

• Not “ability alone”
• Not preference/compatibility
• Instead: whether the organization can assign each person an effective role, and whether the leader can also take the correct role.

Leaders who can discern roles appropriately are the ones who get the team to function and scale.

• Concept referenced: “quiet leader” and discerning roles (role assignment as the management lever)

---

Metrics / KPIs mentioned (mostly operational/organizational)

No direct business KPIs like revenue, CAC, LTV, or churn were provided. The only quantified metrics were related to the speaker’s training business:

• Presentation frequency: 200+ times/year
• Repeat rate: over 90%
• Number of courses: ~30 courses
• Enrollment: 250,000+ people enrolled
• Broadcast time: from 7:30 AM (Voicy)

---

Actionable recommendations (condensed)

• Implement open-book management: share sales/participation plans and competitor context before asking for alignment.
• Run a two-stage involvement process: 1) 1:1 with key members to shape constructive input 2) group forum to finalize shared understanding
• Assign clear roles after input, and ask for “volunteering” with full context (reduce fear/ambiguity).
• Avoid “surprise policy announcements”; always communicate the rationale and future implications.
• Use role-based promotion thinking: promote based on role assignment effectiveness, not personal liking.

---

Presenters / sources

• Presenter/Speaker: The author-trainer described as a former Recruit (元リクルート) “national sales #1” and management training instructor; also promotes their books and training platform.
• Sources referenced: Their own book(s) mentioned in the video:
  • Quiet Leader (やる気を高めるマネジメント文脈で「クワイエットリーダー」)
  • A “role discernment” book (roles/quad leader theme)
• Organizations/platforms referenced for learning/training: U-Ademy (online learning), Voicy (audio broadcast).