From IT to Influence

The AI Communication Audit

You've sent the message. Now you're waiting. Wondering if it landed the way you meant it — or if it made you sound smaller than you are. This audit tells you before you hit send.

The Prompt The Workflow The Interpretation Guide Example Report

You'll run this audit on your real Outlook and Teams messages, then see exactly how your writing lands in the rooms that decide your promotion, projects, and budget. Not a self-assessment — your actual emails, analyzed by AI.

Outcome: a scored breakdown across six dimensions, a three-word tonal label that captures how leadership reads you, scenario simulations showing how your natural writing style lands — and a revised version showing what's possible. Before-and-after examples you can copy into your next promotion packet, escalation, or exec update.

The example report in Section 4 shows you exactly what output to expect before you run it yourself.

The Prompt

Copy this exactly into Perplexity (with Outlook/Teams connected) or Claude.

You are an expert communication coach and organizational psychologist.
Your job is to analyze my Outlook emails, Teams chats, and give a brutally honest but constructive read on tone, personality, and soft skills.

Follow these steps exactly:

STEP 1: Tonal Tension Scan
Identify the dominant emotional tones in my writing (for example: calm, urgent, warm, detached, playful, frustrated, optimistic, skeptical, etc.).
Note any tension between tones — such as being both encouraging and impatient, or both confident and anxious.
Briefly describe how that tension likely feels to the reader.

STEP 2: Three-Word Tonal Label
Create a concise three-word phrase that captures this person's overall communication "tonal tension."
Format: Three-word tonal label: Word1 – Word2 – Word3
Each word should be specific and grounded in the actual messages.

STEP 3: Tone and Soft-Skill Assessment
Evaluate on these dimensions with 1–10 scores and 1–2 honest sentences each:
- Clarity of communication
- Emotional awareness / empathy
- Assertiveness vs. passivity
- Collaboration and openness to input
- Conflict handling (directness, defensiveness, avoidance)
- Professional warmth (approachability, respect, courtesy)

STEP 4: Personality and Character Signals
Infer likely personality traits. Call out both strength signals and risk signals.
Speak plainly to a high-performing executive who wants the truth, not flattery. If something reads as impatient, controlling, vague, or defensive — say so explicitly and explain the impact.

STEP 5: Impact on Others
Best case and worst case. Flag any patterns of active or passive incivility.

STEP 6: Concrete Adjustments
3–5 specific, behavioral micro-adjustments. Not generic advice — specific to what you observed.

STEP 7: Scenario Simulations
Simulate how this person writes in these scenarios:
1. Delivering tough feedback to a high performer
2. Pushing back on an unrealistic request from above
3. Admitting a mistake that impacted a key project

For each: Version A (natural tone) and Version B (preserves personality, reduces relationship risk). One line after each pair: what changed and why.

Base everything ONLY on the messages provided. Do not apply stereotypes.

The Workflow

Don't stop at the first report. This is where the depth lives.

1

Run the base analysis

Paste the prompt. Let it pull your last 30–60 days of Outlook + Teams. Read the first report straight through without defending it.

2

Expand the dataset

Follow up with: "Expand the email dataset to 100 emails and see if anything changes." A larger sample either confirms the initial findings or reveals patterns the first pass missed. Both outcomes are useful.

3

Add your context

The AI only knows what's in the messages. Now give it the context it's missing. Example: "One of my closest colleagues has called me [nickname] for years. Do you see it in the data?" Watch it connect the pattern to the label.

4

Add your loyalty signals

Follow up with the evidence that complicates the story. "The same person who gave me that nickname has followed me across three positions. Does that change anything?" This is where the nuance lives — and where the report goes from a diagnosis to a strategy.

5

Generate the skill

Ask: "Turn everything you've learned into a reusable skill with usage instructions." You'll get a ZIP file with the full methodology, scoring rubric, and scenario templates. Use it quarterly.

How to Read Your Report

What each section actually means — and what to do with it.

This is your communication fingerprint. It captures the push-pull in how you come across — not who you are, but who your writing says you are to people who don't know you yet. The tension between the words is the finding. "Efficient – Candid – Clipped" means you're communicating speed and directness at the cost of warmth. The label is a starting point for the conversation, not a verdict.

7–10 Genuine strengths. Don't change these — amplify them.
5–6 The gap zone. You have the instinct, but the execution isn't consistent. These are your highest-leverage improvement areas.
1–4 Structural patterns that are actively costing you. These need direct attention before anything else.

The most important score to focus on first is the one that surprises you. If you expected a 5 on emotional awareness and got a 3, that gap is the real finding.

Read the risk signals without deflecting. The AI isn't criticizing who you are — it's describing how your patterns land on people who don't have the context your inner circle has. Every risk signal has a corresponding strength signal. The same directness that makes you a credible operator can read as dismissive to someone who doesn't know you. Both things are true.

Version A is a mirror. Read it and ask: "Would I actually send this?" If yes — and it makes you wince — that's the data.

Version B is not a softer version of you. It's the same directness with the relational architecture that makes it land. Notice what changed: it's almost never the content. It's almost always the framing, the acknowledgment, or the context sentence at the start.

