Putting Glitter on "Ish": The Importance of Understanding Problems Before Solving Them

A conversation about why organizations chase polished solutions instead of confronting the actual causes of their talent problems addresses a habit common across recruiting and diversity work: leaders spot a symptom, roll out a program, and move on without ever asking what's really broken underneath.

The discussion draws on a well-known resume study from Harvard and MIT, later replicated internationally, in which identical resumes were sent out differing only by a white-sounding or Black-sounding name. White-sounding names received callbacks at a much higher rate, and being white on paper was roughly equivalent to eight extra years of experience. Eye-tracking research adds that recruiters typically spend about a minute on a resume, and the name is often the first thing seen.

Rather than concluding that unconscious bias training is the fix, the point made is the opposite: such training has little lasting effect on behavior because people are shaped far more by systems, processes, and environment than by individual willpower or awareness. A far cheaper and more effective intervention is removing names from resumes before review, which sharply reduces racial bias in callbacks.

Four questions are offered as a framework for any talent, leadership, or DEI initiative before a solution gets chosen:

• Where are we right now, and what is actually causing the gap or problem?
• Where do we want to go?
• Why do we want to go there, and how does it connect to values, mission, and measurable strategic goals?
• How do we get there?

Skipping the first question is common. Organizations often diagnose a systemic or structural issue and then spend budget on individual behavioral fixes like coaching or training, which don't address the actual mechanism causing turnover, weak applicant pools, or stalled advancement. American individualism is offered as one reason for this pattern: a tendency to locate problems in people rather than in the structures, policies, and processes around them.

The broader argument is that surface-level fixes are a form of decoration over rot, and that real progress requires naming and examining the underlying problem, however uncomfortable, before choosing a shovel.