Workplace Trust and Communication

Talk to Me Nice Summary: Minda Harts's Seven Trust Languages

Talk to Me Nice gives people a vocabulary for explaining what trustworthy behavior looks like at work, then asks them to support that conversation with actions rather than reassuring words alone.

One-Sentence Answer

Talk to Me Nice gives people a vocabulary for explaining what trustworthy behavior looks like at work, then asks them to support that conversation with actions rather than reassuring words alone.

What The Book Is About

Minda Harts begins with a problem that a friendly office atmosphere can conceal. A manager may praise an employee while repeatedly avoiding meaningful discussion about opportunities. A colleague may express support but fail to act when support matters. In each case, the person receiving the message must judge whether the relationship is dependable, not simply whether the words sound encouraging.

Harts organizes that judgment around seven workplace trust languages: transparency, security, demonstration, feedback, acknowledgment, sensitivity and follow-through. The framework helps people describe what they need and recognize that another person may need something different. It is not a requirement to select one permanent personality label or to excuse a harmful practice as a mismatch in preferences.

The original work was published on July 22, 2025. The publisher's original ebook record and authorized excerpt give that date and identify Harts as the author. This guide records the original hardcover, ISBN 9781250339980. The July 21, 2026 paperback is a later format of the same work, not a new original book.

We draw on the substantial authorized opening material and Harts's direct author discussions with Steelcase and Workfluencer. These support a focused guide to the framework and its communication implications. We do not claim to have accessed every later chapter. The project-handover case, five organizing themes and practice record below are this guide's own applications.

Who Should Read It

Read this if a workplace relationship repeatedly produces disappointment but the conversation never gets beyond a general accusation of distrust. Managers may find it useful when recognition is plentiful but employees still do not believe commitments, or when different colleagues respond differently to the same attempt at support.

It also suits employees who want language for asking about the information, feedback or consistency they need. Harts's discussion takes inequity and differing experiences seriously; a team does not become equally safe for everyone because a leader announces an open-door policy.

The book is a weaker fit if the immediate task is a formal investigation or a response to violence or abuse. Harts explicitly distinguishes those situations from the trust-repair conversations discussed in the opening material. A considerate conversation should not replace action that the situation requires.

Main Summary

Harts argues that many workplace trust problems remain difficult to address because people have not named the behaviors they expect. A person may say they do not trust a manager while needing clearer information about a decision, reliable feedback or evidence that a commitment will actually be carried out. A vocabulary makes those needs easier to discuss.

Her seven languages concern different aspects of the relationship. Transparency brings relevant information and reasoning into view. Security concerns the conditions in which people can work and speak without unnecessary fear. Demonstration asks whether behavior supports stated values. Feedback provides usable communication about performance and conduct. Acknowledgment recognizes contribution. Sensitivity takes account of different experiences and needs. Follow-through concerns what happens after someone makes a commitment.

The framework is relational rather than one-directional. Employees can explain what they need, colleagues can ask each other, and managers can examine whether their actions support the trust they request. Harts's first-person discussions show how a simple question about the conditions someone needs for good work can be more informative than demanding a yes-or-no declaration of trust.

The book also resists the assumption that a title or long service automatically earns confidence. Its authorized opening discusses promises that do not translate into opportunities and the gap between organizational language and employees' actual experience. Trust therefore requires attention to decisions and conduct, not only a better way of describing them.

A practical application begins with one specific situation and an observable request. The person receiving the request needs to clarify what they can do, what they cannot promise and when they will follow up. The useful outcome is evidence that the relationship can become more dependable. Politeness, an apology or a completed questionnaire cannot by themselves establish that a persistent problem has changed.

Key Ideas

1. Translate a general trust judgment into a specific unmet need

Harts's seven languages offer a way to investigate a broad statement such as distrust without dismissing it. The aim is not to talk someone out of their experience. It is to identify which behavior would give them better evidence about the relationship and whether the other person is willing and able to provide it.

Our fictional case concerns Leah, a designer, and Tomas, a project lead. Leah has been told that she is trusted to manage a handover, but important decisions keep arriving through other people. Tomas believes he has shown confidence by leaving her alone. Leah experiences the same arrangement as uncertainty and exclusion.

