Category: Blog

Your blog category

  • Personalization Pyramid: A Framework for Designing with User Data

    Personalization Pyramid: A Framework for Designing with User Data

    As a UX skilled in today’s data-driven landscape, it’s extremely likely that you’ve been asked to design a personal digital experience, whether it’s a common website, user portal, or local application. Although there is still a lot of advertising hype surrounding personalization programs, there are still very some standardized methods for implementing personalized UX.

    That’s where we come in. We set ourselves the challenge of developing a systematic personalization construction tailored to UX practitioners after finishing dozens of personalization tasks over the past few years. The Personalization Pyramid is a designer-centric model for standing up human-centered personalisation programs, spanning information, classification, content delivery, and general goals. By using this strategy, you will be able to understand the core elements of a modern, UX-driven personalization system ( or at the very least understand enough to get started ).

    Getting Started

    For the sake of this article, we’ll suppose you’re already familiar with the basics of online personalization. A nice guide can be found these: Website Personalization Planning. Although Graphic projects in this field can take a variety of forms, they frequently begin with identical starting points.

    Popular circumstances for launching a personalization task:

    • Your business or client made a purchase to personalize their content management system ( CMS ), marketing automation platform ( MAP ), or other related technology.
    • The CMO, CDO, or CIO has identified personalisation as a target
    • User data is disjointed or confusing
    • You are conducting some sporadic targeting strategies or A/B assessment.
    • On personalization strategy, participants disagree.
    • Mandate of customer privacy rules ( e. g. GDPR ) requires revisiting existing user targeting practices

    A powerful personalization plan will need the same fundamental building blocks regardless of where you begin. We’ve captured these as the “levels” on the tower. Whether you are a UX artist, scholar, or planner, understanding the core components may help make your contribution effective.

    From top to bottom, the rates include:

      North Star: What larger corporate goal is driving the personalization system?
    1. Objectives: What are the specific, tangible benefits of the system?
    2. Touchpoints: Where will the personalized experience been served?
    3. Contexts and Campaigns: What personalization information does the person view?
    4. User Sections: What constitutes a special, suitable market?
    5. What trustworthy and credible information does our professional platform collect to enable personalization?
    6. Natural Data: What wider set of data is potentially available ( now in our environment ) allowing you to optimize?

    We’ll go through each of these amounts sequentially. An associated deck of cards was created to highlight specific examples from each level to make this more meaningful. We’ve included example for you here because we think they’re useful for customisation brainstorming sessions.

    Beginning at the Top

    The tower has the following elements:

    North Star

    With your personalisation plan, whether large or small, you aim for a general north star. The North Star identifies the (one ) overall goal of the personalization program. What do you wish to perform? North Stars cast a ghost. The bigger the sun, the bigger the darkness. Example of North Starts may contain:

      Function: Personalize based on basic customer input. Examples:” Raw” messages, basic search effects, system user settings and settings options, general flexibility, basic improvements
    1. Feature: Self-contained customisation componentry. Examples:” Cooked” notifications, advanced optimizations ( geolocation ), basic dynamic messaging, customized modules, automations, recommenders
    2. Experience: Personal user experiences across several interactions and consumer flows. Examples: Email campaigns, landing pages, advanced messaging ( i. e. C2C chat ) or conversational interfaces, larger user flows and content-intensive optimizations ( localization ).
    3. Solution: Highly differentiating customized product experiences. Example: Standalone, branded experience with personalization at their base, like the “algotorial” songs by Spotify quite as Discover Weekly.

    Goals

    As in any great UX style, personalization may help promote designing with client intentions. Objectives are the military and measurable indicators that will show the success of the overall program. Start with your existing analytics and measurement system, as well as metrics that you can benchmark against. In some cases, new targets may be suitable. The most important thing to keep in mind is that personalisation is never a desired outcome. It is a means to an end. Popular targets include:

    • Conversion
    • Time on work
    • Net promoter score ( NPS)
    • Consumer satisfaction

    Touchpoints

    Touchpoints are where personalisation takes place. As a UX artist, this will be one of your largest areas of responsibility. The touchpoints you have will depend on how your personalization and the related technologies are configured, and they should be based on enhancing a person’s encounter at a specific point in the journey. Touchpoints can be multi-device ( mobile, in-store, website ) but also more granular ( web banner, web pop-up etc. ). Here are some examples:

    Channel-level Touchpoints

    • Email: Role
    • Email: Occasion of available
    • In-store display ( JSON endpoint )
    • Native game
    • Search

    Wireframe-level Touchpoints

    • Web overlay
    • Web call club
    • Web symbol
    • Web content stop
    • Web list

    If you’re designing for online interface, for instance, you will likely need to include personal “zones” in your wireframes. Based on our next stage, settings, and campaigns, the articles for these can be presented dynamically in touchpoints.

    Contexts and Campaigns

    After you’ve outlined some touchpoints, you may consider the actual personal information a user may get. Many personalization tools will refer to these as” campaigns” ( so, for example, a campaign on a web banner for new visitors to the website ). These will be displayed automatically to specific consumer sections, as defined by consumer data. At this stage, we find it helpful to contemplate two distinct concepts: a framework design and a willing design. The environment helps you consider whether a consumer is engaging with the personalization process at the moment, such as when they are simply browsing the web or engaging in a deep dive. Think of it in conditions of activities for data recovery. The content model can then guide you in deciding which personalization to use in terms of the context ( for instance, an” Enrich” campaign that features related articles might be a good substitute for extant content ).

    Personalization Context Model:

    1. Browse
    2. Skim
    3. Nudge
    4. Feast

    Personalization Content Model:

    1. Alert
    2. Create Easier
    3. Cross-Sell
    4. Enrich

    We’ve written a lot more in depth about each of these concepts somewhere, so be sure to check out Colin’s Personalization Content Model and Jeff’s Personalization Context Model.

    User Sections

    User segments can be created based on user research, either prescriptively or adaptively ( e .g., through rules and logic tied to set user behaviors or through A/B testing ). You will need to consider how to treat the logged-in visitor, the guest or returning visitor, for whom you may have a stateful cookie ( or another post-cookie identifier ), or the authenticated visitor at the least. Using the personalisation tower, here are some examples:

    • Unknown
    • Guest
    • Authenticated
    • Default
    • Referred
    • Role
    • Cohort
    • Unique ID

    Actionable Data

    Every business with a modern presence has information. It’s important to inquire about how to use the data you can ethically collect on users, its inherent reliability and value, and how to use it ( sometimes referred to as “data activation” ). Fortunately, the tide is turning to first-party information: a recent study by Twilio estimates some 80 % of firms are using at least some type of first-party information to personalize the customer experience.

    First-party data represents multiple benefits on the UX before, including being relatively simple to acquire, more likely to be accurate, and less susceptible to the” creep issue” of third-party information. Therefore, determining which method of data collection is best for your audiences should be a crucial component of your UX strategy. Here are some examples:

    When it comes to recognizing and making decisions about various audiences and their signals, there is a trend of profiling. As user data volume and time and confidence increase, it varies more granularly to more precise constructs about ever-smaller cohorts of users.

    Although some combination of implicit and explicit data is typically required for any implementation ( more commonly known as first party and third-party data ), ML efforts are typically not cost-effective right away. This is because optimization requires a strong data backbone and content repository. These approaches, however, should be taken into account as part of the overall plan and may in fact help to speed up the organization’s progress overall. At this point, you will typically work with important stakeholders and product owners to create a profiling model. The profiling model includes a defining framework for setting up profiles, profile keys, profile cards, and pattern cards. A multi-faceted approach to profiling which makes it scalable.

    Pulling it Together

    The cards serve as a starting point for an inventory of sorts ( we offer blanks for you to customize your own ), a set of potential levers and motivations for the personalization activities you aspire to deliver, but they are more valuable when grouped together.

    One can begin to trace the entire course of a card’s “hand” from leadership focus down to a strategic and tactical execution. It is also at the heart of the way that both co-authors have organized workshops to build a backlog of programs, which would make a good subject for a separate article.

    In the meantime, it is important to note that each colored class of cards is helpful in understanding the range of options that you might have, as well as making informed choices about who, where, when, and how, will be made these choices.

    Lay Down Your Cards

    Any sustainable personalization strategy must consider near, mid and long-term goals. There is simply no “easy button” where a personalization program can be stood up and immediately see meaningful results, even with the leading CMS platforms like Sitecore and Adobe or the most exciting composable CMS DXP out there. That said, there is a common grammar to all personalization activities, just like every sentence has nouns and verbs. These cards attempt to map that territory.

  • Opportunities for AI in Accessibility

    Opportunities for AI in Accessibility

    I thoroughly enjoyed reading Joe Dolson’s most recent article on the crossroads of AI and availability because of how skeptical he is of AI in general and how many people have been using it. Despite working for Microsoft as an affordability technology strategist and managing the AI for Accessibility grant program, I’m pretty skeptical of AI. As with any tool, AI can be used in quite productive, equitable, and visible ways, and it can also be used in dangerous, unique, and dangerous ones. And there are a lot of uses for the poor midsection as well.

    I’d like you to consider this a “yes … and” piece to complement Joe’s post. I’m no trying to reject any of what he’s saying, but rather to give some context to initiatives and opportunities where AI may produce real, positive impacts on people with disabilities. To be clear, I’m not saying that there aren’t true threats or pressing problems with AI that need to be addressed—there are, and we’ve needed to address them, like, yesterday—but I want to take a little time to talk about what’s possible in hope that we’ll get there one day.

    Other text

    Joe’s article spends a lot of time examining how computer vision versions can create other words. He raises a number of legitimate points about the state of affairs right now. And while computer-vision concepts continue to improve in the quality and complexity of information in their information, their benefits aren’t wonderful. He argues to be accurate that the state of image research is currently very poor, especially for some graphic types, in large part due to the lack of context-based analysis that exists in the AI systems ( which is a result of having separate “foundation” models for text analysis and image analysis ). Today’s models aren’t trained to distinguish between images that are contextually relevant ( that should probably have descriptions ) and those that are purely decorative ( which might not need a description ) either. However, I still think there’s possible in this area.

    As Joe mentions, human-in-the-loop publishing of alt word should definitely be a factor. And if AI can intervene and provide a starting point for alt text, even if the quick reads,” What is this BS?” That’s certainly correct at all … Let me try to offer a starting point— I think that’s a win.

    If we can specifically teach a design to consider image usage in context, it might be able to help us more swiftly distinguish between images that are likely to be attractive and those that are more descriptive. That will help clarify which situations require image descriptions, and it will increase authors ‘ effectiveness in making their sites more visible.

    The image example provided in the GPT4 announcement provides an intriguing opportunity, even though complex images like graphs and charts are challenging to summarize succinctly ( even for humans ). Let’s say you came across a map that was simply the name of the table and the type of visualization it was: Pie table comparing smartphone use to have phone use among US households making under$ 30, 000 annually. ( That would be a pretty bad alt text for a chart because it frequently leaves many unanswered questions about the data, but let’s just assume that was the description in place. ) Imagine a world where users could ask questions about the graphic if your browser knew that that image was a pie chart ( because an onboard model concluded this ).

    • Do more people use smartphones or other types of smartphones?
    • How many more?
    • Do you know of any people who don’t fall under either of these categories?
    • How many is that?

    Setting aside the realities of large language model ( LLM) hallucinations—where a model just makes up plausible-sounding “facts” —for a moment, the opportunity to learn more about images and data in this way could be revolutionary for blind and low-vision folks as well as for people with various forms of color blindness, cognitive disabilities, and so on. It might also be useful in educational settings to assist those who can, as is, comprehend the data contained in these charts.

    What if you could ask your browser to make a complicated chart simpler? What if you demanded that the line graph be isolated into just one line? What if you could ask your browser to change the color combinations in your browser so that it works better for your type of color blindness? What if you asked it to switch colors in favor of patterns? Given these tools ‘ chat-based interfaces and our existing ability to manipulate images in today’s AI tools, that seems like a possibility.

    Now imagine a specially designed model that could take the data from that chart and convert it to another format. For example, perhaps it could turn that pie chart ( or better yet, a series of pie charts ) into more accessible ( and useful ) formats, like spreadsheets. That would be amazing!

    Matching algorithms

    When Safiya Umoja Noble chose to put her book Algorithms of Oppression, she hit the nail on the head. Although her book focused on the ways that search engines can foster racism, I believe it’s equally true that all computer models have the potential to foster conflict, prejudice, and intolerance. We all know that poorly designed and maintained algorithms are incredibly harmful, whether it’s Twitter that keeps bringing you the most recent tweet from a drowsy billionaire, YouTube that keeps us in a q-hole, or Instagram that keeps us guessing what natural bodies look like. A large portion of this is a result of a lack of diversity in the people who design and construct them. When these platforms are built with inclusively baked in, however, there’s real potential for algorithm development to help people with disabilities.

    Take Mentra, for example. They serve as a network of employment for people who are neurodivers. Based on more than 75 data points, they match job seekers with potential employers using an algorithm. On the job-seeker side of things, it considers each candidate’s strengths, their necessary and preferred workplace accommodations, environmental sensitivities, and so on. On the employer side, it considers each work environment, communication factors related to each job, and the like. Mentra made the decision to change the script when it came to the typical employment websites because it was run by neurodivergent people. They lower the emotional and physical labor on the job-seeker side of things by recommending available candidates to companies who can then connect with job seekers they are interested in.

    When more people with disabilities are involved in developing algorithms, this can lower the likelihood that these algorithms will harm their communities. That’s why diverse teams are so important.

    Imagine if the social media company’s recommendation engine was tuned to prioritize follow recommendations from people who discussed topics of interest to those who were fundamentally different from your current sphere of influence. For instance, if you were to follow a group of non-disabled white male academics who talk about AI, it might be advisable to follow those who are disabled, aren’t white, or aren’t men who also talk about AI. If you took its recommendations, perhaps you’d get a more holistic and nuanced understanding of what’s happening in the AI field. These same systems should also use their understanding of biases about particular communities—including, for instance, the disability community—to make sure that they aren’t recommending any of their users follow accounts that perpetuate biases against (or, worse, spewing hate toward ) those groups.

    Other ways that AI can helps people with disabilities

    I’m sure I could go on and on about using AI to assist people with disabilities, but I’m going to make this last section into a bit of a lightning round if I weren’t trying to put this together in between other tasks. In no particular order:

      Voice preservation. You may have seen the VALL-E paper or Apple’s Global Accessibility Awareness Day announcement or you may be familiar with the voice-preservation offerings from Microsoft, Acapela, or others. It’s possible to train an artificial intelligence model to mimic your voice, which can be incredibly helpful for those who have ALS ( Lou Gehrig’s disease ), motor neuron disease, or other medical conditions that can make it difficult to talk. This is, of course, the same tech that can also be used to create audio deepfakes, so it’s something that we need to approach responsibly, but the tech has truly transformative potential.
    • Voice recognition. Researchers are assisting people with disabilities in the collection of recordings of people with atypical speech, thanks to the assistance of the Speech Accessibility Project. As I type, they are actively recruiting people with Parkinson’s and related conditions, and they have plans to expand this to other conditions as the project progresses. More people with disabilities will be able to use voice assistants, dictation software, and voice-response services as a result of this research, which will result in more inclusive data sets that will enable them to use their computers and other devices more easily and with just their voices.
    • Text transformation. The most recent generation of LLMs is quite capable of changing existing text without giving off hallucinations. This is incredibly empowering for those who have cognitive disabilities and who may benefit from text summaries or simplified versions, or even text that has been prepared for Bionic Reading.

    The value of various teams and sources of data

    We must acknowledge the importance of our differences. The intersections of the identities we live in have an impact on our lived experiences. These lived experiences—with all their complexities ( and joys and pain ) —are valuable inputs to the software, services, and societies that we shape. Our differences must be reflected in the data we use to develop new models, and those who provide it need to be compensated for doing so. Inclusive data sets produce stronger models that promote more justifiable outcomes.

    Want a model that doesn’t demean or patronize or objectify people with disabilities? Make sure that you include information about disabilities that is written by people who have a range of disabilities and that is well represented in the training data.

    Want a model that doesn’t use ableist language? You might be able to use already-existing data sets to create a filter that can read ableist language before it is read. That being said, when it comes to sensitivity reading, AI models won’t be replacing human copy editors anytime soon.

    Want a copilot for coding that provides recommendations that are accessible after the jump? Train it on code that you know to be accessible.


    I have no doubt that AI can and will harm people … today, tomorrow, and well into the future. But I also believe that we can acknowledge that and, with an eye towards accessibility ( and, more broadly, inclusion ), make thoughtful, considerate, and intentional changes in our approaches to AI that will reduce harm over time as well. Today, tomorrow, and well into the future.


    Many thanks to Kartik Sawhney for helping me with the development of this piece, Ashley Bischoff for her invaluable editorial assistance, and, of course, Joe Dolson for the prompt.

  • I am a creative.

    I am a creative.

    I am a artistic. What I do is alchemy. It is a secret. Instead of letting it get done by me, I do it.

    I am a innovative. This tag is not appropriate for all creatives. Not all people see themselves in this manner. Some innovative people practice technology in their work. That is their reality, and I respect it. Sometimes I even envy them, a minor. But my operation is different—my becoming is unique.

    Apologizing and qualifying in advance is a diversion. That’s what my mind does to destroy me. I’ll leave it alone for today. I may regret and be qualified at any time. After I’ve said what I should have. Which is challenging enough.

    Except when it flows like a wine valley and is simple.

    Sometimes it does. Maybe I have to make something right away. When I say something at that time, I’ve learned not to say it because people often don’t work hard enough to acknowledge that the idea is the best idea even when you know it’s the best idea.

    Maybe I work and work and work until the thought strikes me. It occasionally arrives right away, but I don’t remind people for three weeks. Sometimes I blurt out the plan so quickly that I didn’t stop myself. like a child who discovered a prize in a box of Cracker Jacks. I occasionally manage to escape this. Maybe other people agree: yes, that is the best plan. Most days they don’t and I regret having given way to joy.

    Passion should only be saved for the meet, when it matters. not the informal gathering that two different gatherings precede that meeting. Anyone knows why we have all these sessions. We keep saying we’re going to get rid of them, but we just keep trying to find different ways to get them. They occasionally yet excel. But occasionally they are a hindrance to the real job. The percentages between when conferences are important, and when they are a sad distraction, vary, depending on what you do and where you do it. also who you are and what you do. Suddenly I digress. I am a artistic. That is the design.

    Sometimes, despite many hours of diligent effort, someone is hardly useful. Maybe I have to take that and move on to the next task.

    Don’t question about method. I am a artistic.

    I am a artistic. I don’t handle my goals. And I don’t handle my best tips.

    I can nail aside, surround myself with information or photos, and maybe that works. I can go for a walk, and occasionally that functions. There is a Eureka that has nothing to do with sizzling crude and flowing pots. I may be making dinner. I frequently have a sense of direction when I awaken. The idea that may have saved me disappears almost as frequently as I become aware and part of the world once more in a mindless weather of oblivion. For imagination, I believe, comes from that other world. The one we enter in aspirations, and possibly, before conception and after death. But that’s for writers to know, and I am not a writer. I am a artistic. And it’s for philosophers to build massive forces in their imaginative world that they claim to be true. But that is another diversion. And it’s miserable. Possibly on a much bigger issue than whether or not I am creative. But that’s also a step backwards from what I’m trying to say.

    Often the process is evasion. And horror. You know the cliché about the abused designer? It’s true, even when the artist ( and let’s put that noun in quotes ) is trying to write a soft drink jingle, a callback in a tired sitcom, a budget request.

    Some individuals who detest being called artistic perhaps been closeted artists, but that’s between them and their gods. No offence meant. Your wisdom is correct, too. My needs are own, though.

    Creatives understand creatives.

    Negatives are aware of cons, just like queers are aware of queers, just like real rappers are aware of true rappers. Creatives feel enormous regard for creatives. We love, respect, emulate, and nearly deify the excellent ones. To revere any man is, of course, a horrible mistake. We have been warned. We know much. We know people are really people. They dispute, they are depressed, they regret their most critical decisions, they are weak and thirsty, they can be cruel, they can be just as terrible as we can, if, like us, they are clay. But. But. However, they produce this incredible point. They give birth to something that may not occur before them and couldn’t exist without. They are thought’s founders. And I suppose, since it’s only lying it, I have to put that they are the mother of technology. Ba ho backside! Okay, that’s done. Continue.

    Creatives disparage our personal small successes, because we compare them to those of the wonderful people. Wonderful video! Also, I‘m no Miyazaki. Now THAT is glory. That is brilliance straight out of the mouth of God. This half-starved small item that I made? It essentially fell off the pumpkin vehicle. And the carrots weren’t even new.

    Creatives knows that, at best, they are Salieri. That is what Mozart’s artists do, actually.

    I am a artistic. I haven’t worked in advertising in 30 times, but in my hallucinations, it’s my former artistic managers who judge me. They are correct in doing so. I am very lazy, overly simplistic, and when it actually counts, my mind goes blank. There is no supplement for innovative function.

    I am a innovative. Every project I create has a goal that makes Indiana Jones appear to be a retiree snoring in a deck head. The more I pursue creativity, the faster I can finish my work, and the longer I brood and circle and gaze aimlessly before I can finish that work.

    I can move ten times more quickly than those who aren’t creative, those who have just been creative for a short while, and those who have just had a short time of creative work. Only that I work twice as quickly as they do, putting the work away, just before I do it, When I put my mind to it, I am so confident in my ability to do a wonderful career. I am that attached to the excitement scramble of delay. I also have a fear of the climb.

    I am not an actor.

    I am a artistic. No an actor. Though I dreamed, as a child, of eventually being that. Some of us criticize our abilities and fear our own accomplishments because we are not Michelangelos and Warhols. That is narcissism—but at least we aren’t in elections.

    I am a innovative. Though I believe in reason and science, I decide by intelligence and desire. And sit with what follows—the disasters as well as the achievements.

    I am a artistic. Every term I’ve said these may offend another artists, who see things differently. Ask two artists a problem, get three ideas. Our dispute, our enthusiasm about it, and our responsibility to our own reality are, at least to me, the facts that we are artists, no matter how we may think about it.

    I am a artistic. I lament my lack of taste in the areas of human knowledge that I know quite little, that is to say about everything. And I trust my preference above all other items in the regions closest to my soul, or perhaps, more precisely, to my passions. Without my passions, I’d probably have to spend the majority of our time looking ourselves in the eye, which is something that almost none of us can do for very much. No seriously. No actually. Because many in existence, if you really look at it, is terrible.

    I am a artistic. I believe, as a family believes, that when I am gone, some little good part of me will take on in the head of at least one other people.

    Working frees me from worrying about my job.

    I am a innovative. I fear that my little product will disappear.

    I am a innovative. I’m too busy making the next thing to devote too much time to it, especially since practically everything I create did achieve the level of success I conceive of.

    I am a artistic. I think that method is the greatest secret. I think it is so important that I’m actually foolish enough to publish an essay I wrote into a little machine without having to go through or edit it. I didn’t do this generally, I promise. But I did it right away because I was even more frightened of forgetting what I was saying because I was afraid of you seeing through my sad movements toward the wonderful.

    There. I think I’ve said it.

  • Weekend Favs February 22nd

    Weekend Favs February 22nd

    Weekend Favs February 22nd written by John Jantsch read more at Duct Tape Marketing

    My weekend blog post routine includes posting links to a handful of tools or great content I ran across during the week. I don’t go into depth about the finds, but I encourage you to check them out if they sound interesting. The photo in the post is a favorite for the week from an online […]

    The 7 Roles Every Small Business Owner Must Master (and How to Manage Them All) written by John Jantsch read more at Duct Tape Marketing

    The Duct Tape Marketing Podcast with John Jantsch

    In this episode of the Duct Tape Marketing Podcast, I discussed the many hats small business owners wear and how to manage them effectively. Running a business often feels like spinning plates—balancing leadership, sales, client management, and more. Without the right systems in place, entrepreneurs can quickly become overwhelmed.

    I broke down the seven essential roles every small business owner must master and shared practical strategies for streamlining operations, leveraging automation tools, and using business delegation to scale efficiently. From marketing strategy to project management, these insights help entrepreneurs focus on business growth while reducing day-to-day chaos.

    Mastering these small business management roles is key to scaling a business without burnout. By delegating, automating, and focusing on core priorities, entrepreneurs can build a more sustainable and profitable business.

    Key Takeaways:

    • CEO Vision: Small business owners must take time to plan long-term goals and growth strategies to avoid getting stuck in daily tasks.
    • Sales & Marketing: Consistently generating leads and automating follow-ups ensures a steady pipeline of clients.
    • Strategic Planning: A repeatable marketing strategy helps differentiate your business and deliver measurable results.
    • Project & Client Management: Using productivity tools for entrepreneurs like Monday or Asana simplifies workflow and client communication.
    • Finance & Accounting: Outsourcing bookkeeping frees up time and ensures financial stability.
    • Time Management & Delegation: Leveraging virtual assistants for business and outsourcing for small businesses reduces workload while improving efficiency.
    • Automation & AI: Sales automation and business process automation help small business owners scale without increasing workload.

    Chapters:

    [00:26] Juggling Multiple Roles
    [04:38] The CEO Role
    [05:37] The Sales Person Role
    [07:09] The Strategist Role
    [08:46] The Project Manager Role
    [09:49] The Marketing Role
    [12:59] The Client Manager Role
    [13:56] The 4-Prong Approach

     

    John Jantsch (00:00.866)

    Hello and welcome to another episode of the Duct Tape Marketing Podcast. This is John Jantsch and no guest today, just me, solo show. Those of you out in TV land, see I’ve got my DTM hat wearing just for this solo show. So what are we gonna talk about today? Remember when I was a little kid, I went to the circus, probably many of you did as well. I think they still have it around. Anyway.

    They had the elephants and the trapeze and all that stuff, right? But my favorite, always remember was like this guy that would have like seven or eight plates and you’d have them spinning on these long big sticks. You’ve probably seen somebody do that before as well. And you know, it’s just as one would start to drop, he’d get over there and get that one going again. And then he’d find another one that was getting ready to drop and he’d do that one again. you know, years later, I find that and maybe some of you can relate running a business is a lot like that, isn’t it?

    feel like we’re constantly spinning plates. And there’s a reason for that. Unless you have 50 or 100 people working for you, you’ve probably got multiple roles. In fact, the typical small agency owner, marketing consultant, that’s who we work with. That’s who I want to talk with, talk about today. I would say that we’ve all got like seven roles that we have to do every single day, maybe or maybe a lot of them we’re not doing, but they still follow us, right? And so

    I want to talk today about what those roles are, but then I want to spend some time focused on how we actually free ourselves from the chaos of that, of the, many of those roles. mean, there’s so many amazing tools today that we have available to us. mean, AI being one of them, of course, but a lot of automation tools that really can make life a lot easier.

    There’s a couple other things, certainly delegation to VAs and things. So I’m going to cover all of those today. So let’s go with the seven roles, what they are first off. The first one is CEO. mean, whatever you call yourself, somebody’s got to have, somebody’s the leader, that’s probably you, has to have a vision for the business. so, and that’s a role that I see that doesn’t get played very often. But if we’re not looking up and occasionally saying what needs to happen or where do I want to be this time next year?

    John Jantsch (02:12.75)

    be really, really simple. I mean, you don’t obviously have the same needs as a large organization for a CEO, but somebody who’s at least somebody that being you, who’s at least thinking about like, where am I trying to take this thing? What’s the big picture? All right. Number two, salesperson. Nobody’s going to make it rain, but you, right? I mean, you’re out there generating leads. You’re out there having those meetings. You’re out there closing those deals. That’s a, that’s obviously a very important role that you have to play typically.

    Strategist, if you are a marketing consulting firm, if you’re an agency, you need to develop strategy for your clients. That’s really what’s going to differentiate you from everybody else who’s making those marketing plans, who’s helping that client decide where they’re trying to go. Project manager, right? Once you get the client, you do the strategy, you turn into a project manager, managing maybe its vendors or managing projects, campaigns, whatever the work calls for, there is essentially a project manager.

    role in it. Then client manager, we have to do the reporting, we have to actually if we’re gonna, if we’re gonna have long term retainer clients, which are my favorites, we’re gonna have to actually maintain that relationship, we’re gonna have to be showing value, week in, week out, month in, month out. And that’s a role. That’s a that’s a function inside of business. And then finally, do we call it accountant? I don’t know. It’s a finance role. Somebody has to collect the money, somebody has to send out the invoices, somebody has to balance the

    The checkbook, somebody has to make sure that bills are being paid on time, right? So there is that bookkeeping function. most people that I work with, agency owners, didn’t go into business because they love doing that work, but it’s an essential role. So of these roles, I think the key is to decide.

    which ones are the most important? You know, you can make a case for all of them, right? But there’s no question that selling work, doing strategy, maintaining clients, maybe marketing your own business. I mean, these are roles that really have to be done on a consistent basis if you’re going to grow the business until you start getting help, until you can start getting into the role where maybe you are doing one or two of these and you have people doing some of the other roles.

    John Jantsch (04:31.576)

    So how do you balance that idea that some roles are more important than others, but you can’t just simply neglect or abdicate any of roles. So let’s go through those and talk about maybe how you not escape the role, but escape the chaos of either doing the role poorly or not at all. All right, so the first one, CEO. This is something that in a small business, I mean,

    Time blocking is is the probably the only way you’re going to get to this right? If you just put it down as a task, think big about my business and then that like everything else on your checklist has to be addressed first. You’ve got to give yourself. I don’t care what it is, but let’s just pretend it is. Monday afternoon, block off two hours and use that two hours to think about the future of your business. The vision of business where you’re trying to go.

    who you need to be doing that with, what you need to be doing without kind of feeling like, in between that, I’m gonna return email and I’m gonna do this project proposal for a prospect. No, that time is your big thinking time. If you don’t do it, if you don’t take that time to analyze where you are, where you’re going, where you wanna be, where the opportunities are, it never gets done. And then you just get really trapped in, gosh, wonder what I did today. Don’t know, I sure was busy, right?

    So having that time is how you play the CEO role. Now the salesperson role, you’ve got to really get good at automating a lot of your follow-up. mean, if you are putting, if you’re generating leads by inviting them to webinars or you’re writing, having eBooks or things that they can download, checklists that they can download, you want to make, you know, the active campaigns of the world, the HubSpots of the world will allow you to create a 15 series email follow-up series

    that just heaps value after value after value conversation and does it really automatically. I mean, that one’s kind of a no brainer because you really want to be taking a look, know, sale, active campaign, HubSpot, both also have pipeline. So you want to be taking a look at, are people I’ve talked to, here are people I want to talk to, here are people that have expressed interest but not move forward. You want to be having that kind of conversation where you can use those tools to automate

    John Jantsch (06:54.862)

    You know, if you move somebody from, we had this conversation or we had this meeting, now I’m going to move them to another stage in the pipeline. And that’ll automatically continue to nurture them with a different series of emails because they’ve moved to a different spot in the journey. So it takes time to set some of those things up, but really from a salesperson standpoint, you have to do it. Sales and marketing are something that you have to do every single day. And if you don’t set those things up,

    you’ll not only be dropping opportunities, but you’ll be very inconsistent in terms of pipeline. And I think that’s one of the real killers with a smaller business because you get busy and then you look up one day and go, we haven’t been doing any marketing. Now the strategist role, mean, here’s the pitch from duct tape marketing. If you’re an agency or to this role, developing marketing strategy, developing the master plan for a client.

    is something that you need to have a repeatable proven system for. If you are constantly making it up with every new client, reacting to what they say they want, here’s a hint. They don’t know what they want. Well, they know what they want. They don’t know what they need. They come to you with a list of tactics. We need you to do our social media and run that campaigns and produce content. What they need is a marketing plan, a marketing strategy that really differentiates them.

    And that’s something that we license to agencies, fractional CMOs, consultants as the strategy first leadership system. They need leadership and they need scope. They need you to tell them what to do. They need you to lead them. So having a proven system to do that, quite frankly, is absolutely how you escape really that role from drowning you. Cause that’s, you know, I’ve talked to many, many business owners, many, many agency owners, and that’s the role that

    consumes in some cases the greatest amount of time because it’s custom work every single time you do it. So what I imagine if you actually had a client come to you and say, hey, we need a website. You say, yes, you do. But first you need strategy first. And here’s how. And then you literally went down the process step by step. Here’s the process. You taught others in your organization to run many aspects of the process. You don’t have to think about what are we going to do? We’re going to do strategy first.

    John Jantsch (09:16.588)

    I mean, it’s a game changer. All right, let’s keep moving. Project manager. So you got to work, you develop strategy. They say, the strategy’s brilliant. Who’s gonna do this? And you say, well, I guess we are. And so there, again, using tools like, and we happen to use Monday, project management tools that allow you to not only show your client everything’s on track, give them unified communication.

    give them access to all the reports, setting up a project management process that uses a technology like Monday or ClickUp or Asana. mean, there are a dozen, they probably all work about the same way. It’s essential, I think, if you are going to make this work. And a great deal of the things I’ve talked about, AI can play a real role in helping you. It can help you create, it can help you analyze your sales calls, past sales calls. It could help you create that email nurture

    Setup that I talked about it could actually help you Set up repetitive tasks in some of the the you know, most of these tools today are building AI into it You can set up repetitive tasks in those All right marketing Your own agency. This is probably the one that gets most people I mean We were a lot of successful agencies in there and I can’t tell how many times they’ve said so they’re coming to us, you know analyzing our program and saying

    and don’t look at my website because it’s a work in progress or it needs to be updated or I don’t know what it is. Maybe some of you have experienced that, right? We all do. It’s so hard to work on our own stuff because we’re working on our clients’ stuff. We’ve successfully done where we’ve actually, we have project managers in our business and we actually assign a project manager to our business as a client.

    And I suggest that that’s how you have to look at it is you are one of your clients, you’ve got to get that work done. And that’s where really, you know, delegation, having somebody on board to do it. Consistently producing content, reproducing content, a lot of the AI tools, I never advise anybody to go to chat GPT, and say, give me a blog post on x words, but it does a great job of outlining

    John Jantsch (11:34.466)

    hub pages or outlines for bigger topics or giving you ideas. Then you write the content in your point of view, your voice. And then it does a really good job at repurposing that content into video scripts, into webinars, into LinkedIn posts. And then of course, you know, all of the social networks now tools like Buffer, Hootsuite, Zapier, Zapier, depending upon how you say it.

    Lately, all of these tools really allow you to take a long piece of content, turn it into a hundred social posts, schedule those social posts out. The tools now will analyze. Lately is a great tool. It’ll actually analyze your content for what will get the most engagement. So there are many things that you can do and it’s not just a matter of spraying stuff around, but today, our clients, our prospects are actually

    participating in a lot of networks. They’re getting their information a lot of different places. And so to some degree, we have to have that content in the format that they want it. Video, audio, text, short form, long form, both in video, long form, short form. So I mean, it’s overwhelming job to do that. And so using some of these assistants to really help you can be key. And before I go any farther, let’s use that word assistant again.

    There are so many great ways for you to get virtual assistance. And it may not be, you’re gonna go out and find the marketer of the century and you’re going to delegate all your marketing to them. But maybe your first step is to actually say, look, of these seven roles that John’s talking about, which ones, what are those that I can’t do, I don’t like to do, maybe aren’t as essential for my business?

    You know, finance is essential, but it’s not essential that you do it. That’s one that there are a ton of people out there that just basic bookkeeping can be purchased very inexpensively and it’ll get done right. It’ll get done on time. You will have your invoices going out. So, you know, there are places where, you know, investing in your business to get to free up not just time, not just tasks, but maybe even headspace. You know, some of these roles you don’t get to because you just don’t have the headspace.

    John Jantsch (14:00.814)

    I think we covered, no, I’m down to client manager, keeping clients happy. Boy, I tell you, this is one where we have heavily used AI. And the reason is because a lot of the reports that we get, you use tools like SEMrush and you use Google Analytics and you get these reports, you get a lot of data, but making sense out of the data, extracting anything that demonstrate to a client, here’s the value of what we’re doing.

    AI is tremendous at actually analyzing those results. you know, using tools for that. In terms of accounting, again, I’m sure I don’t think there’s an AI tool out there that’ll send invoices. The day’s coming. We will have that. But in terms of the accounting role, I would definitely say that’s one that find somebody to do that. If you’re doing that yourself, it’s not getting done well. It’s not getting done on time. And that’s going to seriously hurt your business.

    Here’s kind of the four prong approach, if you will.

    John Jantsch (15:08.216)

    Figure out what’s important, figure out what you like to do and what you’re good at doing. What’s the most valuable to your business and focus on creating systems and processes around those things that free up some of your time. Think about what you could delegate. And again, the list for that is what do I hate doing? What am I not good at doing? What maybe doesn’t move the needle?

    if I’m doing it. And those are the first things that you should delegate and outsource so that you’re not doing them. The trouble with a lot of agencies is that, even solopreneurs, maybe you have three or four clients. And so, hey, I can do all this work. But then you look up one day and you can’t. You’re designing the websites, you’re writing all the copy, you’re doing all the things, and all of a sudden, you’ve got as much as you’ve

    got on your plate, can no longer look for clients. You can no longer do really great work. You’re getting burned out. So, you know, delegating and outsourcing as soon as possible is a real key here. So the seven roles that I defined are important. They’re the plates that you have to keep spinning. But guess what? You can build foundations under those plates. They don’t have to be a little skinny stick anymore. So

    That’s my two cents. If you’d like to know more about the duct tape marketing strategy first leadership system that we licensed to agencies and consultancies, check out duct tape marketing.com. We’d love to visit with you about how we might be able to bring our proven systems processes, almost business in a box. These seven roles are all covered in our training. So we can bring you that proven system so that you

    can actually start getting out there and doing your best work, having a life, scaling a business that serves that life. All right, thanks for tuning in. Love to hear your feedback on today’s show and hopefully we’ll run into you one of these days out there on the road.

    powered by

     

     

  • User Research Is Storytelling

    User Research Is Storytelling

    Ever since I was a boy, I’ve been fascinated with movies. I loved the characters and the excitement—but most of all the stories. I wanted to be an actor. And I believed that I’d get to do the things that Indiana Jones did and go on exciting adventures. I even dreamed up ideas for movies that my friends and I could make and star in. But they never went any further. I did, however, end up working in user experience (UX). Now, I realize that there’s an element of theater to UX—I hadn’t really considered it before, but user research is storytelling. And to get the most out of user research, you need to tell a good story where you bring stakeholders—the product team and decision makers—along and get them interested in learning more.

    Think of your favorite movie. More than likely it follows a three-act structure that’s commonly seen in storytelling: the setup, the conflict, and the resolution. The first act shows what exists today, and it helps you get to know the characters and the challenges and problems that they face. Act two introduces the conflict, where the action is. Here, problems grow or get worse. And the third and final act is the resolution. This is where the issues are resolved and the characters learn and change. I believe that this structure is also a great way to think about user research, and I think that it can be especially helpful in explaining user research to others.

    Use storytelling as a structure to do research

    It’s sad to say, but many have come to see research as being expendable. If budgets or timelines are tight, research tends to be one of the first things to go. Instead of investing in research, some product managers rely on designers or—worse—their own opinion to make the “right” choices for users based on their experience or accepted best practices. That may get teams some of the way, but that approach can so easily miss out on solving users’ real problems. To remain user-centered, this is something we should avoid. User research elevates design. It keeps it on track, pointing to problems and opportunities. Being aware of the issues with your product and reacting to them can help you stay ahead of your competitors.

    In the three-act structure, each act corresponds to a part of the process, and each part is critical to telling the whole story. Let’s look at the different acts and how they align with user research.

    Act one: setup

    The setup is all about understanding the background, and that’s where foundational research comes in. Foundational research (also called generative, discovery, or initial research) helps you understand users and identify their problems. You’re learning about what exists today, the challenges users have, and how the challenges affect them—just like in the movies. To do foundational research, you can conduct contextual inquiries or diary studies (or both!), which can help you start to identify problems as well as opportunities. It doesn’t need to be a huge investment in time or money.

    Erika Hall writes about minimum viable ethnography, which can be as simple as spending 15 minutes with a user and asking them one thing: “‘Walk me through your day yesterday.’ That’s it. Present that one request. Shut up and listen to them for 15 minutes. Do your damndest to keep yourself and your interests out of it. Bam, you’re doing ethnography.” According to Hall, [This] will probably prove quite illuminating. In the highly unlikely case that you didn’t learn anything new or useful, carry on with enhanced confidence in your direction.”  

    This makes total sense to me. And I love that this makes user research so accessible. You don’t need to prepare a lot of documentation; you can just recruit participants and do it! This can yield a wealth of information about your users, and it’ll help you better understand them and what’s going on in their lives. That’s really what act one is all about: understanding where users are coming from. 

    Jared Spool talks about the importance of foundational research and how it should form the bulk of your research. If you can draw from any additional user data that you can get your hands on, such as surveys or analytics, that can supplement what you’ve heard in the foundational studies or even point to areas that need further investigation. Together, all this data paints a clearer picture of the state of things and all its shortcomings. And that’s the beginning of a compelling story. It’s the point in the plot where you realize that the main characters—or the users in this case—are facing challenges that they need to overcome. Like in the movies, this is where you start to build empathy for the characters and root for them to succeed. And hopefully stakeholders are now doing the same. Their sympathy may be with their business, which could be losing money because users can’t complete certain tasks. Or maybe they do empathize with users’ struggles. Either way, act one is your initial hook to get the stakeholders interested and invested.

    Once stakeholders begin to understand the value of foundational research, that can open doors to more opportunities that involve users in the decision-making process. And that can guide product teams toward being more user-centered. This benefits everyone—users, the product, and stakeholders. It’s like winning an Oscar in movie terms—it often leads to your product being well received and successful. And this can be an incentive for stakeholders to repeat this process with other products. Storytelling is the key to this process, and knowing how to tell a good story is the only way to get stakeholders to really care about doing more research. 

    This brings us to act two, where you iteratively evaluate a design or concept to see whether it addresses the issues.

    Act two: conflict

    Act two is all about digging deeper into the problems that you identified in act one. This usually involves directional research, such as usability tests, where you assess a potential solution (such as a design) to see whether it addresses the issues that you found. The issues could include unmet needs or problems with a flow or process that’s tripping users up. Like act two in a movie, more issues will crop up along the way. It’s here that you learn more about the characters as they grow and develop through this act. 

    Usability tests should typically include around five participants according to Jakob Nielsen, who found that that number of users can usually identify most of the problems: “As you add more and more users, you learn less and less because you will keep seeing the same things again and again… After the fifth user, you are wasting your time by observing the same findings repeatedly but not learning much new.” 

    There are parallels with storytelling here too; if you try to tell a story with too many characters, the plot may get lost. Having fewer participants means that each user’s struggles will be more memorable and easier to relay to other stakeholders when talking about the research. This can help convey the issues that need to be addressed while also highlighting the value of doing the research in the first place.

    Researchers have run usability tests in person for decades, but you can also conduct usability tests remotely using tools like Microsoft Teams, Zoom, or other teleconferencing software. This approach has become increasingly popular since the beginning of the pandemic, and it works well. You can think of in-person usability tests like going to a play and remote sessions as more like watching a movie. There are advantages and disadvantages to each. In-person usability research is a much richer experience. Stakeholders can experience the sessions with other stakeholders. You also get real-time reactions—including surprise, agreement, disagreement, and discussions about what they’re seeing. Much like going to a play, where audiences get to take in the stage, the costumes, the lighting, and the actors’ interactions, in-person research lets you see users up close, including their body language, how they interact with the moderator, and how the scene is set up.

    If in-person usability testing is like watching a play—staged and controlled—then conducting usability testing in the field is like immersive theater where any two sessions might be very different from one another. You can take usability testing into the field by creating a replica of the space where users interact with the product and then conduct your research there. Or you can go out to meet users at their location to do your research. With either option, you get to see how things work in context, things come up that wouldn’t have in a lab environment—and conversion can shift in entirely different directions. As researchers, you have less control over how these sessions go, but this can sometimes help you understand users even better. Meeting users where they are can provide clues to the external forces that could be affecting how they use your product. In-person usability tests provide another level of detail that’s often missing from remote usability tests. 

    That’s not to say that the “movies”—remote sessions—aren’t a good option. Remote sessions can reach a wider audience. They allow a lot more stakeholders to be involved in the research and to see what’s going on. And they open the doors to a much wider geographical pool of users. But with any remote session there is the potential of time wasted if participants can’t log in or get their microphone working. 

    The benefit of usability testing, whether remote or in person, is that you get to see real users interact with the designs in real time, and you can ask them questions to understand their thought processes and grasp of the solution. This can help you not only identify problems but also glean why they’re problems in the first place. Furthermore, you can test hypotheses and gauge whether your thinking is correct. By the end of the sessions, you’ll have a much clearer picture of how usable the designs are and whether they work for their intended purposes. Act two is the heart of the story—where the excitement is—but there can be surprises too. This is equally true of usability tests. Often, participants will say unexpected things, which change the way that you look at things—and these twists in the story can move things in new directions. 

    Unfortunately, user research is sometimes seen as expendable. And too often usability testing is the only research process that some stakeholders think that they ever need. In fact, if the designs that you’re evaluating in the usability test aren’t grounded in a solid understanding of your users (foundational research), there’s not much to be gained by doing usability testing in the first place. That’s because you’re narrowing the focus of what you’re getting feedback on, without understanding the users’ needs. As a result, there’s no way of knowing whether the designs might solve a problem that users have. It’s only feedback on a particular design in the context of a usability test.  

    On the other hand, if you only do foundational research, while you might have set out to solve the right problem, you won’t know whether the thing that you’re building will actually solve that. This illustrates the importance of doing both foundational and directional research. 

    In act two, stakeholders will—hopefully—get to watch the story unfold in the user sessions, which creates the conflict and tension in the current design by surfacing their highs and lows. And in turn, this can help motivate stakeholders to address the issues that come up.

    Act three: resolution

    While the first two acts are about understanding the background and the tensions that can propel stakeholders into action, the third part is about resolving the problems from the first two acts. While it’s important to have an audience for the first two acts, it’s crucial that they stick around for the final act. That means the whole product team, including developers, UX practitioners, business analysts, delivery managers, product managers, and any other stakeholders that have a say in the next steps. It allows the whole team to hear users’ feedback together, ask questions, and discuss what’s possible within the project’s constraints. And it lets the UX research and design teams clarify, suggest alternatives, or give more context behind their decisions. So you can get everyone on the same page and get agreement on the way forward.

    This act is mostly told in voiceover with some audience participation. The researcher is the narrator, who paints a picture of the issues and what the future of the product could look like given the things that the team has learned. They give the stakeholders their recommendations and their guidance on creating this vision.

    Nancy Duarte in the Harvard Business Review offers an approach to structuring presentations that follow a persuasive story. “The most effective presenters use the same techniques as great storytellers: By reminding people of the status quo and then revealing the path to a better way, they set up a conflict that needs to be resolved,” writes Duarte. “That tension helps them persuade the audience to adopt a new mindset or behave differently.”

    This type of structure aligns well with research results, and particularly results from usability tests. It provides evidence for “what is”—the problems that you’ve identified. And “what could be”—your recommendations on how to address them. And so on and so forth.

    You can reinforce your recommendations with examples of things that competitors are doing that could address these issues or with examples where competitors are gaining an edge. Or they can be visual, like quick mockups of how a new design could look that solves a problem. These can help generate conversation and momentum. And this continues until the end of the session when you’ve wrapped everything up in the conclusion by summarizing the main issues and suggesting a way forward. This is the part where you reiterate the main themes or problems and what they mean for the product—the denouement of the story. This stage gives stakeholders the next steps and hopefully the momentum to take those steps!

    While we are nearly at the end of this story, let’s reflect on the idea that user research is storytelling. All the elements of a good story are there in the three-act structure of user research: 

    • Act one: You meet the protagonists (the users) and the antagonists (the problems affecting users). This is the beginning of the plot. In act one, researchers might use methods including contextual inquiry, ethnography, diary studies, surveys, and analytics. The output of these methods can include personas, empathy maps, user journeys, and analytics dashboards.
    • Act two: Next, there’s character development. There’s conflict and tension as the protagonists encounter problems and challenges, which they must overcome. In act two, researchers might use methods including usability testing, competitive benchmarking, and heuristics evaluation. The output of these can include usability findings reports, UX strategy documents, usability guidelines, and best practices.
    • Act three: The protagonists triumph and you see what a better future looks like. In act three, researchers may use methods including presentation decks, storytelling, and digital media. The output of these can be: presentation decks, video clips, audio clips, and pictures. 

    The researcher has multiple roles: they’re the storyteller, the director, and the producer. The participants have a small role, but they are significant characters (in the research). And the stakeholders are the audience. But the most important thing is to get the story right and to use storytelling to tell users’ stories through research. By the end, the stakeholders should walk away with a purpose and an eagerness to resolve the product’s ills. 

    So the next time that you’re planning research with clients or you’re speaking to stakeholders about research that you’ve done, think about how you can weave in some storytelling. Ultimately, user research is a win-win for everyone, and you just need to get stakeholders interested in how the story ends.

  • To Ignite a Personalization Practice, Run this Prepersonalization Workshop

    To Ignite a Personalization Practice, Run this Prepersonalization Workshop

    Picture this. You’ve joined a squad at your company that’s designing new product features with an emphasis on automation or AI. Or your company has just implemented a personalization engine. Either way, you’re designing with data. Now what? When it comes to designing for personalization, there are many cautionary tales, no overnight successes, and few guides for the perplexed. 

    Between the fantasy of getting it right and the fear of it going wrong—like when we encounter “persofails” in the vein of a company repeatedly imploring everyday consumers to buy additional toilet seats—the personalization gap is real. It’s an especially confounding place to be a digital professional without a map, a compass, or a plan.

    For those of you venturing into personalization, there’s no Lonely Planet and few tour guides because effective personalization is so specific to each organization’s talent, technology, and market position. 

    But you can ensure that your team has packed its bags sensibly.

    There’s a DIY formula to increase your chances for success. At minimum, you’ll defuse your boss’s irrational exuberance. Before the party you’ll need to effectively prepare.

    We call it prepersonalization.

    Behind the music

    Consider Spotify’s DJ feature, which debuted this past year.

    We’re used to seeing the polished final result of a personalization feature. Before the year-end award, the making-of backstory, or the behind-the-scenes victory lap, a personalized feature had to be conceived, budgeted, and prioritized. Before any personalization feature goes live in your product or service, it lives amid a backlog of worthy ideas for expressing customer experiences more dynamically.

    So how do you know where to place your personalization bets? How do you design consistent interactions that won’t trip up users or—worse—breed mistrust? We’ve found that for many budgeted programs to justify their ongoing investments, they first needed one or more workshops to convene key stakeholders and internal customers of the technology. Make yours count.

    ​From Big Tech to fledgling startups, we’ve seen the same evolution up close with our clients. In our experiences with working on small and large personalization efforts, a program’s ultimate track record—and its ability to weather tough questions, work steadily toward shared answers, and organize its design and technology efforts—turns on how effectively these prepersonalization activities play out.

    Time and again, we’ve seen effective workshops separate future success stories from unsuccessful efforts, saving countless time, resources, and collective well-being in the process.

    A personalization practice involves a multiyear effort of testing and feature development. It’s not a switch-flip moment in your tech stack. It’s best managed as a backlog that often evolves through three steps: 

    1. customer experience optimization (CXO, also known as A/B testing or experimentation)
    2. always-on automations (whether rules-based or machine-generated)
    3. mature features or standalone product development (such as Spotify’s DJ experience)

    This is why we created our progressive personalization framework and why we’re field-testing an accompanying deck of cards: we believe that there’s a base grammar, a set of “nouns and verbs” that your organization can use to design experiences that are customized, personalized, or automated. You won’t need these cards. But we strongly recommend that you create something similar, whether that might be digital or physical.

    Set your kitchen timer

    How long does it take to cook up a prepersonalization workshop? The surrounding assessment activities that we recommend including can (and often do) span weeks. For the core workshop, we recommend aiming for two to three days. Here’s a summary of our broader approach along with details on the essential first-day activities.

    The full arc of the wider workshop is threefold:

    1. Kickstart: This sets the terms of engagement as you focus on the opportunity as well as the readiness and drive of your team and your leadership. .
    2. Plan your work: This is the heart of the card-based workshop activities where you specify a plan of attack and the scope of work.
    3. Work your plan: This phase is all about creating a competitive environment for team participants to individually pitch their own pilots that each contain a proof-of-concept project, its business case, and its operating model.

    Give yourself at least a day, split into two large time blocks, to power through a concentrated version of those first two phases.

    Kickstart: Whet your appetite

    We call the first lesson the “landscape of connected experience.” It explores the personalization possibilities in your organization. A connected experience, in our parlance, is any UX requiring the orchestration of multiple systems of record on the backend. This could be a content-management system combined with a marketing-automation platform. It could be a digital-asset manager combined with a customer-data platform.

    Spark conversation by naming consumer examples and business-to-business examples of connected experience interactions that you admire, find familiar, or even dislike. This should cover a representative range of personalization patterns, including automated app-based interactions (such as onboarding sequences or wizards), notifications, and recommenders. We have a catalog of these in the cards. Here’s a list of 142 different interactions to jog your thinking.

    This is all about setting the table. What are the possible paths for the practice in your organization? If you want a broader view, here’s a long-form primer and a strategic framework.

    Assess each example that you discuss for its complexity and the level of effort that you estimate that it would take for your team to deliver that feature (or something similar). In our cards, we divide connected experiences into five levels: functions, features, experiences, complete products, and portfolios. Size your own build here. This will help to focus the conversation on the merits of ongoing investment as well as the gap between what you deliver today and what you want to deliver in the future.

    Next, have your team plot each idea on the following 2×2 grid, which lays out the four enduring arguments for a personalized experience. This is critical because it emphasizes how personalization can not only help your external customers but also affect your own ways of working. It’s also a reminder (which is why we used the word argument earlier) of the broader effort beyond these tactical interventions.

    Each team member should vote on where they see your product or service putting its emphasis. Naturally, you can’t prioritize all of them. The intention here is to flesh out how different departments may view their own upsides to the effort, which can vary from one to the next. Documenting your desired outcomes lets you know how the team internally aligns across representatives from different departments or functional areas.

    The third and final kickstart activity is about naming your personalization gap. Is your customer journey well documented? Will data and privacy compliance be too big of a challenge? Do you have content metadata needs that you have to address? (We’re pretty sure that you do: it’s just a matter of recognizing the relative size of that need and its remedy.) In our cards, we’ve noted a number of program risks, including common team dispositions. Our Detractor card, for example, lists six stakeholder behaviors that hinder progress.

    Effectively collaborating and managing expectations is critical to your success. Consider the potential barriers to your future progress. Press the participants to name specific steps to overcome or mitigate those barriers in your organization. As studies have shown, personalization efforts face many common barriers.

    At this point, you’ve hopefully discussed sample interactions, emphasized a key area of benefit, and flagged key gaps? Good—you’re ready to continue.

    Hit that test kitchen

    Next, let’s look at what you’ll need to bring your personalization recipes to life. Personalization engines, which are robust software suites for automating and expressing dynamic content, can intimidate new customers. Their capabilities are sweeping and powerful, and they present broad options for how your organization can conduct its activities. This presents the question: Where do you begin when you’re configuring a connected experience?

    What’s important here is to avoid treating the installed software like it were a dream kitchen from some fantasy remodeling project (as one of our client executives memorably put it). These software engines are more like test kitchens where your team can begin devising, tasting, and refining the snacks and meals that will become a part of your personalization program’s regularly evolving menu.

    The ultimate menu of the prioritized backlog will come together over the course of the workshop. And creating “dishes” is the way that you’ll have individual team stakeholders construct personalized interactions that serve their needs or the needs of others.

    The dishes will come from recipes, and those recipes have set ingredients.

    Verify your ingredients

    Like a good product manager, you’ll make sure—andyou’ll validate with the right stakeholders present—that you have all the ingredients on hand to cook up your desired interaction (or that you can work out what needs to be added to your pantry). These ingredients include the audience that you’re targeting, content and design elements, the context for the interaction, and your measure for how it’ll come together. 

    This isn’t just about discovering requirements. Documenting your personalizations as a series of if-then statements lets the team: 

    1. compare findings toward a unified approach for developing features, not unlike when artists paint with the same palette; 
    2. specify a consistent set of interactions that users find uniform or familiar; 
    3. and develop parity across performance measurements and key performance indicators too. 

    This helps you streamline your designs and your technical efforts while you deliver a shared palette of core motifs of your personalized or automated experience.

    Compose your recipe

    What ingredients are important to you? Think of a who-what-when-why construct

    • Who are your key audience segments or groups?
    • What kind of content will you give them, in what design elements, and under what circumstances?
    • And for which business and user benefits?

    We first developed these cards and card categories five years ago. We regularly play-test their fit with conference audiences and clients. And we still encounter new possibilities. But they all follow an underlying who-what-when-why logic.

    Here are three examples for a subscription-based reading app, which you can generally follow along with right to left in the cards in the accompanying photo below. 

    1. Nurture personalization: When a guest or an unknown visitor interacts with  a product title, a banner or alert bar appears that makes it easier for them to encounter a related title they may want to read, saving them time.
    2. Welcome automation: When there’s a newly registered user, an email is generated to call out the breadth of the content catalog and to make them a happier subscriber.
    3. Winback automation: Before their subscription lapses or after a recent failed renewal, a user is sent an email that gives them a promotional offer to suggest that they reconsider renewing or to remind them to renew.

    A useful preworkshop activity may be to think through a first draft of what these cards might be for your organization, although we’ve also found that this process sometimes flows best through cocreating the recipes themselves. Start with a set of blank cards, and begin labeling and grouping them through the design process, eventually distilling them to a refined subset of highly useful candidate cards.

    You can think of the later stages of the workshop as moving from recipes toward a cookbook in focus—like a more nuanced customer-journey mapping. Individual “cooks” will pitch their recipes to the team, using a common jobs-to-be-done format so that measurability and results are baked in, and from there, the resulting collection will be prioritized for finished design and delivery to production.

    Better kitchens require better architecture

    Simplifying a customer experience is a complicated effort for those who are inside delivering it. Beware anyone who says otherwise. With that being said,  “Complicated problems can be hard to solve, but they are addressable with rules and recipes.”

    When personalization becomes a laugh line, it’s because a team is overfitting: they aren’t designing with their best data. Like a sparse pantry, every organization has metadata debt to go along with its technical debt, and this creates a drag on personalization effectiveness. Your AI’s output quality, for example, is indeed limited by your IA. Spotify’s poster-child prowess today was unfathomable before they acquired a seemingly modest metadata startup that now powers its underlying information architecture.

    You can definitely stand the heat…

    Personalization technology opens a doorway into a confounding ocean of possible designs. Only a disciplined and highly collaborative approach will bring about the necessary focus and intention to succeed. So banish the dream kitchen. Instead, hit the test kitchen to save time, preserve job satisfaction and security, and safely dispense with the fanciful ideas that originate upstairs of the doers in your organization. There are meals to serve and mouths to feed.

    This workshop framework gives you a fighting shot at lasting success as well as sound beginnings. Wiring up your information layer isn’t an overnight affair. But if you use the same cookbook and shared recipes, you’ll have solid footing for success. We designed these activities to make your organization’s needs concrete and clear, long before the hazards pile up.

    While there are associated costs toward investing in this kind of technology and product design, your ability to size up and confront your unique situation and your digital capabilities is time well spent. Don’t squander it. The proof, as they say, is in the pudding.

  • The Wax and the Wane of the Web

    The Wax and the Wane of the Web

    When you begin to believe you have everything figured out, everyone does change, in my experience. Simply as you start to get the hang of injections, diapers, and ordinary sleep, it’s time for solid foods, potty training, and nighttime sleep. When those are determined, school and occasional naps are in order. The pattern continues.

    The same holds true for those of us who are currently employed in design and development. Having worked on the web for about three years at this point, I’ve seen the typical wax and wane of concepts, strategies, and systems. Every day we as developers and designers re-enter the familiar pattern, a brand-new engineering or thought emerges to shake things up and completely alter the world.

    How we got below

    I built my first website in the mid-’90s. Design and development on the web back then was a free-for-all, with few established norms. For any layout aside from a single column, we used table elements, often with empty cells containing a single pixel spacer GIF to add empty space. We styled text with numerous font tags, nesting the tags every time we wanted to vary the font style. And we had only three or four typefaces to choose from: Arial, Courier, or Times New Roman. When Verdana and Georgia came out in 1996, we rejoiced because our options had nearly doubled. The only safe colors to choose from were the 216 “web safe” colors known to work across platforms. The few interactive elements (like contact forms, guest books, and counters) were mostly powered by CGI scripts (predominantly written in Perl at the time). Achieving any kind of unique look involved a pile of hacks all the way down. Interaction was often limited to specific pages in a site.

    The beginning of website standards

    At the turn of the century, a new cycle started. Crufty code littered with table layouts and font tags waned, and a push for web standards waxed. Newer technologies like CSS got more widespread adoption by browsers makers, developers, and designers. This shift toward standards didn’t happen accidentally or overnight. It took active engagement between the W3C and browser vendors and heavy evangelism from folks like the Web Standards Project to build standards. A List Apart and books like Designing with Web Standards by Jeffrey Zeldman played key roles in teaching developers and designers why standards are important, how to implement them, and how to sell them to their organizations. And approaches like progressive enhancement introduced the idea that content should be available for all browsers—with additional enhancements available for more advanced browsers. Meanwhile, sites like the CSS Zen Garden showcased just how powerful and versatile CSS can be when combined with a solid semantic HTML structure.

    Server-side language like PHP, Java, and.NET took Perl as the primary back-end computers, and the cgi-bin was tossed in the garbage bin. With these better server-side instruments came the first time of online applications, starting with content-management systems ( especially in the blog space with tools like Blogger, Grey Matter, Movable Type, and WordPress ). AJAX opened the door to sequential connection between the front end and back end in the mid-2000s. Immediately, websites may update their information without needing to refresh. A grain of JavaScript systems, including Prototype, YUI, and jQuery, were created to aid designers in creating more trustworthy client-side interactions across browsers with wildly varying standards support. Techniques like photo alternative enable skilled manufacturers and developers to use fonts of their choosing. And technology like Flash made it possible to include movies, sports, and even more engagement.

    These new technology, standards, and approaches reinvigorated the market in many ways. As manufacturers and designers explored more diversified styles and designs, website design flourished. However, we also relied heavily on numerous exploits. When it came to basic layout and text styling, early CSS was a significant improvement over table-based layouts, but its limitations at the time meant that designers and developers still rely heavily on images for complex shapes ( such as rounded or angled corners ) and tiled backgrounds (among other hacks ) for the appearance of full-length columns. All kinds of nested floats or absolute positioning ( or both ) were necessary for complicated layouts. The big five typefaces were initially influenced by display and photo replacement, but both tricks caused accessibility and performance issues. And JavaScript books made it simple for anyone to add a dash of connection to pages, even at the expense of double, also quadrupling, the get size of basic websites.

    The internet as application platform

    The balance between the front end and the back end continued to improve, leading to the development of the latest web application time. Between expanded server-side programming languages ( which kept growing to include Ruby, Python, Go, and others ) and newer front-end tools like React, Vue, and Angular, we could build fully capable software on the web. Alongside these equipment came others, including creative type control, build technology, and shared bundle libraries. What was once mainly used for linked papers turned into a world with limitless possibilities.

    At the same time, wireless equipment became more ready, and they gave us online access in our wallets. Mobile applications and flexible style opened up possibilities for new contacts anytime, anywhere.

    This fusion of potent portable devices and potent development resources contributed to the growth of social media and various consolidated tools for user interaction and consumption. As it became easier and more popular to interact with others immediately on Twitter, Facebook, and yet Slack, the need for held private websites waned. Social media provided relationships on a global level, with both the positive and negative effects.

    Want a much more thorough story of how we came to be around as well as some other perspectives on how we can get better? ” Of Time and the Web” was written by Jeremy Keith. Or check out the” Web Design History Timeline” at the Web Design Museum. A joy visit through” Internet Artifacts” is also provided by Neal Agarwal.

    Where we are now

    In the last couple of years, it’s felt like we’ve begun to achieve another big tone level. As social-media programs bone and fade, there’s been a growing interest in owning our own articles again. From the tried-and-true classic of hosting plain HTML files to static site generators and content management systems of all kinds, there are many different ways to create websites. We lose essential infrastructure for discovery and connection because of social media’s fracture, which also comes with a price. Webmentions, RSS, ActivityPub, and other tools of the IndieWeb can help with this, but they’re still relatively underimplemented and hard to use for the less nerdy. We can create incredible personal websites and update them frequently, but without discovery and connection, it can feel as though we could as well be yelling into the void.

    Browser support for CSS, JavaScript, and other standards like web components has accelerated, especially through efforts like Interop. In a fraction of the time that they once did, new technologies gain universal support. I frequently find out about a new feature and check its browser support only to discover that its coverage has already exceeded 80 %. The barrier to using more recent techniques isn’t browser support anymore; it’s more often the speed at which designers and developers can learn what’s available and how to adopt it.

    Today, with a few commands and a couple of lines of code, we can prototype almost any idea. With all the tools we currently have, it is simpler than ever to launch a new venture. However, the upfront cost these frameworks may save in initial delivery eventually comes down as the maintenance and upgrading they become a part of our technical debt.

    Adopting new standards can sometimes take longer if we rely on third-party frameworks because we might have to wait for those frameworks to adopt them. These frameworks—which used to let us adopt new techniques sooner—have now become hindrances instead. Users must wait for scripts to load before they can read or interact with pages, as these same frameworks frequently come with performance costs as well. And when scripts fail ( whether through poor code, network issues, or other environmental factors ), there’s often no alternative, leaving users with blank or broken pages.

    Where do we go from here?

    Today’s hacks help to shape tomorrow’s standards. And there’s nothing inherently wrong with embracing hacks —for now—to move the present forward. Problems only arise when we refuse to acknowledge that they are hacks or when we choose not to replace them. What can we do to create the web’s future that we desire?

    Build for the long haul. Optimize for performance, for accessibility, and for the user. Weigh the costs of those developer-friendly tools. They may make your job a little easier right now, but how do they affect everything else? What’s the cost to users? To future developers? To standards adoption? The convenience may be worthwhile at times. It’s occasionally just a hack that you’ve gotten used to. And occasionally, it prevents you from pursuing better options.

    Start from standards. Standards change over time, but browsers have done a remarkably good job of staying current with outdated standards. The same isn’t always true of third-party frameworks. Even the most heinous of HTML from the 1990s still function perfectly today. Even after a few years, the same can’t be said about websites created with frameworks.

    Design with care. Whether your craft is code, pixels, or processes, consider the impacts of each decision. Many modern tools have the convenience of making the necessary decisions that have led to its design and not always considering the effects those decisions can have. Use the time saved by modern tools to consider more carefully and design with consideration rather than rush to “move fast and break things”

    Always be learning. If you’re always learning, you’re also growing. Sometimes it may be hard to pinpoint what’s worth learning and what’s just today’s hack. Even if you were to concentrate solely on learning standards, you might end up focusing on something that won’t matter next year. ( Remember XHTML? ) However, ongoing learning opens up new connections in your brain, and the techniques you learn in one day may be used to guide different experiments in the future.

    Play, experiment, and be weird! This web that we’ve built is the ultimate experiment. Despite being the largest human endeavor in human history, each of us has the ability to make their own money there. Be courageous and try new things. Build a playground for ideas. Create absurd experiments in your own crazy science lab. Start your own small business. There has never been a more empowering place to be creative, take risks, and explore what we’re capable of.

    Share and amplify. As you experiment, play, and learn, share what’s worked for you. Write on your own website, post on whichever social media site you prefer, or shout it from a TikTok. Write something for A List Apart! But take the time to amplify others too: find new voices, learn from them, and share what they’ve taught you.

    Go forth and make

    As designers and developers for the web ( and beyond ), we’re responsible for building the future every day, whether that may take the shape of personal websites, social media tools used by billions, or anything in between. Let’s imbue our values into the things that we create, and let’s make the web a better place for everyone. Create something that you are uniquely qualified to make. Then share it, make it better, make it again, or make something new. Learn. Make. Share. Grow. Rinse and repeat. Every time you think that you’ve mastered the web, everything will change.

  • Dope Girls Cast: Meet the 1920s-Set BBC Drama’s Characters

    Dope Girls Cast: Meet the 1920s-Set BBC Drama’s Characters

    Dope Women is not your grandmother’s historical play (unless of course, your aunt has lived a existence, has good style in TV, and frankly, could do with a bit more value and a bit less disdain from people assuming that she won’t be able to see anything that isn’t presented by Alan Titchmarsh ). To try ]… ]

    The post Dope Girls Cast: Meet the 1920s-Set BBC Drama’s Characters appeared first on Den of Geek.

    Dope Girls is not your grandma’s historical drama (unless of course, your grandma has lived a life, has good taste in TV, and frankly, could do with a bit more respect and a bit less condescension from people assuming that she won’t be able to watch anything that isn’t presented by Alan Titchmarsh ).

    To try again then, Dope Girls is no Downton Abbey. It might be set in the same time period, but this tale of Soho women dancing with danger, death and well, other dancers in the nightclubs where they work is a world away from the genteel intrigues of the Earl of Grantham.

    With a cast including actors from the US, Australia and the UK, here’s who’s playing who in BBC One’s new Saturday night series.

    cnx. cmd. push ( function ( ) {cnx ( {playerId:” 106e33c0-3911-473c-b599-b1426db57530″, }). render ( “0270c398a82f44f49c23c16122516796” ), }),

    Eliza Scanlen as Violet Davies

    Violet is a new recruit to the Metropolitan police service hoping to be chosen for &#8220, The Female Experiment&#8221, in which women were first made officers in the UK. She&#8217, s tough, alone and has nothing to lose, which makes her a dangerous prospect.

    She’s played by Australian actor Eliza Scanlen, whose breakout roles came in HBO’s 2018 adaptation of Gillian Flynn’s Sharp Objects, and in Greta Gerwig’s 2019 feature film Little Women, in which Scanlen played second-to-youngest March sister Beth. She’s recently appeared opposite Doctor Who‘s Ncuti Gatwa in this year’s National Theatre production of The Importance of Being Earnest.

    Julianne Nicholson as Kate Galloway

    A brunette woman in a black coat in BBC One's Dope Girls

    Kate is cruelly forced to find her own way after she loses her job, and has to go to extreme lengths to provide a living for her and her teenage daughter Evie, a clever girl with the potential to be among the first women in the UK to go to university.

    She’s played by US actor Julianne Nicholson, who’s currently appearing as the wealthy Sinatra in Disney/Hulu political thriller Paradise ( which has just been renewed for a second season ). She’s known for Law &amp, Order, The Outsider, having played Esther in Boardwalk Empire, Lillian in Masters of Sex and Lorri in the first season of Kate Winslet-starring crime drama Mare of Easttown.

    Umi Myers as Billie Cassidy

    Umi Meyers wearing a dress and fur coat in BBC One's Dope Girls

    Billie is a Soho nightclub dancer who lives a bohemian, drink and drug-fuelled lifestyle with her singer friend Eddie Cobb. She’s played by Umi Myers, a recent graduate of the Guildhall School of Music and Drama, with previous stage parts and an appearance in Bob Marley: One Love. Dope Girls is Myers ‘ first television lead role.

    Geraldine James as Isabella Salucci

    Geraldine James in a blue dress in BBC One's Dope Girls

    The matriarch of the fearsome Salucci crime family, Isabella is a ruthless survivor who&#8217, s held her clan together through the War and much more. She’s played by Geraldine James, a familiar face on screen and stage who’s had a long and healthy career going back to the late 1970s. To some TV viewers, she’ll always be indivisible from the part of Sarah in The Jewel in the Crown, to others, she’ll be best recognised as Rose from Band of Gold, Milner in Channel 4’s Utopia, Mrs Hudson in the Guy Ritchie Sherlock Holmes films, and Marissa in Anne With an E, to name just a few.

    Dustin Demri-Burns as Damaso Salucci

    Dustin Demri-Burns wearing a dark suit in BBC One's Dope Girls

    A Salucci son, Damaso is a member of a powerful Soho crime family, and has a terrifying brutal side. He’s played by Dustin Demri-Burns, who’s well known for comedy roles in Cardinal Burns, Stath Lets Flats, GameFace and Am I Being Unreasonable?, but has an equally healthy career in dramas with a comedic edge from The Great to Slow Horses, Britannia, Sweetpea and The Decameron.

    Ian Bonar as Sgt Frank Turner

    A profile of Ian Bonar's face in BBC One's Dope Girls

    Sgt Turner is helping to run The Female Experiment, which saw the UK&#8217, s first female police officers. He&#8217, s a complicated man who does n&#8217, t wield his power well, and makes an early enemy of Violet. He’s played by Ian Bonar, who recently appeared opposite Peter Capaldi in Apple TV +’s Criminal Record, as well as roles across various TV genres, from I May Destroy You to New Blood, Vera and many more.

    Fiona Button as Sophie Asquith-Gore

    Fiona Button wearing a white and green dress in BBC One's Dope Girls

    The wife of a wealthy and important government minister, and the mother to Evie&#8217, s friend Alice, Sophie is grieving the brother she lost in the war, and thinks that she can still speak to him via a medium. She’s played by actor-director Fiona Button, who’s known for the role of Rose Defoe in Abi Morgan’s legal drama The Split, and was recently seen as Denise in series three of Industry, as well as in Grantchester, Out of Her Mind, and plenty of theatre productions.

    Nabhaan Rizwan as Silas Huxley

    Nabhaan Rizwan in BBC One's Dope Girls

    Medium and occultist Silus Huxley takes money from the wealthy to help them contact their dead. He’s played by Nabhaan Rizwan, who recently played Dionysus in Netflix’s KAOS, as well as appearing opposite his brother Mawaan Rizwan in his sitcom Juice, and in the US playing Frank in Station Eleven, after his breakout role in 2018’s BBC crime drama Informer.

    Will Keen as Frederick Asquith-Gore

    A powerful government minister who&#8217, s set on rooting out the rot in London &#8217, s seedy nightclubs, Frederick Asquith-Gore is played by screen and stage actor Will Keen ( incidentally, the father of Logan and His Dark Materials ‘ Dafne Keen ), who recently appeared in BBC drama Wolf Hall as Thomas Cranmer, as well as playing Lord Belzagar in the second season of Lord of the Rings: The Rings of Power, Norfolk in My Lady Jane, the Queen’s private secretary in The Crown, and David in Ridley Road, as well as appearing in feature film Operation Mincemeat and more.

    ALSO APPEARING

    A man holding two fans in BBC One's Dope Girls

    &#8211, Musical stage and screen actor Michael Duke as nightclub singer Eddie Cobb.
    The Outrun and The Power‘s Eilidh Fisher as Kate’s daughter Evie Galloway.
    The Bay, The Reckoning, True Detective and Strike‘s Eloise Thomas as Evie’s schoolfriend Alice Asquith-Gore.
    The Sixth Commandment‘s, Ghosts‘ and Lead Balloon‘s Anna Crilly as butcher Anne Sanders.
    Bridgerton and The Bastard Son and the Devil Himself‘s Priya Kansara as nightclub dancer Lily Lee.
    Heartstopper‘s Ben Hope, aka Sebastian Croft as nightclub owner Silvio Salucci.
    The Newsreader and The Inheritance‘s Rory Fleck Byrne as returned soldier Luca Salucci.

    Dope Girls airs on BBC One and streams on BBC iPlayer.

    The post Dope Girls Cast: Meet the 1920s-Set BBC Drama&#8217, s Characters appeared first on Den of Geek.

  • Beware the Cut ‘n’ Paste Persona

    Beware the Cut ‘n’ Paste Persona

    This Person Does Not Exist is a website that generates human faces with a machine learning algorithm. It takes real portraits and recombines them into fake human faces. We recently scrolled past a LinkedIn post stating that this website could be useful “if you are developing a persona and looking for a photo.” 

    We agree: the computer-generated faces could be a great match for personas—but not for the reason you might think. Ironically, the website highlights the core issue of this very common design method: the person(a) does not exist. Like the pictures, personas are artificially made. Information is taken out of natural context and recombined into an isolated snapshot that’s detached from reality. 

    But strangely enough, designers use personas to inspire their design for the real world. 

    Personas: A step back

    Most designers have created, used, or come across personas at least once in their career. In their article “Personas – A Simple Introduction,” the Interaction Design Foundation defines personas as “fictional characters, which you create based upon your research in order to represent the different user types that might use your service, product, site, or brand.” In their most complete expression, personas typically consist of a name, profile picture, quotes, demographics, goals, needs, behavior in relation to a certain service/product, emotions, and motivations (for example, see Creative Companion’s Persona Core Poster). The purpose of personas, as stated by design agency Designit, is “to make the research relatable, [and] easy to communicate, digest, reference, and apply to product and service development.”

    The decontextualization of personas

    Personas are popular because they make “dry” research data more relatable, more human. However, this method constrains the researcher’s data analysis in such a way that the investigated users are removed from their unique contexts. As a result, personas don’t portray key factors that make you understand their decision-making process or allow you to relate to users’ thoughts and behavior; they lack stories. You understand what the persona did, but you don’t have the background to understand why. You end up with representations of users that are actually less human.

    This “decontextualization” we see in personas happens in four ways, which we’ll explain below. 

    Personas assume people are static 

    Although many companies still try to box in their employees and customers with outdated personality tests (referring to you, Myers-Briggs), here’s a painfully obvious truth: people are not a fixed set of features. You act, think, and feel differently according to the situations you experience. You appear different to different people; you might act friendly to some, rough to others. And you change your mind all the time about decisions you’ve taken. 

    Modern psychologists agree that while people generally behave according to certain patterns, it’s actually a combination of background and environment that determines how people act and take decisions. The context—the environment, the influence of other people, your mood, the entire history that led up to a situation—determines the kind of person you are in each specific moment. 

    In their attempt to simplify reality, personas do not take this variability into account; they present a user as a fixed set of features. Like personality tests, personas snatch people away from real life. Even worse, people are reduced to a label and categorized as “that kind of person” with no means to exercise their innate flexibility. This practice reinforces stereotypes, lowers diversity, and doesn’t reflect reality. 

    Personas focus on individuals, not the environment

    In the real world, you’re designing for a context, not for an individual. Each person lives in a family, a community, an ecosystem, where there are environmental, political, and social factors you need to consider. A design is never meant for a single user. Rather, you design for one or more particular contexts in which many people might use that product. Personas, however, show the user alone rather than describe how the user relates to the environment. 

    Would you always make the same decision over and over again? Maybe you’re a committed vegan but still decide to buy some meat when your relatives are coming over. As they depend on different situations and variables, your decisions—and behavior, opinions, and statements—are not absolute but highly contextual. The persona that “represents” you wouldn’t take into account this dependency, because it doesn’t specify the premises of your decisions. It doesn’t provide a justification of why you act the way you do. Personas enact the well-known bias called fundamental attribution error: explaining others’ behavior too much by their personality and too little by the situation.

    As mentioned by the Interaction Design Foundation, personas are usually placed in a scenario that’s a “specific context with a problem they want to or have to solve”—does that mean context actually is considered? Unfortunately, what often happens is that you take a fictional character and based on that fiction determine how this character might deal with a certain situation. This is made worse by the fact that you haven’t even fully investigated and understood the current context of the people your persona seeks to represent; so how could you possibly understand how they would act in new situations? 

    Personas are meaningless averages

    As mentioned in Shlomo Goltz’s introductory article on Smashing Magazine, “a persona is depicted as a specific person but is not a real individual; rather, it is synthesized from observations of many people.” A well-known critique to this aspect of personas is that the average person does not exist, as per the famous example of the USA Air Force designing planes based on the average of 140 of their pilots’ physical dimensions and not a single pilot actually fitting within that average seat. 

    The same limitation applies to mental aspects of people. Have you ever heard a famous person say, “They took what I said out of context! They used my words, but I didn’t mean it like that.” The celebrity’s statement was reported literally, but the reporter failed to explain the context around the statement and didn’t describe the non-verbal expressions. As a result, the intended meaning was lost. You do the same when you create personas: you collect somebody’s statement (or goal, or need, or emotion), of which the meaning can only be understood if you provide its own specific context, yet report it as an isolated finding. 

    But personas go a step further, extracting a decontextualized finding and joining it with another decontextualized finding from somebody else. The resulting set of findings often does not make sense: it’s unclear, or even contrasting, because it lacks the underlying reasons on why and how that finding has arisen. It lacks meaning. And the persona doesn’t give you the full background of the person(s) to uncover this meaning: you would need to dive into the raw data for each single persona item to find it. What, then, is the usefulness of the persona?

    The relatability of personas is deceiving

    To a certain extent, designers realize that a persona is a lifeless average. To overcome this, designers invent and add “relatable” details to personas to make them resemble real individuals. Nothing captures the absurdity of this better than a sentence by the Interaction Design Foundation: “Add a few fictional personal details to make the persona a realistic character.” In other words, you add non-realism in an attempt to create more realism. You deliberately obscure the fact that “John Doe” is an abstract representation of research findings; but wouldn’t it be much more responsible to emphasize that John is only an abstraction? If something is artificial, let’s present it as such.

    It’s the finishing touch of a persona’s decontextualization: after having assumed that people’s personalities are fixed, dismissed the importance of their environment, and hidden meaning by joining isolated, non-generalizable findings, designers invent new context to create (their own) meaning. In doing so, as with everything they create, they introduce a host of biases. As phrased by Designit, as designers we can “contextualize [the persona] based on our reality and experience. We create connections that are familiar to us.” This practice reinforces stereotypes, doesn’t reflect real-world diversity, and gets further away from people’s actual reality with every detail added. 

    To do good design research, we should report the reality “as-is” and make it relatable for our audience, so everyone can use their own empathy and develop their own interpretation and emotional response.

    Dynamic Selves: The alternative to personas

    If we shouldn’t use personas, what should we do instead? 

    Designit has proposed using Mindsets instead of personas. Each Mindset is a “spectrum of attitudes and emotional responses that different people have within the same context or life experience.” It challenges designers to not get fixated on a single user’s way of being. Unfortunately, while being a step in the right direction, this proposal doesn’t take into account that people are part of an environment that determines their personality, their behavior, and, yes, their mindset. Therefore, Mindsets are also not absolute but change in regard to the situation. The question remains, what determines a certain Mindset?

    Another alternative comes from Margaret P., author of the article “Kill Your Personas,” who has argued for replacing personas with persona spectrums that consist of a range of user abilities. For example, a visual impairment could be permanent (blindness), temporary (recovery from eye surgery), or situational (screen glare). Persona spectrums are highly useful for more inclusive and context-based design, as they’re based on the understanding that the context is the pattern, not the personality. Their limitation, however, is that they have a very functional take on users that misses the relatability of a real person taken from within a spectrum. 

    In developing an alternative to personas, we aim to transform the standard design process to be context-based. Contexts are generalizable and have patterns that we can identify, just like we tried to do previously with people. So how do we identify these patterns? How do we ensure truly context-based design? 

    Understand real individuals in multiple contexts

    Nothing is more relatable and inspiring than reality. Therefore, we have to understand real individuals in their multi-faceted contexts, and use this understanding to fuel our design. We refer to this approach as Dynamic Selves.

    Let’s take a look at what the approach looks like, based on an example of how one of us applied it in a recent project that researched habits of Italians around energy consumption. We drafted a design research plan aimed at investigating people’s attitudes toward energy consumption and sustainable behavior, with a focus on smart thermostats. 

    1. Choose the right sample

    When we argue against personas, we’re often challenged with quotes such as “Where are you going to find a single person that encapsulates all the information from one of these advanced personas[?]” The answer is simple: you don’t have to. You don’t need to have information about many people for your insights to be deep and meaningful. 

    In qualitative research, validity does not derive from quantity but from accurate sampling. You select the people that best represent the “population” you’re designing for. If this sample is chosen well, and you have understood the sampled people in sufficient depth, you’re able to infer how the rest of the population thinks and behaves. There’s no need to study seven Susans and five Yuriys; one of each will do. 

    Similarly, you don’t need to understand Susan in fifteen different contexts. Once you’ve seen her in a couple of diverse situations, you’ve understood the scheme of Susan’s response to different contexts. Not Susan as an atomic being but Susan in relation to the surrounding environment: how she might act, feel, and think in different situations. 

    Given that each person is representative of a part of the total population you’re researching, it becomes clear why each should be represented as an individual, as each already is an abstraction of a larger group of individuals in similar contexts. You don’t want abstractions of abstractions! These selected people need to be understood and shown in their full expression, remaining in their microcosmos—and if you want to identify patterns you can focus on identifying patterns in contexts.

    Yet the question remains: how do you select a representative sample? First of all, you have to consider what’s the target audience of the product or service you are designing: it might be useful to look at the company’s goals and strategy, the current customer base, and/or a possible future target audience. 

    In our example project, we were designing an application for those who own a smart thermostat. In the future, everyone could have a smart thermostat in their house. Right now, though, only early adopters own one. To build a significant sample, we needed to understand the reason why these early adopters became such. We therefore recruited by asking people why they had a smart thermostat and how they got it. There were those who had chosen to buy it, those who had been influenced by others to buy it, and those who had found it in their house. So we selected representatives of these three situations, from different age groups and geographical locations, with an equal balance of tech savvy and non-tech savvy participants. 

    2. Conduct your research

    After having chosen and recruited your sample, conduct your research using ethnographic methodologies. This will make your qualitative data rich with anecdotes and examples. In our example project, given COVID-19 restrictions, we converted an in-house ethnographic research effort into remote family interviews, conducted from home and accompanied by diary studies.

    To gain an in-depth understanding of attitudes and decision-making trade-offs, the research focus was not limited to the interviewee alone but deliberately included the whole family. Each interviewee would tell a story that would then become much more lively and precise with the corrections or additional details coming from wives, husbands, children, or sometimes even pets. We also focused on the relationships with other meaningful people (such as colleagues or distant family) and all the behaviors that resulted from those relationships. This wide research focus allowed us to shape a vivid mental image of dynamic situations with multiple actors. 

    It’s essential that the scope of the research remains broad enough to be able to include all possible actors. Therefore, it normally works best to define broad research areas with macro questions. Interviews are best set up in a semi-structured way, where follow-up questions will dive into topics mentioned spontaneously by the interviewee. This open-minded “plan to be surprised” will yield the most insightful findings. When we asked one of our participants how his family regulated the house temperature, he replied, “My wife has not installed the thermostat’s app—she uses WhatsApp instead. If she wants to turn on the heater and she is not home, she will text me. I am her thermostat.”

    3. Analysis: Create the Dynamic Selves

    During the research analysis, you start representing each individual with multiple Dynamic Selves, each “Self” representing one of the contexts you have investigated. The core of each Dynamic Self is a quote, which comes supported by a photo and a few relevant demographics that illustrate the wider context. The research findings themselves will show which demographics are relevant to show. In our case, as our research focused on families and their lifestyle to understand their needs for thermal regulation, the important demographics were family type, number and nature of houses owned, economic status, and technological maturity. (We also included the individual’s name and age, but they’re optional—we included them to ease the stakeholders’ transition from personas and be able to connect multiple actions and contexts to the same person).

    To capture exact quotes, interviews need to be video-recorded and notes need to be taken verbatim as much as possible. This is essential to the truthfulness of the several Selves of each participant. In the case of real-life ethnographic research, photos of the context and anonymized actors are essential to build realistic Selves. Ideally, these photos should come directly from field research, but an evocative and representative image will work, too, as long as it’s realistic and depicts meaningful actions that you associate with your participants. For example, one of our interviewees told us about his mountain home where he used to spend every weekend with his family. Therefore, we portrayed him hiking with his little daughter. 

    At the end of the research analysis, we displayed all of the Selves’ “cards” on a single canvas, categorized by activities. Each card displayed a situation, represented by a quote and a unique photo. All participants had multiple cards about themselves.

    4. Identify design opportunities

    Once you have collected all main quotes from the interview transcripts and diaries, and laid them all down as Self cards, you will see patterns emerge. These patterns will highlight the opportunity areas for new product creation, new functionalities, and new services—for new design. 

    In our example project, there was a particularly interesting insight around the concept of humidity. We realized that people don’t know what humidity is and why it is important to monitor it for health: an environment that’s too dry or too wet can cause respiratory problems or worsen existing ones. This highlighted a big opportunity for our client to educate users on this concept and become a health advisor.

    Benefits of Dynamic Selves

    When you use the Dynamic Selves approach in your research, you start to notice unique social relations, peculiar situations real people face and the actions that follow, and that people are surrounded by changing environments. In our thermostat project, we have come to know one of the participants, Davide, as a boyfriend, dog-lover, and tech enthusiast. 

    Davide is an individual we might have once reduced to a persona called “tech enthusiast.” But we can have tech enthusiasts who have families or are single, who are rich or poor. Their motivations and priorities when deciding to purchase a new thermostat can be opposite according to these different frames. 

    Once you have understood Davide in multiple situations, and for each situation have understood in sufficient depth the underlying reasons for his behavior, you’re able to generalize how he would act in another situation. You can use your understanding of him to infer what he would think and do in the contexts (or scenarios) that you design for.

    The Dynamic Selves approach aims to dismiss the conflicted dual purpose of personas—to summarize and empathize at the same time—by separating your research summary from the people you’re seeking to empathize with. This is important because our empathy for people is affected by scale: the bigger the group, the harder it is to feel empathy for others. We feel the strongest empathy for individuals we can personally relate to.  

    If you take a real person as inspiration for your design, you no longer need to create an artificial character. No more inventing details to make the character more “realistic,” no more unnecessary additional bias. It’s simply how this person is in real life. In fact, in our experience, personas quickly become nothing more than a name in our priority guides and prototype screens, as we all know that these characters don’t really exist. 

    Another powerful benefit of the Dynamic Selves approach is that it raises the stakes of your work: if you mess up your design, someone real, a person you and the team know and have met, is going to feel the consequences. It might stop you from taking shortcuts and will remind you to conduct daily checks on your designs.

    And finally, real people in their specific contexts are a better basis for anecdotal storytelling and therefore are more effective in persuasion. Documentation of real research is essential in achieving this result. It adds weight and urgency behind your design arguments: “When I met Alessandra, the conditions of her workplace struck me. Noise, bad ergonomics, lack of light, you name it. If we go for this functionality, I’m afraid we’re going to add complexity to her life.”

    Conclusion

    Designit mentioned in their article on Mindsets that “design thinking tools offer a shortcut to deal with reality’s complexities, but this process of simplification can sometimes flatten out people’s lives into a few general characteristics.” Unfortunately, personas have been culprits in a crime of oversimplification. They are unsuited to represent the complex nature of our users’ decision-making processes and don’t account for the fact that humans are immersed in contexts. 

    Design needs simplification but not generalization. You have to look at the research elements that stand out: the sentences that captured your attention, the images that struck you, the sounds that linger. Portray those, use them to describe the person in their multiple contexts. Both insights and people come with a context; they cannot be cut from that context because it would remove meaning. 

    It’s high time for design to move away from fiction, and embrace reality—in its messy, surprising, and unquantifiable beauty—as our guide and inspiration.

  • Voice Content and Usability

    Voice Content and Usability

    We’ve been conversing for many thousands of years. Whether to present information, perform transactions, or just to check in on one another, people have yammered aside, chattering and gesticulating, through spoken discussion for many generations. Only recently have we begun to write our conversations, and only recently have we outsourced them to the system, a system that exhibits a far greater affection for written communications than for the vernacular rigors of spoken speech.

    Computers have issues because conversation is more important than written speech, between spoken and written. To have productive conversations with us, machines may struggle with the messiness of mortal speech: the disfluencies and pauses, the gestures and body language, and the variations in word choice and spoken dialect that is stymie even the most carefully crafted human-computer interaction. Speaking language also has the advantage of face-to-face contact, which allows us to view visual social cues in the human-to-human scenario.

    In contrast, written language develops its own fossil record of dated terms and phrases as we commit to recording and keeping usages long after they are no longer relevant in spoken communication ( for example, the salutation” To whom it may concern” ). Because it tends to be more consistent, smooth, and proper, written word is necessarily far easier for devices to interpret and know.

    This pleasure is not available in spoken speech. There are verbal cues and outspoken behaviors that mimic conversation in complex ways, including how something is said, never what. These are the nonverbal cues that ornament conversations with emphasis and emotional context. Whether rapid-fire, low-pitched, or high-decibel, whether satirical, awkward, or groaning, our spoken speech conveys much more than the written word had ever muster. As designers and content planners, we face significant challenges when it comes to tone interfaces, the machines with which we speak.

    Voice-to-voice relationships

    We interact with voice interfaces for a variety of reasons, but according to Michael McTear, Zoraida Callejas, and David Griol in The Conversational Interface, those motivations by and large mirror the reasons we initiate conversations with other people, too ( ). We typically strike up a dialogue as a result:

    • we require something ( such as a transaction ),
    • we want to know something ( information of some sort ), or
    • We are sociable creatures, and we need a talk partner.

    These three categories, which I refer to as interpersonal, technical, and prosocial, also apply to virtually every voice interaction: a solitary conversation that begins with the voice interface’s initial greeting and ends with the user leaving the interface. Notice here that a conversation in our individual sense—a chat between people that leads to some result and lasts an arbitrary length of time—could encompass many interpersonal, technical, and interpersonal voice interactions in succession. In other words, a voice interaction is a conversation, but it is not always just one voice interaction.

    Most voice interfaces are more gimmicky than captivating in pure prosocial conversations because most people find it difficult to trust their machines to actually understand how we’re doing and to give them the kind of glad-handing we crave. There’s also ongoing debate as to whether users actually prefer the sort of organic human conversation that begins with a prosocial voice interaction and shifts seamlessly into other types. In fact, Michael Cohen, James Giangola, and Jennifer Balogh advise sticking to user expectations by imitating how they interact with other voice interfaces rather than trying too hard to be human, which could lead to alienation of them ( ).

    That leaves two different types of conversations we can have with one another that a voice interface can also have easily, including one that is transactional and one that is informational, teaching us something new ( “discuss a musical” ).

    Transactional voice interactions

    When you order a Hawaiian pizza with extra pineapple, you’re typically having a conversation and a voice interaction when you’re tapping buttons on a food delivery app. The conversation quickly shifts from a brief smattering of neighborly small talk to ordering a pizza ( generously topped with pineapple, as it should be ) when we walk up to the counter and place an order.

    Alison: Hey, how’s it going?

    Burhan: Hello and welcome to Crust Deluxe! It’s chilly outside. How can I help you?

    Can I get a Hawaiian pizza with extra pineapple, Alison?

    Burhan: Yes, but what size?

    Alison: Large.

    Burhan: Anything else?

    Alison: No, that’s it.

    Burhan: Something to drink?

    Alison: I’ll have a bottle of Coke.

    Burhan, you know what. That’ll be$ 13.55 and about fifteen minutes.

    A service rendered or a product delivered, as each incremental disclosure in this transactional conversation reveals more and more of the desired transactional outcome. Conversations that are transactional have certain characteristics: they are direct, precise, and cost-effective. They quickly dispense with pleasantries.

    Informational voice interactions

    In the meantime, some conversations are primarily about getting information. Though Alison might visit Crust Deluxe with the sole purpose of placing an order, she might not actually want to walk out with a pizza at all. She might be interested in trying kosher or halal dishes, trying gluten-free dishes, or something else entirely. Even though we have a prosocial mini-conversation once more at the beginning to establish politeness, we’re after much more.

    Alison: Hey, how’s it going?

    Burhan: Hello and welcome to Crust Deluxe! It’s chilly outside. How can I help you?

    Alison: Can I ask a few questions?

    Burhan: Of course! Continue straight ahead.

    Alison: Do you have any halal options on the menu?

    Burhan: Absolutely! On request, we can make any pie halal. We also have lots of vegetarian, ovo-lacto, and vegan options. Are you considering any additional dietary restrictions?

    Alison: What about pizzas that are gluten-free?

    Burhan: We can definitely do a gluten-free crust for you, no problem, for both our deep-dish and thin-crust pizzas. Anything else I can say to you to help?

    Alison: That’s it for now. Good to know. Thank you!

    Burhan: Anytime, please.

    This is a very different dialogue. Here, the goal is to obtain a particular set of facts. Informational conversations are research expeditions to gather data, news, or facts in search of the truth. Voice interactions that are informational might be more long-winded than transactional conversations by necessity. In order for the customer to understand the key takeaways, responses are typically longer, more in-depth, and carefully communicated.

    Voice-to-text interfaces

    At their core, voice interfaces employ speech to support users in reaching their goals. However, just because an interface has a voice component doesn’t mean that every user interaction with it is mediated through voice. We’re most concerned in this book with pure voice interfaces because multimodal voice interfaces can lean on visual components like screens as crutches, which are completely dependent on spoken conversation and lack any visual component, making them much more nuanced and challenging to deal with.

    Though voice interfaces have long been integral to the imagined future of humanity in science fiction, only recently have those lofty visions become fully realized in genuine voice interfaces.

    IVR ( interactive voice response ) systems

    Written conversational interfaces have been a part of computing for many decades, but voice interfaces first started to appear in the early 1990s with text-to-speech ( TTS ) dictation programs that recited written text aloud as well as speech-enabled in-car systems that gave directions to a user-provided address. With the advent of interactive voice response ( IVR ) systems, intended as an alternative to overburdened customer service representatives, we became acquainted with the first true voice interfaces that engaged in authentic conversation.

    IVR systems made it easier for businesses to cut down on call centers, but they soon gained notoriety for their clunkiness. Similar to the corporate world, these systems were primarily created as metaphorical switchboards to direct customers to a real phone agent (” Say Reservations to book a flight or check an itinerary” ), and chances are you’ll have a conversation with one when you call an airline or hotel conglomerate. Despite their functional issues and users ‘ frustration with their inability to speak to an actual human right away, IVR systems proliferated in the early 1990s across a variety of industries (, PDF).

    IVR systems have a reputation for having less scintillating conversation than we’re used to in real life ( or even in science fiction ), but they are great for highly repetitive, monotonous conversations that typically don’t veer from a single format.

    Readers of screens

    Parallel to the evolution of IVR systems was the invention of the screen reader, a tool that transcribes visual content into synthesized speech. For Blind or visually impaired website users, it’s the predominant method of interacting with text, multimedia, or form elements. Readers of screens represent perhaps the closest equivalent we have today to an out-of-the-box implementation of content delivered through voice.

    Among the first screen readers known by that moniker was the Screen Reader for the BBC Micro and NEEC Portable developed by the Research Centre for the Education of the Visually Handicapped (RCEVH) at the University of Birmingham in 1986 ( ). The first IBM Screen Reader for text-based computers was created by Jim Thatcher in the same year, which was later recreated for computers with graphical user interfaces ( GUIs ) ( ).

    With the rapid expansion of the web in the 1990s, there was an explosion in the demand for user-friendly tools. Thanks to the introduction of semantic HTML and especially ARIA roles beginning in 2008, screen readers started facilitating speedy interactions with web pages that ostensibly allow disabled users to traverse the page as an aural and temporal space rather than a visual and physical one. In other words, screen readers for the web “provide mechanisms that translate visual design constructs—proximity, proportion, etc. —into useful information,” according to Aaron Gustafson in A List Apart. ” At least they do when documents are authored thoughtfully” ( ).

    Although incredibly instructive for voice interface designers, screen readers have a major flaw: they’re challenging to use and consistently verbose. Sometimes awkward pronouncements that name every manipulable HTML element and announce every formatting change are made because the visual structures of websites and web navigation don’t translate well to screen readers. For many screen reader users, working with web-based interfaces exacts a cognitive toll.

    Chris Maury, an advocate for voice quality and voice engineer, examines why the screen reader experience is not appropriate for users who rely on voice in Wired:

    I hated the way Screen Readers operated from the beginning. Why are they designed the way they are? It makes no sense to present information visually and then only to have that information translated into audio. All the time and effort put into creating the ideal user experience for an app is wasted, or worse, it has a negative effect on blind users ‘ experience. ( ) _ _ _

    Well-designed voice interfaces can often be more effective than long-winded screen reader monologues in guiding users to their destination. After all, users of the visual interface have the advantage of freely scurrying around the viewport to find information without worrying about it. Blind users, meanwhile, are obligated to listen to every utterance synthesized into speech and therefore prize brevity and efficiency. Users with disabilities who have long had no choice but to use clumsy screen readers might find that voice interfaces, especially more contemporary voice assistants, provide a more streamlined experience.

    Voice-overseers are

    When we think of voice assistants (the subset of voice interfaces now commonplace in living rooms, smart homes, and offices), many of us immediately picture HAL from 2001: A Space Odyssey or hear Majel Barrett’s voice as the omniscient computer in Star Trek. Voice-overseers are are akin to personal concierges that can answer questions, schedule appointments, conduct searches, and perform other common day-to-day tasks. And they’re rapidly gaining more attention from accessibility advocates for their assistive potential.

    Before the earliest IVR systems found success in the enterprise, Apple published a demonstration video in 1987 depicting the Knowledge Navigator, a voice assistant that could transcribe spoken words and recognize human speech to a great degree of accuracy. Then, in 2001, Tim Berners-Lee and others created their vision for a Semantic Web “agent” that would carry out routine tasks like” checking calendars, making appointments, and finding locations” (, behind paywall ). Apple’s Siri finally made voice assistants a reality for consumers until 2011 when they were available.

    Thanks to the plethora of voice assistants available today, there is considerable variation in how programmable and customizable certain voice assistants are over others ( Fig 1.1 ). At one extreme, everything but vendor-provided features are locked down. For instance, when Apple’s Siri and Microsoft’s Cortana were released, they couldn’t extend their existing capabilities. There are no other means by which developers can interact with Siri at a low level, aside from predefined categories of tasks like sending messages, hailing rideshares, making restaurant reservations, and other things, which are still unavoidable today.

    At the opposite end of the spectrum, voice assistants like Amazon Alexa and Google Home offer a core foundation on which developers can build custom voice interfaces. For this reason, developers who feel stifled by the limitations of Siri and Cortana are increasingly using programmable voice assistants that are capable of customization and extensibility. Google Home enables the programming of arbitrary Google Assistant skills, while Amazon offers the Alexa Skills Kit, a developer framework for creating custom voice interfaces for Amazon Alexa. Today, users can choose from among thousands of custom-built skills within both the Amazon Alexa and Google Assistant ecosystems.

    As businesses like Amazon, Apple, Microsoft, and Google continue to occupy their positions, they’re also selling and open-sourcing an unheard array of tools and frameworks for designers and developers that aim to make creating voice interfaces as simple as possible, even without code.

    Often by necessity, voice assistants like Amazon Alexa tend to be monochannel—they’re tightly coupled to a device and can’t be accessed on a computer or smartphone instead. In contrast, many development platforms, such as Google’s Dialogflow, have omnichannel capabilities that allow users to create a single conversational interface that then becomes a voice interface, textual chatbot, and IVR system upon deployment. In Chapter 4, we’ll explore some of the possible effects these variables might have on how you build out your design artifacts, but I don’t recommend any particular implementation strategies in this design-focused book.

    Voice Content

    Simply put, voice content is voice-transmitted content. Voice content must be free-flowing and organic, contextless and concise—everything written content isn’t enough to preserve what makes human conversation so compelling in the first place.

    Our world is replete with voice content in various forms: screen readers reciting website content, voice assistants rattling off a weather forecast, and automated phone hotline responses governed by IVR systems. We’re most concerned with the content in this book being delivered auditorically, not as an option but as a necessity.

    Our initial foray into informational voice interfaces will likely be to provide user content, for many of us. There’s only one problem: any content we already have isn’t in any way ready for this new habitat. How can we improve the conversational content on our websites? And how do we create fresh copy that works with voice movements?

    Lately, we’ve begun slicing and dicing our content in unprecedented ways. Websites are, in many ways, massive vaults of what I call macrocontent: lengthy prose that can last for miles in a browser window while extending like microfilm viewers of newspaper archives. Microcontent was defined as permalinked pieces of content that stay legible regardless of the environment, such as email or text messages back in 2002, well before the present-day ubiquity of voice assistants.

    A day’s weather forcast]sic], the arrival and departure times for an airplane flight, an abstract from a long publication, or a single instant message can all be examples of microcontent. ( ) _ _ _

    I would update Dash’s definition of microcontent to include all instances of bite-sized content that transcends written communiqués. After all, today we encounter microcontent in interfaces where a small snippet of copy is displayed alone, unmoored from the browser, like a textbot confirmation of a restaurant reservation. The best way to learn how to stretch your content to the limits of its potential is through microcontent, which will inform both established and new delivery methods.

    Voice content stands out as being unique because it illustrates how content is experienced in space as opposed to time. We can glance at a digital sign underground for an instant and know when the next train is arriving, but voice interfaces hold our attention captive for periods of time that we can’t easily escape or skip, something screen reader users are all too familiar with.

    We need to make sure that our microcontent truly performs well as voice content because it is essentially composed of isolated blobs without any connection to the channels in which they will eventually end up. This means focusing on the two most crucial characteristics of robust voice content: voice content legibility and voice content discoverability.

    Our voice content’s legibility and discoverability in general both depend on how it manifests in terms of perceived space and time.