{"id":1916,"date":"2025-11-27T06:08:15","date_gmt":"2025-11-27T06:08:15","guid":{"rendered":"https:\/\/plainlii.com\/?p=1916"},"modified":"2025-11-27T08:36:13","modified_gmt":"2025-11-27T08:36:13","slug":"visual-plain-language-guide","status":"publish","type":"post","link":"https:\/\/plainlii.com\/es\/2025\/11\/27\/visual-plain-language-guide\/","title":{"rendered":"A Visual Plain Language Guide Comes to Life: visualizing the RAISE\u2122 Framework in 10 Steps"},"content":{"rendered":"

The Visual Plain Language Guide began as a doodle. I sketched a triangle between a reader, the form we were trying to improve, and the cumbersome process behind that form. I was trying to explain that plain language isn\u2019t just about choosing shorter words or trimming complex sentences. It\u2019s about removing friction between the reader and the message. Just like that the idea was born to create the Visual Plain Language Guide. <\/strong>The goal was to make clarity visible! (Find the Guide in our Resources Page<\/a>).<\/p>\n

This post walks through how the guide came to life: the problems it aimed to solve, the research behind it, and the design decisions that shaped the final framework.<\/p>\n

Why I Created the Visual Plain Language Guide<\/strong><\/h2>\n

The guide began from a simple question I kept getting in workshops, client projects, and conversations with other communicators:<\/p>\n

\u201cPlain language makes sense in theory \u2014 but how do I see<\/em> it?\u201d<\/strong><\/p>\n

Plain language is often taught as a set of writing rules, but what I witnessed repeatedly were moments of visual confusion<\/em>:<\/p>\n

    \n
  • \n

    text structured in ways readers couldn\u2019t navigate<\/p>\n<\/li>\n

  • \n

    ideas buried because the hierarchy didn\u2019t guide the eye<\/p>\n<\/li>\n

  • information mapped in the writer\u2019s mind, but not for the reader\u2019s brain<\/li>\n<\/ul>\n

    Those who know me a little know I am BIG on cohesion<\/strong> <\/em>and coherence<\/strong><\/em>–the visible links and the underlying clarity of thought that go into good writing. So I set out to show<\/strong><\/em>, even if a little, how these come to life. And I started sketching. I started with my existing RAISE\u2122 wheel and it all evolved from there.<\/p>\n

    Those sketches became motifs: the target for goals<\/strong> (page 9), the puzzle pieces for flow<\/strong> (page 22), the hand and heart for empathy<\/strong> (page 23). Eventually, they evolved into a unified visual language to communicate the concepts<\/em> of plain language \u2014 not within design, but through<\/em> design.<\/p>\n

    A Visual Guide \u2014 Not a Design Guide<\/strong><\/h2>\n

    One thing I want readers to understand is: This isn\u2019t a guide about visual design. It\u2019s a guide that uses<\/em> visual design to teach plain language.<\/strong><\/p>\n

    Every icon and layout choice serves a conceptual purpose:<\/p>\n

      \n
    • \n

      The RAISE\u2122 principles wheel<\/strong> (page 6) represents balance and interplay.<\/p>\n<\/li>\n

    • \n

      The quadrants of clarity<\/strong> (page 7) visualize the differences in clarity and gobbledygook for lay and specialized communication.<\/p>\n<\/li>\n

    • \n

      The 10-step circular diagram<\/strong> (page 8) positions clarity as an iterative, non-linear process.<\/p>\n<\/li>\n<\/ul>\n

      I didn\u2019t set out to create a \u201cpretty PDF.\u201d I set out to make abstract principles visible and memorable<\/em>. In the Visual Plain Language Guide, each visual is tied to a principle or technique for making communication easier to find, understand, and use.<\/p>\n

      How the Guide Took Shape<\/strong><\/h2>\n

      Here\u2019s the development journey behind the scenes:<\/p>\n

      1. Grounding the guide in international standards<\/strong><\/h3>\n

      Years before the ISO 24495-1 Plain Language Standard existed, I developed the RAISE\u2122 model<\/strong>\u2014Relevance, Access, Intelligibility, Suitability, and Efficacy\u2014as a practical way to explain what makes communication clear. It grew out of years of observing where communication breaks down and noticing that \u201cunderstanding\u201d isn\u2019t one thing; it\u2019s a combination of how clearly something is expressed<\/strong> (intelligibility) and how well it fits the reader\u2019s needs and context<\/strong> (suitability).<\/p>\n

      When ISO began drafting what would become the first international plain language standard, I was invited to join the technical committee responsible for shaping it. It was remarkable to see how closely the developing ISO principles aligned with the structure I had already been using in RAISE\u2122\u2014even though the model predated the standard.<\/p>\n

      The only real difference is conceptual emphasis. ISO includes \u201cUnderstandable\u201d as one of its five principles, while in RAISE\u2122 that idea unfolds into its two essential dimensions:<\/p>\n

        \n
      • \n

        Intelligibility<\/strong> \u2014 the clarity and precision of the expression<\/p>\n<\/li>\n

      • \n

        Suitability<\/strong> \u2014 the appropriateness and resonance of the style for the intended readers<\/p>\n<\/li>\n<\/ul>\n

        Together, they capture what understanding actually<\/em> requires in real-world communication: clarity expressed in a style that meets readers where they are.<\/p>\n

        Because of this natural alignment, RAISE\u2122 maps cleanly to the ISO standard, allowing the guide to stand on an internationally recognized foundation while preserving the nuance, depth, and reader-centered structure that originally inspired RAISE\u2122.<\/p>\n

        2. Turning research into approachable visuals<\/strong><\/h3>\n

        Once I knew the guide needed to show<\/em> plain language, not just explain it, I returned to the research. Studies on cognitive load, reading behavior, and visual processing all point to the same truth: people understand faster when information is paired with clear, meaningful visuals. Not decorative visuals \u2014 but visuals that orient, anchor, and reinforce meaning.<\/p>\n

        So I began developing a visual vocabulary<\/strong> for the guide: a system of icons, metaphors, colors, and spatial patterns that help readers grasp concepts at a glance. Every visual decision had a purpose:<\/p>\n

          \n
        • \n

          The magnifying glass + lightbulb + gear<\/strong> (page 4) conveys \u201cfind, understand, use.\u201d<\/p>\n<\/li>\n

        • \n

          The audience icons (page 12) show diversity without over-specificity.<\/p>\n<\/li>\n

        • \n

          The color palette leans friendly and modern \u2014 bright but soft, not childish.<\/p>\n<\/li>\n<\/ul>\n

          The visuals aren\u2019t decoration; they\u2019re cognitive scaffolding.<\/p>\n

          3. Building a structure readers can follow at a glance<\/strong><\/h3>\n

          The guide mirrors the very principles it teaches:<\/p>\n

            \n
          • \n

            Clear sections (Goals \u2192 Readers \u2192 Structure \u2192 Design \u2192 Words \u2192\u2026)<\/p>\n<\/li>\n

          • \n

            Consistent iconography<\/p>\n<\/li>\n

          • \n

            Headings that double as meaning cues<\/p>\n<\/li>\n

          • \n

            Logical flow from \u201cthinking\u201d steps to \u201ccrafting\u201d steps to \u201crefining\u201d steps<\/p>\n<\/li>\n<\/ul>\n

            This scaffolding is visible on nearly every page, especially the 10-step cycle on page 8 of the Visual Plain Language Guide.<\/p>\n

            4. Iterating through testing and feedback<\/strong><\/h3>\n

            Just as step 10 of the guide emphasizes Get Feedback<\/em> (page 27), I moved through several cycles of:<\/p>\n

              \n
            • \n

              testing concepts with writers and editors<\/p>\n<\/li>\n

            • \n

              adjusting language<\/p>\n<\/li>\n

            • \n

              simplifying visuals<\/p>\n<\/li>\n

            • \n

              refining metaphors<\/p>\n<\/li>\n

            • \n

              tweaking contrast and spacing<\/p>\n<\/li>\n<\/ul>\n

              Each iteration made the guide more coherent, lighter, and more intuitively navigable.<\/p>\n

              Why the Guide Looks Playful<\/strong><\/h2>\n

              Plain language can feel rigid or even simplistic. I wanted to challenge that perception.<\/p>\n

              That\u2019s why the guide uses:<\/p>\n

                \n
              • rounded icons<\/strong>, not rigid lines<\/li>\n
              • asymmetric silhouettes<\/strong>, giving movement and energy<\/li>\n
              • vivid colors that signal friendliness<\/strong><\/li>\n
              • visual metaphors<\/strong><\/em> that feel human<\/em>, like the helping hand or warm lightbulb<\/li>\n<\/ul>\n

                This visual tone embodies the empathy at the heart of plain language (step 8, page 23).<\/p>\n

                Icon System Inside Visual Plain Language Guide<\/h3>\n

                Here are the icons for each of the ten steps of the Visual Plain Language Guide.<\/p>\n

                \"Circular
                Circular diagram of the Visual Plain Language Guide showing 10 steps for plain language: goals, readers, structure, design, words, sentences, links and flow, empathy, revision, and feedback<\/figcaption><\/figure>\n

                What the Visual Plain Language Guide Aims to Do<\/strong><\/h2>\n

                Ultimately, the guide is meant to:<\/p>\n

                  \n
                • \n

                  make plain language principles more teachable<\/em><\/p>\n<\/li>\n

                • \n

                  help teams create better documents, services, and policies<\/p>\n<\/li>\n

                • \n

                  support trust, clarity, and usability (page 29)<\/p>\n<\/li>\n

                • \n

                  show that communication can be both rigorous and inviting<\/p>\n<\/li>\n<\/ul>\n

                  In other words, the guide exists to turn the journey from ideas to results<\/em> (page 33) into something clearer, lighter, and more human.<\/p>","protected":false},"excerpt":{"rendered":"

                  The Visual Plain Language Guide began as a doodle. I sketched a triangle between a reader, the form we were trying to improve, and the cumbersome process behind that form. I was trying to explain that plain language isn\u2019t just about choosing shorter words or trimming complex sentences. It\u2019s about removing friction between the reader […]<\/p>","protected":false},"author":1,"featured_media":1906,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"default","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[10,69,12],"tags":[],"class_list":["post-1916","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-plain-language","category-communication","category-writing"],"_links":{"self":[{"href":"https:\/\/plainlii.com\/es\/wp-json\/wp\/v2\/posts\/1916","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/plainlii.com\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/plainlii.com\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/plainlii.com\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/plainlii.com\/es\/wp-json\/wp\/v2\/comments?post=1916"}],"version-history":[{"count":0,"href":"https:\/\/plainlii.com\/es\/wp-json\/wp\/v2\/posts\/1916\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/plainlii.com\/es\/wp-json\/wp\/v2\/media\/1906"}],"wp:attachment":[{"href":"https:\/\/plainlii.com\/es\/wp-json\/wp\/v2\/media?parent=1916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/plainlii.com\/es\/wp-json\/wp\/v2\/categories?post=1916"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/plainlii.com\/es\/wp-json\/wp\/v2\/tags?post=1916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}