What Decisive Leaders Actually Do: Breaking the Status Quo in Four Thinking Modes and a Five-Meter Radius

Posted Apr 16, 2026

27 min read

AI-Generated Content

This article was generated by AI. The accuracy of the content is not guaranteed, and we accept no responsibility for any damages resulting from use of this article. By continuing to read, you agree to the Terms of Use.

Who this is for: PMs, tech leads, engineering managers, and mid-career engineers who want to change their organization from the inside
Assumed background: Some experience running a team helps, but non-technical leaders can follow along
Reading time: ~25 minutes

Overview

“Leaders who break the status quo need decisiveness and vision.” This kind of abstraction offers nothing to a leader actually trying to move. The question needs to be reframed: what exactly does a status-quo-breaking leader do, in what order, and with which skills?

At the center of the answer sits the dividing line between “commitment” and “rational judgment.” Rational judgment means picking the option everyone can see is correct once the data is in and responsibility is clearly assigned elsewhere. Commitment, by contrast, means acting under uncertainty while owning the outcome personally and carrying the work through to the end¹². In Japan’s precedent-driven corporate culture, many leaders hide decision avoidance behind a performance of rational judgment. That pattern is the breeding ground of the status quo.

Commitment is not a matter of grit, though. It decomposes into trainable skills: the four thinking modes of critical thinking, backcasting, agile thinking, and diversity-oriented thinking³, the “intellectual stimulation” component of transformational leadership⁴, and ten concrete skills for minimizing resistance⁵.

This article uses Futa Sakai’s “commitment vs. rational judgment” frame as its spine, then decomposes the structure of status-quo-breaking. Along the way it draws on Kotter’s change process⁶⁷, Edmondson’s work on psychological safety⁸, and Samuelson & Zeckhauser’s status quo bias⁹, and lands on practical tactics a PM or tech lead can apply within their own five-meter radius—the phrase Sakai uses for the team or sub-unit immediately around you, the people you can actually reach without organizational permission.

The article is built to be read in two modes. One is self-examination of your own leadership. The other is observation—reading the leaders around you to see whether they are performing leadership, actually doing it, or actively harming the organization. Every section ends with an observation lens that sorts behavioral signals into three layers: performative, functional, and harmful. These are observable behavior patterns, not character judgments—read them that way.

1. Why most leaders stall at “breaking the status quo”

Status quo bias doesn’t yield to willpower

Samuelson & Zeckhauser’s classic 1988 study experimentally demonstrated that humans irrationally keep choosing the current state over alternatives⁹. The pattern shows up clearly in consequential real-world decisions—health insurance choices, retirement plan changes, and so on.

The implication matters: “not changing” often isn’t an active judgment at all, but passive acceptance of a default. And the person who accepted the default still tells themselves they “thought it through carefully.” That self-flattering illusion is the first wall between a leader and actual change.

“Rational judgment” as a disguise for decision avoidance

Futa Sakai—CEO of Momentor, previously responsible for codifying DeNA’s management training—describes this structure as the contrast between commitment and rational judgment¹².

Rational judgment: choosing an option that’s fully supported by data, where others (executives or the market) bear the risk, and that’s defensible to anyone who asks
Commitment: taking on an uncertain project and personally owning the outcome through to the finish

What actually happens in most organizations, Sakai argues, is decision avoidance dressed up as rational judgment. Questions like “do we have a case study from another company?” or “what does the data say?” frequently function not as requests for information but as mechanisms for diffusing responsibility.

The structural pattern where Japanese companies kill innovation through precedent worship and other-company-case worship has been documented repeatedly in the trade press¹⁰. Saying “we’d be the first in the industry” stops an internal proposal dead, while “other companies are already doing it” gets it through—this asymmetry isn’t about individual risk aversion. It’s what you get when the system only rewards rational judgment.

The trap that hits IT leaders hardest: data worship

The lean toward rational judgment runs even stronger in engineering. A/B test results, metric trends, performance indicators—these are supposed to be inputs to commitment, not substitutes for it. But the moment a leader says “let’s move once the data is in,” they’ve stopped deciding and started waiting for the data to decide for them.

