Designing in teams with different stakeholders can be incredibly complex. Each person looks at projects through their own lens, and can potentially introduce jargon and concepts that are confusing to others. Simplicity advocate Ella Stoner knows this scenario all too well. It’s what led her to create an easy three-step tool for recognizing problems and developing solutions. By getting everyone on the same page and creating an understanding of what the simplest solution is, designers can create products with customer needs in mind.

‍

Ella’s background

‍

Ella Stoner is a CX Designer at Spark in New Zealand. She is a creative thought leader and a talented designer who has facilitated over 50 Human Centered Design Workshops. Ella and her team have developed a cloud product that enables businesses to connect with Public Cloud Services such as Amazon, Google and Azure in a human-centric way. She brings a simplistic approach to her work that is reflected in her UX New Zealand talk. It’s about cutting out complex details to establish an agreed starting point that is easily understood by all team members.

‍

Contact Details:

You can find Ella on LinkedIn.

‍

Improving creative confidence 🤠

‍

Ella is confident that she is not the only designer who has felt overwhelmed with technical and industry specific jargon in product meetings. For example, on Ella’s first day as a designer with Spark, she attended a meeting about an HSNS (High Speed Network Services) tool. Ella attempted to use context clues to try and predict what HSNS could mean. However, as the meeting went on, the technical and industry-specific jargon built on each other and Ella struggled to follow what was being said. At one point Ella asked the team to clarify this mysterious term:

‍

“What’s an HSNS and why would the customer use it?” she asked. Much to her surprise, the room was completely silent. The team struggled to answer a basic question, about a term that appeared to be common knowledge during the meeting. There’s a saying, “Why do something simply when you can make it as complicated as possible?”. This happens all too often, where people and teams struggle to communicate with each other, and this results in projects and products that customers don’t understand and can’t use. Ella’s In A Nutshell tool is designed to cut through all that. It creates a base level starting point that’s understood by all, cuts out jargon, and puts the focus squarely on the customer. It:

• condenses down language and jargon to its simplest form
• translates everything into common language
• flips it back to the people who’ll be using it.

‍

Here’s how it works:

‍

First, you complete this phrase as it pertains to your work: “In a nutshell, (project/topic) is (describe what the project or topic is in a few words), that (state what the project/topic does) for (indicate key customer/users and why). In order for this method to work, each of the four categories you insert must be simple and understandable. All acronyms, complex language, and technical jargon must be avoided.  In a literal sense, anyone reading the statement should be able to understand what is being said “in a nutshell.” When you’ve done this, you’ll have a statement that can act as a guide for the goals your project aims to achieve.

‍

Why it matters 🤔

‍

Applying the “In A Nutshell” tool doesn’t take long. However, it's important to write this statement as a team. Ideally, it’s best to write the statement at the start of a project, but you can also write it in the middle if you need to create a reference point, or any time you feel technical jargon creeping in.

‍

Here’s what you’ll need to get started:

‍

• People with three or more role types (this accommodates varying perspectives to ensure it’s as relevant as possible)
• A way to capture text - i.e. whiteboard, Slack channel, Miro board
• An easy voting system - i.e., thumbs up in a chat

‍

Before you start, you may need to pitch the idea to someone in a technical role. If you’re feeling lost or confused, chances are someone else will be too. Breaking down the technical concepts into easy-to-understand and digestible language is of utmost importance:

‍

1. Explain the Formula to the team..
2. Individually brainstorm possible answers for each gap for three minutes.
3. Put every idea up on the board or channel and vote on the best one.

‍

Use the most popular answers as your final “In a Nutshell” statement.

‍

Side note: Keep all the options that come through the brainstorm. They can still be useful in the design process to help form a full picture of what you’re working on, what it should do, who it should be for etc.

Being able to design for different perspectives and preferences is a real skill, and it’s extremely difficult. It can become even harder when designing for neurodiverse audiences, where people are hard-wired in unique ways. However, being able to cater to neurodiverse preferences is extremely important.

‍

