> ## 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.
# Leadership Prompt Playbook
> Ready-to-use GEMS prompts for the Thinker, Assistant, and Creator roles. Copy, fill in the placeholders, and go.
export const GlossaryRow = ({title, description, children, flip = false, titleClassName = "text-2xl font-semibold tracking-tight text-zinc-950 dark:text-white", descriptionClassName = "mt-3 text-base leading-7 text-zinc-700 dark:text-zinc-300"}) => {
return
{}
{title}
{description ?
{description}
: null}
{}
;
};
These prompts are drawn from the Pathfindr Leadership Prompt Playbook by Dawid Naude. Each one uses the GEMS framework: Goal, Environment, Method, Sources. Copy the template that fits your task, replace every `[placeholder]` with your own details, and delete any fields that do not apply.
***
## Thinker prompts
Use these when you need AI to research, analyse, or stress-test your thinking before you make a decision.
### Market research brief
Use this when you need fast context on a market, sector, or competitive landscape before making a strategic decision. Paste in your business context so the output is specific to your situation rather than generic.
```text theme={null}
Goal
- Persona: Senior strategy analyst
- Primary Objective: Brief me on [market or sector]
to inform a [decision you are making]
by [timeframe]
Environment
- Organisation: [Size, industry, relevant
history, and why this market matters]
- In Scope: [e.g. market size, key players,
growth drivers, barriers to entry]
- Out of Scope: [e.g. international markets,
data prior to 2020]
Method
- Structure: Executive briefing with
sections for [section 1], [section 2],
[section 3], and a go/no-go framing
- Tone: Direct and analytical
- Flag any figures I should verify before using
in a formal document
Sources
- Use current sources.
Prioritise [preferred source
types, e.g. government data,
industry reports, analyst coverage]
```
***
### Competitor dossier
Use this to build a fast profile of a competitor before a pitch, strategy review, or board discussion. Works best with a web-connected AI tool or deep research agent.
```text theme={null}
Goal
- Persona: Competitive intelligence analyst
- Primary Objective:
Profile [Competitor name] in
Australia and deliver a one-page briefing
with cited sources
Environment
- My organisation: [Industry, size, and
how we position against this competitor]
- What I need this for: [e.g. upcoming pitch /
strategy review / board update]
Method
- Cover: revenue signals, estimated headcount,
recent customer wins or losses, pricing signals,
hiring themes
- Infer strategic intent from the evidence
- Flag anything that warrants a direct response from us
- Deliver as a one-pager. Include citations.
Sources
- Use web search. Prioritise: LinkedIn, ASX or press
releases, industry news, job ads.
```
***
### Signal reading
Use this when a competitor has published something — an interview, an announcement, a job ad — and you want to extract the strategic signal from it quickly.
```text theme={null}
Goal
- Persona: Strategy analyst reading between the lines
- Primary Objective: Analyse this [interview /
announcement / article] and infer what [competitor]
is likely to do next
Environment
- Market: Australian / ANZ
- Our position: [Brief description of how we compete
with this organisation]
Method
- Identify the stated strategy
- Infer the unstated strategy from the evidence
- Flag contradictions or inconsistencies
- List likely ANZ moves in the next [6 / 12] months
- Use numbered points. Be direct.
Sources
- Source material: [paste article, interview transcript,
or announcement here]
```
***
### Devil's advocate
Use this when you have a plan or position and want AI to argue against it. The goal is to surface risks and blind spots before you commit — not to get validation.
```text theme={null}
Goal
- Persona: Sceptical [board member / investor /
regulator — choose the most relevant]
- Primary Objective: Argue against the following plan
and surface every significant risk or assumption
I may have missed
Environment
- Background: [Paste your plan, proposal, or
decision here]
- In Scope: [e.g. strategic risks, financial assumptions,
execution risks, market assumptions]
- Out of Scope: [e.g. minor stylistic or formatting issues]
Method
- Numbered list of risks, ranked by severity
- Do not soften the critique
- Ask me for anything missing before you start
Sources
- Plan or proposal: [paste here]
```
***
### Policy crash course
Use this when a regulation, compliance requirement, or government policy has changed and you need to understand it fast. Paste in any source material you have, or ask AI to research it for you.
```text theme={null}
Goal
- Persona: Compliance adviser to a mid-market
Australian business
- Primary Objective: Brief me on [regulation or
policy topic] and tell me what we need to do
Environment
- Organisation: [Size, industry, relevant structure,
e.g. 150-person business with staff in three states]
- Current state: [What we currently have in place,
if anything]
- Timeframe: [Any known deadlines]
Method
- Summarise what the regulation requires
- Explain who is affected and how
- Provide a practical checklist of actions
- Flag any areas where I should seek legal advice
before acting
Sources
- Use current Australian government or regulatory
sources. Cite them so I can verify.
- Internal documents: [paste if relevant]
```
***
### Customer insight synthesis
Use this after gathering sales calls, interview notes, or survey responses. Paste in your raw notes and let AI surface the patterns — then validate the output against what you already know.
```text theme={null}
Goal
- Persona: Customer research analyst
- Primary Objective: Turn these [X] notes into the top
five jobs-to-be-done, each with a direct quote
Environment
- Customer type: [Role, industry, company size]
- What we are trying to understand: [e.g. why customers
choose us, what is blocking purchase, what they
wish we offered]
Method
- Identify the top five jobs-to-be-done from the notes
- Support each with at least one direct quote
- Note any patterns that appear across multiple customers
- Flag anything that contradicts our current assumptions
Sources
- Notes: [paste sales call notes, interview transcripts,
or survey responses here]
```
***
## Assistant prompts
Use these when you need AI to turn an existing input into a structured output — drafts, summaries, action lists, and formatted documents.
### Prioritisation
Use this when your day is full and you need to cut through the noise fast. Paste in your calendar and let AI apply the Eisenhower matrix so you spend the day on what actually matters.
```text theme={null}
Goal
- Persona: Executive chief of staff
- Primary Objective: Turn today's calendar into three
must-dos and a clear delegation list
Environment
- Role: [Your role, e.g. CEO / GM / Director]
- Organisation: [Industry and rough size]
- Situation: [Any context on what is at stake this week,
e.g. end of quarter, board meeting tomorrow]
Method
- Apply the Eisenhower matrix to each calendar item
- For each must-do, give a one-line reason why it matters
- List everything that should be delegated this week
and suggest who should own it
- Be direct. Do not soften the output.
Sources
- Today's calendar: [paste or describe your schedule]
```
***
### Inbox triage
Use this when your inbox is out of control. Paste in the emails and let AI sort them into actions, delegates, and declines — with draft replies ready to send.
```text theme={null}
Goal
- Persona: Executive assistant to a time-poor leader
- Primary Objective: Condense [X] emails into a
clear action plan with draft replies
Environment
- My role: [Your role]
- Communication style: Direct. Plain Australian tone.
No unnecessary softening.
- Standing context: [e.g. current priorities, key
relationships, sensitivities AI should know]
Method
- Group into: three actions, one delegate, one decline
- Draft replies for each action item
- Flag any GST, invoice, or compliance issues
that need same-day attention
Sources
- Emails: [paste email content here]
```
***
### Meeting notes to actions
Use this after any meeting where decisions were made and actions assigned. Paste in raw notes — even messy ones — and specify who the output is for so the format and level of detail is right.
```text theme={null}
Goal
- Persona: Executive assistant summarising for a
time-poor leader
- Primary Objective: Turn these meeting notes into
a structured action list for [audience]
Environment
- Meeting type and purpose: [e.g. quarterly strategy
review, client debrief, board pre-read]
- Attendees: [List key people. Note anyone absent
who needs a briefing.]
- In Scope: Decisions made, action items, unresolved issues
- Out of Scope: General discussion that did not lead
to a decision or action
Method
- Three sections: Key Decisions, Action Items
(with owner and due date), Unresolved Issues
- Tone: [Direct and professional / Warm and accessible]
- [One page / Two pages] maximum. Bullet points.
Sources
- Meeting notes: [paste here]
```
***
### Meeting prep
Use this before any significant customer or stakeholder meeting. The more context you provide about the relationship and the agenda, the more specific and useful the briefing.
```text theme={null}
Goal
- Persona: Senior research analyst preparing a
pre-meeting briefing
- Primary Objective: Build a one-page briefing for
a meeting with [name or company] on [date]
Environment
- My role: [Your role]
- Their role: [Name, title, organisation]
- Meeting purpose: [What you are meeting to discuss
or decide]
- Relationship: [New prospect / existing client /
partner / internal stakeholder]
Method
- Cover their recent ASX announcements, press releases,
or LinkedIn activity
- Note any open issues, tickets, or NPS data on our side
- Close with three sharp questions worth asking in
the meeting
- Keep it to one page. No filler.
Sources
- Account notes or open issues: [paste if available]
- Use web search for public announcements and
LinkedIn activity
```
***
### Client communication
Use this when you need to draft a sensitive or high-stakes client email. The more context you give about the relationship and the situation, the less generic the output.
```text theme={null}
Goal
- Persona: Senior communications writer
- Primary Objective: Draft [an email / a letter /
a message] to [describe the client or recipient]
about [topic]
Environment
- Situation: [What happened, what the client knows
so far, and the relationship context]
- In Scope: [e.g. accountability, revised timeline,
next step]
- Out of Scope: [e.g. internal details the client
does not need to know]
Method
- Tone: [Direct and professional / Warm and empathetic /
Formal — choose one]
- Under [word count] words
- Include [specific element, e.g. a revised timeline
and one clear next step]
Sources
- Any relevant background or prior correspondence:
[paste here]
```
***
### Difficult conversations
Use this when you need to address underperformance, missed targets, or a behavioural issue in writing. The more specific you are about the situation, the less generic the draft.
```text theme={null}
Goal
- Persona: Senior HR adviser and communications writer
- Primary Objective: Draft [written note / email /
talking points] addressing [the issue] with
[individual / team]
Environment
- Audience: [Individual / team / department]
- Situation: [What has happened — be specific about
the gap between expected and actual performance
or behaviour]
- Relationship: [Direct report / peer / external partner]
Method
- State the current situation with specific metrics
or examples
- State what is expected going forward
- Describe the support available
- Set a review date
- Tone: firm, fair, and direct. Not punitive.
Sources
- Relevant data or examples: [paste performance
figures, incidents, or prior feedback here]
```
***
### 1:1 preparation
Use this before a high-stakes one-on-one with a team member at risk of leaving. The more context you give about the person and the relationship, the more specific and useful the output.
```text theme={null}
Goal
- Persona: Executive leadership coach
- Primary Objective: Prepare me for a candid 1:1
with [describe the person — role, tenure, situation]
Environment
- Context: [What is happening — e.g. high performer
showing signs of disengagement, possible flight risk]
- Relationship: [Direct report / skip level /
long tenure / recent hire]
- What I want from the conversation: [e.g. understand
their situation, retain them, agree on a path forward]
Method
- Draft six candid questions covering progression,
flexibility, and compensation
- For each question, note what I am listening for
- Close with a simple retention plan I could propose
if the conversation goes well
Sources
- Relevant context — recent performance, feedback,
known concerns: [paste or describe]
```
***
### Culture and engagement insights
Use this after a staff survey, engagement pulse, or team retrospective. Paste in the raw comments and let AI find the themes — then validate before you act.
```text theme={null}
Goal
- Persona: Organisational development adviser
- Primary Objective: Turn these survey comments into
themes and a set of experiments to run next quarter
Environment
- Team or organisation size: [X people]
- Context: [What prompted the survey, any known issues]
- Constraints: [Budget, authority, timeline]
Method
- Identify the top three themes from the comments
- For each theme, propose two practical experiments
to run next quarter
- For each experiment: include a rough cost, a suggested
owner, and how to measure success
- Be direct. Do not over-engineer the recommendations.
Sources
- Survey comments or feedback: [paste here]
```
***
### Daily executive brief
Use this to set up a morning briefing routine. Works well as a standing prompt you run each morning with a web-connected tool. Customise the industry and regulatory bodies relevant to your sector.
```text theme={null}
Goal
- Persona: Chief of staff preparing the morning brief
- Primary Objective: Summarise today's most relevant
news for a [role] in [industry]
Environment
- Industry: [Your sector]
- Regulatory bodies I track: [e.g. ATO, Fair Work,
ACCC, ASIC, APRA]
- Timezone: [e.g. AEST]
Method
- Five relevant industry stories with a one-line
"so what" for each
- Any material updates from [regulatory bodies]
- Notable competitor moves
- Flag anything requiring a decision or response today
Sources
- Use web search. Prioritise sources from the
last 24 hours.
```
***
## Creator prompts
Use these when you need AI to generate something new — a first draft, a set of ideas, a visual, or an interactive output.
### Pitch or proposal narrative
Use this when you need a first draft of a client-facing document. Paste in your Thinker research output as the source — this connects the two roles and produces a far more specific result than starting from scratch.
```text theme={null}
Goal
- Persona: Senior [business writer / strategist /
communications director — choose one]
- Primary Objective: Write a [length, e.g. two-page]
[document type, e.g. pitch narrative / proposal /
executive summary] for [opportunity or purpose]
Environment
- Client or audience: [Describe who this is for,
their role, and what they care about]
- Opportunity: [What you are proposing and why now]
- In Scope: [e.g. client problem, your approach,
proof points, next step]
- Out of Scope: [e.g. technical implementation detail,
pricing]
Method
- Narrative arc: [e.g. open with client problem,
introduce approach, reference experience,
close with next step]
- Tone: [e.g. Confident and direct. Not salesy.]
- Audience: [Job title or description of the reader]
Sources
- Thinker research output or briefing documents:
[paste here]
```
***
### Board update
Use this when you need to turn a strategy note or board pack into a structured summary and slide outline. Paste in the source document and specify your board's communication preferences.
```text theme={null}
Goal
- Persona: Senior communications adviser to a CEO
- Primary Objective: Turn this quarter's strategy note
into a two-page summary and a six-slide outline
Environment
- Board composition: [e.g. seven directors, mix of
financial and operational backgrounds]
- Communication preference: Measured, evidence-based.
No corporate hedging.
- Market context: Australian. Reference local conditions
where relevant.
Method
- Two-page summary: lead with decisions required,
follow with key data, close with recommended actions
- Six-slide outline: sequence for a 20-minute board slot
- Tone: measured and direct throughout
Sources
- Board pack or strategy note: [attach or paste]
```
***
### Investor or stakeholder communication
Use this when you need to rewrite a sensitive communication about a price change, policy update, or service adjustment. The more context you give about the audience, the less generic the output.
```text theme={null}
Goal
- Persona: Senior communications writer
- Primary Objective: Rewrite this [email / letter /
announcement] so it is clear, direct, and covers
everything the recipient needs to know
Environment
- Recipients: [e.g. retail investors / wholesale
clients / partner organisations]
- Subject matter: [e.g. price rise / policy change /
service update]
- Sensitivities: [e.g. GST implications, timing,
who is affected]
Method
- Be clear on what is changing, who is affected,
the timeline, and any financial or compliance details
- Add a short FAQ covering the most likely questions
- No hedging. No passive voice.
- Under [word count] words.
Sources
- Original draft: [paste here]
```
***
### Speechwriting
Use this to draft a short, direct address for a staff town hall, all-hands, or team meeting. Works best when you are specific about what has happened and what you want people to feel or do differently.
```text theme={null}
Goal
- Persona: Executive speechwriter
- Primary Objective: Draft a [60 / 90 / 120]-second
opening address for [event name or type]
Environment
- Audience: [Your team / all staff / leadership group]
- Context: [What has happened that prompted this
address, e.g. tough quarter, restructure, milestone]
- What I want them to feel leaving the room:
[e.g. clear on direction, trusted, held accountable]
Method
- Be direct, respectful, and specific
- Name the situation plainly. Do not soften it.
- Reference [cost discipline / service levels /
the specific issue] with concrete detail
- Close with a clear next step or ask
Sources
- Briefing notes or data to reference: [paste if relevant]
```
***
### Idea generation and scoring
Use this when you need a range of options fast. The scoring criteria force AI to evaluate rather than just list, which makes the output far more useful for prioritisation decisions.
```text theme={null}
Goal
- Persona: Product strategist with commercial judgement
- Primary Objective: Generate [10] ideas for
[opportunity or problem] and score them
Environment
- Organisation: [Size, industry, current constraints]
- Target customer: [Who we are solving for]
- Constraints: [Budget, team size, timeline,
anything out of scope]
Method
- Generate [10] ideas
- Score each on: impact, ease of execution,
and time-to-value
- Recommend the top three to test within [4 weeks /
one quarter]
- Be direct about trade-offs
Sources
- Context on current offerings or past experiments:
[paste if available]
```
***
### Objection testing
Use this before a pricing change, product launch, or major proposal. Simulating the hardest questions forces you to tighten your position before you are in the room.
```text theme={null}
Goal
- Persona: Sceptical [CFO / procurement lead /
board member] at a [X]-person [industry] company
- Primary Objective: React to the proposal below and
list every significant objection
Environment
- Their situation: [Describe the buyer — size, industry,
current pressures, likely priorities]
- What we are proposing: [Brief description of the
offer, price, or change]
Method
- List the most likely objections in order of severity
- For each objection, draft a tight, numbers-backed
response
- Flag any objections we do not currently have
a strong answer to
Sources
- Our proposal or pricing information: [paste here]
- Relevant case studies or proof points:
[paste if available]
```
***
### Image generation
Use this formula for any image generation tool. The more specific the aesthetic and composition, the less you need to iterate.
```text theme={null}
Goal
- Primary Objective: Generate an image of [subject]
for use in [context, e.g. executive presentation,
client proposal, internal comms]
Environment
- Brand context: [Any colours, style guidelines,
or visual language to follow]
- Where this will be used: [e.g. slide deck, website,
printed document]
Method
- Subject: [Describe the main subject in detail]
- Setting: [Where is it? Describe the environment
or background]
- Aesthetic: [Photorealistic / illustration /
dark mode / minimalist / watercolour — choose one]
- Composition: [Wide shot / close-up / overhead /
portrait / first person]
Sources
- Brand colours or reference images: [paste hex codes
or describe visual references]
```
***
### Turn output into an interactive webpage
Use this as a follow-up to any structured output — a process, a workflow, a set of data. Works well in ChatGPT and Gemini. The result is a shareable visual that is far easier to absorb than a document.
```text theme={null}
Goal
- Primary Objective: Turn the output above into
a [process diagram / infographic / workflow /
interactive summary] as a shareable webpage
Environment
- Audience: [Who will view this?]
- Where it will be shared: [e.g. sent as a link,
embedded in a proposal, presented in a meeting]
Method
- Style: [Minimalist / dark mode / branded with
these colours: hex codes]
- Keep it easy to absorb at a glance
- Prioritise clarity over completeness
Sources
- Previous output: [reference the output above
or paste here]
```
***
### Data dashboard — two-prompt workflow
Use this when you need to visualise financial or operational data for a non-technical audience. Run prompt one to plan the dashboard, then prompt two to build it. Splitting the task produces significantly better results than asking for everything at once.
```text theme={null}
Prompt 1 — Plan the dashboard
Goal
- Primary Objective: Read [document name] and identify
the most important [financial / operational] numbers
Environment
- Audience: [e.g. non-financial executive team]
- Brand: [Colour palette or hex codes if known]
Method
- Identify the key metrics and figures to display
- Recommend a chart type for each metric
- Propose a simple layout
- Do not build anything yet — produce a plan only
Sources
- Document: [attach or paste]
---
Prompt 2 — Build the dashboard
Goal
- Primary Objective: Code the dashboard from the
plan above
Method
- Keep it easy to understand for [describe audience]
- Use the colours and layout from the plan
- Output as a self-contained webpage
```