Company-wide AI coding tool rollouts, architecture overhauls, changes to review culture—these changes all include dimensions where computing an ROI in advance is fundamentally impossible. A leader who keeps asking for “more data” in those domains is, without noticing, reinforcing status quo bias.

Observation lens: distinguishing commitment from decision avoidance

Performative signs: greenlights the project before defining exit criteria or success thresholds, then retrofits the failure narrative (“not enough data,” “the team couldn’t execute”) after the fact. The decision-meeting notes have no owner and nobody remembers whose call it was
Functional signs: writes down in their own words, before starting, something like “if metric X drops below threshold we pull out” or “if we can’t hit Z within Y months we pivot.” The team knows unambiguously who owns the project
Harmful signs: outsources the decision itself to a subordinate or junior while keeping the advisor role for themselves. Deliberately leaves expectations vague so that when it fails they can say “they decided, I just delegated”

2. The watershed between commitment and rational judgment

flowchart TB
    Start["Should we push<br>this initiative?"]
    Start --> Q1{"Is outcome<br>uncertainty<br>high?"}
    Q1 -->|Low| Rational["Rational judgment zone<br>Data decides<br>Anyone reaches same answer"]
    Q1 -->|High| Q2{"Who owns<br>failure?"}
    Q2 -->|Someone else| Avoidance["Decision avoidance<br>=<br>Rational judgment theater"]
    Q2 -->|I do| Decision["Commitment zone<br>Carry it through<br>Outcome-focused"]
    Rational --> Done["Execute"]
    Decision --> Done
    Avoidance --> Stagnation["Status quo persists<br>Opportunity cost<br>stays invisible"]

Two axes: uncertainty and ownership

Mapped out, the boundary between commitment and rational judgment comes down to two questions: is the outcome highly uncertain and who owns the failure.

Rational judgment works when uncertainty is low and the data determines the answer. “Follow the data” is correct here, and a leader’s personality contributes little.

Commitment is required when uncertainty is high and the data alone cannot produce a conclusion. Repeating “we need a bit more data” in that zone isn’t choosing—it’s deferring choice indefinitely. Sakai calls this rational judgment theater¹².

A checklist for situations that demand commitment

Typical commitment-zone scenarios on an engineering team:

Refactoring technical debt: short-term feature velocity drops in service of medium- and long-term throughput
Introducing a new development style (AI pair programming, trunk-based development, monorepo migrations): the learning curve eats months before benefits show up
Changing review culture or quality bars: existing team members resist, and a quantitative ROI upfront is effectively impossible
Raising the hiring bar: headcount stays open longer than the business wants
Killing a project that isn’t producing results: you have to face sunk cost directly

None of these will ever move under “decide once the data is in.” What needs deciding is direction under data scarcity, and the deliverable is a hypothesis paired with a commitment to carry it through.

3. Four thinking modes for leaders who break the status quo

Ending at “have the courage” would just reproduce the abstraction this article opened by criticizing. So here’s the decomposition of the thinking modes that actually support commitment.

Insource identifies four thinking modes as essential for leaders in turbulent times: critical thinking, backcasting, agile thinking, and diversity-oriented thinking³. These four complement the four components of transformational leadership—idealized influence, inspirational motivation, intellectual stimulation, and individualized consideration⁴.

3-1. Critical thinking: question inherited premises

Critical thinking is the refusal to swallow “the way things are done,” existing practices, and tacit assumptions whole³.

On an engineering team, that looks like:

“Is this code review process actually improving quality—and if so, which part of it?”
“Could this meeting be replaced by an async document?”
“Does the rationale we used for this tech selection still hold in the current context?”

In Bass & Avolio’s (1994) transformational leadership model, intellectual stimulation is defined as leader behavior that prompts members to question inherited premises and explore new approaches⁴. The point isn’t to order people to “think harder”—it’s that the leader models critical questions, and that shifts the team’s default thinking mode.

Observation lens: critical thinking vs. reflexive criticism