Designer Kalina Tyrkiel says between 15-20% of people around the world are neurodiverse, which is a significant proportion. Various conditions such as dyslexia, attention deficit disorders, and autism can have considerable impacts on how people interact with interfaces and platforms. By considering these implications, designers can dramatically improve the accessibility of their work and improve engagement for neurodiverse individuals. Even simple tweaks like using an actual number instead of writing it out (i.e., 1 instead of “one”) can make a huge difference. 

‍

Kalina explores universal tips and techniques that allow designers to cater for neurodiverse audiences.

‍

Kalina’s background 

‍

Kalina Tyrkiel is a content designer with a unique background that spans both technical UX skills and a human-centric approach to design. She primarily works as a designer for Polish healthtech company DocPlanner, connecting users with relevant health services. Her background as a trained psychologist significantly supports her work and provides a deeper understanding into how people think.  She is also a UX writing trainer and university lecturer, which further speaks to her expertise.

‍

Contact Details:

You can find Kalina on LinkedIn.

‍

Words that welcome: content design with neurodiversity in mind 📖

‍

Neurodiversity is often misunderstood by society at large. Neurodiverse conditions often exist on a spectrum, and solutions that work for one person don’t necessarily work for someone else. Similarly, neurodiversity often comes in batches. Kalina outlines how 60% of people with ADHD also have traits of autism. This further complicates their perspectives and needs.

‍

So this leaves us with a pressing question. How can designers cater for all people with such different needs? Kalina describes how designing for a neurodiverse audience is actually not much different from designing for a neurotypical audience. For example, on any given day, individuals experience varying levels of stress or relaxation which impacts their energy and attention levels. 

‍

What to keep in mind when designing for neurodiverse audiences 

‍

1. Provide clear instructions

• Use bullet points and lists for better scannability
• For different options, use if/then tables
• Reduce the probability of displaying an error message. For example, when requiring a new password, outline password requirements up front.

‍

2. Make the purpose clear

For example, ensure the title aligns with the content the user can expect. Misalignment can create significant confusion for neurodiverse audiences.

‍

3. Don’t justify text

Justifying text and varying the spacing between words makes it harder to read, particularly for dyslexic users.

4. Include different ways to access content

For example, some people may prefer voice search, others may prefer content that’s not in a video. Again, this is no different from neurotypical audiences.

‍

5. Keep it simple 

The simpler the interface and the simpler the copy, the better. Pay attention to consistency too - if a platform or site varies a lot, this can be confusing. 

‍

Why it matters 💥

‍

Considering neurodiverse audiences in the design process is critical in making platforms easy to use for all people. The needs of neurodiverse users can amplify problems or create critical issues out of something that’s a minor inconvenience for someone else. Again, a 15-20% audience is not insignificant, so it pays to be mindful of their needs. So how can you actually do it?

‍

Hire for diversity 🌍

Having diverse teams can bring a broad array of perspectives to the design process. Just remember that not all neurodiverse people think the same. Dr Stephen Shore said “when you know one person with autism, you know one person with autism”.  Think about diversity as creating preferences, rather than labels. Ask respectfully about someone’s preferences and don’t judge them (or others) based on their condition.

‍

Tools and techniques 🛠️

‍

• In videos, use closed captions, not just subtitles - they can be much more user-friendly. Keep them to 40 characters per line, and up to two lines of similar length. 

‍

Interestingly, closed captions and subtitles are also being more and more preferred by younger generations. 

‍

• Kalina recommends Hemingway as a tool to keep language simple and consistent.
  
• Neurodiversity.design is a website that enables designers to get insights about fonts, typography, interfaces and other general design elements with an eye to neurodiverse audiences.

‍

‍

When you have a small design team or none at all, how do you ensure that your content is consistent, has the right tone, and is captivating? It can be difficult, but it doesn’t have to be! Julia Steffen, Principal Content Designer at Varis, spoke at UX New Zealand, the leading UX and IA conference in New Zealand hosted by Optimal Workshop, about how startups can achieve impactful content and delight users. 

‍

