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

# Meet Your Exec AI Assistant

> Move from using AI occasionally to directing it deliberately — and understand why that shift changes everything.

<img src="https://mintcdn.com/pathfindr/I3XbhzOlK6BeuXVO/images/LCWeek2Rundown.webp?fit=max&auto=format&n=I3XbhzOlK6BeuXVO&q=85&s=e0939eb126f7265c60e08ae5b80ab1f0" alt="leadership cohort structure Pn" noZoom={true} width="1920" height="1080" data-path="images/LCWeek2Rundown.webp" />

Most leaders have tried AI at least once. They pasted something in, got something back, and moved on. That is not the same as having an AI assistant. An assistant you brief. An assistant that knows what you need before you finish explaining it. That is what this week builds.

Right now, you are at a turning point in your AI journey. You have moved past curiosity. The next step is confidence — knowing how to shape a conversation so AI works with you, not just for you. That is the difference between AI as a novelty and AI as a genuine productivity lever.

<CardGroup cols={3}>
  <Card title="Thinker, Assistant, Creator" icon="square-1">
    Three roles, one framework — learn to direct AI depending on what you need it to do
  </Card>

  <Card title="The GEMS framework" icon="square-2">
    A single prompt structure that works across every role and every AI tool
  </Card>

  <Card title="Your Knowledge Base" icon="square-3">
    Give AI the context it needs to stop being generic and start being useful to your specific business
  </Card>
</CardGroup>

***

## Where you are on the journey

AI tools sit on a maturity curve. Most executives who arrive at this program have been using AI as a chatbot — and some have pushed further than that. They ask questions. They get answers. Sometimes it is useful. Often it feels hit and miss.

The next stage is workflow. This is where AI stops being a search engine and starts being something closer to a well-briefed team member. You direct it with a role. You give it context. You specify what you want back. The output quality jumps significantly.

<Info title="Why this matters for where you are going">
  Every AI agent you will eventually build runs on the same logic you will practise this week. Learning to direct them manually now is the groundwork for automating that direction later.
</Info>

***

## What you will do this week

You will work through the three AI roles using a single prompting framework — GEMS — applied to real work from your own context. You will also build a simple knowledge base that makes AI responses immediately more relevant to your business.

By the end of this week, you will have reusable prompts, a clear framework for deciding which role to assign, and a practical picture of where AI can take time off your plate right now.

<CardGroup cols={2}>
  <Card title="Thinker, Assistant, Creator" icon="hat-wizard" href="/leadership-cohort/week-2-meet-your-exec-ai-assistant/thinker-assistant-creator">
    One page covering all three roles, the GEMS framework, and example prompts you can adapt immediately
  </Card>

  <Card title="Building a Project Knowledge Base" icon="database" href="/leadership-cohort/week-2-meet-your-exec-ai-assistant/building-a-project-knowledge-base">
    Give AI persistent context so it understands your business, not just your prompt
  </Card>
</CardGroup>