Before their conversation, Leah can list a recent event, its effect on her work and the missing behavior. An unannounced change to the client brief caused rework; she needed the decision and its rationale before revising the design. That description gives Tomas something more useful to answer than a demand to prove he trusts her.

Harts's framework allows more than one language to matter. Leah may need transparency about decisions and acknowledgment of her ownership. The preferences may also change with the task. Our exercise should not become a label such as Leah being a transparency person whose other concerns can be ignored. The goal is a request connected to a real situation, with room for correction if the first explanation does not capture what happened. A manager should hear the concern before assigning it a category.

2. Make transparency and security concrete without promising everything

Transparency and security can support one another, but neither is achieved by a slogan. In her author discussions, Harts connects trust with a clearer account of what is happening and a more humane way of involving the people affected. A leader who knows more than others has to consider what the information gap does to their work.

Tomas may not be able to share every discussion with a client. He can still distinguish what is decided, what is uncertain, what Leah needs to act on and when an update will be available. If he uses confidentiality to avoid explaining any part of a change, the team cannot tell a legitimate restriction from an unwillingness to communicate.

The practical request could concern a brief decision note before work resumes. It would name the current instruction, its owner and the remaining uncertainty. This is our proposed arrangement, not a template from Harts's book. It gives Leah a way to proceed without pretending that Tomas can eliminate every future change.

Security also requires a response to questions. If Tomas invites concerns and then treats a clarification as disloyalty, the invitation provides little reason to speak next time. He can explain which decisions are open for input and which are already settled, and respond to an objection without humiliating its holder. This does not guarantee psychological or job security. It makes the immediate interaction more legible and leaves visible the larger conditions that a conversational agreement alone cannot repair.

3. Separate a statement of support from demonstration and follow-through

Demonstration and follow-through ask for evidence after words. A statement of values needs conduct that makes it credible; a particular commitment needs an action that can be completed and checked. Harts's distinction helps explain why repeated reassurance can become frustrating when the practical relationship remains unchanged.

Tomas might say he values Leah's judgment. Demonstration would include involving her at the point where that judgment can affect the design, rather than asking for endorsement after a decision is final. If he promises to send a revised brief on Wednesday, follow-through concerns whether the brief arrives or whether he communicates a change before the deadline passes.

Our application is to use a small commitment record with an owner, an action and a realistic time. Keep it proportionate to the work. A shared handover note can support coordination; an elaborate surveillance system would introduce a different trust problem. The record should also distinguish a firm promise from an intention that depends on someone else's response.

When a commitment is missed, acknowledge the miss and its effect before explaining the reason. Then decide what can be done now and whether the original arrangement was realistic. Harts's interviews emphasize self-correction rather than avoidance after a mistake. A single correction is useful evidence, but it does not cancel a recurring pattern. Leah remains entitled to evaluate what actually happens over time, and Tomas remains responsible for changing the behavior rather than demanding immediate forgiveness.

4. Use feedback and acknowledgment to improve understanding, not to trade favors

Feedback and acknowledgment serve related but distinct purposes. Feedback helps someone understand a behavior, its effect and a possible adjustment. Acknowledgment recognizes a contribution that might otherwise remain invisible. A compliment is not a substitute for useful information, and critical feedback should not erase credit for work someone actually did.

Suppose Leah's handover missed a dependency. Tomas can identify the missing detail and explain the problem it created, then ask what would make the dependency easier to catch. That is more usable than a judgment about Leah lacking commitment. He can also recognize the parts of her preparation that helped the team without turning the conversation into a formula of praise followed by criticism.

For the person receiving feedback, Harts's Workfluencer discussion highlights the effect of the response on the relationship. Leah can ask for clarification and decide whether the criticism is accurate. She does not have to agree with every assessment to show that she has heard it. If she disagrees, she can explain the evidence rather than retaliate against the person who raised the concern.

Acknowledgment should also be specific and fair. If another designer identified the dependency, credit should follow that contribution. Private appreciation may be appropriate in one situation and visible attribution in another. Ask rather than assume. Our suggested test is whether both people understand the work more accurately afterward. Neither feedback nor acknowledgment should operate as a bargain in which courtesy buys silence about a genuine problem.