In her talk, Julia shares her most useful tips, tricks, and rules of thumb to ensure meaningful content design. She also shares some helpful tools to achieve maximum efficiency.

‍

Julia Steffen bio 🎤

‍

Julia has worked in content for 10+ years at St.Jude, Wunderman Thompson, MetaLab, and Grubhub. She is based in the United States and is the Principal Content Designer at Varis.

‍

Contact Details:

Email address: julia.steffen@govaris.com

You can find Julia on LinkedIn

‍

Content design for startups - How to work lean, have maximum impact, and get all the high-fives ✋🏽✋🏻✋🏿

‍

Why should you care about content design? Julia argues that “content design is product success”. Because Julia specifically talks about content design in relation to startups, she focuses on how to achieve the best results possible with a small, lean team. To that end, Julia discusses four must-haves for content design:

‍

1. Voice
2. Tools for efficiency
3. Words in the experience
4. Ways to check, test, and perfect your words

‍

Voice 🎙️

‍

Why is your company’s voice important? Voice tells your users who you are, creates meaningful connections, and provides valuable signals that convey whether or not your company is deserving of trust. Choosing the voice for your startup begins with a competitor audit.  Documenting who you compete against, and how you might want to differentiate your startup is crucial to finding your corner of the market. For example, is your voice welcoming, gentle, and positive, or are you more formal and technical? 

‍

User research can also be really helpful when determining and monitoring your voice. Involve your research team and learn what does and doesn’t delight your audience when it comes to your messaging.

‍

It’s also important to map your voice to your startup’s values. Be sure to connect to your mission and your brand. Julia sums up product voice as:

‍

Product voice = your values + space to differentiate + what research tells you

‍

So, when you find your voice, where can you lean into it? There are several key areas or moments that provide opportunities to share your unique voice, such as:

• Notifications: Emails, SMS, and in-app messages are a great place to delight customers
• Success states: Celebrate with your users in your voice (and remove any anxiety that may be there)
• Empty states: They aren’t just a chance to educate, they’re a chance to add some interest or fun (or to mask a UX issue).
• Placeholder text: If a field is well labeled, you can use this section to bring joy and reduce a user’s anxiety.
• Onboarding: You never get a second chance to make a first impression. Make it count!

‍

Tools for efficiency ⚒️

‍

To remain lean and efficient as a startup, one of the best things you can do is create a style guide. This helps to keep your content and voice consistent. For example, what pronouns do you use in your interface, do you capitalize certain words, etc? There is actually a lot to consider here, so Julia points viewers to various resources that allow you to copy and paste, such as Quinn Keast’s Product Language Framework.

‍

A glossary or language bank is also important. Record branded words, terms that you never use, and terms that you’ve heard your users say organically. This helps to ensure that you’re using language that resonates with your audience and language that reduces cognitive load as much as possible.

‍

Pro tip: Use the Writer app with Figma. This integration helps to ensure that your style guide is actually used! It includes your style guide and glossary so that you’re being consistent as you work. You can also use the Hemingway app or Grammarly to look out for passive voice, hard-to-parse sentences, and overall readability.

‍

Words in the experience – writing for content design 📝

‍

The first thing Julia points out when approaching writing is the need to be user-focused. This might seem obvious to UX practitioners, but word selection can be nuanced, and subtle changes can be powerful. For example, instead of writing “[Your company] introduces a new feature”, think about how can you change the statement to be more about what the new feature means for the user, rather than your company. Here are a few rules of thumb to help refine your writing.

‍

• Clarity over cleverness. Unless you’re clear and the message is understood by your user, even the best jokes and wittiest phrases in the world will be wasted.
• Write like you’re having a conversation with your Grandmother. Be clear and don’t use too much jargon.
• Think like the best content designers. Writing is a process and there are several things to consider, such as the purpose of your copy, the context that it’s being read, and what emotion the reader might be feeling at that moment, etc. Julia offers the Microcopy Canvas as a useful tool for startups, which is a helpful writing template/worksheet created by Jane Ruffino.

‍

Ways to check, test, and perfect your words 👀

