Playbook: Alex for Business Analysts and Knowledge Workers

Your reference for applying Alex to analysis, reporting, strategic communication, and organizational influence. Ready-to-run prompts for the real work of knowledge professionals — not the sanitized textbook version.

What This Guide Is Not

This is not a habit formation guide (see Self-Study Guide for that). This is a domain use-case library — the specific things Alex can do in your work, and how to do them well.

Where to Practice These Prompts

Every prompt in this guide works with any AI assistant — ChatGPT, Claude, GitHub Copilot, Gemini, or whatever tool you prefer. The prompts are the skill; the tool is just where you type them. Pick the one you’re comfortable with and start today.

For an integrated experience, the Alex VS Code extension (free) was purpose-built for this workshop. It understands business analysis context, lets you save effective prompts with /saveinsight, and brings your playbook and practice exercises into one workspace. VS Code is a free editor that takes minutes to set up, even if you’ve never used it before.

You don’t need a specific tool to benefit. You need the habit of reaching for AI when the work is genuinely hard — not just when it’s repetitive.

Core Principle for Knowledge Workers

In business environments, the most valuable outputs are clarity and decision-readiness. Alex’s highest value is helping you move from scattered information to structured, audience-ready documents faster — without losing nuance.

The key pattern to master: brief Alex with context before asking for output. The more specific you are about audience, decision being supported, and format required, the better the output and the less editing you’ll need.

The harder truth: most knowledge worker AI use is shallow. People ask for drafts and accept generic output. The professionals who get real leverage treat Alex as a sparring partner — they push back, ask follow-up questions, stress-test conclusions, and ask what they’re missing. That is where the real value lives.

The Seven Use Cases

1. Executive Briefing and Reporting

The knowledge worker’s reporting challenge: Senior stakeholders have seconds of attention. The report that reads like a story of your analysis process is the report that gets skimmed. Executives want the answer first, then the evidence. Flipping that instinct is the hardest thing about upward communication.

When to use: Preparing reports, memos, or briefings for senior stakeholders. Translating complex analysis into decision-ready summaries.

Prompt pattern:

I'm preparing a [briefing / executive summary / memo] for [audience: VP / Board / Director].
Topic: [describe the situation or analysis].
Decision or action I need from them: [be specific].
Key facts: [list 3-5 most important data points or findings].

Structure this as:
1. Situation (2 sentences)
2. Key findings (3 bullets)
3. Options and recommendation
4. What I need from them

Follow-up prompts:

What questions will they likely ask that I'm not answering in this document?

Cut this to half the length. Keep the recommendation and the top finding.

Rewrite the options section — make the tradeoffs clearer without adding length.

This executive cares most about [risk / cost / speed / people impact]. Reframe the recommendation through that lens.

Try this now: Your CEO wants a 2-page briefing on whether to enter the Southeast Asian market by Friday. You have market sizing data from three conflicting reports, a competitor who launched there 6 months ago, and a CFO who wants proof of ROI within 18 months. Paste the raw data and conflicting numbers into the briefing prompt. The output will not replace your judgment — but it will give you a structured first draft in 15 minutes instead of 4 hours.

2. Scenario and Options Analysis

The knowledge worker’s options challenge: Most options analyses land as “here are three things we could do, all reasonable.” What executives actually want is a clear recommendation they can defend — with the logic that preempts the objections they will face. The analysis is not the deliverable; the defensible recommendation is.

When to use: Structuring a business case, evaluating options, or building a scenario model for a presentation.

Prompt pattern:

I'm building an options analysis for [decision or initiative].
The three scenarios I'm considering: [describe each briefly].
Key evaluation criteria: [cost / time / risk / strategic fit].
Constraint I cannot compromise on: [budget ceiling / timeline / compliance requirement].

Help me:
1. Build a comparison framework that makes tradeoffs visible
2. Identify which criteria the decision really turns on
3. Surface my unstated assumptions in each scenario
4. Construct the argument for the strongest option

Follow-up prompts:

What am I assuming in Scenario 2 that might not hold?

Play the role of a critic of my recommended option. What is the strongest case against it?

What evaluation criterion will someone on the executive team add that I have not included?

Build the 2x2 risk/reward matrix for these options.

3. Meeting Preparation

The knowledge worker’s meeting challenge: Most people walk into meetings with a vague sense of what they want and no plan for what can go wrong. Preparation is not about having the right answers — it is about having modeled the conversation well enough that nothing surprises you.

When to use: Before important meetings — stakeholder alignment, budget reviews, project kick-offs, difficult conversations.

Prompt pattern:

I have a meeting with [role] on [topic].
I need to achieve [outcome: decision / alignment / approval / information].
Their likely position: [what you expect them to say or resist].
My constraints: [what I cannot compromise on].

Help me prepare:
1. A clear opening statement (30-60 seconds)
2. The two or three points I must land
3. Likely objections and my responses
4. What success looks like vs. what good enough looks like
5. What I should and should not bring up

Follow-up prompts:

What could go wrong in this meeting that I have not planned for?

They are going to try to delay the decision. How do I create urgency without being adversarial?

Write the follow-up email that captures what was agreed and who owns what.

4. Process Documentation and Improvement

The knowledge worker’s process challenge: Process documentation gets written for audits, not for understanding. It is either too high-level to be useful (the policy document nobody reads) or too low-level to survive any change (the five-page procedure that is already wrong). The useful documentation lives in between — and it is hard to write.

When to use: Documenting how something works, identifying inefficiencies, or preparing for a process review.

