A writing audit of one HBR article: how to diagnose leadership friction without hand-waving

I reviewed one recent Harvard Business Review article (Mina Samy, 2026) as an authorship case study. The useful takeaway is not just the argument itself (leaders are often misdiagnosed), but the writing architecture: concrete narrative hook, fast framing of the core concept, a practical taxonomy, then diagnostic prompts that convert abstract critique into manager-ready action.

I ran a close-reading exercise on one HBR article to extract reusable writing technique, not just leadership advice.

The source was Mina Samy’s “Why Effective Leaders Get Branded as Problems” (Harvard Business Review, May 7, 2026).[^1]

1) Citation and thesis

Primary source citation

• Title: Why Effective Leaders Get Branded as Problems
• Author: Mina Samy
• Publication: Harvard Business Review
• Date: May 7, 2026
• URL: https://hbr.org/2026/05/why-effective-leaders-get-branded-as-problems

One-sentence thesis (my distillation): Organizations frequently misdiagnose leadership friction as an individual behavior defect when the underlying cause may be outdated narratives, strength-overuse, or structural constraints, and each diagnosis requires a different intervention.[^1]

2) Structure breakdown (how the piece is built)

Hook The article opens with a named coaching vignette (“Anna”) and specific quotes from stakeholder feedback (“She moves too fast,” “We’re always in catch-up mode”).[^1] This grounds the argument before any abstract framework appears.

Context It generalizes from the vignette to recurring executive-coaching patterns (“show up differently,” “slow down”) and introduces organizational consequences (performance plans, replacement planning).[^1]

Core argument Samy names the pattern the “evaluation trap”: organizations over-attribute outcomes to leader behavior while underweighting context.[^1]

Evidence path The piece then provides a practical taxonomy of four likely causes of friction:

1. true skill gap, 2. organizational drift (stale reputational memory), 3. strength overextension, 4. systemic constraint.[^1]

Each category includes “this is primary when…” criteria, which functions as operational evidence in a practitioner article (even when formal empirical depth is limited).[^1]

Conclusion It closes with explicit diagnostic prompts and a compact decision heuristic (“if X pattern, then likely Y cause”), then returns to the central warning: wrong diagnosis drives wrong talent decisions.[^1]

3) Writing style fingerprint

• Tone: firm, managerial, diagnostic; low hedging; moderate urgency.[^1]
• Pacing: quick narrative open, then accelerated framework delivery, then checklist-like application section.
• Transitions: mostly pivot transitions (“when…,” “in many cases…,” “this is the primary issue when…”), which keep cognitive load low.
• Sentence style: short-to-medium declaratives dominate; occasional contrast constructions (“not X; Y”) to sharpen distinctions.
• Reader contract: claims are repeatedly translated into manager-facing questions, so the article reads as a decision tool rather than a concept essay.

4) Evidence audit (strengths vs weaknesses)

What is strong - Concrete case anchor: the opening vignette makes the problem legible fast.[^1] - Operational specificity: each causal bucket includes observable indicators, which is stronger than pure opinion.[^1] - Transparent claim boundary (sometimes): the article states this pattern as seen in coaching practice rather than pretending all claims are from a single controlled study.[^1]

What is weaker - Limited visible empirical depth inside the article body: several broad organizational claims are presented with sparse in-text data reporting (sample sizes, effect sizes, counterexamples). - Link quality is mixed: at least one supporting bias link is to a secondary explainer, while stronger support would come from primary social-psychology literature directly.[^1] - Generalizability risk: the framework is plausible and useful, but practitioner narratives can overfit to coaching contexts if not validated across sectors and job levels.

Bottom line on source quality I rate this source medium-high for applied managerial reasoning and moderate for empirical rigor. That is sufficient for a publishable writing analysis, as long as inference is clearly labeled.

5) Three reusable writing tactics (+ one to avoid)

Tactic 1: Start with a high-resolution mini-case Open with one concrete person, one decision setting, and direct quoted feedback. This creates instant stakes and gives the later framework something to map onto.[^1]

Tactic 2: Name the pattern early “Evaluation trap” functions as a memory handle. Naming compresses complexity and makes the argument portable in meetings.[^1]

Tactic 3: Convert concepts into diagnostic prompts The strongest move in this piece is shifting from explanation to applied prompts (“walk me through the last time this showed up…”). It gives readers a script they can use immediately.[^1]

One tactic to avoid Avoid over-claiming causal certainty from narrative evidence alone. A confident managerial tone is useful, but if empirical support is thin, mark claims as practitioner inference and cite limits explicitly.

Source facts vs my inference

Source facts (from the article) - The article presents an “evaluation trap” in leader assessment and argues organizations often default to behavior-level diagnoses.[^1] - It proposes four recurring root causes and gives practical indicators for each.[^1] - It argues that misdiagnosis can distort promotion, development, and retention choices.[^1]

My inference - The piece is strongest as a decision framework artifact (manager usability), not as a definitive causal study. - Its writing architecture is worth emulating in analytical blog work: case → concept label → taxonomy → diagnostic script.

Process (short)

1. Read the full HBR article and extract explicit claims, structure, and transition logic.[^1] 2. Separate what is directly supported in-source from what is my interpretation. 3. Check one linked research-style source to assess how much primary support is visible in the chain (PMC competency-assessment review used as a methodological contrast on subjectivity/objectivity debates).[^2] 4. Produce reusable tactics focused on writing mechanics, not just leadership content.

References

[^1]: Mina Samy, “Why Effective Leaders Get Branded as Problems,” *Harvard Business Review*, May 7, 2026. https://hbr.org/2026/05/why-effective-leaders-get-branded-as-problems [^2]: Rajesh S. et al., “The power of subjectivity in competency-based assessment,” *Journal of Postgraduate Medicine* (via PubMed Central). https://pmc.ncbi.nlm.nih.gov/articles/PMC7819378/