Performative signs: applies critical lenses only to other people’s proposals, never to their own past decisions or their own department’s assumptions. Asks “why did you decide that?” but won’t accept the same question aimed back
Functional signs: re-examines “is the call I made last year still correct in today’s context?” in public. When their premises break, they change direction based on the facts rather than protecting face
Harmful signs: turns critique into personal attack—”reckless,” “you don’t understand reality”—and that labeling shuts down the original point. The team learns “it’s safer to say nothing,” and dissent evaporates

3-2. Backcasting: reason backward from the ideal future

Backcasting defines not “a future reachable by extending the present trend” but “the ideal future we want to reach,” then works backward from there to the present³.

In product management and architecture, over-reliance on forecasting (building up from what’s currently possible) makes you a slave to existing constraints. Phrases like “our infrastructure can’t support that” or “our current team composition can’t handle it” are often signals that backcasting has been quietly abandoned.

Sakai warns about how relentless short-term rationalization pushes out “work that doesn’t convert to numbers quickly—new businesses, organizational development—but that matters most”¹¹. Backcasting is also a thinking device for getting investments that can’t be defended on short-term ROI onto the consensus table.

Observation lens: backcasting vs. vision announcements

Performative signs: declares “where we should be in three years” and stops there. No concrete bridge connects that future state to this quarter’s moves, and day-to-day decisions revert to the old defaults
Functional signs: the ideal future state is connected, stepwise, to what’s being worked on this month and this week. Any team member can immediately answer “which future milestone does this piece of work feed?”
Harmful signs: repeatedly proclaims an unreachable ideal and assigns the blame for missed targets to “insufficient commitment on the ground.” Pointing out the gap between vision and reality gets dismissed as “defeatism,” while revising the vision gets rejected as “wavering”

3-3. Agile thinking: give up the perfect plan

Agile thinking runs rapid “small plan → execute → evaluate → improve” cycles³. Engineers know this well, but one misunderstanding shows up reliably in organizational-change contexts.

Agile thinking is not an excuse for having no plan. The direction—the future defined by backcasting—stays fixed. What becomes experimental is the route to that destination. That’s the actual meaning.

Common traps for leaders on the ground:

Trying to build the perfect migration plan, the project sits idle for six months (= decision avoidance)
Conversely, running experiments without sharing any direction, the team thrashes (= agile theater)

Observation lens: agile thinking vs. undecided direction

The key differentiator isn’t “is there a direction or not”—it’s whether decisions are being recorded. Performative leaders rebrand indecision as “flexibility,” let priorities shift every quarter without ever holding retrospectives on prior decisions, and members can’t tell what they’re currently aiming at. Functional leaders fix the direction, keep only the route experimental, and sprint by sprint the learnings and discards are recorded; any direction change is explained as a consequence of that learning. On the harmful end, direction shifts constantly, whipsawing the team, no record of why, and “I never said that” deflects any pointed-out contradiction. Team confusion gets attributed to “execution problems” in individuals.

3-4. Diversity-oriented thinking: build multiple perspectives into the decision

Diversity-oriented thinking treats diversity of age, gender, experience, and discipline as a source of adaptability and innovation, not as a compliance checkbox³.

On engineering teams, diversity of technical background (frontend / backend / infra / data / AI) and career path (career-changers from other industries, people with experience on different stacks) reduces decision-making blind spots. A meta-analysis of shared leadership reports that team heterogeneity and a positive internal environment promote the emergence of shared leadership, which in turn correlates positively with team performance¹².

Conversely, a team made up of members with similar backgrounds has a structural problem: the leader can’t easily spot the assumptions they don’t know they’re making. Diversity-oriented thinking is better framed not as “we respect diversity” ethics, but as a technique for improving decision quality.

Observation lens: diversity-oriented thinking vs. demographic diversity

Performative signs: the conversation stops at demographic attributes (age, gender, background). Minority opinions get voiced in meetings but never make it into the final call; “we heard you” closes the loop
Functional signs: meeting notes and decision docs record dissenting opinions that weren’t adopted and the reasons they were rejected. In review conversations, the leader can name, positively, members who raised views opposed to their own
Harmful signs: diverse hires are used for external PR and internal optics while being functionally excluded from consequential decisions (tokenization). Members who raise dissent get marked down as “culture fit concerns,” and decisions cycle through a same-looking inner circle of yes-people

