> For the complete documentation index, see [llms.txt](https://jamiewen00.gitbook.io/tech-lead-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jamiewen00.gitbook.io/tech-lead-handbook/communication/use-positive-language.md).

# Use Positive Language

## **The What**

Present yourself 100% and stay positive. avoid unintentionally planting doubts or negative thoughts in your audience's mind.

## **The How**

**Negative Language**

Words like “just”, “only”, “small”, or “but” can unintentionally downplay the value of your work.

**Reframe Positively**

Instead of saying, “We are a small team”, say “We are a dedicated team focused on xxx”.

**Focus on Strengths** 

Highlight the strengths and benefits of your proposal or solution. Emphasise what makes your approach unique and valuable. 

## ✅ Exceptions

* Acknowledging limitations can build trust. Transparently communicating can set realistic expectations
* Be honest. Saying “I don’t know” can be strong. 
* Be accountable. Avoid making unrealistic promises.

## **🔴 Red Flags**

* Avoid overcompensating 
* Don’t making unrealistic promises
* Avoid credibility issues


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://jamiewen00.gitbook.io/tech-lead-handbook/communication/use-positive-language.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.