Professional communication and career conversations

Great on the Job Summary: Jodi Glickman's Work Conversations

*Great on the Job* treats effective workplace communication as a set of learnable conversational practices, helping readers make requests, share information and maintain useful professional relationships.

One-Sentence Answer

Great on the Job treats effective workplace communication as a set of learnable conversational practices, helping readers make requests, share information and maintain useful professional relationships.

What The Book Is About

Jodi Glickman addresses the ordinary exchanges that can be surprisingly difficult at work: approaching a busy colleague, asking for help, obtaining useful feedback and explaining what you do. The emphasis is on usable conversational mechanics, rather than waiting to become naturally charismatic.

The Macmillan publisher page and authorized excerpt identify the full subtitle, the May 2011 edition and a concrete example of that approach. Its opening chapter presents a three-step hello: introduce yourself, explain the purpose and check whether the person has time to speak. The excerpt also presents a two-step goodbye, joining thanks with forward momentum.

Glickman's Harvard Business School alumni interview describes GIFT: generosity, initiative, forward momentum and transparency. Those are four principles, not five. Our five priorities below are an editorial organization combining these ideas with the opening-conversation mechanics. The retailer sample-delivery case is an original application, with invented people and wording, rather than a case reported in the book.

Who Should Read It

This is a useful starting point if you know your technical work but hesitate over how to approach someone, admit a gap in your knowledge or ask for a decision. It can also help a career changer who understands professional behavior in one setting but is learning the conversational expectations of another.

The book's concrete style suits readers who want something to practice aloud. A prepared structure can reduce the effort of beginning, especially when a request feels socially risky. The aim is to make the purpose understandable, not to recite a formula regardless of the listener's answer.

Its limits matter. Published in 2011, the book includes phone and office interactions whose principles need adaptation for asynchronous messages and different workplace cultures. Communication skill can help your work become easier to understand; it cannot guarantee promotion, fair evaluation or a supportive manager. If the central difficulty is serious conflict or an unfair working arrangement, polished phrasing alone will not resolve it.

Main Summary

Glickman's practical premise is that workplace communication can be learned at the level of a particular exchange. Asking for help, delivering an update and beginning a call are different tasks. Readers can prepare the purpose and a useful structure instead of treating every conversation as a test of personality.

The GIFT principles offer an orientation for those exchanges. Generosity considers what the other person needs. Initiative contributes an active next move. Forward momentum keeps the interaction connected to what happens afterward. Transparency makes relevant information available. These four principles should not be confused with one mandatory script; the publisher's excerpt shows separate mechanics for opening and ending a conversation.

Our fictional case follows Rina, a new account coordinator at a homeware wholesaler. Eighty retailer sample packs must leave on Thursday, but two destinations lack confirmed delivery details. Rina has checked the order records and sent one unanswered request. She now needs help from the account manager before the courier collection is booked. Her first impulse is to approach with a long apology and an unsorted explanation of everything she tried.

A more useful exchange identifies the task, the missing information and the decision required. Rina checks whether the manager can speak, explains the two exceptions and offers a limited next action. She can complete the confirmed destinations now while the manager decides how to handle the others. She is clear about what remains unconfirmed instead of silently treating an old address as current.

This guide uses the case to explore several ways of being helpful without hiding uncertainty or taking authority you do not have. A good result is an agreed action, a responsible person and a visible remaining issue. It is not proof that a new employee has mastered every workplace relationship or earned a particular career outcome.

Key Ideas

1. Give a live conversation a recognizable beginning

The three-step hello in the authorized excerpt is specific: introduction, purpose and a question about availability. The value lies in orienting the listener and giving them a choice about timing. Our application is to make those functions natural for the relationship instead of turning a familiar coworker into a stranger through an unnecessarily formal introduction.

Rina does not need to explain her job title to a manager who works with her every day. She does need to identify why she is interrupting. A useful opening names the Thursday sample collection and asks whether the manager can spare a few minutes to decide two delivery exceptions. That is more considerate than beginning with the complete story while the manager is leaving for another meeting.

If the answer is no, use the information. Ask for an appropriate time or another responsible person, taking account of the actual deadline. A timing question becomes empty politeness if you continue the pitch after the listener says they cannot speak. Equally, avoid making a genuinely urgent deadline invisible in an effort to sound undemanding.