4. Skills for minimizing resistance—courage alone won’t get you there

Commitment plus the four thinking modes still won’t move an organization. Existing structures generate resistance without fail. Managing that resistance isn’t a courage problem; it’s a specific skill problem.

Harvard Business Review (the Japanese DIAMOND edition) lays out “ten steps for breaking the status quo without a fight”⁵. The author, Timothy Clark (founder of LeaderFactor), emphasizes that challenging the status quo requires more than courage—it requires learned skills.

Translated into engineering context, the core of those skills looks like this:

Pre-built pitch material: structured argument, not emotional appeal. On an engineering team, that means a short document (an ADR or a condensed design doc) laying out “current problem → proposal → anticipated objections → responses → verification method”
Maintaining respectful dialogue: cleanly separating disagreement from attack. Concretely, swap “your call was wrong” for “the assumptions at the time have since changed, so I’d like to update the decision”
Tension-defusing humor: detaching the argument from personal judgment. The same framing that already works in code review culture—”this is improvement feedback, not a performance evaluation”—extends to decision debates
Dislodging entrenched frames: recognizing that data and logic alone can’t shake priors. Bring in first-hand examples from a different company, or experimental results from a different internal team, to stop treating the existing system’s constraints as givens
Routing around insufficient authority: bottom-up change fails at the front door. Design the path in stages from the start: experiment inside your own team → share with adjacent teams → propose to the platform team → company-wide rollout

Observation lens: resistance-minimizing skill vs. appeals to authority

Performative signs: leans on authority—”the exec said so,” “this is how they do it overseas.” When dissent surfaces, shows personal displeasure to close the conversation
Functional signs: shows the adopted option side by side with rejected alternatives and explains the rationale point by point. The person who raised dissent still feels safe raising dissent next time
Harmful signs: puts on a respectful face in the room while freezing dissenters out behind the scenes—dropped from important projects, marked down in reviews, transferred to another department. The surface stays pleasant, but what the team actually learns is the informal rule: disagreeing hurts your career

Kotter’s 8 steps: the systematized process

For a systematic change process, John Kotter’s 8 steps have been the standard for decades⁶:

Create a sense of urgency
Build a guiding coalition
Form a strategic vision
Enlist a volunteer army
Enable action by removing barriers
Generate short-term wins
Sustain acceleration
Institute change

A note on the famous statistic: the widely cited claim that “about 70% of organizational change efforts fail” doesn’t appear in those exact words in Kotter’s 1995 HBR article⁷. It’s been noted that the first place Kotter himself spells out that ratio is his 2008 book A Sense of Urgency. Earlier source data traces to Hammer & Champy’s (1993) reengineering research and Beer & Nohria’s (2000) organizational change research¹³. Worth double-checking attributions when citing the statistic.

Either way, the empirical regularity—that change efforts which skip Kotter’s 8 steps fail at a high rate—is supported by years of observation from practitioner consultants and researchers.

The power of short-term wins

Within the 8 steps, step 6—generating short-term wins—is especially load-bearing for leaders on the ground. Kotter frames results as “wins are the molecules of results”⁶.

The reason change gets resisted hardest is simple: the transition period before results become visible is long enough to drain the driver’s energy. Deliberately engineering some visible win within three to six months—deployment time reduced under the new flow, review velocity improvements, specific defect reductions from a new tool—is what keeps change going.

5. Start from a five-meter radius: shared leadership and psychological safety

You don’t have to carry the whole-org transformation alone. Sakai is blunt: “Start with your own team, or your business unit, or whatever’s within your own five-meter radius”².

Strategy: start with a local win

This maps directly to Kotter’s “guiding coalition” and “short-term wins.” Instead of aiming at company-wide change from day one, produce a success case within arm’s reach first—and let it spread.

For a PM or tech lead, a five-meter radius usually means:

Your own squad or scrum team (5-10 people)
Your direct reports (3-5 people)
A specific repo or service where you have technical authority

