Workplace communication and practical Nonviolent Communication

Words That Work in Business Summary: NVC at Work Without Awkward Scripts

Words That Work in Business helps readers practice NVC internally and translate it into ordinary workplace requests, so using the method does not depend on coworkers learning its terminology.

One-Sentence Answer

Words That Work in Business helps readers practice NVC internally and translate it into ordinary workplace requests, so using the method does not depend on coworkers learning its terminology.

What The Book Is About

You leave a communication workshop with a useful model, try it on a colleague, and receive a puzzled look. This is the problem Lasater addresses: how to carry a different intention into an established workplace without turning each exchange into a demonstration of a formula.

The second-edition publisher page credits Ike Lasater as author and Julie Stiles as editor, and identifies difficult conversations, feedback, meetings, and workplace relationships as the book's territory. The authorized sample makes the learning problem especially clear: NVC concerns connection and intention, while sentence patterns are aids to practice. This is not Frank Luntz's Words That Work, a different book about how messages are heard. Lasater's volume applies needs-based communication to the person you must work with again tomorrow.

Who Should Read It

Read it if a recurring exchange with a colleague brings out a reaction you dislike, or if you know the NVC distinctions but hesitate to use them in your organization's normal language.

It is less suitable as your only introduction to NVC. It also does not replace employment procedures, a fair investigation, workload decisions, or a formal boundary. If the obstacle is a resource shortage or a manager punishing reasonable disagreement, better phrasing alone will not remove it. The book is strongest when you have some room to change how you prepare, listen, ask, and learn from an exchange.

Main Summary

Lasater treats workplace NVC as a skill that can be developed in small, repeated attempts. Knowing a sequence of words is different from being able to use it while stressed, interrupted, or worried about professional standing. The book therefore addresses the gap between understanding a method and having it available during an ordinary workday.

Its practical emphasis includes silent practice, requests, and learning from what happened. You can examine your reaction internally before trying a new sentence aloud. You can also consider another person's possible needs without declaring that you know their motives. This gives the method a place in workplaces where explicit emotional vocabulary might feel unusual or be received badly.

The opening sample uses Lasater's experience as a trial lawyer to illustrate the difficulty of changing communication in a setting with strong expectations. Its broader lesson for this guide is that professional conventions need not dictate every possible response. You can remain recognizable within a role while asking more clearly for what would help the work.

The book's learning cycle also changes what happens after an unsuccessful exchange. Instead of merely blaming yourself or the colleague, examine which needs your response served and which it left unmet. Keep what worked and rehearse a more useful alternative. This does not excuse a harmful remark; an apology or repair may still be necessary.

For a concrete application, imagine operations receiving incomplete sales handoffs. The usual response is an accusatory message, followed by defensiveness and another incomplete file. A different preparation could identify the missing information, the operational risk, and one realistic request. It is to establish a usable agreement while preserving the ability to discuss obstacles. The handoff case developed below is an original exercise, not a case from the book.

Key Ideas

1. Start internally when speaking the formula would get in the way

Lasater gives silent practice a place in workplace learning. The distinction is useful because many people assume they must either announce NVC or abandon it. An internal pause creates another option: use the distinctions to understand your reaction, then choose words that suit the conversation.

Suppose you read a handoff note that says the customer is ready, but the promised service date is missing. Your immediate thought is that sales never does the job properly. Before replying, ask what that thought is trying to protect. Perhaps you need reliable information to schedule staff. Perhaps you also want your team's work recognized. Separating those concerns makes a more precise response possible.

Then consider the sender's possible situation. They may be under pressure to complete a sale, may not know which field is essential, or may have omitted it carelessly. Those are competing possibilities. Silent empathy is a way to reduce premature certainty, not a license to pick a flattering explanation and treat it as fact.

Your eventual message might simply ask for the service date before a stated scheduling deadline. There is no requirement to display every internal step. The measure is whether you can speak more honestly and listen more accurately. If a private pause becomes a way to avoid raising a real problem indefinitely, it has lost its purpose. Use it to prepare contact, rather than replacing the contact the work requires.

