Error Domain
Generally speaking, domain errors aren’t something you want to encounter. This is because they can be a pain to fix, and they’re a pain to see. This is especially true for users that have to make a lot of changes to their computers, or that are on a network where the latest software updates haven’t been made available yet.
There’s a chance that you have one of these pesky errors on your hands, and the best way to fix it is to do a bit of detective work. A good place to start is with the files and folders you have access to on your system. You can find out if you have the proper permissions by right-clicking on your desired file, directory or folder and going to “Security”.
Next, look into the function names and symlinks. This will give you an idea of what’s available to you, and help you narrow down your search for the correct one. The best part is that you may be able to make your system much more efficient in the process. For instance, you might be able to get rid of the error message altogether if you use a good file manager like Windows Explorer or the Mac OS X Finder. That way, you can get a much more reliable set of files and folders, and you can get back to the business of making changes to your systems. In short, these tips and tricks should make your system faster and more secure in the process.
Error Message
Error messages are used to convey information to users. They are often displayed using a dialog box and must be written with specific guidelines. They should provide quick and thorough answers, guidance, actions, and instructions.
When you write an error message, follow Spectrum’s in-product voice principles: Rational (clear and understandable), Human (friendly, honest, and responsible), and Focused (concise and simple). These rules are designed to empower users by providing them with quick and accurate information that they can use to solve their problems.
Avoid phrases such as “please,” “sorry,” and “can’t.” These words may cause the error message to sound sloppy, unprofessional, or insensitive. They can also make people feel hesitant about attempting to resolve the problem.
Use double quotation marks to indicate object names and exclude fully qualified file paths and URLs from the main instruction unless necessary. This makes it easier for the user to parse the text and to avoid potentially embarrassing statements.
A rename error is an error in which an item cannot be moved because the item name does not exist in another location. This error is a common one, and the message should be clear enough so that users can quickly find the item with a search function or a file-browsing tool.
The example above left is a good example of an error message that is clear and helpful. It explains what the error is, why it occurred, and when possible, how to overcome it.
If a problem can only be solved by contacting an administrator, avoid promoting this option in error messages, as it may not be the most effective solution. However, if this option is the only way to solve the problem, it can be helpful to offer it in error messages.
For most error messages, you can select an appropriate default command to send the user. This is especially true for unknown errors and for those affecting network connectivity.
As you design error messaging, use this information to decide what details to include in the main instruction and which to provide as supplemental instruction text. You can then create error messages that provide only the information needed to resolve the problem.
When you need to provide additional information, consider directing users to a Help link. This can be a simple link to an online Help content page, which allows you to add or update the content before the program is released.
You can also provide an error code instead of a supplemental instruction if you need to give the user more detail about the problem or solution. The error code should provide the user with useful information that is beyond the scope of the main instruction, such as ways to avoid the problem in the future.
Error messages can be an invaluable UX resource if they are written correctly. They should be written with the help of writers and editors to ensure they meet all of Spectrum’s in-product voice guidelines.