That’s where you run experiments with new development flows, new review culture, new AI tool patterns, and surface the results. If word-of-mouth and internal Slack carry those results to other teams, you now have a negotiation lever for promoting the change to a company-wide initiative.

Observation lens: five-meter strategy vs. empty slogan

Performative signs: repeats slogans like “start small” and “ship a small win” but has no concrete design for the experiment—no metrics, no retrospective records. Six months in, they can’t tell you what changed
Functional signs: experiment duration, success criteria, and exit conditions are written down, and results are reviewed with actual numbers. There’s a concrete negotiation process running to propagate successful small experiments to other teams
Harmful signs: hoards the small success as personal credit and deliberately blocks replication (withholds access so other teams can’t reproduce it, dismisses similar parallel efforts). Treats the five-meter radius as a personal fiefdom and kills off the organization’s chance to learn

Management democratization and shared leadership

Sakai advocates a “management democratization model”—making management and people-development theory usable not just by managers but by everyone².

Academically this overlaps with shared leadership. Multiple meta-analyses report a robust positive relationship between shared leadership and team outcomes, and the effect is stronger where task interdependence and within-team trust are both high¹². Whether task complexity moderates the effect is less settled (Nicolaides et al. 2014 report stronger effects at higher complexity, D’Innocenzo et al. 2016 observe the opposite tendency)¹⁴. In IT development—where interdependence and trust drive outcomes—the structure where every member owns a slice of leadership likely outperforms a single leader deciding everything.

Psychological safety as a precondition

For shared leadership to function, though, psychological safety has to exist first. Edmondson (1999), studying 51 manufacturing teams, showed that psychological safety (a team’s shared belief that interpersonal risk-taking is safe) elevates team performance through the mediating mechanism of learning behavior⁸.

A leader who wants to break the status quo has to set up an environment where the members can challenge existing premises too, not just the leader. Concretely:

Respond to “there’s no precedent” or “what we have works fine” not with hostility but with constructive questioning
Treat a member’s failure as learning material, not grounds for blame
Openly share your own judgment errors

None of this is moralism. It’s the technical precondition for shared leadership to work.

Observation lens: psychological safety vs. “everyone gets along”

The core test is whether bad news reaches the leader. In a performative environment, the team atmosphere is warm, there’s no visible conflict, but substantive dissent and bad news never reach the leader—and afterward the leader laments “why didn’t anyone tell me sooner,” repeatedly. In a functional environment, members can say “I disagree” or “this approach carries risk” openly, bad news surfaces early, and the leader responds with questions rather than blame. In a harmful environment, the member who raised the bad news gets labeled “negative” or “a complainer” and pays for it in evaluations or assignments; members showing signs of mental strain get treated as “no longer combat-ready.” At that point it’s not psychological safety—the baseline affect is psychological fear.

The final condition: persistence

One more of Sakai’s central lines: “Only the people who persist change their companies”².

Commitment, the four thinking modes, resistance-minimizing skills, the five-meter-radius strategy—none of these pay back in the short term. The coordination cost is heavy, the time to results is long, and critics and dropouts show up throughout.

This is where the distinction between commitment and rational judgment shows up most sharply. A leader operating on rational judgment quits when they judge the cost no longer matches the expected return (because that’s rational). A leader operating on commitment sees the cost and carries through anyway. The difference between the two isn’t ability or intelligence—it reduces to a single question: do they own the outcome personally, in their own name?

Observation lens: persistence vs. stubbornness

Performative signs: when short-term results don’t arrive, externalizes (“the environment was wrong,” “team execution was weak”). Or conversely, keeps going past obvious failure and outsources the “we should stop” call to a team member
Functional signs: whether the decision is to pull out or to push on, they put their own name on the conclusion. If they pull out, they record “what we learned” and “how we’re updating our decision criteria” as institutional knowledge
Harmful signs: pushes failure onto subordinates while retroactively constructing “I expressed concerns early on” as their own position. Edits or deletes inconvenient past statements in Slack or meeting notes, or obfuscates with “I don’t recall”

Summary

The conditions for a leader who breaks the status quo aren’t charisma or personality traits. They’re the following decomposable skill set:

