Another DAM Blog

Blog about Digital Asset Management


1 Comment

How do I address user error?

Many people do not read instructions. They may enjoy reading what they want to read, but instructions are not one of those preferred works of non-fiction that come to mind. When was the last time you read instructions? Why? There is often the assumption and expectation things will be easy to understand and easy to use. When we download a new software application to one of our devices, do you see piles of instructions, guides, or manuals? Not likely.

And are we expecting other people to read instructions as well? Newsflash: many do not read instructions even if their lives depend on it. Some manufacturers in certain sectors include instructions to supply warnings, notices and legal documentation attempting to limit their liability in the case their product or service is (was) used incorrectly and disaster occurs. An example of this was a product mailed to homes as a free sample. This sample came in a small packet and included an image of a lemon on it. People instantly assumed it was lemonade mix, so they mixed it with water and drank it without ever reading what it said on the packet. The organization received countless calls and complaints from potential consumers who got sick. Most of them did not read the fact that this was dishwasher soap with a new lemon scent and an added citric acid cleaning agent. Reading is either clearly overrated for the masses or a means of separating the people who want to be informed from those who are too lazy/busy to bother.

Some manufacturers do not even include instructions anymore. Why? The product or service should be easy enough and users should just want to use it. They expect user adoption magically happen with some high hopes.  Maybe that works with some mobile devices and some of their respective apps through simple, smart design. Never mind the precautions, warnings or issues that could arise. What could possibly go wrong? Users are smart enough to just know how to use it, right? Well, if you add some humans to any equation, you will get some inconsistencies, variables, and yes… errors. Sure, we can blame the:

  • poorly designed user interface (usability testing can help identify these issues)
  • lack of forethought in the system implementation, so everyone must think like the person who created it (user testing can help identify these issues as long as they walk through all the processes and note what/where is a miss)
  • the whoops on the real world which avoids the end-to-end walk-through of a solution to be sure it works

One organization had a lot of user errors, so they started focusing on the tasks that caused the user errors and tracked them.  This could identify system flaws needing correction.  Here is how to start on the path of accountability. Every instance an error happened:

  • the user was tracked by name (who)
  • the type of error was tracked (what)
  • the frequency of the error was tracked (when)
  • where the issue was occurring in the system was tracked (where)
  • what the user did incorrectly to cause the error was tracked (why)
  • the recommended changes to the process were communicated and documented (how)

Every time an error happened, a template email was sent to that individual user and their supervisor which included:

  • their specific error
  • the impact of this error to other users and the system (there often was one)
  • a recommended fix (for the user to complete)
  • a set time frame to fix the error properly (one to two business days)
  • a follow-up to be sure it was completed and the error log to close out that particular instance of that error.

Before implementing this error correction, the policy was fully documented and shared openly. As soon as this process started, error rates dropped significantly.  That is the effect of accountability. Prior to this, accountability was not visible. Note that errors do not completely disappear because “perfection” is not a realistic goal for any organization. There is room for improvement for users, processes, and likely the system.

How to have MORE errors

There are the counterpoints to all this…

  • Assume too much or just assume everything will work the way you expect it to (just like the world will continue to revolve around you)
  • Ignore all issues you encounter. Do not verbally mention nor document in writing the issues for anyone to know about.
  • Do not test thoroughly or just ignore all testing completely  (The testing fairy is coming soon. Just don’t wake up from that dream)
  • Do not verify any information down the exact character. In fact, just do not check on anything at all
  • Do not follow specific instructions. Do not have clear, up to date instructions. In fact, do not have any instructions at all (see assumptions for similar results).
  • Do not explain how nor why something works nor even IF it actually works. People are just supposed to know this simply by osmosis or being born with this information.
  • Do not have a simple, easy to use GUI. If you really try, you could skip having a GUI completely. 
  • Ignore all usability experts and their literature. Why would you want anyone to actually use the system your company paid for?
  • Believe everyone works and thinks like you (revisit assumptions again)
  • Be sure to have extra slow processors to make people believe the system is frozen or non-functional. It might be acceptable in some people’s mind if a simple process with a few bits of data take a half-hour to two hours to yield the results requested.
  • Be sure to blame the end-user when the system is not working, but it is best if the results are inconsistent just for that added bonus.
  • Confusion is always welcome. With open arms.
  • Do not document anything. When working with other companies, trust everyone freely and believe that they will document everything for you, understand it all your way, and do not share this documentation openly.
  • Believe everything (including coding) is really easy and it will automagically be completed overnight flawlessly. Every day. With no documentation nor specifications. Nor testing.
  • Every IT department can read minds. They have an app for that.
  • Eventually, everyone can read your mind.
  • Trust everyone. What could possibly go wrong? You do not need any verification either.
  • Do not plan ahead.
  • Do not train users. Ok, maybe once and believe they will remember it all. 
  • Do not supply any ongoing support for your user community. They will figure it out.
  • Errors go away if you ignore them enough. Errors do not multiply when you do this. Errors are so much fun. Dream of getting more over time and it will happen in reality.
  • Never take any vacation nor breaks. It will not catch up with you in any way.

