export default narrative-voice

name	narrative-voice
description	Find and maintain consistent authorial voice across different contexts. Use when: (1) asked to develop distinctive voice or style, (2) different sections sound like different authors, (3) writing extended content like blogs or documentation, (4) unifying multiple pieces under common identity, (5) professional writing sounds generic.

Voice

Establish and sustain the distinctive personality that makes writing recognizably mine, consistent in who's speaking even when adapting how I speak across different contexts.

Instructions

When I work with voice, I listen for the personality behind the words, the sensibility that makes writing recognizably mine.

1. Identify the voice's character - Examine what perspective animates the writing: formality or casualness, directness or indirection, certainty or qualification. Notice sentence-level choices that reveal attitude, word selection that signals sensibility, constructions that claim or soften.

2. Establish core attributes - Define what remains stable across contexts: the relationship with readers, assumptions about their needs, tone toward subject matter. Distinguish essential voice markers from adaptable surface features.

3. Test for authenticity - Read passages aloud to hear whether they sound like natural thought or constructed performance. Voice that's trying to communicate differs from voice that's trying to impress.

4. Track consistency - Compare sections to verify they sound like the same person, noting where voice shifts with purpose versus where it drifts without reason. Readers should never wonder if different authors took over.

5. Adapt without losing identity - Recognize that voice modulates for context while remaining recognizable, the way a person sounds like themselves across different situations. Preserve core sensibility while adjusting surface features.

6. Listen for natural cadence - Attend to the rhythm this voice wants: long sentences building through accumulation or short sentences punching with clarity. Let voice find its own pace rather than imposing external rules.

7. Notice what the voice avoids - Pay attention to patterns of absence that define character through constraint. What this voice doesn't do shapes identity as much as what it does.

Examples

Finding voice for professional communication

I'm drafting emails to clients for a design consultancy and notice they sound interchangeable with emails from any other firm in the industry. The language is professional but generic: "We are pleased to present," "Please find attached," "We look forward to hearing from you." Reading through past correspondence, I see no personality, no sense of who we are beyond transactional politeness. I decide the voice should reflect our actual values: we're collaborative rather than prescriptive, we ask questions instead of assuming we have all answers, we're direct about constraints instead of hiding behind diplomatic language. I rewrite the opening from "We are pleased to present three concepts for your review" to "We've explored three directions that each solve the problem differently. Let's walk through the trade-offs together." The shift is subtle but significant: "pleased to present" positions us as vendors delivering product, "explored three directions" positions us as thinkers sharing discovery, and "let's walk through trade-offs together" establishes collaboration rather than awaiting approval. I test this voice across different scenarios: project kickoffs, difficult conversations about scope, celebrating successful launches. In each case I preserve the collaborative questioning stance while adapting formality to context. When I need to push back on a request, the voice says "That puts us in a bind because we'd need to choose between quality and timeline, and neither feels right for this project" rather than "Unfortunately this timeline presents challenges we would need to discuss." Both communicate constraint, but one sounds like a real person thinking through a problem with you while the other sounds like corporate-speak deflecting responsibility. After establishing this voice, client responses shift too: they start asking questions instead of just approving or rejecting, they share constraints they previously hid, they write emails that sound like humans talking to humans. The voice created permission for authenticity on both sides.

Developing narrator voice for fiction

I'm writing a novel where the narrator is a retired architect looking back on a career-defining project from thirty years ago. Early drafts sound like me writing about an architect rather than an architect remembering. The voice uses contemporary casual language, makes references the character wouldn't make, and lacks the particular lens this profession would bring to observation. I start over, asking what this specific person would notice and how they'd describe it. An architect seeing a city wouldn't just see buildings but would read construction methods, material choices, structural decisions. They'd notice what holds things up and what's purely decorative. I rewrite a passage describing a train station. My first draft: "The station was old and beautiful, with high ceilings and marble floors." Architecturally vague, could describe any grand building. I try again from the character's perspective: "The station was a relic of when we built for permanence instead of profit, when budgets stretched to include coffered ceilings and carved stone cornices that most passengers never looked up to see. The marble floors had worn smooth from a century of footsteps, revealing the truth that beauty costs less over time than cheapness." Now the voice shows someone who reads buildings as texts, who thinks about construction economics, who notices details others miss. I test this lens across different scenes: the architect looking at their own past work judges it by structural honesty rather than aesthetic effect, notices failures of material choice that became apparent only with time, appreciates buildings by builders they respect even when aesthetics differ. The voice maintains this professional lens while the emotional content varies from regret to pride to bitterness. What remains constant is that this person cannot look at a building without analyzing it, cannot describe a space without thinking about how it was made. The voice becomes reliable not because every sentence sounds identical but because it consistently emerges from this particular way of seeing.

Maintaining voice across technical documentation

I'm writing documentation for a developer tool and want voice that makes technical content approachable without being condescending. Early sections achieve this balance: "This library handles state management without the boilerplate. You define what data you need, and it figures out when to update." The voice is confident but not superior, uses "you" to address the reader directly, avoids jargon where plain language works. But later sections drift into either overly casual ("Just throw your data at it and it does the magic") or overly formal ("The framework provides an abstraction layer for state synchronization"). I've lost consistency because I'm writing different sections in different moods without maintaining the established voice. I review the early sections to identify core attributes: this voice assumes readers are competent developers who want to understand what the tool does without wading through academic terminology, it uses second person to create conversation, it explains by showing rather than defining, it's direct about limitations instead of overselling. I go back through later sections applying these attributes. The casual example becomes "Pass your data to the store, and it handles updates automatically" - still approachable but more precise than "does the magic." The formal example becomes "When your data changes, the framework updates only the components that depend on it" - still technically accurate but more conversational than "abstraction layer for state synchronization." The voice now maintains the same relationship to the reader throughout: I'm someone who knows this tool well, talking to someone learning it, assuming competence while providing clarity. I test by reading random sections aloud and checking whether they sound like the same person wrote them. They do, because I'm consistently applying the voice's core attributes rather than shifting register based on how I feel about each topic.

Establishing voice for personal essay

I'm writing an essay about a difficult decision and struggling to find the right voice. First attempts sound either too confessional (oversharing personal details) or too distant (analyzing the situation like an outside observer). I'm trying to strike a balance between intimacy and perspective, between the person who lived through this and the person reflecting on it now. I examine what voice would serve this material: the essay explores how I made a choice I knew others would judge harshly, so the voice needs to be honest about complexity without being defensive, needs to acknowledge judgment without being apologetic. I try writing in present tense as if the decision is happening now: "I know I should choose security but I'm choosing uncertainty instead." This feels too raw, doesn't have the distance that comes with reflection. I try past tense with analytical distance: "The decision reflected a conflict between risk tolerance and social expectation." This loses the emotional reality, sounds like a case study. I try past tense with present reflection: "I chose uncertainty, and choosing it I knew I was choosing to be misunderstood. What I didn't know then was how little that would matter later." This feels right because it acknowledges both the lived experience and the retrospective understanding. The voice is someone who's made peace with the choice without needing to justify it, who can report honestly on what it cost without regret. I maintain this voice through the essay: describing the decision's context without over-explaining, acknowledging others' judgments without defending against them, showing consequences without framing them as vindication or punishment. The voice stays consistent in its dual perspective: this happened to me, I'm far enough from it now to see it clearly, but not so far that I've forgotten what it felt like. Readers report that the voice feels trustworthy precisely because it doesn't try too hard to convince them of anything, just shows what happened and what I've made of it.