> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textql.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Module 1 · Ask Your Team’s Questions

> Goal: three asks — a number, a why, and decision support — the way you’d ask a (very fast) team. (~10 minutes)

**Goal:** three asks — a number, a why, and decision support — the way you'd ask a (very fast) team.

## 1.1 · The number

```text Prompt theme={null}
Revenue this quarter versus plan?
```

<Check>
  **You'll see:** the number, the plan, the gap — in seconds, not in next Tuesday's deck.
</Check>

## 1.2 · The why

The follow-up that normally costs a week of analyst time:

```text Prompt theme={null}
What's driving the miss?
```

<Check>
  **You'll see:** the gap decomposed — which segment, which product, volume or price — with the biggest contributor named. No new meeting was scheduled to produce this.
</Check>

## 1.3 · Decision support

```text Prompt theme={null}
I'm deciding [whether to expand the EMEA team]. What should I look at first?
```

<Check>
  **You'll see:** the relevant evidence assembled — trends, comparisons, capacity signals — framed for the decision, not just dumped. You direct the follow-ups from here, conversationally.
</Check>

<Note>
  Here's the real exercise: think of the question you *didn't* ask in the last board meeting because the answer would have taken analytics a week. Ask it now.
</Note>

<Frame caption="Ask what you would ask your team.">
  <img src="https://textqllabs.github.io/workshops/executives/assets/exec-m1-ask.png" alt="Ask what you would ask your team." />
</Frame>

### ✅ Checkpoint

* [ ] You got a number, a why, and decision support without leaving the conversation
* [ ] You asked the question you skipped in the last board meeting