Getting Along Summary: Amy Gallo on Difficult Coworkers

Key Ideas

1. Describe the behavior before choosing an archetype

Gallo's categories offer a vocabulary for recurring difficulties. Our application begins one step earlier: write down the behavior that makes the category seem relevant. Otherwise the label can quietly become the evidence. Once you call a colleague a political operator, even an ordinary private conversation may start to look like a scheme.

Mira's first description is that Nolan undermines everything. It is emotionally understandable and operationally weak. A more useful account distinguishes three events: he agreed to a corrections deadline, the corrections were absent when the shared plan went out, and he later questioned two entries in another channel. Those observations identify a handover problem without claiming access to his intentions. They also leave open whether the second channel has become the team's usual place for urgent exceptions.

Try making two columns before the next discussion. Put observable actions in one and interpretations in the other. Include facts that complicate your preferred explanation: a request you sent late, a correction you overlooked or a responsibility nobody assigned. This does not require pretending that repeated harmful behavior is harmless. It makes the account more accurate and the request easier to evaluate.

Use an archetype as a provisional lens for selecting an approach, not as a title to announce in the meeting. Nolan can dispute being passive-aggressive indefinitely. He can answer a much more concrete question about which log entries he needs changed before the agreed cut-off and where he will record them.

2. Choose the work outcome that would make an intervention useful

The wish to expose an unreasonable colleague can overpower the reason you need to interact. Gallo's emphasis on an actual goal is valuable because a conflict offers many tempting side quests. You can spend an hour proving that a remark was unfair and still leave without the information needed for tomorrow's work.

In the museum case, Mira initially wants Nolan to acknowledge that he has made her look incompetent. Recognition may matter, but it does not define the immediate handover. She writes a narrower outcome: one current condition log, with unresolved entries visible before the installation team receives its instructions. That statement guides whom to involve, what to ask and when a conversation has done enough.

A reader can prepare three lines: the work affected, the minimum useful change and the next decision if nothing changes. For Mira, the minimum is that Nolan marks disputed entries in the shared log by Wednesday at three. If he cannot, they need an agreed person to decide which version goes forward. She no longer has to settle every disagreement about their history to make that request.

Keep the outcome realistic about authority. A coordinator cannot simply impose a process on another department. Mira proposes the arrangement and asks the exhibition lead to resolve ownership if necessary. The goal clarifies the conversation while leaving legitimate objections available. It becomes a practical test of cooperation rather than an order disguised as a request for better teamwork.

3. Consider another perspective without explaining away the impact

Gallo's general principles include questioning the completeness of your own perspective and noticing bias. That is particularly relevant when the same behavior admits more than one explanation. A colleague who raises risks may be obstructing progress, protecting a responsibility you overlooked or doing some of both.

Nolan's skeptical comments concern a genuine difference between two loan records. Mira has interpreted their timing as a personal attack. Both facts can matter: the correction may be necessary, and the way it arrives may make the handover unreliable. Treating either fact as cancelling the other creates a false choice between defending herself and acknowledging useful information.

For an original practice exercise, ask what the colleague might be trying to prevent, then check rather than assume. Mira can ask which uncertainty makes Nolan unwilling to confirm the log. His answer may identify a missing photograph, a lender's unresolved instruction or a concern about responsibility. She can then distinguish a substantive obstacle from the need to change the communication process.

Perspective-taking does not oblige her to absorb endless late corrections or accept insulting remarks. It gives her a better basis for the next request. If the records remain incomplete, she can propose a visible unresolved-items section. If the record is complete but Nolan continues making vague accusations, she has learned something different. The purpose is to improve the explanation enough to choose an action, not to invent a sympathetic motive that makes every action acceptable.

4. Match the response to power, exposure and available support

A technique that feels safe with a friendly peer can carry different consequences with someone who controls assignments, promotion or access to information. Gallo discusses those differences in her author interview. Our application is to assess the setting as carefully as the wording instead of making direct confrontation the universal measure of courage.

Mira and Nolan work in different departments, and he controls records she needs. She can ask for a process agreement, but repeated public challenges could make the dependency worse. She chooses a short planned discussion with the exhibition lead available for an ownership decision. This is a task-specific arrangement, not an attempt to assemble an audience against him.

Before a conversation, identify what the other person controls, what you can document accurately and who has a legitimate role if the request fails. Decide also what you do not need to disclose. An exhaustive account of every frustration can distract from the immediate work and expose private information about other colleagues. A short factual chronology is often more usable than a dossier of suspected motives.

There are limits to an interpersonal experiment. If a pattern involves threats, discrimination or retaliation, an appropriate support or reporting route may be needed. Do not turn that into a rule that every disagreement needs formal escalation. The relevant question is whether the proposed conversation is proportionate to the behavior and whether the person attempting it has a reasonable way to protect their interests if it goes poorly.

5. Test a change in the dynamic and decide what the result permits

The experiment perspective prevents two opposite mistakes: expecting one conversation to transform the relationship and repeating the same unsuccessful tactic indefinitely. Gallo describes incremental learning rather than a guaranteed conversion into friendship. Our practical addition is to define an observation period and a decision before beginning the experiment.

Mira proposes one handover cycle. Nolan will place corrections in the shared log, identify any entry awaiting external confirmation and respond before the Wednesday cut-off. Mira will send the working version early enough for that review and stop distributing partial updates in separate messages. Each person has an observable contribution. The test is whether the team can identify the current version without reconstructing a chain of disagreements.

After the handover, she can compare what happened with the agreement. Were corrections in one place? Were unresolved issues visible? Did the installation team receive conflicting instructions? Her irritation is relevant, but it is not the only measure. A less friendly yet more dependable exchange can be a useful improvement. Conversely, a pleasant meeting followed by another missing record is evidence that the operational problem remains.

Choose a next action from that evidence. Keep a helpful process, revise a specific weak point or ask the responsible manager to change the dependency. Stop trying to extract a satisfying emotional ending from a person who will not provide it. A bounded experiment is useful because it produces a decision about the work, even when it cannot produce the relationship you would prefer.