Report a typo

An easier way to report typographical errors

Project description

Problem

Solution

Role

Team

Table of Contents

Note: The first iteration of this is launched! Go ahead and try highlighting body paragraphs and report typos as you wish!

How would you feel if you find a typo or a grammatical error on a news article from your favorite news source? How does the context and source in which you read a typo influence your reaction? More importantly, have you tried doing something about it?

From a handful of people I talked to, the answers were unanimous. Unless it's your friend's writing and it's an important writing, who cares as long as the meaning is intact?

Who cares? If I can understand it?

Even if you have all the time and motivation in the world, the costs of reporting an error traditionally heavily outweighs the benefit.

The costs clearly outweighed the benefit

To report a typographical error, one needs to find the author's contact, inform the precise location of the error, then elaborate on the error if it was not already evident. Even then, it is not guaranteed that the author is going to review it and make the change. Clearly, the uncertainties and tedious steps do not warrant the benefit of most typos.

But what if we lower the cost to report a typo? Can we lower the effort required to report an error to cross the threshold of action?

Moving the dot across the threshold of action by reducing difficulty of task.

Maybe the problem isn't that people don't care enough to alert the publisher/author, but the process of reporting such error is tedious and not worth the effort? i

Requirements

I outlined the requirements below:

Easy to use

The solution should only do one thing and do it well. Keep its purpose crystal clear, avoid complexities and feature creeps.

Easy to learn how to use (aka Good learnability)

Definitely should not require a manual to operate, nor a forum post that walks people through the steps. My benchmark is that my mom should be able to learn to use without any help.

Discoverability

Users need to be able to find that this feature exists.

Effective

Users must somewhat believe that their suggestion will be taken into account and that their efforts are not in vain.

Ideation: Keeping it simple

I suppressed my urge to add luxurious features to keep the solution simple and laser focused on reporting typos or grammatical errors.

Rough Ideation sketches. Bottom right: comparing the number of steps of different flows.

First iteration/MVP

I kept the first iteration as the bare minimum as a proof of concept. Visitors can simply highlight any text with an error, and send the excerpt as an email to the author (me). My website will be the testing grounds for this feature to get user feedback and later in the future could potentially be a plugin for other site owners to integrate, or implement this feature as part of an existing product such as Grammarly.

Highlight text, click on “Report a typo” and redirect to email template with the typo quoted. User can send right away, or leave a personal note.


I believe this MVP is an elegant solution for it's simplicity and flexibility. However, it's poor discoverability must be addressed.

Addressing poor discoverability

It has been over a month and I have only received 1 typo report from a friend. Possible explanations include:

  1. Visitors aren't aware of the feature
  2. Visitors didn't find or care enough to report any typo
  3. Visitors were reluctant to share their private email address

Although all three are reasonable contributors, in this feature update, I specifically addressed poor discoverability with a floating notifications pop up. Below I iterated on two positions.

With this in floating notification published in the Journal pages, I will continue it's popularity. In addition, I have integrated Hotjar to visitor's behaviours when encountering the new floating notification.

Frequently Anticipated Questions

Why reveal upon highlighting text?

This was inspired from a feature on Medium.com, where users can share quotes from an article on social media platforms. I noticed the similarity between sharing a quote on social media and reporting a typographical error. i

This decision was certainly a trade-off between discoverability and distract-ability. Having this “Report a typo” button be more prominent would only be beneficial for specific and rare use case when users are looking to report a typo but becomes a distraction in all other instances.

Also, the highlighted text can be used to identify the sentence/word of the error, minimizing burden on users to fill in information.

Why text label rather than icon?

Even universal icons can be susceptible to varying interpretations across population and cultures. To make my design friendly to all, text label is leaves little room for misinterpretation.

Why the term “Report a typo”?

Why not any of… “Report a typo or grammatical errors”, “Report an issue” or, “Send an email”? I chose “Report a typo” because:

  1. It is concise
  2. Its purpose is communicated clearly
  3. Its semi transparent user expectation of what comes next

I anticipate “report an issue” to be a vague statement and are commonly used to report severe technical issues. Whereas a "reporting a typo" is specific and casual, with the tone implying that there are no issue too small to be reported, even typos.

Why redirect to email template?

Emails are like a text editor, and gives users free reign over what and how they want to file a report. It encourages suggestions and side discussions i. To make it easier, I added a default ready-to-send template to be or sent right away or edited.

Left: Adobe Photoshop crash report. Right: Email template for reporting an error.

What problems do you anticipate?

Poor discoverability

Because of it’s low discoverability, the feature may not be useful. I will be paying close attention to the metrics! Suggestions for non-disruptive ways to educate users of this feature is welcomed! i

User Privacy

Users are required to disclose their email address to report a typo and is prone to abuse by web owners.


Web Owner Privacy

contact information of report recipient is disclosed to the public and will be prone to abuse.


Regulating ill-intended behavior

Must address spams, fictitious reports, collecting personal information, and false positives reports.

Next steps?

Thank you for reading 👏

You are awesome for scrolling all the way through! I would love to get in touch with you, so please reach out via email!