2. Separate the intention to connect from a memorized sentence

The authorized sample explicitly distinguishes NVC's intention from its syntax. Practice language can help you notice differences among observations, judgments, feelings, needs, requests, and demands. Yet the wording used for learning need not be delivered unchanged in every professional setting.

In a project channel, a long emotional statement can obscure a simple operational question. Conversely, a very short instruction can conceal an unspoken accusation. Work on both layers. First clarify internally what happened and why it matters. Then ask what the other person needs to hear to understand the issue and respond.

For example, an operations analyst might write that two handoffs arrived without a service date, that scheduling cannot be completed without it, and that the date is needed by midday. This is ordinary business language. The message is more credible if the analyst is also prepared to hear that the customer has not confirmed a date. That information may require a different workflow, not merely more forceful wording.

Do not use natural language as an excuse to remove the substance of a request. A pleasant message saying it would be great if everyone could be more mindful still leaves people guessing. Equally, do not grade a colleague's sincerity by whether they use the vocabulary you learned. The book is useful when it makes a real exchange clearer. It becomes less useful if it creates a new standard by which one employee is always the enlightened speaker and everyone else is a problem to correct.

3. Make the next request smaller than the whole relationship problem

Clear requests are a central part of Lasater's approach. The practical challenge is that a workplace complaint often carries several months of history. A single message then asks the recipient to repair trust, become more considerate, improve quality, and meet a deadline all at once.

Reduce the immediate request to an action someone can identify. In the handoff case, ask the account owner to fill one missing field or mark the date unconfirmed by a specific time. Leave room to explain an obstacle. This produces information for the next conversation.

An answerable request also reveals whether the proposed action fits the problem. If sales cannot supply a date before customer approval, repeatedly demanding the field earlier will not help. You may need an explicit provisional status, a different handoff point, or a person responsible for chasing confirmation. The exchange becomes more useful when a refusal or difficulty can change your understanding of the process.

There are limits to how much choice exists at work. A required compliance step may remain mandatory. State that honestly rather than pretending every instruction is optional. Even then, you can discuss timing, support, unclear definitions, or what to do when completion is impossible. Clarity about authority and consequences makes the conversation more trustworthy. It prevents a courteous phrase from disguising a demand that everyone is expected to recognize but nobody is allowed to name.

4. Use the aftermath of a mistake as practice material

The book's learning cycle includes noticing needs met and unmet, along with mourning and celebration. For a communication reader, the value is a more specific response to the moment when you realize you handled an exchange badly. Instead of deciding you are hopeless or that the other person made you react, examine the actual sequence.

Take a message you regret. What did you notice before sending it? What did you hope the sharp wording would achieve? What did the reply reveal? Perhaps the message secured a fast answer while damaging willingness to raise future difficulties. Both outcomes belong in the account. Recognizing one need met does not require ignoring the cost to another.

If repair is appropriate, address the behavior and its impact. An apology followed immediately by a lecture about the colleague's mistakes is unlikely to help. Acknowledge your own contribution first, then arrange a separate discussion of the underlying issue. This is an application of the learning emphasis, not a scripted sequence prescribed by the book.

Choose one alternative to rehearse. You might practice asking for missing information without making an inference about character. The goal is to make a different response easier to reach next time. Record evidence of progress as well: you paused, asked one question, or discovered a constraint before escalating. Learning becomes more accurate when it can notice partial improvement without declaring the whole conflict resolved or demanding perfect calm in every interaction.

5. Practice within ordinary work instead of waiting for a major confrontation

The second-edition sample describes recurring practice opportunities and its Practice Pause prompts. That emphasis matters because a high-stakes dispute is a difficult place to learn an unfamiliar behavior. Repetition in smaller exchanges gives you a chance to discover which wording feels clear and which sounds artificial.

