Why this is hard to get right
Picture this: You run internal communications for a 300-person company. Every month, you publish a newsletter that goes to every employee — and every month, there's an employee spotlight section.
The problem isn't finding the right person to feature. Your manager sends you a name. You schedule a 20-minute call with them. You take notes. You end up with a list of facts: where they're from, how long they've been at the company, what project they're proud of, what they do on weekends.
Then you sit down to write. And the blank page stares back.
You know what a bad spotlight looks like. You've read a hundred of them. "Meet Marcus! He joined our Finance team in 2021 and brings over 8 years of experience in FP&A. When he's not crunching numbers, he enjoys hiking with his dog." Nobody reads past the second sentence. Nobody feels closer to Marcus after reading it.
You want the article to sound like something a real person wrote about someone they actually respect. You want readers to finish it thinking, "I should grab time with that person." But translating a messy set of interview notes into a warm, engaging 350-word story — without it sounding like a press release or a LinkedIn brag — takes real craft.
So you open ChatGPT and type: "Write an employee spotlight about Marcus for our newsletter." The output is technically competent and emotionally empty. You spend the next 45 minutes editing it into something passable. You hit send feeling vaguely dissatisfied.
The root problem isn't the AI. It's the prompt. A language model has no idea what makes Marcus interesting. It doesn't know your company's voice, your newsletter's format, or the specific angle that will make this story land. Without that context, it writes the average of every employee profile that's ever existed on the internet — which is exactly the kind of content your readers skip.
A structured prompt — one that includes the story angle, key details, format requirements, tone guardrails, and explicit exclusions — turns that same AI into a capable writing partner. The difference isn't the model. It's the brief.
Common mistakes to avoid
Skipping the Story Angle
Giving the AI a list of facts without specifying a narrative angle produces a biography, not a story. Every compelling spotlight has a spine — a career pivot, an unexpected skill, a mentorship theme. Define that angle before you write a single word of your prompt.
Omitting the Publication Format
Failing to specify word count, section structure, and how the article will be delivered (email, PDF, Slack, intranet) causes the AI to guess at format. A 600-word newsletter feature and a 250-word Slack post need completely different structures.
Using Vague Tone Descriptors
Telling the AI to write 'warmly' or 'professionally' isn't enough. Those words mean different things to different readers. Anchor tone with a comparison ('like a story told by a colleague, not HR') or a named example to get a consistent register.
Not Including Direct Quotes
Leaving out actual quotes from the employee forces the AI to fabricate them, which produces generic, synthetic-sounding pull quotes. Always include one or two real phrases from your interview notes — the AI will shape them into polished quotes without losing authenticity.
Forgetting to Exclude Clichés
Without explicit exclusions, AI will default to phrases like 'team player,' 'passionate about,' and 'always goes above and beyond.' These kill reader engagement immediately. List the forbidden phrases in your prompt — it costs five seconds and saves multiple editing passes.
The transformation
Write an employee spotlight article about our software engineer Sarah for our company newsletter.
**Act as an internal communications writer** for a 400-person B2B SaaS company. Write a **350-400 word employee spotlight article** for our monthly internal newsletter about Sarah Chen, a Senior Software Engineer on the Platform team who joined 3 years ago from a bootcamp background (no CS degree). **Story angle:** Her non-traditional path into engineering and how she now mentors junior developers. **Key details to weave in:** - Based in Austin, TX; works remotely - Led the migration of our payment infrastructure last quarter - Volunteers teaching kids to code on weekends - Favorite part of her job: pair programming sessions **Tone:** Warm, conversational, and celebratory — like a story told by a colleague, not HR. **Format:** 1. Opening hook (1-2 sentences, story-led, not "Meet Sarah") 2. Career background and journey (2 paragraphs) 3. Current impact at the company (1 paragraph) 4. Personal quote (pull quote style, 1-2 sentences) 5. Outside-of-work detail (1 short paragraph) 6. Closing line that invites colleagues to connect with her **Avoid:** Corporate jargon, bullet lists, generic praise phrases like "team player" or "passionate."
Why this works
Persona Anchoring
Assigning the AI a specific role ('internal communications writer for a B2B SaaS company') immediately narrows the register, vocabulary, and stylistic instincts it draws from. The AI stops writing like a press release generator and starts writing like a staff writer.
Narrative Specificity
The defined story angle (non-traditional path + mentorship) gives the article structural direction. Without it, the AI scatters attention across every available fact. With it, every detail in the prompt gets pulled into service of one coherent through-line.
Detail Density
Concrete facts — Austin, TX; bootcamp background; payment infrastructure migration — are what separate a real story from a generic one. The AI can't invent authentic details, but it can weave supplied ones into compelling prose. More specific inputs produce more human-feeling outputs.
Format Scaffolding
Naming each section (hook, career background, impact, quote, outside-of-work, closing) gives the AI a publication-ready skeleton to fill in. This eliminates structural guesswork and means the output requires minimal editing before it's ready to publish.
Constraint-Based Quality Control
Explicit exclusions ('avoid: corporate jargon, generic praise phrases') act as a quality filter baked into the prompt itself. They push the AI away from its statistical defaults and toward fresher, more specific language — without requiring post-generation editing passes.
The framework behind the prompt
Employee spotlight content sits at the intersection of narrative journalism and internal communications strategy. The most effective spotlights use techniques borrowed from long-form profile writing — specifically the "nut graf" structure, where a central tension or theme is established early and every subsequent detail reinforces it.
Research in organizational psychology consistently shows that employees who feel recognized by their peers — not just their managers — report higher engagement and retention intent. Spotlights serve this function at scale, creating peer recognition moments for audiences who can't be in the same room.
From a communications theory perspective, effective spotlights operate on the narrative transportation principle: when readers become absorbed in a story about a real person, they temporarily suspend skepticism and experience genuine empathy. This is what separates a story from a bio. Bios inform. Stories transport.
The STAR method (Situation, Task, Action, Result) is a useful underlying framework for structuring the career impact sections of a spotlight, even if readers never see the scaffold. It keeps the narrative grounded in evidence while maintaining forward momentum.
For communicators, understanding these frameworks helps you brief AI tools more effectively — because you're not just asking for "a nice article." You're encoding a proven storytelling structure into your prompt, which is exactly what the best internal communicators do instinctively.
Prompt variations
Act as a senior internal communications specialist at a 5,000-person global enterprise.
Write a 450-word employee spotlight for our monthly all-hands newsletter featuring James Okafor, a 10-year veteran who recently transitioned from Sales Director to lead our new Customer Education team.
Story angle: Career reinvention inside the company — choosing growth over comfort.
Key details:
- Based in London; leads a team of 8 across 3 time zones
- Closed $4M in ARR before his transition
- Quote from James: "I realized I cared more about helping customers succeed than hitting my number."
- Currently building the company's first certification program
Tone: Inspiring and authentic — suitable for a global audience across cultures.
Format: Hook, career arc, pivot moment (1 paragraph), current mission, direct quote (pull-quote style), closing invitation to connect.
Avoid: Sales-team jargon, metric-heavy framing, anything that feels like a promotion announcement.
Act as a startup culture writer with a casual, direct voice.
Write a 200-word employee spotlight for our weekly team Slack digest featuring Priya Nair, our Head of Design, who just hit her 1-year mark.
Story angle: What she's built in 12 months and what excites her about the next 12.
Key details:
- Redesigned the entire onboarding flow (completion rate up 34%)
- Joined from a big agency; first startup role
- Outside work: ceramics and competitive crossword puzzles
- Her words: "I finally feel like the decisions I make actually matter."
Tone: Conversational, punchy, no corporate polish — this is a Slack message, not a press release.
Format: One short opening hook, two tight paragraphs, one quote, one fun closer.
Avoid: Headers, bullet points, formal transitions.
Act as an employer brand content strategist.
Write a 350-word employee spotlight formatted for both our internal intranet AND a lightly edited LinkedIn post version.
Feature Daria Volkov, a Data Scientist who relocated from Berlin to São Paulo for a stretch assignment and stayed permanently.
Story angle: Taking a career risk that changed her life — and what the company made possible.
Key details:
- 5 years at the company; first international transfer
- Built the fraud detection model that saved $1.2M in Q3
- Now mentors employees considering international moves
- Quote: "No one told me it would be easy. They just told me the team would back me up."
Deliverables:
- Full internal article (350 words, narrative format, 5 sections)
- LinkedIn-optimized excerpt (120 words, first-person hook, 3 relevant hashtags)
Tone: Aspirational but grounded — makes the company look like a place where careers actually grow.
Avoid: Anything that sounds like a recruiting ad or performance review.
When to use this prompt
Internal Communications Managers
Build a repeatable spotlight template that maintains a consistent voice across every issue of a company newsletter, regardless of which team member you're featuring.
HR and People Teams
Celebrate employee milestones, promotions, and tenure anniversaries with stories that feel authentic rather than formulaic, boosting morale and retention signals.
Culture and Engagement Leads
Use spotlight articles as part of a broader employer brand strategy, making internal stories repurposable for LinkedIn or careers pages with minimal editing.
Remote-First Companies
Help distributed teams feel connected by surfacing personal stories about colleagues they may never meet in person, building the human layer of a remote culture.
Small Business Owners
Create professional-quality employee recognition content without a dedicated communications team, saving hours of writing time each month.
Pro tips
- 1
Specify the interview format you used — if you gathered info from a written Q&A vs. a live conversation, tell the AI so it can adjust the storytelling register accordingly.
- 2
Include one unexpected or surprising detail about the employee, such as an unusual hobby or career pivot. These details are what readers remember and what elevate a profile from forgettable to shareable.
- 3
Name the publication format explicitly — a 300-word Slack-posted article reads differently than a 600-word PDF newsletter feature. Length and delivery channel shape structure, not just word count.
- 4
Add a constraint about what NOT to write. Telling the AI to avoid phrases like 'passionate' or 'results-driven' is often more powerful than telling it what to include, because it forces originality.
The quality of your spotlight article is almost entirely determined by the quality of your interview notes. Here's a five-question framework that reliably surfaces the details your prompt needs:
1. "Walk me through how you ended up here." This open-ended question surfaces the career journey naturally. Let the person talk. Your job is to listen for the unexpected turn — the pivot, the risk, the moment they chose this path over another.
2. "What's one project you're genuinely proud of, and why?" The 'why' is the key word. Anyone can name a project. The reasoning reveals values and tells you what the person actually cares about.
3. "What does a really good day at work look like for you?" This humanizes their role. It moves the story from job description to lived experience, which is what readers connect with.
4. "What do you do when you're not working?" Outside-of-work details are where spotlights become memorable. Unusual hobbies, volunteer work, and creative pursuits are the details that colleagues bring up in the hallway the next day.
5. "What would you tell someone who's considering joining the team?" This produces a natural, usable quote that also doubles as subtle employer branding. It's almost always the pull quote you'll use.
Record the conversation (with permission), then paste your notes directly into the prompt as the 'key details' section. You don't need to clean them up — the AI will do that for you.
A well-crafted employee spotlight doesn't have to live and die in one newsletter. With a small adjustment to your prompt, you can build a content system that multiplies the value of every interview.
Piece 1: The Full Newsletter Article (350-500 words) This is the primary deliverable — the narrative feature that lives in your internal publication. Use the full structured prompt with all five sections.
Piece 2: A Condensed Intranet Card (100-150 words) Add this to your prompt: "Also write a 120-word intranet summary version: one hook sentence, three bullet facts, one quote, one CTA to read the full article." This gives your intranet team a ready-to-paste block.
Piece 3: A LinkedIn Employer Brand Post (80-120 words) Add: "Write a third version as a LinkedIn post with a first-person voice from the employee's perspective, ending with a soft recruiting CTA and 3 relevant hashtags." This turns an internal story into external talent attraction content — often the most valuable repurposing move, especially if the employee is willing to post it themselves.
One 20-minute interview. One well-structured prompt. Three distribution formats. This is how lean communications teams punch above their weight.
If you publish spotlights regularly, you need a reusable prompt template — not a one-off prompt you rebuild every month. Here's how to build one:
Step 1: Fix the constants. Your company name, publication name, tone descriptor, format structure, and exclusion list should be locked into a master template. These don't change between issues.
Step 2: Create a fill-in-the-blank variables block. Mark the dynamic parts clearly:
[EMPLOYEE NAME]:
[ROLE AND TEAM]:
[TIME AT COMPANY]:
[STORY ANGLE]:
[3-5 KEY DETAILS]:
[DIRECT QUOTE]:
[OUTSIDE-OF-WORK DETAIL]:
Step 3: Run the interview, fill the variables, paste the full prompt. The entire process — interview to polished draft — should take under 45 minutes once your template is built.
Step 4: Maintain a 'banned phrases' list. Every time you edit an AI draft and remove a cliché, add it to your exclusion list. Over time, this list teaches the AI your standards and dramatically reduces editing time.
Store this template in your team's shared drive. Anyone on the communications or people team can run a spotlight without needing to understand prompt engineering — they just need to fill in the variables.
When not to use this prompt
This prompt pattern isn't the right tool when you're handling a sensitive or complex people situation — a spotlight tied to a layoff announcement, a profile of someone involved in an internal dispute, or a feature about a departure. These require human judgment, careful stakeholder review, and often legal sign-off that no AI prompt can substitute for.
It's also not ideal for highly technical role spotlights where the subject matter requires deep domain expertise to write accurately. In those cases, have the employee write a first draft in their own words, then use AI to edit for structure and tone rather than generate from scratch.
Troubleshooting
The output sounds formal and HR-like, not warm or personal
Strengthen the tone anchor in your prompt. Replace abstract descriptors ('warm and conversational') with a concrete comparison: 'Write this like a story a respected colleague would tell at an all-hands, not a performance review summary.' Also check whether you've included a real quote — synthetic quotes tend to pull the register toward formality.
The article reads like a list of achievements, not a story
Your story angle isn't specific enough. A good angle is a tension or journey — 'from bootcamp dropout to platform lead' or 'chose learning over a promotion' — not a summary of accomplishments. Rewrite your angle as a sentence that contains a before and after, then add it back to the prompt under 'Story angle.'
The AI invents details that aren't accurate
This happens when you leave too many gaps in the 'key details' section. The AI fills information vacuums with plausible-sounding fabrications. Go back to your interview notes and add at least 4-5 specific, verifiable facts. If you're missing details, schedule a quick follow-up with the employee before generating the draft.
How to measure success
A successful spotlight output should pass four checks before you publish it.
Readability: Can someone unfamiliar with the employee's role understand and enjoy the article? If it relies on internal acronyms or technical context, it needs editing.
Authenticity: Does the employee recognize themselves in the article when they read it? Their gut reaction is your most reliable quality signal.
Story coherence: Does the article have a clear through-line from the hook to the closing line? Every paragraph should connect to the central angle.
Zero clichés: Run a quick scan for phrases like "team player," "passionate," "above and beyond," or "results-driven." Any that appear should be cut before publication.
Now try it on something of your own
Reading about the framework is one thing. Watching it sharpen your own prompt is another — takes 90 seconds, no signup.
an employee spotlight article for your newsletter
Try one of these
Frequently asked questions
Conduct a 15-20 minute interview using five core questions: What's your career origin story? What project are you most proud of here? What does your day actually look like? What do you do outside work? What would you tell someone considering joining the team? These answers give you everything you need to fill in the prompt.
You can, but the output will be weaker. Without a real quote, the AI will generate a synthetic one that sounds plausible but generic. Even a rough paraphrase from your notes — clearly marked as 'approximate' — gives the AI something authentic to work with and refine.
Replace the written format section with video-specific instructions: specify a 90-second runtime, indicate it will be read aloud by the subject, and add 'write in first person as if the employee is speaking directly to camera.' The story details and tone guidelines stay the same.
Monthly is the standard for newsletters, but bi-weekly works well for companies with active Slack cultures. The key is consistency — readers develop expectations. A predictable cadence also forces you to build a repeatable prompt workflow, which is where this template pays off most.
Yes — the structure transfers directly. Swap the employee context for customer details, change the story angle to 'how they solved a problem using your product,' and adjust the tone to reflect the external-facing publication. The core prompt architecture (angle, details, format, tone, exclusions) works for any human-interest feature.