I only wish these were all so ridiculous that these did not ever happen nor were even thought of. Sadly, they actually do. Too often.

How do you address user error?


Leave a comment

What is the life cycle of DAM assets?

Digital assets have a life cycle just like plants and animals. Your organization may acquire, create or even re-purpose digital assets which are:

  • a major milestone in the organization’s history
  • historical (good or bad)
  • required by law or other regulations
  • repeatedly used or requested

What are the signs that digital asset is coming to the end of its life cycle?

Is the asset:

  • Dated (is everyone wearing bell bottoms, plaid and have long sideburns? This could be a sign unless you are covering 1970 revivals)
  • Too generic? Or is it too specific to be of interest to your audience?
  • Antiquated (do you hear dinosaurs roaming or modems dialing for a connection? Or is an abacus the most advanced technology available?)
  • Not downloaded/ordered/requested/used in the past 5 years. (A DAM solution should be able to report the number of times an asset has been downloaded/ordered/requested/used. This is a major indicator.)

If the case is the asset has not been downloaded/ordered/requested/used in over 5 years, it may be time to migrate the asset to an archive outside of the DAM. Or maybe just keep a proxy of the asset in the DAM along with a location/contact for the archive that has a high quality copy of the digital asset. Just keep in mind not to delete all copies of those legacy digital asset  (you know, those assets supposedly at the end of their life cycle), unless required by law or regulation.

  • How many pieces of documentation do you keep for your assets? (This would explain the history and ownership of your digital assets, sometimes known as provenance)
  • How will this content be changed over the life cycle of the asset?
  • How many people do you have accessing this information? (History of the asset as seen from the DAM reports)
  • What is the total value of your asset related projects per year? (Do you keep in mind the value of these projects and assets?)
  • How many people can you afford to have managing this documentation? (This is documented in writing by someone, right?)
  • What happens when someone uses the wrong information? (Do you like errors and inconsistency?)
  • Is any of this a matter of proper version control? (Do you really want to know how many systems fail to have this today? Too many.)

If the digital asset is needed ‘forever,’ consider what file format it is kept in, since this format may not be supported ‘forever.’  These assets may need to be converted into different (more current) file formats. Refer to Another DAM podcast interview with Linda Tadic who speaks about this as well as the time frame to revisit these things.

Consider the same with physical media storage such the evolution of audio from wax cylinders to LPs (33.3 and 45) to 8 tracks to audio tapes to CDs… now on hard drives and portable MP3 players.

How many digital assets do you actively use today?

If you wanted to archive this music, what format do we store this for high quality, everyday listening, or did we all keep all formats/players? Not likely. While some purist may continue to play these antique tools of the past purely for nostalgic reasons, most of these formats do not keep these physically degrading/fading media formats. Instead, we keep the highest quality digital copy of important audio we need to keep. The ones of value. The digital asset.

Consider the same with the evolution of photography:

In less than 200 years, photography went from wet plates to large format to medium format to 35 mm celluloid film then to eventually digital capture. Digital camera sales have surpassed film camera sales for several years now. Some companies are re-purposing their photography infrastructure for something the market actually wants to buy today. Most photographers want to see their images now. Sometimes, even their subjects want to see their image now as well.

When it came to film photography, the photographer often used to hand off the (analog) film for processing and printing to a lab. With digital photography, the photographer often is the lab as well.

Like most digital assets…

We want them now. We may even need them now. For the projects at hand. For the time being.

Our attention span and patience for finite search results (to find the right asset) are constantly getting shorter. We are spoiled thanks to really good search engines and more importantly, their search results. Be sure your digital assets are not just searchable, but found when needed. If these assets can not be found in a DAM, their life cycle is quite limited. Be aware of how to find these digital assets again.

If you need vendor neutral assistance or advice on digital asset life cycles, let us know.

What is the life cycle of your digital assets?