For an asynchronous message, adapt the purpose rather than imitating a call word for word. Put enough context and the actual question in the message so the recipient can respond when available. Sending only a greeting and waiting can create another interruption. This digital adaptation is our editorial extension of the book's respect for attention, not a claim that its 2011 phone examples describe every current messaging convention.

2. Make generosity concrete in the help you request

Generosity can sound like a personality virtue until you ask what it changes in a particular interaction. Glickman's GIFT orientation invites attention to the other person. Our application is to reduce avoidable work for the recipient while keeping the request complete enough to answer. Being considerate does not require hiding that you need help.

Rina's unsorted explanation would make the account manager reconstruct the whole delivery list. Instead, she brings two exceptions, the last confirmed contact for each and the specific uncertainty. One retailer has moved premises; the other has not named a receiving contact. She explains what she has already checked without presenting a defensive inventory of every minute she spent.

Before asking for help, separate what you can do from what requires someone else's access, experience or authority. A person can give better assistance when they know whether you need a missing fact, a judgment between options or permission to proceed. Rina needs the account manager's relationship with the retailers; she does not need the manager to rebuild the entire courier booking.

This preparation should remain proportionate. Do not spend hours polishing a request that needs to be raised promptly, and do not withhold it because you cannot anticipate every possible answer. Generosity also includes allowing a colleague to point out a simpler route. The goal is a manageable contribution they can assess, rather than a performance proving that you should never have needed assistance in the first place.

3. Show initiative by proposing a next move within your authority

Initiative is useful when it advances the work, but it can become a source of trouble if it conceals an unauthorized decision. The GIFT principle gives a reader a reason to arrive with something more useful than a transfer of worry. Our application adds a boundary: distinguish a proposed action from an action you are entitled to take.

Rina could say that the delivery list is a mess and ask what to do. She could also choose the old addresses and hope the issue disappears. A better contribution is to separate the confirmed seventy-eight packs from the two exceptions, prepare the confirmed part of the booking and ask whether the others should wait for confirmation or be handled separately. The manager can evaluate a decision rather than absorb an undefined problem.

Write a short proposal containing what you recommend, why it helps and what needs agreement. Do not disguise a choice already made as a request for input. If another person's budget, customer commitment or workload changes, explain that consequence before proceeding. The right amount of initiative depends on the role and the organization's established boundaries.

An experienced colleague may reject your suggested route. That does not make preparing it wasted effort. Ask what consideration you missed and update your understanding of the task. Rina might discover that split collections add an unnecessary charge or that one retailer can receive the pack through a different branch. Initiative works best as a prepared contribution to a decision, with room for relevant information to change it.

4. Use transparency to distinguish facts, assumptions and open questions

Transparency is one of Glickman's four named principles. In this guide's application, it means making relevant uncertainty understandable early enough for another person to act. It does not mean broadcasting every thought, sharing private information indiscriminately or replacing a clear update with a stream of unfiltered anxiety.

Rina knows that two delivery details are unconfirmed. She suspects one retailer has moved, and she has an old address in the records. Those are different kinds of information. If she says all deliveries are ready because most are ready, the manager may book the collection on a false understanding. If she says nothing is ready, she conceals the substantial portion that can proceed.

Try preparing an update in three short parts: confirmed position, open issue and next decision. The wording might state that seventy-eight destinations are confirmed, two require current receiving details, and a decision is needed before the booking cut-off. These are original case details, not a named three-part method from the book. They make the principle easier to use without inventing an official framework.

Include what would change your update. If the retailer confirms the address, Rina can finish the entry. If the information does not arrive in time, the manager must choose an alternative. Honest uncertainty is useful when it points toward that decision. It is less useful when it becomes either an apology for everything that might go wrong or a vague warning that leaves colleagues unable to identify the actual remaining risk.

5. End with thanks and a clear connection to what follows

The publisher's opening-chapter excerpt describes a two-step goodbye: thank the other person and maintain forward momentum. Its broad lesson is that an ending shapes the next interaction. Our application is to close a working conversation with an accurate understanding of what follows, without inventing a commitment on the other person's behalf.