Prompt pattern:

I need to document [process name or type] for [purpose: onboarding / audit / improvement].
The process involves: [describe the steps you know].
Pain points in the current process: [where it breaks down, where time is lost, where handoffs fail].

Structure this with: purpose, scope, steps with owners, decision points, exception handling, and known failure modes.

Follow-up prompts:

Where are the most common failure points in this type of process?

What steps could be eliminated or automated without reducing quality?

A new employee doing this process for the first time — where will they get stuck?

What does good look like for this process and how would we measure it?

5. Data Narrative and Visualization Guidance

The knowledge worker’s data challenge: Most business data presentations are collections of charts looking for a story. The audience sees the charts, agrees they are interesting, and leaves without changing what they do. A data narrative has one clear message, uses charts as evidence for that message, and tells the audience what to do differently.

When to use: When you have data and need to tell a coherent story from it, or decide how to visualize it.

Prompt pattern:

I have data showing [describe what the data shows at a high level].
Audience: [role, what they care about, what they currently believe].
Message I want to land: [state it in one sentence].
Decision or behavior I want to influence: [be specific].

Structure the narrative:
1. What context the audience needs first
2. The key comparison that makes the message undeniable
3. Chart types that best support this story (and what to avoid)
4. How to handle data that complicates the message
5. The closing call to action

Follow-up prompts:

What is the most misleading way this data could be read? How do I prevent that interpretation?

Write the caption for the most important chart — one sentence telling the reader what to think.

Someone will argue the data shows the opposite. What is their strongest argument and how do I address it?

6. Organizational Influence and Managing Up

The knowledge worker’s influence challenge: This is the part of knowledge work that no textbook covers and most professionals learn the hard way. You have no formal authority over the people you need to influence. Your analysis is correct but the decision is not going your way. Your manager does not understand what you do well enough to advocate for it. This is where careers actually happen.

When to use: Getting buy-in across functions, influencing peers and senior leaders, managing your relationship upward, navigating organizational dynamics.

Prompt pattern:

I need to influence [role] to [what you want them to do or decide].
Their current position: [what they think or want].
Their incentives and pressures: [what they are measured on, worried about, or answerable to].
My relationship with them: [direct report / peer / skip level / external].
What I have tried: [what has not worked].

Help me:
1. Identify the real objection behind their stated position
2. Find the framing that makes my request feel like it solves their problem
3. Anticipate second-order concerns I have not addressed
4. Plan the approach — conversation, email, or sequence

Follow-up prompts:

They keep saying yes in meetings and doing nothing. What is actually happening and how do I break the pattern?

My manager does not advocate for my team in senior meetings. How do I change that without making it awkward?

I need to push back on a direction from above without appearing difficult. Help me frame the pushback.

I am right and they are wrong but they outrank me. What is the constructive path?

7. Synthesizing Complexity Into a Point of View

The knowledge worker’s synthesis challenge: You read 40 articles, attended six meetings, and have 18 tabs open. You have a vague sense of what you think but cannot articulate a crisp point of view. This is one of the most common and most expensive failure modes in knowledge work — consuming inputs without producing a clear conclusion.

When to use: After deep research, when you have too much information to organize, or when you need to form and communicate a clear opinion on a complex topic.

Prompt pattern:

I have been researching [topic / decision / situation].
Here is what I know: [summarize key inputs — rough is fine].
Here are the tensions I see: [what seems to contradict or complicate the picture].
My gut instinct: [what you currently think, even if you cannot fully defend it].

Help me:
1. Separate what I know from what I am assuming
2. Name the core question the evidence is pointing to
3. Build a defensible point of view I could present to a senior audience
4. Identify what additional information would change my conclusion

Follow-up prompts:

What is the argument I am not giving enough weight to?

Play devil's advocate. What is the case for the opposite conclusion?

What would someone who has been in this industry for 20 years say that I am probably missing?

Write this as a one-page "here is what I think and why" memo.

What Great Looks Like

After consistent use, you should notice:

• Executive communications land faster with fewer revision cycles
• You walk into difficult meetings with documented preparation, not just confidence
• Your data presentations have a clear message that people can repeat back to you
• You are making better use of your own expertise — Alex handles the structure, you handle the judgment
• You have a growing library of saved prompt patterns tailored to your specific stakeholders and environment

The mark of expertise is not using AI the most — it is briefing it with enough precision that the first output is genuinely useful. That discipline is built, not given.

Your AI toolkit: These prompts work in ChatGPT, Claude, Copilot, Gemini — and in the Alex VS Code extension, which was designed around them. Start with whatever you have. The skill transfers across all of them.

Your First Week Back: Practice Plan

Month 2–3: Advanced Applications

Track Your Growth

Stakeholder Knowledge Base Build a stakeholder context file for each key person you work with regularly.

/saveinsight title="[Role] stakeholder profile" insight="Cares most about: [priorities]. Common objections: [list]. Best communication style: [direct/narrative/data-first]. What gets ignored: [format or framing that does not land]." tags="stakeholder"

Repeating Report Templates For reports you write weekly or monthly, build a standing prompt template. Paste the new numbers, run the template, edit the result. Hours become minutes.

Cross-Functional Alignment When coordinating across teams with competing priorities:

I need to align [Team A] and [Team B] on [decision].
Team A's priorities: [what they are measured on].
Team B's priorities: [what they are measured on].
What framing makes this decision feel like a win for both sides without misrepresenting it?

Continue your practice: Self-Study Guide — the 30/60/90-day habit guide.