> 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/dont-lecture-about-philosophy.md).

# Don't Lecture About Philosophy

Demonstrate philosophy in conduct instead of displaying doctrines

> **Also known as:** Don't Lecture

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

Demonstrate philosophy in conduct instead of displaying doctrines.

## At a Glance

* **Use when:** You are tempted to correct, impress, or instruct people who did not ask.
* **Trains:** humility, example, and appropriate speech
* **Time:** One to ten minutes.
* **Timing:** Before or during the relevant situation.

## Purpose

Epictetus repeatedly warns students not to display philosophical principles before people who have not asked for them. In *Enchiridion* 46, he compares this display to sheep producing grass for the shepherd instead of wool. Philosophy should become conduct. Explain it when teaching is your role or someone sincerely asks; otherwise, let the practice show.

**Core Stoic Skill:** Humility, example, and appropriate speech in conversation.

## How to Practice

1. **Check your role.** Determine whether instruction has been requested or belongs to your responsibility.
2. **Check your motive.** Look for the desire to appear wise or win the exchange.
3. **Offer only what helps.** Answer the actual question in plain language.
4. **Return to practice.** Demonstrate the principle through conduct.

## Example: An Unrequested Lesson

A friend complains about a delayed flight. You are tempted to explain the dichotomy of control. The friend needs help finding a new connection and a little patience from you. You provide both; you save the lecture.

## Common Mistakes

* **Withholding needed teaching.** Teach clearly when it is your role or the person asks.
* **Using doctrine to dismiss distress.** Attend to the person and practical need.
* **Making silence a display of superiority.** Quiet contempt is still contempt.
* **Correcting vocabulary instead of helping.** Use technical terms only when they clarify.
* **Mistaking quotation for embodiment.** The test is conduct.

## In-the-Moment Phrases

* “Show the principle.”
* “Was I asked to teach?”

## 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* 46
* Epictetus, *Discourses* 3.21.4–6

## 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/dont-lecture-about-philosophy.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.