After discussing the exceptions, Rina could leave with a relieved thank-you and forget whether the manager intended to make the calls immediately. A more useful ending names what she will do and checks the remaining responsibility. She will prepare the confirmed booking; the manager will contact the two retailers; they will check again before the courier cut-off. If the manager has only suggested asking someone else, the recap should say that instead of upgrading a suggestion into an accepted assignment.

Keep the closing proportionate to the exchange. A brief thank-you and a reliable follow-up may be enough after a small question. A consequential decision may warrant a short written recap where the people involved normally track that work. Do not copy extra recipients merely to make yourself look diligent.

Follow-through then supplies the credibility that phrasing cannot. Rina needs to complete the action she accepted and flag any new obstacle before the next decision point. A polished closing loses value when nobody acts on it. Conversely, a plain, accurate ending can support a useful professional relationship because colleagues can tell what was agreed and do not need to chase an avoidable ambiguity the following morning.

Practical Takeaways

  1. Prepare the purpose before a live approach. State the task and the decision you need, then check whether the person has time for that conversation.
  2. Send a complete asynchronous question. Include relevant context, the request and a real deadline where one exists. Adapt the book's phone etiquette to the channel instead of sending a greeting that requires a reply before the purpose appears.
  3. Separate the exception from the whole task. Show which part is ready and which part needs help. Let the recipient assess the actual scope of the problem.
  4. Identify the kind of help needed. Ask for information, judgment, access or authorization. If you are unsure which is missing, say what you cannot decide yet.
  5. Offer a proportionate next action. Suggest what you can do now and identify any decision that belongs to someone else. Keep proposals visibly separate from promises already made.
  6. Report uncertainty accurately. Use confirmed facts and label assumptions. Explain what missing information would change the plan rather than sounding certain to avoid embarrassment.
  7. Close and follow through. Thank the person, confirm your own action and check any remaining responsibility. Deliver the promised update through the agreed work channel.

How To Apply It

Rehearse one request that combines GIFT with a real constraint

The sample-pack scenario is an invented exercise. It combines a new employee, a busy manager, missing information and a deadline.

Before the conversation, Rina prepares a small exceptions list. She records the two retailer names, the missing receiving details and the last attempted contact. She also identifies which parts of the booking she can prepare without making a new customer commitment.

For a live approach, an original opening could be: Can we spend a few minutes on Thursday's sample collection? Seventy-eight destinations are confirmed; two still need receiving details. I need your advice before the courier cut-off. She adds a relevant introduction when approaching someone who does not know her.

She then makes a specific proposal: I can prepare the confirmed portion now. For the two exceptions, would you contact the retailers, or is there someone else with current details? The manager may provide an answer, redirect her or explain that the booking should be handled differently. Rina listens rather than defending the proposal because she rehearsed it.

If the answer is that the manager cannot help before the cut-off, she asks who has authority to choose the fallback. She should not interpret a busy person's silence as permission to use an unconfirmed address. She also tells the responsible person that a decision remains open.

The closing names the actual arrangement. If the manager accepts the retailer calls, Rina thanks them and confirms when she will report the booking status. If nobody accepts them, the record remains an open assignment. A short recap should make that difference visible.

Finally, choose one question for feedback after the delivery decision: Was my request clear enough for you to identify what I needed? This is a suggested practice question, not a verbatim Glickman script or a report of a successful test. The answer can help Rina improve the next request without treating one imperfect conversation as a verdict on whether she belongs at work.

Notable Ideas, Paraphrased

  • Respect for attention becomes practical when a person knows who is approaching, why and whether the timing works.
  • Helpful initiative offers a possible next step while leaving the appropriate person able to decide.
  • A courteous ending gains value when the following action is clear and dependable.

Best Related Books

  • The Communication Code helps identify the kind of response wanted from an exchange. Compare it when a colleague gives advice but you actually need clarification, collaboration or another form of attention.
  • The Language of Leadership moves toward a leader's responsibility to make messages useful for a team. Choose it when your next challenge is explaining direction to others, rather than making an individual request.
  • Words That Work in Business offers a needs-aware approach to workplace exchanges. It provides a useful comparison when you want to examine an underlying concern instead of concentrating mainly on conversational mechanics.

Internal Links

Explore Communication Books and the books to improve communication collection. For a manager's follow-up to a request for help, see The Coaching Habit; to clarify the response you are requesting, use The Communication Code.