In Communication

Much of how respect is experienced comes down to tone—particularly in written communication, where brevity is common
and intent is not always clear.

A short email can read as efficient or dismissive, depending on context. A direct message can feel focused—or abrupt. Associates are attuned to these distinctions.

Messages like “See me” or “Call me,” without context, rarely create urgency alone. More often, they create uncertainty. They shift attention away from the work itself and toward interpretation—what went wrong, what is expected, and how the interaction will unfold.

Over time, patterns in communication begin to signal more than the substance of the message. They signal how approachable a partner is, how feedback will be delivered, and whether questions are welcome.

In that sense, tone is not incidental to leadership. It is one of its most visible expressions.

For partners, small adjustments in communication can meaningfully shift how that tone is received. Providing even a brief line of context—“nothing urgent, but let’s connect when you have a moment”—can eliminate unnecessary anxiety. Framing requests with timing—“tomorrow is fine” or “when you have availability”—creates clarity without sacrificing efficiency. And when possible, replacing ambiguity with specificity allows associates to focus on the work rather than interpreting the message.

These are minor changes in form. But from the associate perspective, they signal something significant: awareness, intention, and respect.

In Recognition

Recognition in law firms is often associated with outcomes—successful deals, favorable rulings, or strong work product.

From the associate perspective, respect is often conveyed earlier and more simply through acknowledgment like a brief note recognizing effort, a moment taken to confirm that work was helpful, or an indication that time invested was seen. These moments are easy to overlook, particularly in fast-moving practices. But their absence is not.

When effort goes unacknowledged, associates do not assume it was understood. More often, they assume it was unnoticed—or expected without consideration. Over time, this shapes engagement. Associates become more transactional in their approach, mirroring what they experience.

Recognition does not require formality. It requires attention.

In practice, this can be as simple as incorporating acknowledgment into existing workflows—adding a line when returning edits, noting when a turnaround was particularly quick, or following up after a filing or closing to recognize the contribution. Even brief, specific recognition—“this section was especially strong” or “this was helpful in moving things forward”—carries disproportionate weight.

These moments do not interrupt the pace of work. They reinforce it.

In Feedback

Few areas communicate respect—or the lack of it—more clearly than feedback.

Edits returned without explanation may be efficient, but they leave associates to infer reasoning on their own. In some cases, that inference is correct. In others, it is not. What is lost in that gap is development.

Associates will often view redlines as stylistic—preferences rather than substance. But in many cases, those edits reflect something more deliberate. Experienced partners are not simply revising language; they are shaping tone, framing arguments, and refining how a point will be received by a client, court, or counterparty.

Persuasive writing, in particular, is rarely accidental. Word choice, structure, and emphasis are often doing more work than is immediately visible. When that reasoning is not shared, the edit is seen—but the judgment behind it is not. The result is missed learning and, over time, missed alignment. Even brief context—why a change was made, what a client may expect, how an argument could be strengthened—transforms feedback from correction into instruction.

The same is true in how assignments are handled. Work that is reassigned without explanation, or priorities that shift without context, can feel less like coordination and more like instability.

Associates do not expect exhaustive explanations. But they do notice when none are given.

And over time, that distinction becomes meaningful.

Partners can address this without materially increasing their time investment. A short summary at the top of a redline—identifying key themes in the edits—can orient an associate immediately. Calling out one or two recurring points—tone, structure, or framing—provides clarity without requiring line-by-line explanation. And when work is reassigned or priorities shift, a brief explanation—“this needs to move more quickly than expected” or “we’re adjusting approach based on client feedback”—grounds the change in context rather than leaving it open to interpretation.

These practices do more than improve work product. They make visible the judgment that underlies it.

The Accumulation of Small Moments

Rarely does a single interaction define how respect is experienced.

It is the accumulation that matters.

An abrupt email here.
An unexplained edit there.
A missed acknowledgment after a long stretch of work.

Individually, each moment is easy to justify. Collectively, they form a pattern.

And that pattern answers a question associates are always, if quietly, considering:

Am I being treated as someone worth developing—or simply as someone relied upon to produce?

For partners, this means that consistency—not perfection—is what ultimately shapes perception. Small habits—adding context, acknowledging effort, explaining changes—compound quickly.

And just as quickly, their absence does the same.

The Bottom Line

Respect is not built through occasional, visible acts. It is built—or eroded—through repeated, everyday interactions.

An email can shape the tone of a day.
Over time, it can shape the tone of a relationship.

Associates are not looking for perfection. They are looking for signals.

Signals that their work is understood.
That their time is valued.
That their development matters.

Those signals rarely come from formal processes.

They show up in the small moments.

Weekly Reflection: If your day-to-day interactions were the only measure of your leadership, what would they suggest about how you value your team?