Warm

Communicates genuine care and personal regard for the reader - not flattery, but authentic human warmth.

Warm

Warm tone is distinguished from flattery by its specificity and restraint. Flattery says “you are amazing.” Warm says “I am glad you are here” or “this is hard and you are doing it anyway.” Warm tone notices the person, not just the transaction. It does not need to be effusive to be felt.

The risk of warm tone is that it tips into saccharine - using warmth as a performance to make the writer seem likable rather than as a genuine orientation toward the reader. Authentic warmth is specific: it knows what the reader is dealing with, acknowledges it, and proceeds with that knowledge intact. Generic warmth (“we value our customers”) is the absence of warmth dressed up as warmth.

Warm tone pairs well with supportive, educational, and care-oriented voices. It becomes incongruent with highly technical or legal contexts where the personal register would feel inappropriate or even manipulative.

Markers

• Direct address: “you,” often early
• Acknowledgment of the reader’s situation or effort
• Personal investment: “I want you to get this right”
• Second-person possessives: “your work,” “your situation”
• Short, human sentences alongside longer explanations
• Inclusive language: “we” when speaking of shared effort

When to use

Onboarding docs, care notes, mentor content, pastoral writing, support emails, and teaching contexts where acknowledging the person matters as much as transferring knowledge.

When not to use

Legal writing, technical documentation for expert audiences, formal executive communication, post-mortems, and contexts where personal register would feel manipulative.

Pairs well with

pastoral, friendly-mentor, encouraging

Often confused with

encouraging: Warm is a general orientation of care toward the reader. Encouraging is specifically motivational - it is about activating forward motion and naming capability. You can be warm without being encouraging, and you can encourage without warmth (though warmth helps).

empathetic: Warm is a steady, general regard you can sustain across an entire document without ever naming the reader’s specific situation. Empathetic tone is a foreground move that opens by naming the precise difficulty the reader is in, at a moment when that naming is the point. Warmth can carry ordinary content; empathetic tone is reserved for moments of real difficulty and leads with the hardship, not with gladness.

Tells

• Direct address: “you,” often early
• Acknowledgment of the reader’s situation or effort
• Personal investment (“I want you to get this right”)
• Second-person possessives (“your work,” “your situation”)
• Short, human sentences alongside longer explanations
• Inclusive language (“we” when speaking of shared effort)

Anti-patterns

• Reaching for flattery (“you are amazing”) in place of specific regard - Warmth is distinguished from flattery by specificity and restraint; it notices the actual person (“I am glad you are here”), where flattery inflates and asks nothing of the writer’s attention.
• Opening by naming the reader’s specific hardship as the load-bearing move - That is empathetic, a foreground move reserved for moments of real difficulty; warmth is a steady regard that can carry ordinary content without ever naming a particular situation.
• Treating general care as if it activates the reader toward a next step - That is encouraging, which is motivational and names capability; warmth notices and regards the reader but does not, on its own, push toward forward motion.

Failure modes

• Over-hits care into the saccharine, using warmth to perform likability rather than to regard the reader - Keep it specific and restrained: name the situation, name the effort. Authentic warmth does not need to be effusive to be felt, and gushing signals performance, which is the absence of warmth dressed up as warmth.
• Over-extends into familiarity that collapses the appropriate distance, presuming an intimacy the relationship has not earned - Warmth regards the reader without claiming closeness it does not have; keep the regard genuine but calibrated to the actual relationship, since forced intimacy makes the reader withdraw rather than feel met.

Instruction

Write in a warm tone. Communicate genuine care for the reader - not flattery, not performance,
but specific and authentic regard. Address them directly as "you." Acknowledge what they are
dealing with. Use "I want you to get this right" or "I am glad you are here" rather than "we
value your feedback." Keep warmth specific - name the situation, name the effort. Do not tip
into saccharine: warm is restrained and real, not gushing. Unlike an empathetic tone, you need
not lead by naming the reader's specific hardship; warmth is a steady regard you can carry even
through ordinary content, centering gladness and care before moving to the substance.

Related

Pairs well with

Pastoral, Friendly Mentor, Encouraging

Avoid with

Operator, Pragmatic Architect, Matter of Fact

Often confused with

Encouraging, Empathetic

Examples

Should we adopt async-first standups?

Hey team,

I want to share something I have been sitting with for a few weeks, and I want your honest reaction to it.

Our standup is not working well for everyone on this team. I know that. The people joining at 9:30pm their time - I see you, and I appreciate that you keep showing up. That should not be the ask. You should not have to choose between participating in the team rhythm and having a life after 9pm.