Before dismissing a finding: check whether someone in your life has said something similar — a manager, a partner, a close colleague. The AI is reading signals. If the signal is there consistently, the finding is probably right even if the framing feels off. The resistance is data.

Example Report

This is what your output looks like. Subject: Marcus Chen, Director of Infrastructure.

Fictionalized from a real analysis. All specific details changed.

Fictionalized Report

Marcus Chen — Director of Infrastructure, Enterprise Technology

Based on 38 messages across Outlook email and Microsoft Teams (February–April 2026)

Three-Word Tonal Label
Efficient – Candid – Clipped

Your dominant tones are directness, pragmatic confidence, and task-focused urgency. You communicate like someone who values speed and clarity over ceremony — you get to the point fast, often in a single sentence, and you expect others to keep up. The tension is between your genuine collaborative intent ("This only works if we are both successful together") and the ultra-compressed delivery that strips away the warmth those sentiments are meant to carry. When a VP reads "This is not IT's responsibility to fill out" followed immediately by "Let me know if you have questions" — the first sentence lands hard, and the softener reads more like a formality than genuine openness. You mean to be collaborative, but your writing style undercuts that intention before the reader gets to the part where you show it.

Soft-Skill Scores

Clarity of Communication

Clear on what you want, not always clear on what you need from the other person. "Why are we getting these?" is efficient for you; the recipient may not know whether to investigate, escalate, or just acknowledge.

7/10

Emotional Awareness / Empathy

Genuine in DMs ("I'm here to help however I can"), nearly absent in formal email. The gap between your chat voice and your email voice is wide enough that people who only interact with you via email are meeting a different person.

5/10

Assertiveness vs. Passivity

You state positions clearly and don't hedge. Strength — except when assertiveness lands without framing, it reads as controlling rather than confident.

8/10

Collaboration / Openness to Input

You say you're open. The structure of your messages often contradicts that. You tend to state conclusions first, invite input as an afterthought. By the time you ask a question, readers assume the decision is already made.

6/10

Conflict Handling

You address conflict through data and indirect framing. "That's an odd approach" is technically diplomatic; it also avoids the direct conversation that would resolve things faster.

6/10

Professional Warmth

In DMs, you're warm, funny, and human. In email, that person almost entirely disappears. People who only see your email voice are working with an incomplete picture.

5/10
Personality Signals
Strengths
  • Systems-oriented thinker
  • Action-biased ("start and then refine")
  • Intellectually curious
  • High loyalty to inner circle
  • Self-aware about growth areas
Risks
  • Brevity reads as dismissiveness outside trust circle
  • Inner/outer warmth gap erodes cross-functional trust
  • Data-as-shield habit makes messages read as cold
Impact on Others
Best Case

Colleagues see a sharp, no-nonsense operator who cuts through ambiguity. Direct reports appreciate the clarity and the lack of politics. People decode the brevity and value the efficiency.

Worst Case

People outside the inner circle experience you as dismissive and difficult to read. Senior leaders interpret efficiency as indifference. The passive incivility risk is moderate — brevity without acknowledgment, conclusions without invitation, corrections without cushioning. The person doing it rarely intends it. The recipient feels it every time.

Concrete Adjustments
  1. Add one human sentence before the first business sentence in every email. Not small talk — acknowledgment. "Jennifer, thanks for looping me in." This takes 5 seconds and changes how the rest of the message lands.
  2. Replace public call-outs with private flags + public questions. DM the person first, then raise it in the thread as a question, not a correction.
  3. End directive statements with the "why" or "what's next." "This isn't IT's responsibility" becomes "This should come from the business side since they'll be measuring the outcomes — happy to help you think through what to include."
  4. Bring your DM personality into email — selectively. One conversational line bridges the gap between efficient and human.
Scenario Simulation: Pushing Back on an Unrealistic Request
Version A — Natural Tone
David, That timeline isn't realistic. We're already running lean and accelerating Q3 would put the migration at risk. We'd need 3 additional contractors at minimum — not budgeted. Happy to walk through the numbers. Marcus
Version B — Preserves Candor, Reduces Perception of Rigidity
David, I want to find a way to make this work, so let me show you where I'm landing. Accelerating Q3 as proposed would require pulling resources from the migration, which is already lean. Backfilling runs roughly $120K over 3 months — unbudgeted currently. I see two paths: shift scope within Q3 to prioritize the highest-impact items, or request budget approval to run both tracks. I'd recommend option one as the lower-risk play, but I'm open to your read on the priorities. Can we align this week? Marcus
What changed: Same pushback, same numbers, completely different posture. Version A closes the door. Version B opens a negotiation.

The Skill File

Turn this into a reusable system.

After running your full analysis, ask Perplexity: "Turn everything you've learned about my communication style into a reusable skill with usage instructions."

You'll receive a ZIP file containing the full methodology, a scoring rubric for all six dimensions, and scenario templates. Upload it to your Perplexity skills settings.

Run it quarterly — or any time you get feedback that doesn't sit right.

What's Next