home/roleplay/tone-encouraging-vs-instructional

Tone Encouraging vs Instructional

GPTClaudeGemini··943 copies·updated 2026-07-14
tone-encouraging-vs-instructional.prompt
---
diff_pair_id: tone-encouraging-vs-instructional-a-hard-year-in-review
topic_slug: a-hard-year-in-review
topic_label: A personal year-end reckoning with a difficult year
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:** A personal year-end reckoning with a difficult year
**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`

The project was called Meridian, and it failed. Not in a way I could blame entirely on bad luck or misaligned stakeholders - though both were present. It failed in part because I held the original vision too long when the evidence said revise, and by the time I revised, we had run out of runway. Liora, my co-lead, saw it coming six weeks before I did. I was not willing to hear it. That is not a comfortable thing to write.

The relationship - I will not name it, because some things lose something when they get named - changed because I could not be present in the way the other person needed. I was pouring everything into Meridian and calling it unavoidable. It probably was not unavoidable. That is also not comfortable to write.

Here is what I can actually say, though - and I am saying it as carefully as I said the harder things above: I stayed. I did not disappear into distraction or exit early. When Meridian wound down, I sat with the team through the close. When the relationship shifted, I showed up to those conversations even when they were painful. I did not do everything right, but I stayed present.

That matters because staying when you want to leave is the thing you build on. I am not further along than I think I am - I think the year cost what it cost. But I have handled things I did not know I could handle. I have a clearer account of where I misread the signals than I did a year ago. That clarity is not free, and it is not nothing. I am going into next year carrying different questions than the ones I started with. That is what I am choosing to take forward.

---

## B: `instructional`

Before you begin, establish what this exercise is: reckoning means accurate accounting of what happened, not resolution. You are not looking for lessons. You are building a clear record.

1. Name what ended. The Foundry project ran for two years and did not ship. If you find yourself softening this - writing "it didn't fully come together" instead of "it failed to reach its goal" - rewrite it. The record needs precision.

2. Name what changed without your choosing. The relationship with Mara shifted over the summer in ways I did not initiate. Before moving to the next step, check whether you are describing what happened or what it felt like. These are different operations. Finish the description first.

3. Separate what you got wrong from what was simply hard. Getting something wrong means: better information was available and you did not use it, or you made a decision you can now see clearly was a mistake. Apply this test when unsure: could you have known at the time? If not, it was not an error. Grief, exhaustion, and overwhelm are not errors.

4. Decide what to carry forward. This is the only forward-facing step, and it is not required. If nothing feels ready to carry, leave this blank. Carrying something forward is not the goal of the exercise. The goal is the accurate record.

If you reach the end and nothing has resolved, that is a correct outcome. Some years do not close.

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

roleplaycommunitygeneral

source

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