Workplace Communication
Collaborating in the Workplace Summary: Practice Better Team Conversations
Collaborating in the Workplace treats teamwork as a set of conversational skills that people can rehearse: reconnecting with themselves, hearing another person, making workable requests, and learning from difficult exchanges.
One-Sentence Answer
Collaborating in the Workplace treats teamwork as a set of conversational skills that people can rehearse: reconnecting with themselves, hearing another person, making workable requests, and learning from difficult exchanges.
What The Book Is About
Ike Lasater's short practice guide brings Nonviolent Communication into ordinary working relationships. Its subject is what colleagues actually do when a request sounds threatening, a meeting becomes competitive, or an agreement turns out to mean different things to different people. It moves from personal preparation into conversation and then into recurring workplace situations.
Julie Stiles is credited as editor on the publisher's book page, while the sample title page describes the book as by Lasater with Stiles. Her contribution belongs in an account of the book; she is not presented here as a second principal author. This guide uses the May 2019 PuddleDancer paperback, ISBN 9781934336168, identified by the publisher's bookstore.
The important distinction is between possessing communication vocabulary and being able to use it during a tense interaction. Lasater emphasizes exercises, practice partners, and reflection. The book offers a way to build that capacity; it does not demonstrate that using a particular sentence will fix an unfair workload, override a colleague's refusal, or guarantee a productive team.
Who Should Read It
This is a useful choice for a team member who understands the task but struggles with the conversation around it. A coordinator receiving vague commitments, a supervisor whose feedback provokes defensiveness, or colleagues who repeatedly interrupt one another can connect the exercises to recognizable incidents.
It particularly suits readers willing to practice with another person. Reading a compact explanation of empathy is easier than listening without correcting someone, and the book expects that difference to matter. A manager can participate, but the exercises should not become compulsory disclosures of employees' private feelings.
Readers seeking a comprehensive account of organizational design will need something else. Responsibilities, compensation, authority, and staffing require decisions beyond conversational skill. Where there is harassment or retaliation, communication practice needs appropriate formal protections rather than an expectation that the affected employee will manage everyone's reactions.
Main Summary
Lasater organizes collaboration around the capacity to stay connected to oneself and other people while addressing practical work. The foundations concern noticing a stress response, identifying feelings and needs, and recovering enough presence to choose a response. The publisher's sample section develops these distinctions through explanations and exercises. A need is separated from a particular strategy for meeting it: someone may need reliability without needing one specific colleague to answer every message immediately.
The next movement applies those foundations to conversation. Listening comes before asking people to collaborate. A listener tries to understand the concern beneath the words and makes that understanding available for correction. Making a request then involves asking for something another person can actually consider doing. Agreement requires more than the absence of an objection.
Difficult conversations receive a practice sequence: prepare, rehearse, and debrief. Preparation includes attending to judgments and concerns before entering the exchange. Rehearsal gives people an opportunity to discover where their intentions disappear under pressure. Debriefing examines what happened without converting the entire exercise into another round of blame. The point is accumulated ability, not a single flawless performance.
Later applications address interruptions, refusals, feedback, and appreciation. These are small events with large effects on cooperation. A refusal can reveal a concern that an initial request overlooked. Appreciation can identify a specific helpful contribution instead of offering a vague personality assessment. Feedback can describe an effect and open a discussion about a next action.
The book's contribution is its connection between inner preparation and shared execution. Feeling calmer is not the finished task; colleagues still need to decide who will do what. Equally, a precise action list is fragile if people cannot raise doubts or renegotiate it. The five themes below are this guide's organization of those connected skills, rather than an official five-step method claimed by Lasater.
Key Ideas
1. Self-connection creates a pause in the work, not an escape from it
Lasater starts before the spoken request. When a person hears criticism, the immediate experience may include tension, a rapid defense, or an urge to withdraw. The book asks readers to notice that experience and attend to feelings and needs. In a workplace, this can help distinguish concern about doing good work from the impulse to prove that another department is incompetent.
Consider a designer hearing that a proof was sent late. The first interpretation might be that the coordinator is questioning the designer's commitment. A short pause could reveal something more useful: worry about being blamed for a delay caused by missing specifications. That distinction makes a different response possible. The designer can ask which deadline is being discussed and explain the missing information instead of defending an entire professional identity.
This is an application of the book's self-connection emphasis, not a claim that every reaction has one simple biological cause. People experience pressure differently, and a breathing pause is not treatment or a substitute for rest, support, or safe working conditions.
The practical test is what the pause enables next. If it produces only private insight, the coordination problem remains. If it helps someone state a concrete concern and hear the answer, it has become part of collaboration. A reader can practice with one recurring trigger, note the first interpretation, and rehearse a short factual question before returning to the discussion. The goal is increased choice rather than a performance of permanent composure.
2. Listening needs a visible check on understanding
The book connects listening with being listened to. A colleague cannot inspect another person's good intentions; they can hear whether the response reflects their actual concern. An understanding check therefore makes listening observable. It offers a tentative account and gives the speaker a chance to change it.
Suppose someone objects to adding a final review stage. Responding that everyone cares about quality may sound agreeable while missing the objection. The concern could be that the reviewer is unavailable during the evening shift. A more useful response asks whether the proposed stage would leave that shift unable to finish its work. The answer might confirm the concern, or reveal that the real issue is duplicated checking.
This distinction matters because listening can otherwise become a polite delay before the listener restates the original proposal. A correctable reflection changes the information available to both people. It can also expose a mistaken assumption before that assumption becomes a team commitment.
At work, understanding should remain proportionate to the task. A person may want their scheduling constraint understood without exploring their personal history. Guessing a feeling or need is an invitation to correction, not an authority to tell someone what they really mean. Readers can begin by reflecting the practical concern in ordinary language and asking whether anything important is missing. They should then allow the correction to affect the request. Listening that never changes the next question offers little evidence that understanding has occurred.
3. A request becomes useful when a refusal can inform it
Lasater gives attention both to making requests and to the need behind a refusal. These belong together. If the only acceptable answer is agreement, a question may function as an instruction or demand even when it ends politely. Sometimes a manager is giving a legitimate instruction; clarity about that authority is preferable to disguising it as a free choice.
For a genuinely negotiable request, the recipient needs to understand the action and be able to discuss its cost. Asking a colleague to be more responsive does not specify a behavior. Asking whether they can acknowledge rush-order messages before the afternoon production meeting is more discussable. They might agree, decline, or offer an alternative that fits the shift.
A refusal is not automatically evidence of unwillingness to help. The colleague may be protecting uninterrupted design time or responding to another deadline. These are possibilities to inquire about, not motives to assign. Once the concern is known, the team can consider a shared intake queue or a backup person rather than treating one worker's availability as the only solution.
The agreement also needs a shared meaning. What counts as acknowledgement? Which messages qualify as rush work? What should happen when a deadline cannot be met? These details are original applications of the book's request principle to operational work. They do not guarantee compliance. They make it easier to recognize whether people agreed to the same thing and when a new conversation is required.
4. Preparation, rehearsal, and debriefing turn an incident into a learning opportunity
The book treats difficult conversations as something readers can practice, rather than an exam of natural social ability. Preparation asks what judgments and concerns someone is bringing into the room. Rehearsal lets a practice partner respond in a way that reveals the speaker's habits. Debriefing then asks what can be learned from the exchange.
An employee preparing to raise interruptions might begin with a long explanation of why a teammate is disrespectful. Practicing that opening could show how quickly the discussion becomes a defense of character. A second attempt might identify a specific meeting, describe an unfinished point, and ask for a way to signal that a contribution is not complete. The rehearsal has changed the task from winning a moral case to negotiating participation.
Practice should not depend on making the partner an exaggerated villain. A useful partner can represent an ordinary competing concern: limited meeting time, uncertainty about when to speak, or a different memory of the event. This keeps the exercise open to information that the real conversation may contain.
Debriefing is most useful when it separates observations from verdicts. Where did the speaker speed up? Which question received an actual answer? At what point did the listener stop reflecting and begin rebutting? Readers can select one adjustment for another attempt. Repeated, focused practice gives the book its distinctive value; simply copying a polished script misses much of that learning process.
5. Feedback and appreciation can name contributions without fixing identities
Workplaces often use personality language when they need information about an action. Someone is called careless after one missed check, or brilliant after a successful delivery. Neither statement explains much about what other people could repeat or change. Lasater's attention to feedback and appreciation encourages a more concrete conversation.
For example, a production lead can identify that a designer flagged a missing specification before files reached the printer. That action allowed the team to clarify the job while changes were still possible. Appreciation now communicates a contribution and its significance. It offers useful information without suggesting that the designer is responsible for preventing every future mistake.
Difficult feedback benefits from similar specificity. Naming the missing confirmation, its effect on scheduling, and the need for a reliable handoff provides something to discuss. The person may have relevant information about the process. Treating feedback as a final diagnosis of their attitude would close that route too early.
The book also recognizes that receiving feedback is a skill. A listener may need to understand the incident before deciding whether they accept its interpretation. They can acknowledge an effect without endorsing every judgment attached to it. In practice, readers can prepare one piece of appreciation and one concern using an action, an effect, and a question about what comes next. This is a useful starting point for a conversation, not a formula that makes all evaluations fair or removes legitimate differences in responsibility.
Practical Takeaways
- Pick a recurring work incident rather than trying to improve every conversation simultaneously. Specify what happens and when.
- Before replying to criticism, identify the concrete concern you want addressed. A concern about missing information is easier to discuss than a verdict about respect.
- Reflect a colleague's task-related objection and invite correction before defending your proposal. Let the correction alter your next question.
- Make negotiable requests with an action and a timeframe. Where you are exercising authority, describe the requirement honestly.
- When someone declines, ask which constraint matters. Do not translate the refusal immediately into a conclusion about motivation.
- Rehearse an opening with a willing partner. Ask the partner to represent a plausible competing concern rather than an unreasonable antagonist.
- Debrief one observable habit and choose one adjustment. Avoid turning practice into a grading session about personal worth.
- Express appreciation by naming a contribution and its useful effect. Use the same specificity when raising a problem.
How To Apply It
An original case: a print studio's rush-order handoff
Imagine a small commercial print studio where Nora coordinates customer approvals and Eli prepares production files. This is an original teaching case, not a reported event from Lasater's book. Rush orders sometimes reach the workshop without a clear record of which proof the customer approved. Nora believes Eli disregards the intake notes; Eli thinks Nora promises delivery before the specifications are complete.
Begin with the work problem. They need a reliable way to know whether a job is ready for production. Neither person's opening interpretation establishes why the records are incomplete. Nora can select one recent order and identify the missing approval entry. Eli can describe what information was unavailable when he received it. The conversation has a factual starting point without deciding who is generally conscientious.
Before meeting, each person can practice the book's self-connection emphasis. Nora notices anxiety about disappointing a customer; Eli notices frustration about being held responsible for incomplete instructions. These are their own accounts, not emotions a manager assigns to them. Each prepares a short description of the incident and one question for the other.
During the discussion, Eli reflects that Nora needs confirmation early enough to give an accurate delivery estimate. Nora checks whether Eli needs a single, complete approval record rather than several messages. Either can correct this account. If Nora says the main problem is uncertainty about who owns the final confirmation, the proposed solution needs to address ownership as well as the form.
They can then consider a request: for the next week, could the person confirming the customer proof add the approval version and time to the shared order record before moving the job to production? If a deadline prevents that sequence, who can authorize a different route? Eli might decline responsibility for customer confirmation while agreeing to stop an incomplete job and flag it. That answer contributes information rather than automatically ending cooperation.
A short rehearsal can expose ambiguity. What happens when a customer approves verbally? Which staff member records it? Nora and Eli do not need a lengthy emotional workshop to discover that their proposed agreement has a gap. They can revise the handoff before testing it.
After the trial, a debrief would examine actual records and the experience of using them. It could reveal fewer missing entries, an impractical extra step, or a different bottleneck; no outcome is assumed here. The lesson is the practice sequence: attend to the reaction, understand the concern, negotiate a concrete request, and learn from what the team actually does. A staffing or authority problem uncovered during that process still needs a corresponding organizational decision.
Notable Ideas, Paraphrased
- The conversational skill available under pressure may differ from the skill a person can describe when relaxed.
- A need can be important even when one proposed method of meeting it is impractical.
- A useful refusal gives the team information it did not have when it framed the request.
- Practice becomes productive when people can notice an action and attempt a specific adjustment.
Original Value: When This Book Is Most Useful
Use this book when a team has repeated opportunities to rehearse small changes. Its compactness makes it suited to a practice group that selects one exercise, tries it voluntarily, and returns to what happened. The value lies less in collecting new terminology than in noticing the gap between intention and behavior.
It is less useful as a mandate to make difficult employees more agreeable. If a deadline is impossible, empathy does not create additional hours. If one person can penalize another for refusing, the request is not freely negotiable merely because a feeling and need were mentioned. Reading the book alongside a clear account of responsibilities helps prevent communication practice from becoming a substitute for fair decisions.
Best Related Books
- Conversational Capacity examines the balance between expressing a view and remaining open to learning, useful when a team's exchanges swing between withdrawal and forceful advocacy.
- Crucial Conversations gives a broader framework for high-stakes discussions, while Lasater's booklet foregrounds repeated exercises and recovery of connection.
- Conversations Worth Having offers a complementary focus on the questions and framing that shape collective conversations.
- Collaborative Intelligence is a different book about working across differences in thinking; do not confuse its authors or models with Lasater's NVC practice guide.
Internal Links
Explore the communication book directory to choose a related guide by the problem you need to discuss next.