home/career/tone-encouraging-vs-instructional-2

Tone Encouraging vs Instructional

GPTClaudeGemini··412 copies·updated 2026-07-14
tone-encouraging-vs-instructional-2.prompt
---
diff_pair_id: tone-encouraging-vs-instructional-thanking-a-mentor
topic_slug: thanking-a-mentor
topic_label: Writing to thank a mentor who shaped your career
axis_varied: tone
entry_a: encouraging
entry_b: instructional
generator: tools/diff-pair-generator.py
review_status: reviewed
---

# Diff Pair: Tone swap - `encouraging` vs `instructional`

**Topic:** Writing to thank a mentor who shaped your career
**Axis varied:** tone
**A:** `encouraging` - Speaks to capability and forward motion - not false praise, but genuine belief that the person can do the hard thing.
**B:** `instructional` - Patient, structured teaching that measures its own success by whether the reader can do the thing - not by how much it explains.

## What to notice

Both examples address the same topic and (by default) share every axis other than tone. 
The only deliberate variable is which tone the writing was rendered through. Read both 
and ask: where does the framing change? Where does the vocabulary change? What does the 
reader take away from A that they would not take away from B, and vice versa? The tone 
swap is the entire cause of those differences.

---

## A: `encouraging`

Dana,

I have been trying to figure out how to write this for weeks. What finally got me started: last month I put one of my direct reports forward to lead a project she was not sure she was ready for. Then I spent six weeks resisting the urge to step in while she found her footing. She found it.

Somewhere in those six weeks, I traced where I learned to do that. It went back to you.

A decade ago you recommended me to lead the Calloway integration. I kept telling myself I was not ready. You did not argue with me about it. You told me what you had actually observed: that I had held two difficult client situations together without letting them collapse, and that Calloway needed exactly the kind of steady judgment you had watched me develop over the previous two years. You were not being generous. You were describing something real.

What I did not fully see at the time was what that cost you. Staying close without taking over is harder than taking over. Letting someone work through a hard problem, when you could resolve it yourself in an afternoon, takes a particular patience that is not passive - it is a sustained choice to trust someone's capacity over your own comfort. You made that choice repeatedly.

What you passed forward was not just my confidence. It was a working model of what it looks like to actually believe someone can do something hard - not to hope they can, but to point to the evidence and say: this person, this challenge, now.

I wanted you to know the model is still running.

---

## B: `instructional`

Dear Dana,

Before reading this letter in full, know why you are receiving it: I recently did something I did not know I had learned, and I traced it back to you.

Here is what I need you to understand, in the order it happened.

1. In the autumn of my first year on your team, you nominated me to lead the Radcliffe platform migration - a project that required judgment on decisions I had never made before. You told me I was ready. I disagreed. You were right.

2. For those eight weeks, you stayed available without taking over. When I hit the dependency handoff problem in week four - the one where my team and the receiving team had made incompatible assumptions - you did not solve it. You asked two questions and left. I resolved it the same day.

3. What you were practicing, without labeling it, was a specific pattern: place someone in the condition for success, then get out of their path while remaining within reach. That pattern requires patience that is invisible because it looks like ordinary absence.

Before you read the next step as routine news, note that it is the reason this letter exists.

4. Last month I put a direct report forward for a project she did not feel ready for. When she hit her version of week four, I felt the pull to step in and fix it. I stopped. I asked two questions. I left.

She solved it before the end of the day.

You can now see why I am writing. What you gave me a decade ago was not belief in my potential. It was a transferable procedure. I only recognized it when I ran it on someone else.

when to use it

Community prompt sourced from the open-source GitHub repo product-on-purpose/writing-style-catalog (NOASSERTION). A "Tone Encouraging vs Instructional" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.

tags

careercommunitygeneral

source

product-on-purpose/writing-style-catalog · NOASSERTION