I have been looking at how other teams handle this, and I want to try something: moving to an async standup format for 30 days. Each person posts a short update to #team-standup by 10am their local time - what shipped, what is in progress, what is blocked. If you are blocked, you @mention the person who can help. I commit to reading the channel every morning and making sure blocked items get attention the same day.

What I hope this gives you is the ability to participate in a way that actually fits your day. A standup that requires me to see you all at the same moment was designed for a team that lived in the same building. We are not that team. I want our coordination practice to match the team we actually are.

I do not want to lose the sense of being in this together, so I want to keep a weekly sync on Thursdays - not for status, just for the work that needs real conversation. That is the standup I want to grow.

Can you each take five minutes this week to think about whether this would work for you? Drop your reactions in thread. If there are concerns I have not thought through, I want to hear them before we start.

Grateful to be building this with you.

How to start a morning routine

I have been thinking about your mornings. The real ones, not the ones in the photos.

You probably wake up a little tired. The phone is right there. You check it before your eyes are fully open, and within ninety seconds you are already a step behind the day. Maybe somebody else in the house is also awake, and the morning becomes about them before it becomes about you. By the time you get to work, you feel like you have already lost a small argument with the day.

I want to say first: that is not failure. That is what mornings look like for most thoughtful adults with full lives. The fact that you are even thinking about doing this differently says something kind about how you want to live.

When you build a morning routine, I would like you to start from where you actually are, not where the morning influencers are. You do not have to wake up at 5am. You do not have to run six miles. You do not have to journal three pages. Those things might fit your life eventually, and they might not, and either is fine.

Here is what I would suggest, gently. Pick a small thing that already brings you a little pleasure. Coffee made the slow way. A window open for two minutes while it brews. A book you actually want to read, even one page of it. Do that thing first, before the phone, before the inbox, before the world arrives. That is your routine. That is enough to start.

You will miss days. The kids will wake up early. You will sleep through the alarm. None of that undoes the practice. The routine is not a streak; it is a return. You come back to it the next morning, with the same care, and the days quietly add up.

Be patient with yourself. You are doing something tender here.

How to choose between Postgres and DynamoDB for a new service

Warm on: Choosing between Postgres and DynamoDB

Marcus, Priya, team,

I wanted to write something before Wednesday that is not a decision memo. It is just a note from me, before the meeting, while I have a quiet ten minutes.

Marcus, you have put real work into the DynamoDB case, and I want you to know I have read all of it. Twice on the access-pattern document, three times on the load projections. You did the thing I always hope a senior engineer on this team will do: you took a position the room was not leaning toward and you built it carefully enough that we have to engage with it rather than wave it off. That has been good for the decision and good for me. I want you to walk into Wednesday knowing that your work is part of what made this a real conversation.

Priya, the way you have held this week is not lost on me. You have a Friday deadline that you did not invent, and you are managing the pressure of it without putting that pressure onto Ana and Marcus in a way that would compress their thinking. That is harder than it looks from the inside, and I want you to know I see you doing it.

To the four people in the on-call rotation: whatever we pick on Wednesday, the operational consequences land on you first. I have not forgotten that. I want to make sure that whichever decision we make, you have time in the next two sprints to learn what you need to learn, update what you need to update, and shape the runbook to something you can actually use at 3am. If that means slowing down the notifications launch by a week, we will slow it down by a week. You are not the people I am willing to spend to hit a date.

500K events a day at launch is a number that represents people we are trying to serve well. It is also a number that represents the work this team is going to carry. Both of those things are real, and I want us to make the call on Wednesday with both of them in the room.

Whatever we pick, I am glad I am picking it with you. See you at 2pm.

• Ana

Telling stakeholders a committed feature is being cut this quarter

I want to be honest with you, and I want to do it personally - not through a release note or a changelog entry.

You were promised Insights by the end of Q3. We are not going to deliver it on that timeline, and you deserve a straight explanation of why.

Earlier this year, a mandatory migration of our billing infrastructure surfaced work we had underestimated. That migration is not optional - it underpins how we charge every customer and process every invoice, and it had to be completed correctly. By the time we understood its full scope, it had consumed the engineering capacity we had reserved for Insights. We faced a choice: ship Insights on schedule in a state we knew was incomplete, or delay it and ship something you could actually use. We chose the delay.

Insights will be in your hands in Q1. We are not putting a softer date on it; Q1 is the target and we are treating it as a commitment.

Here is what we are doing before September closes: you will have a CSV export of the underlying Insights data, available directly from your account. It is not the in-app experience we built toward, and we know that. But it means you do not have to wait until Q1 to start working with the data your team cares about. You can pull it into your own tools now, on your own schedule.

I am glad you are still with us through this. Your patience is not something I take for granted, and I want Insights to earn it when it arrives.

Getting a new engineer productive in their first two weeks

