Workplace Communication and Self-Advocacy
The Secret Language of Work Summary: Scripts With a Purpose
The Secret Language of Work makes professional communication more approachable through adaptable scripts, helping readers turn an unspoken need into a clear, purposeful workplace request.
One-Sentence Answer
The Secret Language of Work makes professional communication more approachable through adaptable scripts, helping readers turn an unspoken need into a clear, purposeful workplace request.
What The Book Is About
Erin McGoff writes for people who know what they want to say at work but struggle to phrase it. They may want a more suitable assignment, a realistic deadline or an explanation of what a prospective employer expects. Their difficulty is partly linguistic and partly social: many conventions that appear obvious to an experienced professional were learned from mentors, family or repeated exposure.
The publisher's edition page and authorized opening chapter identify the original US hardcover as a March 10, 2026 release. McGoff uses her early internship experience to explain the cost of leaving expectations unspoken. The rest of her publicly described approach addresses the words people can use to advocate for themselves without surrendering their own personality.
This guide combines that substantial opening excerpt with McGoff's detailed Think Fast, Talk Smart interview and How to Be Awesome at Your Job interview, alongside her own explanation of the book's scope. We have not inspected every script in the full book. The examples below are our own hypothetical wording, rather than reproductions presented as McGoff's scripts.
The useful question is what a script enables you to do: make a request clear, show the relevant trade-off and give another person a workable response. Polished phrasing cannot make an impossible workload possible or guarantee cooperation from an unreasonable manager. Treat the book as a resource for preparation and adaptation, rather than a collection of phrases that produce identical results in every organization.
Who Should Read It
- Early-career professionals who have had little access to informal workplace mentoring.
- Job seekers who want concrete examples alongside general advice about confidence and interviewing.
- Employees who find it difficult to ask for priorities, set expectations or discuss their contribution.
- Readers who prefer adaptable wording and familiar scenarios to a dense theory of organizations.
- People seeking a formal grievance, employment-law answer or specialist negotiation analysis will need resources beyond a communication handbook.
Main Summary
McGoff's starting point is that professional language is learned. Knowing how to make a request, introduce yourself or discuss compensation is not an innate sign of competence. The book aims to make these often-unspoken conventions more accessible through concrete examples and scripts.
The opening chapter connects communication with expectations. A person can appear agreeable while withholding information essential to a productive working relationship. If you say that everything is fine while hoping someone will discover what you really need, the other person may have little basis for changing the situation. The practical alternative is to state a specific concern and a useful next step.
McGoff explains in her Think Fast, Talk Smart conversation that professional communication should remain authentic while responding to the context. She encourages readers to think about the desired outcome and the other person's goals. The objective is not simply to express frustration more elegantly; it is to make a proposal another person can understand and evaluate.
Her public description of the book includes written communication, networking, interviews, negotiation, expectations and boundaries. The detailed Awesome at Your Job interview shows how scripts can handle follow-up resistance as well as an opening request. A workload conversation, for example, can name a capacity constraint and invite a priority decision rather than silently accepting incompatible demands.
The book's appeal is its practical entry point. A reader can rehearse language for a situation that otherwise feels too awkward to begin. Its limits are equally important: a script needs truthful facts, appropriate authority and room for the other person's response. Good wording does not establish a legal entitlement, erase unequal power or prove a promised career outcome. Use the book to prepare a clearer conversation, then assess what actually happens.
Key Ideas
1. Treat professional language as a learnable convention
McGoff describes workplace communication as a hidden curriculum: some people enter professional settings with guidance that others never received. Her publisher excerpt and public explanations challenge the assumption that difficulty finding the words reflects a permanent personal deficiency. This gives the reader a practical reason to study examples rather than wait to feel naturally fluent.
Consider our hypothetical analyst, Maya, who has recently joined a consulting team. She hears colleagues request resources confidently but interprets her own need for help as evidence that she is not ready for the role. A more useful learning task is to identify what those requests contain. Are colleagues naming a deliverable, explaining a constraint and asking a particular person to decide something?
Maya can collect a few nonconfidential examples of clear internal communication and note their functions. She is learning how a request works, not copying another person's mannerisms or storing private messages without permission. A mentor can help explain which conventions are specific to that organization and which are merely one person's preferences.
Our suggested exercise is to rewrite a vague concern into a task another person can respond to. “I am struggling” may be emotionally accurate, but “Could we confirm which analysis is needed for Thursday's review?” identifies a decision. Both statements can matter. Learning professional phrasing should expand your choices, not imply that feelings are illegitimate or that the workplace's conventions are always fair. Once you understand a convention, you can decide how to use or question it more deliberately.
2. Define the outcome before choosing the wording
In her interviews, McGoff returns to the desired outcome of a conversation. This prevents a common mistake: preparing a forceful speech that expresses dissatisfaction without making the required decision clear. A script is more useful when the reader can name what should happen next and why that action matters.
For Maya, “I want my manager to know how stressful this is” may describe a genuine need for acknowledgment. It is different from “I need agreement about which deliverable takes priority.” If she needs both, she can prepare for both. Combining them unconsciously can leave her disappointed even after one has been addressed.
Our preparation method is to complete three lines: the observable situation, the requested change and the person who can authorize it. Suppose two presentations are due on Thursday, and each needs the same specialist review. The situation is not simply that Maya feels busy. It is that the current plan depends on a resource that cannot be in two reviews at once.
She could ask her manager to select a priority, authorize another reviewer or change a delivery date. These options are hypothetical applications, not McGoff's published scripts. They make the underlying request easier to evaluate. Before speaking, Maya should check that the facts and resource estimates are accurate. A clear outcome does not excuse presenting a preference as an unavoidable constraint. Leave room for the manager to supply information Maya lacks, and distinguish a request from a decision she is already authorized to make.
3. Make written communication easy to act on
Written communication is an explicit part of the book's scope, as McGoff explains in her own chapter overview. The reader should approach sample wording as a way to reduce ambiguity for the recipient. An email that sounds polished but hides its request can still fail at its basic task.
Our example is a project message from Maya to a specialist reviewer. A long account of how hard the week has become may leave the reviewer unsure whether she needs advice, sympathy or a meeting. A clearer message can identify the document, the decision it supports, the requested review and the deadline. Relevant context follows in the amount needed to perform the task.
Before sending, Maya can read only the subject line and opening sentences. Can the recipient tell whether an answer is required? Can they find the date and the specific material? If the message includes several questions, can each be answered separately? These are our editorial checks, not a named checklist from the book.
Clarity also requires distinguishing a request from an announcement. “I plan to send the draft at noon” does not secure a promise that the recipient will review it by two. Ask for confirmation where the plan depends on another person's availability. Use the channel appropriate to the situation; an urgent safety concern or formal process may require more than an ordinary email. Shorter writing is useful when it preserves the necessary facts. Removing context until a request becomes cryptic is not an improvement.
4. Turn workload boundaries into an explicit priority conversation
In her Awesome at Your Job interview, McGoff explains how to discuss capacity through the work that needs to be done and the choices available. She also addresses pushback from a difficult manager. This is more realistic than assuming that a single assertive sentence ends every boundary dispute.
Maya can describe the two Thursday deliverables, the review time each requires and the current bottleneck. She can then ask which item should take precedence or what resource should change. The purpose is to make incompatible expectations visible while there is still time to respond, rather than conceal the problem until a deadline is missed.
If the manager says both are essential, Maya needs a second move. Our suggested response is to confirm the shared delivery goal and ask which practical adjustment is available: narrower scope, another reviewer or an agreed extension. She should not invent an available colleague or promise that someone else can absorb the work. Options need to be real and within the appropriate person's authority.
A boundary conversation also benefits from a brief written recap. Record the chosen order, the deliverable affected and when the arrangement will be reviewed. This is useful coordination, not a guarantee against retaliation or misunderstanding. If a manager repeatedly refuses to reconcile demands, wording alone may not resolve the issue. Seek support appropriate to the organization and the problem. McGoff's practical language can help state a constraint; responsibility for adequate staffing and realistic commitments does not belong to the employee's phrasing alone.
5. Advocate through contribution and shared goals, while staying truthful
McGoff's Think Fast, Talk Smart interview connects self-advocacy with the other person's priorities. A request is easier to assess when it explains how the proposed change supports work the organization cares about. That does not make personal needs unimportant; it helps distinguish a decision argument from a private hope that the other person will infer your value.
For Maya, a request to lead a client briefing becomes more concrete when she identifies the relevant experience, the preparation required and the problem she could help solve. “I deserve a chance” communicates a wish. A bounded proposal to prepare one section with supervision allows the manager to evaluate readiness, risk and support.
Our suggested evidence note contains three items: a contribution Maya can document, the next responsibility she wants and the reason the connection is plausible. She should not inflate an individual role in a team result or imply that a successful assignment automatically earns a promotion. Accurate credit strengthens a request more than a dramatic but fragile story.
Prepare for an answer other than yes. The manager may identify a missing skill, a timing constraint or a different route. Maya can ask what evidence would justify revisiting the request and agree a review point if one is appropriate. A useful conversation can clarify expectations even when it does not deliver the preferred outcome immediately. The aim is informed advocacy, not making the other party's goals a pretext for manipulation. Scripts work best when the underlying proposal is honest, specific and open to examination.
Practical Takeaways
- Identify the workplace convention you need to learn rather than labeling yourself as inherently unprofessional.
- Write the desired outcome before rehearsing an awkward conversation.
- Separate an observable workload constraint from an assumption about another person's intentions.
- Give written requests a clear action, relevant material and an explicit date when timing matters.
- Confirm another person's availability instead of treating your announcement as their agreement.
- When demands conflict, ask for a priority or a practical change in resources, scope or timing.
- Support self-advocacy with accurate examples of your own contribution and acknowledge team credit.
- Prepare a follow-up question for a refusal, and record what would justify revisiting the request.
How To Apply It
Prepare a workload conversation in two versions
This original exercise uses Maya's Thursday deadline problem. It is a way to practice the book's purpose-driven approach, not a reproduction of one of its scripts.
Start with a private draft that says exactly what is bothering you. It may include frustration, worry and resentment. Keep that draft private. Its function is to reveal the concerns you need to understand before choosing a professional request.
Next, create a factual version. Name the two deliverables, the work still required, the shared reviewer and the point at which a decision is needed. Check the estimates. If you do not know whether another reviewer is available, mark that as a question rather than presenting a rescue plan you cannot deliver.
Choose the primary request. Maya might need a decision about which presentation receives the specialist's attention first. She can explain the trade-off and ask for direction. If the manager offers a workable alternative, examine it. Do not continue reciting a prepared script after the situation has changed.
Rehearse a pushback version as well. A colleague can play a manager who says both projects matter. Maya then practices asking what will change so that both can be delivered responsibly. The goal is to keep the issue concrete without attacking the manager's character or pretending that polite words create extra hours.
After the conversation, write a short recap of the agreed priority and next step. Ask for correction if the recap does not match the other person's understanding. Judge the exchange by whether the work plan is clearer and more realistic, not by whether your delivery sounded effortless.
What scripts can and cannot do
The subtitle promises scripts across many situations; no handbook can anticipate every organizational culture, legal context or power relationship. Adapt wording to the relationship and task, and do not use an example to bypass a required policy or formal channel. Advice about professional presentation should not become an excuse to blame people for discriminatory treatment.
The independent Resume Rescue review notes the book's informal style. That may make the approach inviting for some readers and distracting for others. If you prefer a more analytical account of negotiation, pair it with Never Split the Difference. For a fuller discussion of the emotions and interpretations within a difficult exchange, consider Difficult Conversations.
Notable Ideas — paraphrased
- Professional phrasing can be learned rather than inherited through informal access.
- A useful script helps another person understand the action you are requesting.
- A boundary becomes easier to coordinate when the associated trade-off is visible.
- Accurate contribution and a clear proposal give self-advocacy something solid to rest on.
Best Related Books
- Never Split the Difference — a broader negotiation companion for readers who want more than sample workplace wording.
- Difficult Conversations — examines the interpretations and feelings that can complicate a direct request.
- Great on the Job — another practical resource for everyday professional communication.
- How to Say Anything to Anyone — relevant when ongoing workplace expectations and candor need attention.