The conceptual distinction between commitment and rational judgment: recognize that “we need more data” in a domain where data will never resolve the call is decision avoidance
Four thinking modes: deploying critical thinking, backcasting, agile thinking, and diversity-oriented thinking situationally
Resistance-minimizing skill: pitch design, respectful dialogue, deliberate engineering of short-term wins
The five-meter-radius strategy: don’t aim at company-wide transformation; produce a local win on your own team first
Psychological safety and shared leadership: build an environment where members can commit in the same way
Persistence: commitment isn’t a one-time choice, it’s the act of carrying through to the end

And each condition has an observational counterpart. What blocks status-quo-breaking isn’t only the leader who can’t commit; it’s also the leader who performs leadership on the surface while showing harmful signs underneath. A regular observational practice—watching whether you’ve drifted to that side, whether the decision environment around you is under that kind of influence—is part of the skill.

In AI-era IT organizations, the fantasy that “data will produce the answer” has never been stronger. But the changes that actually matter—rolling out AI coding, overhauling architecture, shifting review culture—live in the zone where you propose a hypothesis before the data is in and own the outcome yourself.

A non-charismatic, ordinary leader starting from a five-meter radius and persisting until the organization changes—that’s not abstraction. It’s a concrete combination of decomposable skills and repeatable process, and it’s an option you can start on today.

The axis that cuts across every section

Lining up the observation lenses from each section, the behaviors that separate performative leaders from actually-functional ones converge on essentially a single axis.

Are they putting their own name on it?

Is the decision being issued in their own name? (In rational judgment theater, when it fails the grammatical subject shifts to “the data,” “the team,” or “the environment”)
Are they applying to their own assumptions the same scrutiny they apply to other people’s? (Asymmetry between criticism of others and criticism of self is a signature of critical-thinking theater)
Are direction, exit criteria, and learnings being written down? (What isn’t written can be reinterpreted later to any desired shape)
Is dissent being recorded? (Under a leader who doesn’t, member diversity is purely ornamental)

Whether a junior is evaluating their manager, leaders are evaluating each other, or a leader is self-examining—this single axis surfaces most of what matters. And for the leader’s own reflection: it enables “was I committing today, or was I performing commitment?”

When harmful signs cluster—the self-correction circuit breaks down

The hardest case to handle is when multiple harmful signs appear simultaneously. The canonical pattern is: “doesn’t update their own knowledge (under-studied)” + “rejects talented people’s opinions as threats” + “surrounds themselves with homogeneous yes-people.” Read not as a grab-bag of flaws but as a state in which the organization’s self-correction circuit has stopped functioning, the pattern becomes easier to understand. To be explicit: this isn’t a character-evaluation checklist, it’s an observed composite pattern of behavioral signals.

What makes this cluster tricky is that the three together systematically suppress the person’s own metacognition. External information doesn’t come in (under-studied), what does come in gets deflected as threatening (dissent rejection), and nobody around them points it out (yes-people arrangement). Interventions that rely on the person’s own self-awareness (learning thinking methods, building reflection habits, etc.) tend to show limited effect in practice.

What works realistically here is a layered design that doesn’t depend on the person’s goodwill alone.

At the individual level: without an external shock (business deterioration, talented people leaving, leadership turnover, outside warning), essential change is unlikely
At the peer/member level: the realistic options reduce to exit and documentation. The most capable people leave earliest, so the turnover rate itself functions as an organizational warning indicator. Those who stay can preserve verifiability by keeping personal notes or formal meeting minutes of dissent raised and rejected
At the organizational level: 360-degree reviews, making subordinate turnover a leader evaluation metric, skip-level 1-on-1s (the leader’s leader meets directly with the team), anonymous channels—oversight mechanisms that don’t depend on the person’s self-reporting are what actually bite

One thing worth emphasizing: harmful signs are not just an extension of performative signs. Performative leadership is “the intent is there but execution is weak,” and there’s room for skill-building and environmental change to improve it. Leadership with harmful signs, by contrast, has incentives pointing toward obstructing organizational learning in order to protect the leader’s position, and self-initiated change is structurally unlikely. Treating both the same way leads to being too harsh on improvable leaders and too optimistic about structurally-locked ones.