Priya, I am glad you are here.

The first two weeks on a team like this can feel like a lot is happening at once - new faces, new systems, a codebase that rewards patience, and an on-call rotation that runs whether or not you feel ready for it. You do not need to know everything yet. That is not the goal.

Here is what matters in week one: getting you access, getting you oriented, and starting to understand the shape of the system. We will walk through your local setup together on day one and sort out any accounts that are still pending. Some of this is tedious - there is always a permission that takes an extra day to come through - and that is fine. Use the wait to read. The architecture overview is a good place to start; this team ships every day, and understanding what you are shipping into makes everything else click faster.

In week two, we will pair on a small change together. Not a toy exercise - a real one that ships. The goal is that you walk out of your second Friday having put something into production. That matters to me. It matters because it is yours, and because crossing that line changes how you feel about belonging to the team.

Who owns what is worth learning early. There is a map; we will go through it. When something breaks or confuses you, knowing who to ask is half the solution.

By the end of week two, you should feel like you work here - not just function here.

Writing to thank a mentor who shaped your career

Dana,

I want you to know I’ve been thinking about you lately - not for the first time, but differently.

About ten years ago, you put my name forward to lead the Harmon integration. I remember staring at the project brief and thinking there must have been some mistake. The timeline was tight, the stakeholders were skeptical, and I had only ever been a supporting hand on work like that. I hadn’t earned it yet, or so I thought.

You disagreed. And you didn’t just make the recommendation and step back. You stayed close in a way I didn’t fully appreciate then. You’d check in on how I was handling the Thursday calls. You’d ask about the decision I’d been wrestling with, and you’d listen before you spoke. When I started to spiral after the first milestone slipped, you said something I’ve repeated to myself more times than I can count: “You are not behind. You are right where the work needs you.”

What I didn’t understand at the time was what that cost you. Not just patience, which it clearly did, but the willingness to let it be hard for me when it would have been easier for you to take over. You had to hold yourself back. That is a specific kind of generosity.

I know this because last month I put someone on my team - a younger project lead named Marcus - into a role I wasn’t sure he was ready for. I found myself checking in the way you used to, and saying less than I wanted to. And about three weeks in I realized: I learned this from you.

I don’t know if anyone ever told you that. I’m telling you now.

Reflecting on keeping a discipline of rest

I want to tell you something I have been slow to learn: a day of rest is harder than it sounds, and the difficulty is the point.

You know the pull. It is Sunday morning, or whatever morning you have given yourself, and you think of one email that could wait and somehow cannot. You think of the message you did not send, the task you left at the edge of completion. The work follows you into the quiet not because it demands to, but because you have trained yourself to let it.

I failed at this for a long time. I would declare a rest day and spend it rehearsing the week. I would put down the laptop and pick up my phone. I would find a dozen small ways to stay useful, to keep the meter running, because the alternative - genuine stillness - felt like falling behind.

What I did not expect was what the rest gives back. Not immediately, and not without cost. The first hours are uncomfortable. The silence asks something of you that the work never does: to simply be there, without anything to show for it.

But something shifts, usually by afternoon. The week that felt like a tangle starts to settle. You notice what actually matters. The things you were chasing with such urgency look a little smaller from a day’s distance, and the things you had been ignoring start to surface.

You do not have to have this figured out. If you have tried it and abandoned it, that is where most of us start. The rest is waiting for you to try again.

Marking a long-serving colleague's departure

Howard, you have been here longer than most people have known where they wanted to work.

Twenty-six years in the same role is not something that happens by accident. You chose it, year after year, because the work was worth doing and because the people doing it needed someone steady. That was you. When the system broke at the wrong hour or the deadline moved without warning, people did not panic - they found you. Not because you always had the answer, but because you made the problem feel survivable.

What most of the people you helped will not realize until later is how much of what they know, you gave them. You did not call it mentoring. You called it lunch, or a quick question, or “let me show you how this works.” A dozen careers carry a piece of your patience in them, whether or not they know to name it.

We have been lucky to work alongside you. That is not a thing we say at retirement parties to be polite. It is specific: lucky that you stayed when staying was not glamorous, lucky that you cared about the right things at the right moments, lucky that you noticed the people around you well enough to know what they needed before they asked.

You are leaving the kind of absence that does not fill. We will keep your habits where we can. And we are glad - genuinely glad - that you spent this part of your life with us.

Marking the team shipping a hard, long project

Something I want you to know, before anything else: what you just finished was real. Not flashy, not the kind of thing that earns a headline, but real in the way that only long, careful, grinding work can be.

