ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

How to write a story in first person narrative and make it believable

Updated on September 8, 2014

Tips on writing a compelling first-person narrative story

The first person narrative has a lot of advantages, especially if used properly in the right kind of story. It allows the writer to have his protagonist affect and draw the reader to a personal level. The limited quality of the first person narrative also creates a feel of mystery as both the protagonist and reader watch the story unfold hand in hand.

Writing in the first person point of view is also a suitable choice for beginner writers as it is easier to write. However, there can be a lot of aspects where this kind of narrative, when done the wrong way, can put off or bore the readers. These are a few tips to avoid such mistakes:

Effective writing takes a lot of practice.
Effective writing takes a lot of practice. | Source

1. Make your protagonist engaging and relatable.

I can’t stress this enough. If you think that your protagonist has a personality that might be difficult for the average reader to empathize with, it might be better to stick to other types of narrative. In an effective first person POV, the protagonist is required to maintain a close relationship with the reader. He or she will have to relate thoughts, quirks, desires and secrets as if the reader is their best friend. If the protagonist has a weak pull or an over-the-top one, it will irritate the readers into putting your story away.

2. Limit your protagonist’s knowledge true to his character.

If you have an excellent architect as your protagonist, for example, do not make him an effortless expert in medicine too. This might be a too-obvious, distinct enough example that one might think that this is just common sense. Still, I have read some stories where ordinary-people protagonists happen to expertly talk about a specialized topic, out of the blue and without ever revealing why they could. This is poor characterization.

All humans make false observations.
All humans make false observations. | Source

3. Don’t make your protagonist right all the time.

People in real life often make false assumptions and describe things in the wrong light. I’ve recently read something where the protagonist referred to her roommate as a germophobic person (colloquial for "mysophobic", which means fearful of germs and contamination) when the guy was obviously more like an ataxophobic (fearful of untidiness and disorder). Regarding this point, that story passed. Human beings are not always right and that includes your story’s protagonist.

4. Don’t make your protagonist narrate each of her move in every scene change.

In all honesty, your readers can pick up if the protagonist has already come down from her apartment to her car. You don’t have to show them every time how your protagonist stepped her way down the stairs. Only include these mundane scenes if and only if it is significant or essential to the narrative.

You can't see it when you blush. Instead, you just feel it.
You can't see it when you blush. Instead, you just feel it. | Source

5. Don’t make your protagonist describe something on her face. Especially, when she could not feel it herself.

“My face paled at her grim recount.”
“My cheeks reddened at his confession”

No, just no. Even so, this is a very common mistake. How could the protagonist even make sure of the colors on her face when she’s nowhere near a mirror?

“My eyebrows raised at her grim recount.”
“My cheeks warmed up at his confession.”

6. Do not involve too much (named) characters in your story.

In a first-person narrative story, it is advisable to only name a few characters here and there instead of having a full cast. Named characters are supposed to be the only ones that are important or memorable to the protagonist (the exception to this is if you intend the protagonist to have a knack for remembering names). Also, a possible difficulty of having a lot of named characters is the risk of introducing each and every one of them and thus, making your readers yawn.

7. Don’t create too much back story and most especially, no back story-nceptions.

Protagonist back stories are great when done properly and sparingly in the first few paragraphs of a short story or the first few chapters of a novel just to introduce the narrator’s current standing. They could be written as cohesive inserts after the protagonist is reminded of the past or perhaps, in a dialogue when someone asks them about it. However, when a story is dotted with too much back story here and there, it can repeatedly throw the reader off from the flow of the narrative.

Regarding back stories within a back story— they will always be confusing, regardless of how well they’re written.

Remember watching this movie? It made your mind ache, right?
Remember watching this movie? It made your mind ache, right? | Source

8. Don’t start every sentence with “I”… or any word.

This is a matter of style, and style must be kept fresh all the time. Consecutive I’s or any other word might be invisible to the readers, but once they become aware of the staleness, it can be very jarring.

9. Do show and not just tell (most of the time).

This is the most basic advice in writing fiction, but why did I include “most of the time”? It’s because showing can be abused and taken to a wordy excess. Balance is the key here. Scrutinizing every complex feeling and situation down to the very core in every sentence will drag the story down. A sluggishly-paced narrative can be quite tiring to read. Also, some parts of a story attains better impact when a more direct narration is used.

It does work. Just not all the time and surely not every single time.
It does work. Just not all the time and surely not every single time. | Source

These tips are by no means comprehensive but I’ve drawn them from my experience as an avid reader and an occasional writer. All the pointers here came from what often stops me from reading a piece till end and prevents me from picking it up again. I know that it is mostly based on my tastes but I’ve kept it as sensible as possible. It would make me glad if these tips can help somebody. If you also have any other pet peeves while reading an ineffective first-person narrative story, feel free to comment them down below. I might create a tip out of it and put it here as an addition.


    0 of 8192 characters used
    Post Comment
    • Staceycakes profile image


      4 years ago from Fife, Scotland

      Really great article :) I get a little bit annoyed when writers repeat themselves too much, like with specific words for example. It's easy for readers to pick up on, and I think it can be a sign of poor writing.

    • profile image


      4 years ago

      Very informative article. Thanks for sharing this, it will be a great help for us aspiring beginners.

    • dahoglund profile image

      Don A. Hoglund 

      4 years ago from Wisconsin Rapids

      Good advice. Sometimes a good exercise is to try both ways. I have at times written a scene in the first person and then rewritten it in the third person.. Then I'd ask someone to read both version and tell me which they liked the best.I often find the first person approach makes the scene stronger and gets the reader more involved. sharing


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)