Julia suggests that design reviews are the perfect place to sense-check your words and content. Review your designs intentionally and through a content lens. Again, the Microcopy Canvas can be a useful tool when conducting this step, helping to ensure you have considered the right tone and achieved your purpose with your words.

‍

Following a design review process, it’s important to test for clarity and affinity. Conduct user tests frequently to ensure your words and content are clear, understood, and hitting the mark in the intended way.

‍

Finally, make sure your content goals are recorded in your dashboards. Be accountable to your own success measures, KPIs, and OKRs (Objectives and Key Results). Some metrics that help track success are:

‍

• Onboarding flows
• Notification metrics
• Feature adoption
• Conversion rates

‍

If you’re falling short on some metrics, review your content and try to figure out where words can be sharpened to be clearer, more friendly, or less technical, for example. Then, feed this information into your prioritization and planning. What changes are going to have the most impact on your product’s success? What changes are quick wins? 

‍

Why it matters 🤯

‍

Julia’s talk is important for UX and content designers, particularly those working in startup environments, as it highlights the critical role of content design in achieving product success. The content you share, the voice and tone you adopt, and the clarity of communication, all add to the user's overall experience with your product. Investing time into your content is critical and, as Julia explains, it doesn’t have to put too much stress on your team's workload. If time isn’t invested, however, you may find yourself with poor content, delivering poor experiences, resulting in high customer attrition. 

‍

Efficiency, therefore, should be a focus for startups wanting to achieve great content design without being weighed down. Julia offers pragmatic advice on maintaining consistency through tools like style guides and language banks and by leveraging apps like Hemingway and Grammarly. Tools like these are incredibly helpful when streamlining processes and ensuring a cohesive and polished user interface. 

‍

At the end of the day, Julia stresses the impact that content design has on user experiences and encourages startups to pay close attention to content in ways that are achievable for small teams.

‍

‍

As information professionals, we work with the “stuff” of information in our everyday work. We search for information, we spend time analyzing and synthesizing it, and we carefully create and structure it. Whether you elicit information from users and stakeholders, explore large data sets, design ‘journeys’ or interfaces, or create information architectures, understanding the information you are using and creating as information can help you do your work better.

‍

Kat King, Business Intelligence Analyst at the University of Michigan Library, recently spoke at UX New Zealand, the leading UX and IA conference in New Zealand hosted by Optimal Workshop, about understanding exactly what information is, and where it is, in our work.

‍

In her talk, Kat uses simple examples to teach you to “see” the information around you and understand what makes something “information” in the context of working as a human to accomplish something.

‍

Kat King bio 🎤

‍

Kat King is an Information Architect interested in language, meaning, and the things we make. She currently works as a Business Intelligence Analyst for the University of Michigan Library.

‍

Contact Details:

‍

Email: Katalogofchaos@gmail.com

‍

Where is the information? 📍🗺️

‍

Information theory can be dense and jargon-filled, and discussions in academic texts can feel divorced from the practice of actually working with information. We’re all told that information architecture is much more than website navigation. So, what is it? IA has a reputation for being difficult to understand, and in her talk, Kat attempts to help us understand what it is, where the information is, and what is it that we’re doing when we use IA methods.

‍

Kat defines IA as “the practice of ensuring ontological alignment”. ‘Ontological’ relates to concepts, categories, properties, and relationships. ‘Alignment’ means arrangements into appropriate relative positions. Therefore, information architecture is “the practice of ensuring concepts, categories and their properties and relationships are arranged into appropriate relative positions.”

‍

To align information then, you need to begin by sorting it into concepts and categories, which is difficult because information can sometimes be “slippery and abstract”. Kat argues this is the real reason that IA is sometimes hard to wrap our heads around. So, getting to the heart of the question, what is information? 

‍

Kat defines information as “a patterned relationship between differences that reduces uncertainty”. The key word here is ‘differences’. The trick to understanding and taming information is to identify what is different about sets of information. The next trick is to identify consistencies between these differences.

‍