For fourteen months, your team kept two systems alive at once. The old checkout kept running, transactions clearing, customers checking out, while right underneath it you were building the thing that would replace it entirely. That is not a small ask. It means double the monitoring, double the anxiety at two in the morning, double the careful hands on the deployment scripts. It means walking through the door every day with both systems in your head.

There were two moments where it almost came apart. Priya held the first one together at midnight on a Wednesday, catching a data migration edge case that would have corrupted six weeks of records. Marcus held the second one in the war room the morning of the first launch attempt, when the load test surfaced a race condition no one had predicted. Both of them said the right thing at the right moment - not the heroic thing, just the honest one.

The launch slipped twice. You all know that. You also know why. And when the rollout finally happened, it held. Under peak load, during the highest traffic window of the quarter, the new flow held.

I am glad you were the team that did this work. Not because it went perfectly - it did not - but because when it got hard, you did not look for an exit. You kept going.

That matters. So does your work here.

Arguing a public position on return-to-office

I want you to get something real out of this conversation, not just my opinion wrapped in policy language.

You are navigating something genuinely hard. If you lead a team that thrives on in-person rhythm, you are not wrong that offices build things video calls cannot. If you have built your life around remote work, you are not wrong that the commute hours you reclaimed belong to you. I am not here to dismiss your situation.

Here is where I land: a deliberate hybrid, with a few shared anchor days and the rest flexible. Not as a compromise that pleases no one, but as a structure worth defending on its own terms.

The case for anchor days is not that offices are better. It is that some kinds of trust take a room. When you have worked alongside someone through a hard conversation, or eaten lunch while the project was still uncertain, you carry that into the months of async work that follow. That is worth protecting, and you cannot schedule it in the abstract.

But the rest of your week - the focused work, the deep thinking, your personal rhythms - those belong to you. Forcing that work into an office does not improve it. It costs you time, and it costs us the talent we cannot reach when geography is the filter.

I know this does not satisfy everyone here. Office-first colleagues, I hear that you want the whole team present. Remote advocates, I hear that anchor days feel like the beginning of a slow rollback. Both of you deserve a real answer, not reassurance.

What we owe each other is to design those anchor days with genuine intention - and then to trust you with the rest.

Announcing a new product to an outside audience

We are glad you are here. Tidemark launches next week, and we wanted to introduce it properly - not with a list of features, but with a conversation.

You are probably building something with a small team. You talk to customers, collect what they tell you, and then you face the hard part: turning all of that scattered input into a plan your team and your stakeholders can actually trust. The notes are in the chat tool, the tickets are in the tracker, the sticky note from last quarter is somewhere you have stopped looking. You know what your customers want - mostly - but getting it organized and in front of the right people takes longer than the insight deserves.

Tidemark gathers your feedback from wherever it lives and helps you surface what matters most. It produces a ranked, shareable roadmap you can put in front of anyone - your team, a board member, a reporter. It does not replace your judgment; that is yours. It just gives your judgment something clear to work with.

This is not a tool built for large organizations with full-time researchers. It was made for the teams where one person is doing three jobs and customer feedback is valuable but messy to manage.

If you want early access, the link below will take you straight there. We will walk you through setup personally, and we genuinely want to know what you think.

We are glad you found us.

A personal year-end reckoning with a difficult year

You have been with me through enough that I want to say this plainly: this year was hard, and it did not end well.

The project - the one I had worked on for nearly three years - closed in April without the outcome I had hoped for. I want to be honest about that. I had believed in it more than the evidence warranted. I held on past the point where holding on was wisdom, and when it ended I told myself stories about timing and circumstances that were partly true and partly a way of not looking at my own choices. I got things wrong. The product was not the problem I thought it was. I misread what the people around me needed. I was slower to listen than I should have been.

And then, a few months later, the relationship with Marcus changed - not ended, exactly, but became something different and smaller than what it had been. That one I did not choose and could not fix, and I have had to sit with not knowing what I did or did not contribute to it.

I have tried not to wrap any of this in a gift. Some things just cost you something, and this year cost me. I know you know that too.

What I am carrying forward is a clearer sense of when I am holding on out of fear, and a little more respect for the people who told me hard things early. That is not a silver lining. It is just what I have to show for it, and I wanted you to have the honest version.

Appears in diff-pairs

• warm vs diplomatic (varies tone)
• warm vs empathetic (varies tone)
• warm vs encouraging (varies tone)
• warm vs reverent (varies tone)
• warm vs candid (varies tone)
• warm vs diplomatic (varies tone)
• warm vs reverent (varies tone)
• warm vs encouraging (varies tone)
• warm vs empathetic (varies tone)
• warm vs diplomatic (varies tone)
• warm vs empathetic (varies tone)
• warm vs encouraging (varies tone)
• warm vs reverent (varies tone)