5. Treat sensitivity as attention to differing experience, not a demand for disclosure

Sensitivity matters because people who share an employer do not necessarily experience that workplace in the same way. Harts's opening material connects trust with equity, identity and respect, while her interviews explain how assumptions can conceal what someone needs. A leader cannot infer that a practice is harmless because it has not troubled them personally.

In our example, Leah may not want to explain personal circumstances in order to request a predictable review time. Tomas can respond to the work arrangement itself. He can ask what would help without demanding a private history that Leah does not wish to share. Similarly, an employee should not have to represent an entire demographic group to explain why a particular remark or pattern is damaging.

Sensitivity includes seemingly small acts, such as learning a person's name correctly, and substantive responses to exclusion or disrespect. It also involves listening to the account given rather than reducing every concern to a difference in preferred communication style. Some problems call for a change in decisions or conduct, not a more soothing delivery.

The title's request for nice treatment should not become a rule against legitimate disagreement. A person can be direct about an unfair outcome and still be seeking a trustworthy relationship. Our application is to ask which assumption needs checking, what information the person chooses to share and which action lies within your responsibility. Keep participation voluntary and avoid promising that one considerate exchange will resolve structural inequity or make an unsafe environment safe.

Practical Takeaways

  • Describe one event and its effect before turning a trust problem into a judgment about someone's character.
  • Identify which of the seven languages helps explain the request, while leaving room for several needs.
  • Ask what information another person needs to act, and distinguish a restriction from uncertainty.
  • Explain what is open for input before inviting people to challenge a decision.
  • Convert a promise into a proportionate action, owner and time that both people understand.
  • Acknowledge a missed commitment promptly and repair the practical consequence where possible.
  • Give usable feedback and accurate credit without treating praise as payment for agreement.
  • Respond to a work need without requiring unnecessary disclosure or assuming everyone experiences the workplace alike.

How To Apply It

Choose a relationship and one observable situation

Begin with an interaction you can describe accurately. Leah chooses the unexpected brief change, rather than trying to solve every frustration with the project team. She writes what happened, what it made difficult and what information she lacked. Where she is inferring intention, she marks that inference separately.

She then chooses a request Tomas could answer. The request concerns a decision note and an agreed review point. It does not ask him to certify that the whole workplace is trustworthy. The narrower request gives both participants a way to learn whether a different arrangement helps.

Agree on the response and inspect what happens

Tomas should clarify the part he can own, the information he cannot promise and the event that will trigger an update. Leah can explain what she will do with the information and what she will raise if another conflict appears. Both should understand how the agreement fits the actual decision process.

Review the next two handovers. Did the note arrive before Leah needed to act? Did it distinguish an instruction from a possibility? Was it possible to ask a question without penalty? These are observations about this arrangement, not a validated trust score. If the arrangement did not work, identify the practical reason instead of declaring that the other person failed a personality test.

Keep repair and obligation separate

Someone who has raised a concern does not owe immediate confidence in response to an apology. Trust can require repeated evidence. Nor is the less powerful participant responsible for making every repair succeed. Harts's discussion of trust includes managers and institutions precisely because the conditions of work matter alongside individual advocacy.

Compared with The Speed of Trust, Harts provides a particularly conversational vocabulary for discussing what different people need at work. Compared with Thanks for the Feedback, this framework addresses the wider relationship in which feedback is only one of seven languages. Choose a companion according to the problem rather than assuming that every trust problem is a feedback problem.

Notable Ideas — paraphrased

  • Trust becomes easier to discuss when the missing behavior has a name.
  • A supportive statement needs conduct that makes it credible.
  • The response to a concern affects whether the next concern will be voiced.
  • Different experiences require curiosity about needs, not assumptions about what ought to be enough.

Best Related Books

  • The Speed of Trust — for a broader account of credibility and behavior in relationships and organizations.
  • Thanks for the Feedback — for understanding the challenge of receiving and evaluating feedback.
  • Dare to Lead — for leadership conversations involving vulnerability, courage and clear expectations.
  • Radical Candor — for a related approach to direct, caring feedback in management.

Internal Links