Choose a recurring event with a modest emotional charge. It could be an unclear calendar invitation, a handoff missing one detail, or a request that arrives without a deadline. Work on one distinction for several occurrences. For instance, ask for an observable completion condition rather than promising to communicate better in general.

Make the practice proportionate. You do not need to turn a two-line scheduling question into a facilitated dialogue. Nor should coworkers become involuntary subjects of an exercise. Use the practice to improve your own preparation, question, and follow-through. If you want feedback, ask whether the request was clear and what made it easy or difficult to answer.

After several attempts, look for a work-related result. Are fewer clarification messages needed? Does a colleague tell you earlier when a deadline cannot be met? Is there now an agreed meaning for a completed handoff? These are useful observations, not proof that the book caused an improvement. Many things influence a team. The discipline is to connect practice to a specific communication problem, keep the time cost reasonable, and change the exercise when it is no longer teaching you anything.

Practical Takeaways

  1. Save a tense draft message without sending it, and identify the missing fact or concrete event underneath its accusation.
  2. Name your immediate work need privately before deciding how much personal language belongs in the public exchange.
  3. Treat a guessed need in another person as a question to investigate, not an explanation to announce.
  4. Ask for one action, a completion condition, and a relevant time; explain the operational reason when it is not obvious.
  5. Separate a mandatory requirement from the aspects of implementation that can be negotiated.
  6. After a difficult exchange, record one need served, one need neglected, and one response to rehearse.
  7. Repair your own sharp remark before trying to teach the other person how they should have spoken.
  8. Select a small recurring communication problem and review whether practice is producing clearer agreements.

How To Apply It

An original case: a sales handoff that operations keeps rejecting

An operations analyst receives three customer handoffs without a confirmed start date. Sales considers the deals complete; operations cannot assign staff. The analyst begins composing a group message about sales promising things and leaving everyone else to fix them. This invented case uses the book's practice orientation without reproducing its examples.

First, keep the angry draft private and identify the actionable issue. Three records lack a date. The analyst needs enough notice to schedule coverage. The message should address that situation, rather than prove that a whole department has the wrong attitude.

Next, contact the account owner with a concise factual request. Ask for the date or an explicit unconfirmed status before the planning cutoff, and explain why it matters. The account owner replies that the customer will choose the date after technical approval. That answer changes the process problem: sales has been treating commercial completion and operational readiness as the same milestone.

Arrange a short discussion with the people who can change the handoff. Ask what each team needs before its next step. The analyst discovers that sales needs a way to stop tracking closed commercial tasks, while operations needs a named owner for the remaining date confirmation. Those concerns can coexist if the record contains two statuses rather than one misleading complete label.

Agree on a limited trial: mark commercial completion separately, retain the account owner for confirmation, and notify operations when the date is set. Confirm who will update the record and what happens if the date is still missing near the cutoff. The request becomes a workflow agreement instead of a recurring plea for greater consideration.

At the end of the week, inspect the next few handoffs. If information is still absent, ask whether the definition is unclear, the owner lacks access, or the extra work is unrealistic. Do not assume a new field solved the relationship. The useful change is a repeatable way to notice the issue, ask without accusation, and revise an agreement when the answer reveals something new.

Notable Ideas, Paraphrased

These are interpretive paraphrases, not direct quotations: you can practice a communication intention before speaking it aloud; the syntax is a learning aid rather than the whole skill; an answerable request makes obstacles visible; and a regretted exchange can become material for the next attempt. None means that an employee should tolerate retaliation or take sole responsibility for an organization's problems.

Best Related Books

  • Nonviolent Communication supplies the broader foundation. Lasater's book is a more focused choice when the difficulty is applying that foundation within normal professional exchanges.
  • Difficult Conversations is useful for examining competing interpretations and identity concerns before one consequential discussion. Compare it with Lasater's emphasis on repeated practice at work.
  • Humble Inquiry helps when status and assumptions prevent you from asking what you do not know. It offers a useful companion to the handoff problem's need for genuine questions.

Internal Links