> For the complete documentation index, see [llms.txt](https://wiki.stoicfellowship.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.stoicfellowship.com/wiki/exercises/roles-relationships-and-speech/do-not-speak-too-much-about-yourself.md).

# Do Not Speak Too Much About Yourself

Keep self-reference proportionate to the needs of the conversation

> **Also known as:** Don't Speak About Yourself

> **Practice basis:** Ancient instruction with a modern title

Keep self-reference proportionate to the needs of the conversation.

## At a Glance

* **Use when:** You are tempted to turn a conversation toward your experiences, achievements, or hardships.
* **Trains:** humility, listening, and social attention
* **Time:** One to ten minutes.
* **Timing:** Before or during the relevant situation.

## Purpose

In *Enchiridion* 33.14, Epictetus advises against speaking much about your own deeds or dangers; what interests you does not necessarily interest others. The practice does not prohibit personal disclosure. It prevents the desire for attention from making you the center of every exchange.

**Core Stoic Skill:** Humility, listening, and social attention in conversation.

## How to Practice

1. **Notice the turn.** Catch the urge to answer another person's story with your own.
2. **Test the contribution.** Ask whether your example serves the conversation or seeks attention.
3. **Keep it proportionate.** Share only what helps, then return attention to the other person or common subject.
4. **Listen for duty.** Make room for what the relationship requires you to hear.

## Example: The Matching Story

A friend describes a difficult diagnosis. You have faced something similar, but a long account of your experience would move attention away from the friend. You offer the small part that may help, then ask what support is needed.

## Common Mistakes

* **Withholding relevant experience.** Share when it can genuinely help.
* **Performing humility.** Do not make restraint another way to seek praise.
* **Counting sentences instead of purpose.** A necessary explanation may be long.
* **Using questions to control the conversation.** Listening is not interrogation.
* **Assuming your story is the same.** Let the other person's experience remain their own.

## In-the-Moment Phrases

* “Does this serve the conversation?”
* “Make room.”

## Optional Reflection

Use these questions for journaling or quiet contemplation. Writing is optional.

* What desire was my speech trying to satisfy?
* What would better speech have served?

## Source Anchors

* Epictetus, *Enchiridion* 33.14

## Related Exercises

* [Speak Little and Well](/wiki/exercises/roles-relationships-and-speech/speak-little-and-well.md)
* [Reframing Insults](/wiki/exercises/roles-relationships-and-speech/reframing-insults.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.stoicfellowship.com/wiki/exercises/roles-relationships-and-speech/do-not-speak-too-much-about-yourself.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.