Organize resources so it’s easy to understand. Reduce cognitive load by breaking information down into small, digestible chunks and arranging them into patterns that make sense to the individual. Always start by giving an overview so individuals know how all the smaller chunks fit together.
Use visuals. The brain has an incredible ability to remember visual images so you must exploit that as you look for ways to reinforce key learning points. Create tools that are primarily visual rather than word-based. Use images in place of text (or at least minimize the text). Use videos and animations to help people understand key concepts.
We can drive a lot of effectiveness into our processes by structuring information to make complex documents more transparent and accessible to their users. Visual cues can provide an ‘attention hierarchy’, making sure that what is most important is not overlooked. People tend to find more usable what they find beautiful, and a wall of text simply looks scary, cumbersome, and off-putting for most people. I am a strong advocate of beauty in system design, and I would love to see Quality departments better known for their aesthetic principles and for tying all our documents into good cognitive principles.
Cognitive Load Theory
Cognitive load theory (CLT) can help us understand why people struggle so much in reading and understanding contracts. Developed by John Sweller, while initially studying problem-solving, CLT postulates that learning happens best when information is presented in a way that takes into consideration human cognitive structures. Limited working memory capacity is one of the characteristic aspects of human cognition: thus, comprehension and learning can be facilitated by presenting information in ways minimizing working memory load.
Structure and Display
Information structure (how the content is ordered and organized) and information display (how it is visually presented) play a key role in supporting comprehension and performance. A meaningful information structure helps readers preserve continuity, allowing the formation of a useful and easy-to-process mental model. Visual information display facilitates mental model creation by representing information structures and relationships more explicitly, so readers do not have to use cognitive resources to develop a mental model from scratch.
Leveraging in your process/procedure documents
Much of what is considered necessary SOP structure is not based on how people need to find and utilize information. Many of the parts of a document taken for granted (e.g. reference documents, definitions) are relics from paper-based systems. It is past time to reinvent the procedure.
The format is pivotal. The difficulties we have in quality are really not much different from elsewhere in society in that we are surrounded by confusing documentation and poorly presented explanations everywhere we look, that provide information but not understanding. Oftentimes we rely on canards of “this is what is expected,” “this is what works” – but rarely is that based on anything more than anecdotal. And as the high incidence of issues and the high cost of training shows, less than adequate.
There is a huge body-of-knowledge out there on cognitive-friendly design of visuals, including documentation. This is an area we as a quality profession need to get comfortable with. Most important, we need to give ourselves permission to adapt, modify and transform the information we need into a shape that aids understanding and makes everyone a better thinker.
Work-as-Prescribed (and work-as-instructed) is the creation of tools and technologies to help us think better, understand more and perform at our peak.
Locus of Understanding
Looking at the process at the right level is key. Think of Work-as-Prescribed as a lens. Sometimes you need a high-powered lens so that you can zoom in on a single task. Other times, you need to zoom out to see a set of tasks, a whole process, or how systems interact.
This is the locus of understanding, where understanding happens. When we take this position, we see how understanding is created. Adopting the locus of understanding means going to the right level for the problem at hand. When we apply it to Work-as-Prescribed we are applying the same principles as we do in problem-solving to developing the right tools to govern the work.
An important way to look is distributed cognitive resources, which means anything that contributes to the cognitive work being done. Adjusting the locus of understanding means that you can, and should, treat an SOP as a cognitive resource. Some of the memory is in your head and some is in the SOP. Work-as-prescribed is a cognitive resource that we distribute, routinely and casually across the brain and our quality system in the form of documents and other execution aids.
Other tools, like my favorite whiteboard, also serve as distributed cognitive resources.
So, as our documents and other tools are distributed cognitive resources it behooves us to ensure they are based on the best cognitive principles possible to drive the most benefit.
As an aside, there is a whole line of thought about why some physical objects are better at distributed cognitive resources than electronic. Movement actually matters.
Taking it even further (shifting the locus) we can see the entire quality system as a part of a single distributed cognitive system where cognitive work is performed via the cognitive functions of communicating, deciding, planning, and problem-solving. These cognitive functions are supported by cognitive processes such as perceiving, analyzing, exchanging, and manipulating.
The tools we develop to provide distributed cognitive activity strive to:
Provide short-term or long-term memory aids so that memory load can be reduced.
Provide information that can be directly perceived and used such that little effort is needed to interpret and formulate the information explicitly.
Provide knowledge and skills that are unavailable from internal representations.
Support perceptual operators that can recognize features easily and make inferences directly.
Anchor and structure cognitive behavior without conscious awareness.
Change the nature of a task by generating more efficient action sequences.
Stop time and support perceptual rehearsal to make invisible and transient information visible and sustainable.
Aid processibility by limiting abstraction.
Determine decision making strategies through accuracy maximization and effort minimization.
Plan for the flow of information: Think about paths, relationships, seams, edges and other hand-offs. Focus on the flow of information. Remember that we learn in a spiral, and the content needed for a novice is different from that of an expert and build our documents and the information flow accordingly. This principle is called Sequencing.
Break information down into pieces: Called, Chunking, the grouping together of information into ideally sized pieces. When building Work-As-Prescribed pay close attention to which of these chunks are reusable and build accordingly.
The deeply about context: How a tool is used drives what the tool should be.
Think deeply about information structures: Not all information is the same, not every example of Work-as-Prescribed should have the same structure.
Be conscientiousabout the digital and physical divide: Look for opportunities to integrate or connect these two worlds. Be honest of how enmeshed they are at any point in the system.
We are building our Work-as-Prescribed through leveraging our quality culture, our framework for coordinating work. Pay attention to:
Shared Standards – Ways we communicate
Invisible Environments – Ways we align, conceptually
When design process, procedure and task documentation leverage this principles by build blocks, or microcontent, that is:
about one primary idea, fact, or concept
labeled for clear identification and meaning, and
appropriately written and formatted for use anywhere and any time it is needed.
There is a common miscomprehension that simple means short. That just isn’t true. Simple means that it passes a test for the appropriateness of the size of a piece of content of providing sufficient details to answer a specific question for the targeted audience. The size of the content must effectively serve its intended purpose with efficiency, stripping off any unnecessary components.
We need to strive to apply cognitive thinking principles to our practice. The day of judging a requirements document by its page length is long over.