Combining a writing style with a persona is where the magic happens. Here are battle-tested combinations you can copy and adapt.
For Technical Tutorials:
“Write as an experienced developer who’s shipped production code for 10+ years. Use a conversational tone—explain concepts like you’re pair programming with a smart colleague. Include the ‘why’ behind decisions, not just the ‘how’.”
For Thought Leadership:
“Write as a thoughtful contrarian who questions industry assumptions. Use a reflective, measured pace. Acknowledge what the mainstream gets right before explaining where it goes wrong. No hot takes—substantive critique only.”
For Product Documentation:
“Write as a patient mentor who remembers what it’s like to be new. Use a direct, no-nonsense style. Lead with what users need to do, then explain why. Anticipate common mistakes without being condescending.”
For Blog Posts:
“Write as someone genuinely curious about this topic who’s done the research. Use a storytelling approach—open with a specific scenario or problem, then guide readers to the insight. Keep it conversational but substantive.”
For Email Newsletters:
“Write as a trusted colleague sharing something interesting they found. Use an enthusiastic but not over-the-top tone. Get to the point quickly, but include one or two insights that make it worth reading.”
For Case Studies:
“Write as a skeptical analyst who’s seen too many inflated claims. Use an academic, evidence-based approach. Present challenges honestly before discussing solutions. Let results speak without overselling.”
The Formula:
[Persona with specific experience] + [Writing style] + [Audience context] + [What to emphasize/avoid]
Example: “Write as a senior designer (15+ years) in a direct, practical style for junior designers. Focus on principles over trends. Skip the inspirational fluff.”
What combinations have worked for you? Drop your best prompts below—let’s build a library.
.
