Encouraging
Speaks to capability and forward motion - not false praise, but genuine belief that the person can do the hard thing.
Encouraging
Section titled “Encouraging”Encouraging tone is not cheerleading. Cheerleading says “you have got this!” regardless of the actual situation. Encouraging tone says “I have seen what you can do, and this is within your reach” - and means it. The difference is epistemic: encouraging tone is based on actual evidence and belief, not on the social function of boosting confidence.
Encouraging tone is particularly valuable in educational and coaching contexts because it shifts the reader’s orientation from threat to challenge. The difficult thing becomes evidence of the reader’s capability rather than evidence of their inadequacy. Encouraging tone does not pretend the difficulty is not real - it holds the difficulty and the capability in the same breath.
The risk of encouraging tone is condescension - encouraging someone in a way that implies they need more encouragement than they do. The antidote is specificity: encourage the particular effort, the particular capability, the particular result, not generic “you.”
Markers
Section titled “Markers”- Specific acknowledgment of the effort or capability: “You have done the hard part by…”
- Future-orientation: “Here is what you can do with that”
- Naming the difficulty and the person’s relationship to it: “This is hard, and you are handling it”
- Active belief: “I think you can” not “hopefully you can”
- No false reassurance - if something is hard, say it and then encourage
- Progress markers: “You are further along than you think because…”
When to use
Section titled “When to use”Onboarding content, teaching materials, coaching contexts, feedback delivered with a growth frame, and any time the reader’s belief in their own capability is the obstacle.
When not to use
Section titled “When not to use”Executive reporting, post-mortems, neutral status updates, expert audiences who would find it condescending, and legal or compliance writing.
Pairs well with
Section titled “Pairs well with”friendly-mentor, warm, pastoral
Often confused with
Section titled “Often confused with”warm: Warm is a general orientation of care toward the reader - it notices them and regards them as a person. Encouraging is specifically motivational - it is about activating forward motion and naming capability. Warm can be present without encouraging, and you can encourage without warmth (though warmth makes encouraging land better).
Instruction
Section titled “Instruction”Write in an encouraging tone. You genuinely believe the reader can do the hard thing, and youhave evidence for that belief. Do not cheerlead - do not say "you have got this!" withoutgrounding it. Say "I have seen what you can do with X, and Y is within your reach." Name thedifficulty and hold it next to the capability in the same sentence. Acknowledge the specificeffort or progress already made. Future-orient: "Here is what you do with that." No falsereassurance - if it is hard, say so and then encourage. The difference from cheerleading:you mean it.Related
Section titled “Related”Pairs well with
Section titled “Pairs well with”Friendly Mentor, Warm, Pastoral
Avoid with
Section titled “Avoid with”Matter of Fact, Operator, Candid
Often confused with
Section titled “Often confused with”Examples
Section titled “Examples”Team,
I have watched you show up to that 9am standup for two years, including the people who join at 9:30pm their time, including the people who push through the weeks where it clearly does not fit their day. That kind of reliability is worth naming. You are a team that keeps showing up even when the format is hard.
I want to try something different - not because the effort was wrong, but because I think there is a better way to direct it.
Moving to async standups is a change, and changes like this often feel awkward for the first week or two. You will post an update and wonder if anyone read it. You will hit a blocker and instinctively want to raise your hand in the meeting. That discomfort is normal, and it passes. The teams I have seen make this shift usually hit their stride by week three.
What you have already built is the part that is actually hard: a team that is honest about blockers, that calls out when something is at risk, that does not hide bad news until it becomes a crisis. That does not come from the standup format - that comes from the culture you have built. The format change does not touch that. It just gives it a better container.
Here is what I am asking: give the async format 30 days before you decide whether you like it. Post your updates, mention your blockers, read what your teammates post. If by week four it still does not feel right, we will talk about what to adjust.
You have already done the hard part. This is just changing the tool.
You can build this. I know you have tried before, and I know some of those tries did not stick. That does not mean what you think it means.
Every previous attempt taught you something, even the ones that fell apart by Friday. You learned that 5am is too early for your sleep window. You learned that a journal you do not want to open is not a habit, it is a guilt object. You learned that checking your phone first sets the rest of the morning on a track you cannot easily change. That is real knowledge. It is the kind of knowledge most people never gather, because most people never try.
So when you wake up tomorrow and decide to try again, you are not starting over. You are starting from a much better position than the first time. You know your life. You know your mornings. You know which version of you shows up at 6:30am with a toddler awake.
Here is what I want you to trust. The first hour of your day is shapeable. Not all of it, not perfectly, but enough. You can move ten minutes into your column. You can claim the time before the inbox claims you. You have done harder things than this. You are doing one of them right now, probably, in some other part of your life.
Pick one thing. Make it small enough that you will be slightly embarrassed by how easy it sounds. Drink a glass of water before you touch your phone. Step outside for two minutes. Sit in one chair for the length of one song. Do that, and only that, for two weeks.
You will surprise yourself. Not on day one. Probably not on day three. But somewhere around day ten, you will notice that the mornings feel like yours again. That is the thing you are building toward, and you are entirely capable of getting there.
Encouraging on: Choosing between Postgres and DynamoDB
Section titled “Encouraging on: Choosing between Postgres and DynamoDB”Team,
Wednesday’s meeting is going to feel bigger than it is, and I want to say a few things in advance.
This is a hard call. There is no version of it that does not have real tradeoffs, and either path carries risk we will have to manage. I am not going to pretend otherwise. But I want you to know that this team is well positioned to make this decision and execute on it, and I have specific reasons for believing that.
You have already done the hard part. Marcus, you ran a real load test instead of arguing from intuition. Ana, you mapped the operational cost in concrete terms instead of waving at “ops complexity.” Priya, you held the timeline without compressing the substance. The decision in front of us is hard, but it is hard on top of work that has already been done well. You are further along than this feels.
On the technical question itself: we have shipped at the 500K-events-per-day scale before. We know how to design schemas and partition tables and tune queues at that level. If we pick Postgres, the path is one this team has walked. If we pick DynamoDB, Marcus has done enough discovery work that the learning curve is shorter than it would be for a team starting cold. Either way, we are not stepping off a cliff.
And on the 10x scenario: even if the Slack partnership lands and we have to migrate, that migration is 3 to 6 weeks. That is recoverable. We are not making a decision that will end the company if we get it wrong. We are making a decision that will cost some rework if we miss, and that is a category of cost this team can pay.
What I want you walking into Wednesday with: this is the kind of decision this team is built to make. You have the data, you have the operational instincts, and you have a PM who is going to back the call rather than relitigate it on Friday. Bring the analysis. Disagree where you disagree. Then commit to whatever the room decides and ship it. You can do this part. The hardest part is already behind you.
See you at 2pm Wednesday.
- Ana