References

Numbered in reading order, matched to the inline citations.

Other references (not numbered in the text)

[Behavioral Approach Leadership Theory

PMs Who Break the Status Quo](https://ai-mikan-ch.com/action-oriented-approach-leadership/) - ai-mikan-ch.com (2026). Japanese source. [Reliability: Needs verification] (Supplementary material on the shift from trait theory to the behavioral approach)

“Commitment” and “rational judgment” are completely different / Don’t drift with trendy concepts / Do work you can be proud of at the end of your life (Futa Sakai: Organizational Reform in Practice, Starting from One Person) - NewsPicks NewSchool Lite (2025). Japanese source. [Reliability: Medium] ↩︎ ↩︎² ↩︎³
Reduce manager burden, grow the business—”Management Democratization Model” - Agend, interview with Futa Sakai, CEO of Momentor (July 2024). Japanese source. [Reliability: Medium] ↩︎ ↩︎² ↩︎³ ↩︎⁴ ↩︎⁵ ↩︎⁶
Four Ways of Thinking Required of Leaders Facing an Era of Upheaval - Insource Group Content Development (2025). Japanese source. [Reliability: Medium] ↩︎ ↩︎² ↩︎³ ↩︎⁴ ↩︎⁵ ↩︎⁶
Improving Organizational Effectiveness through Transformational Leadership - Bass, B. M., & Avolio, B. J. (1994). Sage Publications. [Reliability: High] ↩︎ ↩︎² ↩︎³
Ten Steps for Those Who Want to Break the Status Quo Without a Fight: Skill, Not Just Courage, Is Required - Timothy R. Clark, DIAMOND Harvard Business Review (2024). Japanese source. [Reliability: Medium-High] ↩︎ ↩︎²
The 8-Step Process for Leading Change - Kotter Inc. [Reliability: Medium-High] ↩︎ ↩︎² ↩︎³
Leading Change: Why Transformation Efforts Fail - Kotter, J. P. (1995). Harvard Business Review, 73(2), 59-67. [Reliability: High] ↩︎ ↩︎²
Psychological Safety and Learning Behavior in Work Teams - Edmondson, A. C. (1999). Administrative Science Quarterly, 44(2), 350-383. DOI: 10.2307/2666999. [Reliability: High] ↩︎ ↩︎²
Status Quo Bias in Decision Making - Samuelson, W., & Zeckhauser, R. (1988). Journal of Risk and Uncertainty, 1(1), 7-59. DOI: 10.1007/BF00055564. [Reliability: High] ↩︎ ↩︎²
The Entrenched “Precedent and Other-Company-Case” Worship: How Innovation Gets Killed This Way - Nikkei xTECH (2013). Japanese source. [Reliability: Medium] ↩︎
Light a Fire Under Middle Management—Management That Grows People and Changes Organizations - Persol Career techtekt, dialogue with Futa Sakai, CEO of Momentor (June 2025). Japanese source. [Reliability: Medium] ↩︎
A Meta-Analysis of Shared Leadership: Antecedents, Consequences, and Moderators - Wu, Q., Cormican, K., & Chen, G. (2020). Journal of Leadership & Organizational Studies. [Reliability: High] ↩︎ ↩︎²
It’s Time to Abolish the 70% Change Failure Rate Statistic - Enclaria (2014). [Reliability: Medium] (Explanation of the mixed attribution of the 70% statistic) ↩︎
The Shared Leadership of Teams: A Meta-Analysis of Proximal, Distal, and Moderating Relationships - Nicolaides, V. C., et al. (2014). The Leadership Quarterly, 25(5), 923-942. And A Meta-Analysis of Different Forms of Shared Leadership–Team Performance Relations - D’Innocenzo, L., Mathieu, J. E., & Kukenberger, M. R. (2016). Journal of Management. [Reliability: High] (Sources of the conflicting reports on the moderating effect of task complexity) ↩︎

Career & Work

This post is licensed under CC BY 4.0 by the author.