Fluency in Context: How Leaders Signal Expertise Through Cultural Literacy
The courthouse hallway hums with the particular anxiety of the accused—paperwork clutched in hand, eyes scanning for familiar faces among the suits. In this liminal space of *Better Call Saul*, Jimmy McGill spots them: two defendants already represented by a prestigious firm, yet visibly adrift. They have counsel, certainly, but they lack representation. The incumbent attorney practices criminal law; what they require is someone who understands criminality. When McGill approaches, he does not lead with his credentials from the University of American Samoa or his stint at Hamlin, Hamlin & McGill. Instead, he opens with a linguistic feint so precise it functions as both diagnosis and cure. “You don’t need a criminal lawyer,” he tells them, pausing just long enough for confusion to register. “You need a criminal lawyer.”
The scene, early in the show’s second season, finds McGill operating in the aggressive gray market of client acquisition. These defendants have retained a name-brand defense attorney—technically proficient, institutionally respected, yet utterly disconnected from the operational reality of their predicament. They face not merely charges but the intricate machinery of bail schedules, prosecutorial discretion, and the coded negotiations that occur in courthouse corridors rather than courtrooms. McGill recognizes what they actually require: not a jurist who understands the penal code, but an operator who knows how to work the system, who understands that justice is often administered through relationships rather than statutes.
The distinction hinges on a grammatical ambiguity that McGill weaponizes with surgical care. A “criminal lawyer” (adjective-noun) denotes professional specialization—someone who practices criminal law. A “criminal lawyer” (noun adjunct) implies moral alignment with the client’s worldview, someone who inhabits the same shadow economy. By collapsing these meanings into a single phrase, McGill signals that he is not an interpreter standing between them and the institution, but a native speaker of their dialect. The line works not because it is clever, but because it demonstrates that McGill comprehends the gap between institutional legitimacy and operational reality—a gap his competitors, for all their credentials, cannot even perceive.
This moment illuminates a critical dimension of executive influence: expertise is often established not through credentialing but through cultural fluency. In complex systems—whether criminal justice, healthcare, or financial services—formal authority frequently fails to deliver actual utility. The leader who can demonstrate insider status, who can speak the submerged language of a community, wields a persuasive power that outstrips hierarchical rank. McGill’s repositioning exemplifies what sociolinguists call “code-switching as credibility marker.” By deploying terminology that resonates with the defendants’ lived experience rather than their legal documentation, he reframes the purchase decision entirely. The sale is no longer about expertise (which the incumbent possesses in abundance) but about alignment (which only McGill can offer).
For executives, this suggests that strategic repositioning often requires abandoning the vocabulary of competence—certifications, methodologies, frameworks—in favor of linguistic precision that signals systemic comprehension. When a leader speaks with granular accuracy about the constraints, frustrations, and shadow economies of a particular domain, they communicate something that bullet points cannot: they have been in the trenches, not merely studied the maps. This is the difference between epistemic authority (knowing about) and experiential authority (knowing within). McGill does not tell the defendants he understands their world; he demonstrates it by speaking in a register that would be invisible or inappropriate to an outsider.
Consider a consultancy advising mid-market manufacturing firms facing supply chain disruption. The temptation is to enter with frameworks—Lean Six Sigma, agile procurement, digital transformation matrices. Yet the plant manager confronting a union negotiation and a quarterly production deadline does not need methodology; they need someone who understands the specific political economy of their shop floor. The consultant who opens by referencing the “Thursday afternoon scheduling dance with the Teamsters steward” or the particular way that maintenance overtime accrues under the current collective bargaining agreement signals fluency in a way that case studies cannot. Like McGill, they demonstrate that their expertise is embedded rather than imported, proving they understand not just how factories should work but how this factory actually works.
When a data breach exposes customer information, technical leadership often retreats into forensic specificity—hash algorithms, encryption standards, dwell times. But the board and the public do not need a cybersecurity expert; they need a crisis operator who understands the narrative velocity of social media and the regulatory theater of breach notification. The CTO who can articulate not just what happened but how the story will metastasize through Reddit threads and plaintiff-bar websites within twelve hours, who can predict which specific regulator will care about which specific data field, demonstrates the “criminal lawyer” instinct. They prove they know the system from the inside out, not just the technical specifications. This fluency allows them to reframe the conversation from technical remediation to institutional survival.
Technology firms competing for specialized engineering talent frequently default to compensation benchmarking and culture platitudes about “mission” and “impact.” Yet the senior engineer considering leaving a FAANG company for a Series B startup is not optimizing for salary; they are calculating technical autonomy against political risk, estimating how many quarters of technical debt they can tolerate before the product roadmap collapses. The founder who can speak precisely about “how architecture decisions get overruled when Series C pressure hits in Q4,” or who references the specific frustration of watching microservices decay into distributed monoliths, signals that they have inhabited the engineer’s professional trauma. They prove they are not merely hiring talent but hosting refugees from broken systems, demonstrating an insider’s understanding of the difference between writing code and shipping product.
The next time you find your credentials failing to persuade, consider what fluency you might be withholding. In which domains do you speak the language of the initiate rather than the observer? When was the last time you demonstrated expertise not by listing what you know, but by revealing how deeply you understand the world your stakeholders actually inhabit? The answer may determine whether you are seen as a specialist in your field or a genuine operator within it.