This can be a little confusing, so Kat uses the example of picking fruit. We tend to use color (the difference) to identify when fruit is ripe and sweet. We know for a fact that, at some point, the fruit will be at its sweetest and, while there is a scientific way of identifying this point, we have to use the information we have at our disposal instead i.e. the colour of the fruit. The skin of the fruit in this example is like an interface - allowing a flow of information from the fruit’s ripening process to our eyes.

‍

Information categories 🧺🧺🧺

‍

The relationship between the information described in the fruit example can be split into two categories. “Information 1” is a factual, objective description of when the fruit is ripe (i.e. the science of why the fruit is the color that it is right now), whereas our subjective observation, based on color, is “Information 2”.

‍

• Information 1: Matter and energy, and their properties and interactions i.e. the laws of physics and universal truth or rules

‍

Information 1 poses challenges for us because we have a narrow range of perception, attention, and aggregation, which means we, as humans, can’t possibly understand the laws of nature just by observing. We have evolved to be simple, efficient observers of what is important to us. In other words, we don’t need to understand everything in order to get things right. We see patterns and generalize. Going back to the fruit example – we only need to know the color of ripe fruit, not the exact chemistry of why it is ripe.

‍

• Information 2: This is Information 1 that is given meaning by humans. This is done via processing semantic information, or “differences and structures that create meaning for people”.

‍

We use semantic information by processing concepts, patterns, categories, mental models, and even language as inputs to form our understanding. As social animals, we tend to reinforce general ‘truths’ about things because we’re constantly cooperating using shared information. General ‘truths’ are good enough.

‍

Kat uses the following interaction to demonstrate the interplay of different information.

‍

• Person 1: If the raspberries look good, can you get some for me?
• Person 2: How can tell is they’re good?
• Person 1: Get the ones that are the most red.

‍

In this interaction, the different pieces of information can be broken down by category:

‍

• Semantic information = Words and concepts
• Information 1 = Meaningful signs
• Information 2 = Perceptible differences
• Real life information = Raspberries

‍

Using our ability to communicate and understand concepts (words “red”, “good”, and “raspberries”) helps us to understand Information 2 (processing the words and concepts to understand that a red berry is good”), which aligns with Information 1 (the evolutionary science and ongoing consistency of red/ripe berries being sweet) that helps us decide when processing all of this information.

‍

So, now that we understand a little more about information, how does this influence our roles as designers?

‍

Why it matters 👀

‍

Thanks to our individual lived experiences, people have many different inputs/concepts about things. However, Kat points out that we’re pretty good at navigating these different concepts/inputs.

‍

Take conversations, for example. Conversations are our way of getting a “live” alignment of information. If we’re not on the same page we can ask each other questions to ensure we’re communicating semantic information accurately. 

‍

When we start to think about technology and digital products, the interfaces that we design and code become the information that is being transmitted, rather than words in a conversation. The design and presentation become semantic information structures, helping someone to understand the information we’re putting forward. This highlights the importance of aligning the interface (structure and semantic information) and the users' ontology (concepts and categories). For the interface to work, IA practitioners and designers need to know what most people understand to be true when they interact with information, concepts, and categories. 

‍

We need to find some sort of stability that means that most users can understand what they need to do to achieve a goal or make a decision. To do this, we need to find common ground between the semantic information (that might vary between users) so that users can have successful Information 2 style interactions (i.e. absorbing and understanding the concepts presented by the interface).

‍

To wrap up, let’s remind ourselves that information architecture is “the practice of ensuring concepts, categories and their properties and relations are arranged into appropriate and relevant positions”. As IA practitioners and designers, it’s our job to ensure that concepts and categories are arranged in structures that can be understood by the nuance of shared human understanding and semantic information – not just in some physical diagram.

‍

We need to present stable, local structures that help to reduce uncertainty at the moment of interaction. If we don’t, the information flow breaks and we aren’t reducing uncertainty; instead, we create confusion and disappointing user interactions with our digital products. Making sure we present information correctly is important (and difficult!) for the success of our products – and for better or worse, it’s the work of information architecture! 

‍

‍