Blog

However, we’re still very far from this best.

At the time, I didn’t realize yet how to functionally incorporate morality. Yes, I did discover some tools in other jobs that had worked well for me, such as using checklists, premise monitoring, and “dark truth” sessions. I was still struggling for time and support, and at best I had only partially achieved a higher ( moral ) quality of design—which is far from my definition of structurally integrated.

I made a deeper investigation into the main causes of business that prevent us from practicing regular honest style. Today, after much research and experimentation, I believe that I’ve found the code that will let us functionally combine morality. And it’s amazingly easy! However, we must first move out to understand what we’re up against.

Control the structure

Unfortunately, the capitalist system, which promotes consumerism and injustice, is obsessed with the utopian dream of infinite growth. Sea levels, temperature, and our demand for energy continue to rise unquestioned, while the divide between rich and poor continues to increase. Owners expect ever-higher returns on their investments, and firms feel forced to set short-term goals that reflect this. Over the past few decades, those goals have transformed our well-meaning human-centered mentality into a potent tool that encourages ever-higher levels of consumption. When we’re working for an organization that pursues “double-digit growth” or “aggressive sales targets” ( which is 99 percent of us ), that’s very hard to resist while remaining human friendly. We’re a part of the problem, despite our best efforts and the fact that we like to claim that we provide solutions for people.

What can we do to alter this?

We may start by acting on the appropriate level of the system. A method thinker named Donna H. Meadows after outlined ways to influence a system in terms of effectiveness. When you apply these to style, you get:

You can change things like usability ratings or the number of style critiques at the least effective level. But none of that may change the direction of a business.
• Similarly, affecting buffers ( such as team budgets ), stocks ( such as the number of designers ), flows ( such as the number of new hires ), and delays ( such as the time that it takes to hear about the effect of design ) won’t significantly affect a company.
• Instead of focusing on feedback loops like control power, employee reputation, or design-system investments, a company can become more effective at achieving its goals. But that doesn’t alter the goals themselves, which means that the business will also work against your ethical-design ideals.
• Most ethical-design efforts’ current focus is on the exchange of moral techniques, toolkits, articles, conferences, workshops, and other topics. This is also where social style has remained largely theoretical. We’ve been focusing on the wrong level of the system all this day.
• Consider rules, for instance; they consistently surpass information. There can be commonly accepted guidelines, such as how fund works, or a sprint group’s concept of done. However, illegal laws intended to maintain profits is also smother social design, which are frequently revealed through statements like” the customer didn’t ask for it” or “don’t make it very big.”
• Changing the rules without holding official energy is extremely difficult. That’s why the next stage is so significant: self-organization. Research, bottom-up initiatives, love projects, self-steering teams, and other such self-organization techniques all contribute to the resilience and creativity of a business. It’s precisely this diversity of viewpoints that’s needed to functionally address major structural issues like consumerism, wealth inequality, and climate change.
• But objectives and metrics are even more powerful than self-organization. Our companies want to make more money, which means that everything and everyone in the company does their best to… make the company more money. And once I realized that profit is nothing more than a measurement, I understood how crucial a very specific, defined metric can be toward pushing a company in a certain direction.

What is the conclusion? If we truly want to incorporate ethics into our daily design practice, we must first change the measurable objectives of the company we work for, from the bottom up.

Redefine success

Traditionally, we consider a product or service successful if it’s desirable to humans, technologically feasible, and financially viable. You tend to see these represented as equals, if you type the three words in a search engine, you’ll find diagrams of three equally sized, evenly arranged circles.

However, we all know that the three dimensions are not equally important: viability is ultimately what determines whether a product will become functional. So a more realistic representation might look like this:

Viability is the aim, while feasibility and desire are the means. Companies—outside of nonprofits and charities—exist to make money.

A genuinely purpose-driven company would try to reverse this dynamic: it would recognize finance for what it was intended for: a means. Therefore, both the company’s goals and its viability are important in order to realize what they are trying to accomplish. It makes intuitive sense: to achieve most anything, you need resources, people, and money. Fun fact: the Italian language does not distinguish between viability and feasibility; both are merely fattibilità.

But simply swapping viable for desirable isn’t enough to achieve an ethical outcome. Desirability is still linked to consumerism because the associated activities aim to identify what people want—whether it’s good for them or not. When it comes to a product’s desirability goals, such as user satisfaction or conversion, don’t take into account whether it is good for people. They don’t prevent us from creating products that distract or manipulate people or stop us from contributing to society’s wealth inequality. They are ineffective for maintaining a healthy relationship with nature.

There’s a fourth dimension of success that’s missing: our designs also need to be ethical in the effect that they have on the world.

This is hardly a new idea. There are many variations of these models, some calling the fourth dimension accountability, integrity, or responsibility. What I’ve never seen before, however, is the necessary step that comes after: to influence the system as designers and to make ethical design more practical, we must create objectives for ethical design that are achievable and inspirational. There is no single way to accomplish this because it depends greatly on your country’s values, culture, and industry. But I’ll give you the version that I developed with a group of colleagues at a design agency. Consider it a template to get started.

Ensure social justice, equity, and sustainability.

We created objectives that address design’s effect on three levels: individual, societal, and global.

An objective on the individual level teaches us that success transcends the typical area of focus on usability and satisfaction, taking into account factors like how much time and effort are required from users. We pursued well-being:

We create products and services that allow for people’s health and happiness. Our solutions are non-misleading, transparent, non-addictive, and non-misleading. We respect our users ‘ time, attention, and privacy, and help them make healthy and respectful choices.

A societal goal requires us to consider our impact beyond the mere user, widening our focus to the economy, communities, and other involuntary parties. We called this objective equity:

We create products and services that have a positive social impact. We think of racial justice, inclusiveness and diversity of people as teams, users, and customer segments, as well as racial justice and economic equality. We listen to local culture, communities, and those we affect.

Finally, the global goal on the global level aims to keep us in harmony with our only true home, humanity. Referring to it simply as sustainability, our definition was:

We create products and services that reward sufficiency and reusability. Our products are repurposed, given, and given priority to making sustainable choices in order to support the circular economy. We deliver functionality instead of ownership, and we limit energy use.

In essence, ethical design ( to us ) meant achieving well-being for each user and an equitable value distribution within society through a design that can sustain our living planet. When we introduced these objectives in the company, for many colleagues, design ethics and responsible design suddenly became tangible and achievable through practical—and even familiar—actions.

Measure impact

However, defining these goals is still insufficient. What truly caught the attention of senior management was the fact that we created a way to measure every design project’s well-being, equity, and sustainability.

In this overview, you can use examples of metrics to measure your progress toward equity, well-being, and sustainability:

There’s a lot of power in measurement. As the saying goes, what gets measured gets done. This example was once shared by Donella Meadows:

” If the desired system state is national security, and that is defined as the amount of money spent on the military, the system will produce military spending. It may or may not lead to national security.

This phenomenon explains why desirability is a poor indicator of success: it’s typically defined as the increase in customer satisfaction, session length, frequency of use, conversion rate, churn rate, download rate, and so on. But none of these metrics increase the health of people, communities, or ecosystems. What if we instead used ( reduced ) screen time or software energy consumption to measure success?

There’s another important message here. Even if we set an objective to create a calm interface, we might end up with a screen that makes you anxious if we were to pick the wrong metric for calmness, such as the number of interface elements. Choosing the wrong metric can completely undo good intentions.

Additionally, choosing the right metric is enormously helpful in focusing the design team. When you perform the task of selecting metrics for our goals, you are made to consider what success looks like in terms of words and how you can demonstrate that you have met your ethical goals. It also forces you to consider what we as designers have control over: what can I include in my design or change in my process that will lead to the right type of success? The response to this query provides a lot of insight and clarity.

And finally, it’s good to remember that traditional businesses run on measurements, and managers love to spend much time discussing charts ( ideally hockey-stick shaped ) —especially if they concern profit, the one-above-all of metrics. For good or ill, to improve the system, to have a serious discussion about ethical design with managers, we’ll need to speak that business language.

Practice daily ethical design

Once you’ve defined your objectives and you have a reasonable idea of the potential metrics for your design project, only then do you have a chance to structurally practice ethical design. It” simply” becomes a matter of using your imagination and sifting through the knowledge and tools that are already at your disposal.

I think this is quite exciting! It opens a whole new set of challenges and considerations for the design process. Would a simple illustration suffice, or should you go with that energizing video? Which typeface is the most calm and inclusive? What fresh techniques and tools do you employ? When is the website’s end of life? How can you provide the same service while requiring less attention from users? How can you ensure that those who are affected by decisions are present when they are made? How can you measure our effects?

The definition of success will fundamentally alter what doing good design entails.

There is, however, a final piece of the puzzle that’s missing: convincing your client, product owner, or manager to be mindful of well-being, equity, and sustainability. For this, it’s essential to engage stakeholders in a dedicated kickoff session.

Kick it off or return to the pre-existing situation.

The kickoff is the most important meeting that can be so easy to forget to include. There are two main stages in it: 1 ) coordinating expectations; 2 ) defining success as a goal.

In the first phase, the entire ( design ) team goes over the project brief and meets with all the relevant stakeholders. Everyone gets to know one another and express their expectations on the outcome and their contributions to achieving it. Possumptions are raised and discussed. The aim is to get on the same level of understanding and to in turn avoid preventable miscommunications and surprises later in the project.

For instance, we had an online kickoff meeting with the client, a subject matter expert, and two other designers for a recent freelance project that aimed to create a digital platform that facilitates the documentation and communication of US student advisors. We used a combination of canvases on Miro: one with questions from” Manual of Me” ( to get to know each other ), a Team Canvas ( to express expectations ), and a version of the Project Canvas to align on scope, timeline, and other practical matters.

The above is the traditional purpose of a kickoff. However, agreeing on the project’s success means expressing expectations just as crucial as expressing expectations in terms of desire, viability, feasibility, and ethics. What are the objectives in each dimension?

It’s crucial to reach an understanding of what success means at this early stage because you can depend on it for the duration of the project. If, for example, the design team wants to build an inclusive app for a diverse user group, they can raise diversity as a specific success criterion during the kickoff. If the client agrees, the team can refer back to that promise throughout the project. As we agreed in our first meeting, having a diverse user group that includes A and B is essential to creating a successful product. So we do activity X and follow research process Y”. Compare those odds to a scenario where the team had to request permission halfway through the project and didn’t agree to it in advance. The client might argue that that came on top of the agreed scope—and she’d be right.

In the case of this freelance project, to define success I prepared a round canvas that I call the Wheel of Success. An inner ring with the intention of capturing ideas for objectives and an outer ring with the intention of capturing ideas for measuring those objectives are included. The rings are divided into five dimensions of successful design: healthy, equitable, sustainable, desirable, feasible, and viable.

We explored each dimension and recorded ideas on digital sticky notes. Then we discussed our ideas and verbally agreed on the most important ones. For example, our client agreed that sustainability and progressive enhancement are important success criteria for the platform. Additionally, the subject-matter expert stressed the importance of including students from underprivileged and low-income groups in the design process.

After the kickoff, we summarized our ideas and shared understanding in a project brief that captured these aspects:

the project’s history and purpose: Why do we work on this project?
• the problem definition: what do we want to solve?
• the concrete goals and metrics for each success dimension: what do we want to achieve?
• how will we go about defining the scope, process, and role descriptions?

With such a brief in place, you can use the agreed-upon objectives and concrete metrics as a checklist of success, and your design team will be ready to pursue the right objective—using the tools, methods, and metrics at their disposal to achieve ethical outcomes.

Conclusion

A number of my coworkers have questioned me over the past year,” Where do I begin with ethical design?” My answer has always been the same: organize a session with your stakeholders to ( re ) define success. Even though you might not always be 100 percent successful in agreeing on goals that cover all responsibility objectives, that beats the alternative ( the status quo ) every time. There is no skipping this step if you want to be an ethical, responsible designer.

To be even more specific: if you consider yourself a strategic designer, your challenge is to define ethical objectives, set the right metrics, and conduct those kick-off sessions. If you think of yourself as a system designer, you need to understand how your industry influences consumerism and inequality, how finance drives business, and how to think creatively about how to use the most powerful tools to influence the system. Then redefine success to create the space to exercise those levers.

And for those who consider themselves service designers or UX designers or UI designers: if you truly want to have a positive, meaningful impact, stay away from the toolkits and meetups and conferences for a while. Gather your coworkers and set design goals for well-being, equity, and sustainability. Engage your stakeholders in a workshop and challenge them to think of ways to achieve and measure those ethical goals. Take their ideas, make them clear and tangible, ask for their consent, and hold them to it.

Otherwise, I’m genuinely sorry to say, you’re wasting your precious time and creative energy.

Of course, engaging your stakeholders in this way can be uncomfortable. Many of my coworkers had questions to ask, such as” Will they take this seriously?” and “Can’t we just do it within the design team instead”? In fact, a product manager once asked me why ethics couldn’t just be a structured part of the design process—to just do it without spending the effort to define ethical objectives. It’s a tempting thought, isn’t it? We wouldn’t have to have difficult discussions with stakeholders about what values or which key-performance indicators to pursue. It would let us focus on what we like and do best: designing.

However, as systems theory suggests, that’s not enough. For those of us who aren’t from marginalized groups and have the privilege to be able to speak up and be heard, that uncomfortable space is exactly where we need to be if we truly want to make a difference. We can’t continue to live in the design-for-designers bubble and enjoy our privileged working-from-home environment without access to the real world. For those of us who have the possibility to speak up and be heard: if we solely keep talking about ethical design and it remains at the level of articles and toolkits—we’re not designing ethically. It’s just theory. By challenging them to redefine success in business, we must actively engage with our coworkers and clients.

With a bit of courage, determination, and focus, we can break out of this cage that finance and business-as-usual have built around us and become facilitators of a new type of business that can see beyond financial value. We simply need to come to terms with the right goals at the start of each design project, identify the appropriate metrics, and acknowledge that we already have everything in place to begin. That’s what it means to do daily ethical design.

For their inspiration and support over the years, I would like to thank Emanuela Cozzi Schettini, José Gallegos, Annegret Bönemann, Ian Dorr, Vera Rademaker, Virginia Rispoli, Cecilia Scolaro, Rouzbeh Amini, and many others.

The mobile-first style approach is fantastic because it concentrates on what is most important to the consumer, it’s well-practiced, and it’s a well-known layout design for years. But developing your CSS mobile-first should also be fantastic, too…right?

Well, not necessarily. Classic mobile-first CSS development is based on the principle of overwriting style declarations: you begin your CSS with default style declarations, and overwrite and/or add new styles as you add breakpoints with min-width media queries for larger viewports (for a good overview see “What is Mobile First CSS and Why Does It Rock?”). But all those exceptions create complexity and inefficiency, which in turn can lead to an increased testing effort and a code base that’s harder to maintain. Admit it—how many of us willingly want that?

Mobile-first CSS may yet be the best option for your own projects, but you need to first determine how acceptable it is in light of the physical design and user interactions you’re trying to create. To help you get started, here’s how I go about tackling the elements you need to watch for, and I’ll discuss some alternative remedies if mobile-first doesn’t seem to fit your job.

benefits of mobile-first technology

Some of the benefits of mobile-first CSS growth, and why it’s been the de facto growth strategy for so long, make a lot of sense:

Development order. A good development hierarchy is something you can definitely expect from mobile-first; you simply concentrate on the mobile view and start developing.

tested and verified. It’s a tried and tested technique that’s worked for years for a cause: it solves a problem actually also.

prioritizes the smart see. The mobile view is the simplest and arguably the most significant because it covers all the crucial user journeys and frequently accounts for a higher proportion of user visits ( depending on the project ) ).

Prevents desktop-centric growth. It can be tempting to first focus on the desktop perspective because desktop computers are used for growth. No one wants to spend their time retrofitting a desktop-centric website to function on mobile devices, but thinking about smart from the beginning prevents us from getting stuck in the future!

Drawbacks of mobile-first

Model declarations can be set at higher breakpoints and therefore overwritten at higher breakpoints:

more complicated. The farther up the target order you go, the more unnecessary password you inherit from lower thresholds.

higher CSS sensitivity A school name declaration with a restored default value for a style has a higher specificity today. This can be a pain on big projects when you want to preserve the CSS candidates as simple as possible.

Requires more analysis tests. All higher thresholds must be regression tested if changes to CSS at a lower see ( such as adding a new style ) are to be made.

The browser can’t prioritize CSS downloads. At wider breakpoints, classic mobile-first min-width media queries don’t leverage the browser’s capability to download CSS files in priority order.

Property price issue overrules its own.

There is nothing intrinsically wrong with overwriting principles, CSS was designed to do just that. Even so, inheriting wrong values can be laborious and ineffective. When you need to replace styles to restore them to their defaults, which may cause issues after, especially if you’re using a combination of bespoke CSS and power classes, does this also lead to more style specificity. We won’t be able to use a power course for a design that has been restore with a higher precision.

With this in mind, I’m developing CSS with a focus on the default values much more these days. Since there’s no specific order, and no chains of specific values to keep track of, this frees me to develop breakpoints simultaneously. I concentrate on finding common styles and isolating the specific exceptions in closed media query ranges (that is, any range with a max-width set). 

As you can view each target as a clean slate, this strategy opens up some opportunities. It’s acceptable and can be coded in the default style plate if a product’s layout appears to be based on Flexbox at all thresholds. But if it looks like Grid would be much better for large windows and Flexbox for portable, these can both be done entirely freely when the CSS is put into finished media keyword ranges. Additionally, developing simultaneously requires you to have a thorough understanding of any given component in all breakpoints right away. This can help identify issues with the design more quickly in the development process. We don’t want to get stuck down a rabbit hole building a complex component for mobile, and then get the designs for desktop and find they are equally complex and incompatible with the HTML we created for the mobile view!

I encourage you to try this method, even though it won’t work for everyone. There are plenty of resources available to support concurrent development, including Responsively App, Blisk, and many others.

Having said that, I don’t feel the order itself is particularly relevant. If you like to work on one device at a time, are comfortable with focusing on the mobile view, and are familiar with the requirements for other breakpoints, then you should definitely follow the classic development order. The key is to find common styles and exceptions so that you can include them in the appropriate stylesheet, which is a kind of manual tree-shaking procedure! Personally, I find this a little easier when working on a component across breakpoints, but that’s by no means a requirement.

In practice, closed media query ranges

We overwrite the styles in the classic mobile-first CSS, but we can prevent this by using media query ranges. To illustrate the difference ( I’m using SCSS for brevity ), let’s assume there are three visual designs:

• smaller than 768
• from 768 to less than 1024
• 1024 and anything larger

Take a simple example where a block-level element has a default padding of “20px,” which is overwritten at tablet to be “40px” and set back to “20px” on desktop.

.my-block { padding: 20px; @media (min-width: 768px) { padding: 40px; } @media (min-width: 1024px) { padding: 20px; }}

.my-block { padding: 20px; @media (min-width: 768px) and (max-width: 1023.98px) { padding: 40px; }}

The subtle difference is that the mobile-first example sets the default padding to “20px” and then overwrites it at each breakpoint, setting it three times in total. In contrast, the second example sets the default padding to “20px” and only overrides it at the relevant breakpoint where it isn’t the default value (in this instance, tablet is the exception).

The goal is to: 

• Only set styles when needed. 
• Not set them with the expectation of overwriting them later on, again and again. 

To this end, closed media query ranges are our best friend. If we need to make a change to any given view, we make it in the CSS media query range that applies to the specific breakpoint. We’ll be much less likely to introduce unwanted alterations, and our regression testing only needs to focus on the breakpoint we have actually edited. 

Taking the above example, if we find that .my-block spacing on desktop is already accounted for by the margin at that breakpoint, and since we want to remove the padding altogether, we could do this by setting the mobile padding in a closed media query range.

.my-block {  @media (max-width: 767.98px) {    padding: 20px;  }  @media (min-width: 768px) and (max-width: 1023.98px) {    padding: 40px;  }}

The browser default padding for our block is “0,” so instead of adding a desktop media query and using unset or “0” for the padding value (which we would need with mobile-first), we can wrap the mobile padding in a closed media query (since it is now also an exception) so it won’t get picked up at wider breakpoints. At the desktop breakpoint, we won’t need to set any padding style, as we want the browser default value.

Bundling versus separating the CSS

Back in the day, keeping the number of requests to a minimum was very important because the browser's concurrent requests limit (typically around six ) was high. In consequence, using image sprites and CSS bundling was the norm, with all the CSS being downloaded as a single stylesheet with the highest priority.

With HTTP/2 and HTTP/3 now on the scene, the number of requests is no longer the big deal it used to be. By using a media query, we can separate the CSS into several files. The obvious benefit of this is that the browser can now request the CSS it currently requires with a higher priority than the CSS it doesn't. This is more performant and can reduce the overall time page rendering is blocked.

What version of HTTP do you use?

Go to your website and open your browser's dev tools to find out which version of HTTP you're using. Next, select the Network tab and make sure the Protocol column is visible. If "h2" is included in the protocol list, that indicates that HTTP/2 is being used.

Note: To check the Protocol column in your browser's dev tools, right-click any column header ( such as Name ), go to the Network tab, reload your page, and then check the Protocol column.

Also, if your website is still using HTTP/1... WHY?! What are you waiting for? Excellent user support exists for HTTP/2.

splitting the CSS

Separating the CSS into individual files is a worthwhile task. Linking the separate CSS files using the relevant media attribute allows the browser to identify which files are needed immediately (because they’re render-blocking) and which can be deferred. Based on this, it allocates each file an appropriate priority.

In the following example of a website visited on a mobile breakpoint, we can see the mobile and default CSS are loaded with" Highest" priority, as they are currently needed to render the page. The last three CSS files ( print, tablet, and desktop ) are still being downloaded in case they're needed later, but with" Lowest" priority.

Before rendering can begin, the browser will need to download and parse the CSS file when using bundled CSS.

While, as noted, with the CSS separated into different files linked and marked up with the relevant media attribute, the browser can prioritize the files it currently needs. Using closed media query ranges allows the browser to do this at all widths, as opposed to classic mobile-first min-width queries, where the desktop browser would have to download all the CSS with Highest priority. We can’t assume that desktop users always have a fast connection. For instance, in many rural areas, internet connection speeds are still slow. 

Depending on project requirements, the media queries and the number of separate CSS files will vary from project to project, but the example below might look similar.

Depending on the project’s deployment strategy, a change to one file (mobile.css, for example) would only require the QA team to regression test on devices in that specific media query range. Compare that to the prospect of deploying the single bundled site.css file, an approach that would normally trigger a full regression test.

Moving on

The adoption of mobile-first CSS was a significant milestone in web development because it allowed front-end developers to concentrate on mobile web applications rather than creating websites for desktop use and attempting to retrofit them to work on other devices.

I don't think anyone wants to return to that development model again, but it's important we don't lose sight of the issue it highlighted: that things can easily get convoluted and less efficient if we prioritize one particular device—any device—over others. For this reason, it seems natural to concentrate on the CSS in its own right, keeping an eye on both the default setting and the exceptions. I've started to notice subtle simplifications in both the CSS and other developers', and that the work is also a little more organized and effective.

In general, simplifying CSS rule creation whenever we can is ultimately a cleaner approach than going around in circles of overrides. However, the project must fit the methodology you choose. Mobile-first may turn out to be the best option for the situation at hand or not, but first you need to fully comprehend the trade-offs you're entering.

In today’s data-driven environment, it’s becoming more and more possible for you to be asked to create a personal electronic expertise, whether it’s a common website, consumer portal, or indigenous application. However while there continues to be no lack of marketing buzz around personalization systems, we also have very few defined approaches for implementing personalized UX.

We enter that place. After completing tens of personalisation projects over the past few years, we gave ourselves a purpose: could you make a systematic personalization platform especially for UX practitioners? A human-centered personalization program that includes data, classification, content delivery, and general objectives can be compared to the Personalization Pyramid, a design-focused type. By using this strategy, you will be able to understand the core components of a modern, UX-driven personalization system ( or at the very least understand enough to get started ).

Getting Started

We’ll assume that you are already comfortable with the fundamentals of modern personalization for the purposes of this article. A nice guide can be found these: Website Personalization Planning. Although Graphic jobs in this field can take a variety of forms, they frequently start from the same place.

Common scenarios for starting a personalisation 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 customisation as a target
• Consumer data is unclear or disjointed.
• You are running some secluded targeting strategies or A/B tests
• On personalization strategy, participants disagree.
• Mandate of customer privacy rules ( e. g. GDPR ) requires revisiting existing user targeting practices

Regardless of where you begin, a powerful personalization system will require the same key building stones. These are the “levels” on the tower, as we’ve made them. 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 personal service been provided?
3. Contexts and Campaigns: What personalization information does the person view?
4. What makes up a distinct, useable market according to consumer segments?
5. Actionable information: What dependable and credible information is captured by our professional platform to generate personalization?
6. What more extensive set of data is conceivable ( as of right now in our environment ) for personalization?

We’ll go through each of these amounts in change. An associated deck of cards serves as an example of each level’s specific cases to make this more meaningful. We’ve found them helpful in customisation pondering periods, and will include cases for you here.

Starting at the Top

The parts of the pyramids are as follows:

North Star

Ultimately, you want a North Star in your personalization plan, whether big or small. The North Star defines the (one ) overall mission of the personalization program. What do you hope to accomplish? North Stars cast a ghost. The larger the sun, the larger the dark. Example of North Starts may include:

Function: Optimize based on fundamental consumer inputs. Examples:” Raw” messages, basic search effects, system user settings and settings options, general flexibility, basic improvements
1. Self-contained customisation component is a feature. Examples:” Cooked” notifications, advanced optimizations ( geolocation ), basic dynamic messaging, customized modules, automations, recommenders
2. User knowledge: Personal consumer experiences across various user flows and interactions. 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 distinctive, personalized solution experiences. Example: Standalone, branded experience with personalization at their base, like the “algotorial” songs by Spotify quite as Discover Weekly.

Goals

Personalization can help speed up designing with customer intentions, as in any good UX design. Goals are the tactical and measurable metrics that will prove the overall program is successful. A good place to begin is with your current analytics and measurement program and metrics you can benchmark against. In some cases, new goals may be appropriate. The most important thing to remember is that personalization is more of a means of achieving an objective than a desired result. Common goals include:

• Conversion
• Time spent on task
• Net promoter score ( NPS)
• Customer satisfaction

Touchpoints

Touchpoints are where the personalization happens. This will be one of your biggest areas of responsibility as a UX designer. The touchpoints available to you will depend on how your personalization and associated technology capabilities are instrumented, and should be rooted in improving a user’s experience at a particular point in the journey. Touchpoints can be multi-device ( mobile, in-store, website ), but they can also be more specific ( web banner, web pop-up, etc. ). Several examples are given below:

Touchpoints at the channel level

• Email: Role
• Email opens at what time?
• In-store display ( JSON endpoint )
• Native app
• Search

Wireframe-level Touchpoints

• Web overlay
• Web alert bar
• Web banner
• Web content block
• Web home page

If you’re designing for web interfaces, for example, you will likely need to include personalized “zones” in your wireframes. Based on our next step, contexts, and campaigns, the content for these can be presented programmatically in touchpoints.

Contexts and Campaigns

Once you’ve identified some touchpoints, you can decide what kind of personalized content a user will receive. 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 programmatically to specific user segments, as defined by user data. At this stage, we find it helpful to consider two separate models: a context model and a content model. The context helps you consider the level of user engagement at the personalization moment, for instance, if they are just casually browsing information rather than engaging in a deep dive. Think of it in terms of information retrieval behaviors. The content model can then guide you in deciding what kind of personalization to use in 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

Content model for personalization:

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

If you’d like to read more about each of these models, check out Colin’s Personalization Content Model and Jeff’s Personalization Context Model.

User Groups

User segments can be created prescriptively or adaptively, based on user research ( e. g. via rules and logic tied to set user behaviors or via 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. Here are some examples from the personalization pyramid:

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

Actionable information

Every organization with any digital presence has data. It’s important to inquire about how to use the data you can ethically collect on users, its inherent reliability and value, and what is the term for “data activation.” Fortunately, the tide is turning to first-party data: a recent study by Twilio estimates some 80 % of businesses are using at least some type of first-party data to personalize the customer experience.

First-party data has a number of benefits on the user experience front, including being relatively simple to collect, more likely to be accurate, and less susceptible to the” creep factor” of third-party data. So a key part of your UX strategy should be to determine what the best form of data collection is on your audiences. Several examples are given below:

There is a progression of profiling when it comes to recognizing and making decisioning about different audiences and their signals. As user data volume and time and confidence increase, it varies more granularly to more precise constructs about ever-smaller cohorts of users.

While some combination of implicit / explicit data is generally a prerequisite for any implementation ( more commonly referred to as first party and third-party data ) ML efforts are typically not cost-effective directly out of the box. This is because optimization requires a strong data backbone and content repository. But these approaches should be considered as part of the larger roadmap and may indeed help accelerate the organization’s overall progress. At this point, you will typically work with important stakeholders and product owners to create a profiling model. The profiling model includes defining approach to configuring profiles, profile keys, profile cards and pattern cards. a scalable, multi-faceted approach to profiling.

Pulling it Together

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

In assembling a card “hand”, one can begin to trace the entire trajectory from leadership focus down through a strategic and tactical execution. It serves as the foundation for the workshops that both co-authors have conducted to build a program backlog, which would make a good article topic.

In the meantime, what is important to note is that each colored class of card is helpful to survey in understanding the range of choices potentially at your disposal, it is threading through and making concrete decisions about for whom this decisioning will be made: where, when, and how.

Lay Down Your Cards

Any effective personalization plan must take into account near, middle, and long-term objectives. Even with the leading CMS platforms like Sitecore and Adobe or the most exciting composable CMS DXP out there, there is simply no “easy button” wherein a personalization program can be stood up and immediately view meaningful results. Having said that, all personalization activities follow a common grammar, similar to how every sentence contains nouns and verbs. These cards attempt to map that territory.

Humility, a writer’s most important quality, has a great circle to it. What about sincerity, an business manager’s important value? Or a surgeon’s? Or a student’s? They all have excellent sounding voices. When humility is our guiding light, the course is usually available for fulfillment, development, relation, and commitment. We’re going to discuss why in this section.

That said, this is a guide for developers, and to that conclusion, I’d like to begin with a story—well, a voyage, actually. Along the way, I’m going to render myself a little vulnerable. I call it:

The Ludicrous Pate of Justin: A Tale

When I was coming out of arts school, a long-haired, goateed novice, write was a known quantity to me, design on the web, however, was riddled with complexities to understand and learn, a problem to be solved. Although I had formal training in typography, layout, and creative design, what most intrigued me was how these traditional skills could be applied to a young online landscape. This style would eventually form the rest of my profession.

So I devoured HTML and JavaScript novels into the wee hours of the morning and self-taught myself how to code during my freshman year rather than student and go into print like many of my companions. I wanted—nay, needed—to better understand the underlying relevance of what my design decisions may think when rendered in a website.

The so-called” Wild West” of website architecture was the late 1990s and early 2000s. Manufacturers at the time were all figuring out how to use layout and visual connection to the online environment. What were the guidelines? How may we break them and also engage, entertain, and present information? How was my values, which include sincerity, respect, and connection, coincide with that on a more general level? I was eager to find out.

Those are classic factors between non-career relationships and the world of design, even though I’m talking about a different time. What are your main passions, or ideals, that elevate medium? The main themes remain the same, much like the primary parallels between what fulfills you, who is independent of the physical or digital worlds.

First within tables, animated GIFs, Flash, then with Web Standards, divs, and CSS, there was personality, raw unbridled creativity, and unique means of presentment that often defied any semblance of a visible grid. Splash screens and “browser requirement” pages aplenty. Usability and accessibility were typically victims of such a creation, but such paramount facets of any digital design were largely (and, in hindsight, unfairly) disregarded at the expense of experimentation.

For instance, this iteration of my personal portfolio site (” the pseudoroom” ) from that time was experimental if not a little overt in terms of the visual presentation of the idea of a living sketchbook. Very skeuomorphic. On this one, I worked with fellow designer and dear friend Marc Clancy, who is now a co-founder of the creative project organizing app Milanote, to sketch and then play with various user interactions. Then, I’d break it down and code it into a digital layout.

Along with design folio pieces, the site also offered free downloads for Mac OS customizations: desktop wallpapers that were effectively design experimentation, custom-designed typefaces, and desktop icons.

GUI Galaxy was a design, pixel art, and Mac-centric news portal that graphic designer friends and I developed from the beginning.

Design news portals were incredibly popular at the time, and they now accept Tweet-sized, small-format versions of relevant news from the categories I previously covered. If you took Twitter, curated it to a few categories, and wrapped it in a custom-branded experience, you’d have a design news portal from the late 90s / early 2000s.

We as designers had changed and developed a bandwidth-sensitive, award-winning, much more accessibility-conscious website. Still ripe with experimentation, yet more mindful of equitable engagement. There are a few content panes here, with both Mac-focused news and general news (tech, design ) to be seen. We also offered many of the custom downloads I cited before as present on my folio site but branded and themed to GUI Galaxy.

The presentation layer consists of international design, illustration, and news author collaboration, and the backbone of the website was a homegrown CMS. And the collaboration effort here, in addition to experimentation on a’ brand’ and content delivery, was hitting my core. We were creating a larger-than-anyone experience and establishing a global audience.

Collaboration and connection transcend medium in their impact, immensely fulfilling me as a designer.

Now, why am I taking you on this trip through design memory lane? Two reasons.

First of all, there’s a reason for the nostalgia for that design era ( the” Wild West” era, as I put it ): the inherent exploration, personality, and creativity that dominated many design portals and personal portfolio websites. Ultra-finely detailed pixel art UI, custom illustration, bespoke vector graphics, all underpinned by a strong design community.

The web design industry has experienced stagnation in recent years. I suspect there’s a strong chance you’ve seen a site whose structure looks something like this: a hero image / banner with text overlaid, perhaps with a lovely rotating carousel of images ( laying the snark on heavy there ), a call to action, and three columns of sub-content directly beneath. Perhaps there are selections that vaguely relate to their respective content in an icon library.

Design, as it’s applied to the digital landscape, is in dire need of thoughtful layout, typography, and visual engagement that goes hand-in-hand with all the modern considerations we now know are paramount: usability. accessibility Load times and bandwidth- sensitive content delivery. A user-friendly presentation that is relevant wherever they are. We must be mindful of, and respectful toward, those concerns—but not at the expense of creativity of visual communication or via replicating cookie-cutter layouts.

Pixel Issues

Websites during this period were often designed and built on Macs whose OS and desktops looked something like this. Although Mac OS 7.5 is available, 8 and 9 are not very different.

How could any single icon, at any point, stand out and grab my attention, fascinated me? In this example, the user’s desktop is tidy, but think of a more realistic example with icon pandemonium. Or, let’s say an icon was a part of a larger system grouping ( fonts, extensions, control panels ): how did it maintain cohesion within a group as well?

These were 32 x 32 pixel creations, utilizing a 256-color palette, designed pixel-by-pixel as mini mosaics. This seemed to me to be the embodiment of digital visual communication under such absurd restrictions. And often, ridiculous restrictions can yield the purification of concept and theme.

So I started doing my homework and conducting my research. I was a student of this new medium, hungry to dissect, process, discover, and make it my own.

I wanted to see how I could push the boundaries of a 32×32 pixel grid with that 256-color palette, expanding upon the idea of exploration. Those ridiculous constraints forced a clarity of concept and presentation that I found incredibly appealing. I was thrown the digital gauntlet, and that challenge fueled my determination. And so, in my dorm room into the wee hours of the morning, I toiled away, bringing conceptual sketches into mini mosaic fruition.

These are some of my creations that I made using ResEdit, the only program I had at the time, to create icons. ResEdit was a clunky, built-in Mac OS utility not really made for exactly what we were using it for. Research is at the center of all of this work. Challenge. Problem-solving Again, these core connection-based values are agnostic of medium.

There’s one more design portal I want to talk about, which also serves as the second reason for my story to bring this all together.

This is the Kaliber 1000, or K10k, short for. K10k was founded in 1998 by Michael Schmidt and Toke Nygaard, and was the design news portal on the web during this period. It was the ideal setting for me, my friend, with its pixel art-filled presentation, meticulous attention to detail, and many of the site’s more well-known designers who were invited to be news authors. With respect where respect is due, GUI Galaxy’s concept was inspired by what these folks were doing.

For my part, the combination of my web design work and pixel art exploration began to get me some notoriety in the design scene. K10k eventually added me as one of their very select group of news writers to the website’s content.

Amongst my personal work and side projects —and now with this inclusion—in the design community, this put me on the map. Additionally, my design work has started to appear on other design news portals, as well as in publications abroad and domestically. With that degree of success while in my early twenties, something else happened:

I actually changed into a massive asshole in about a year of high school, not less. The press and the praise became what fulfilled me, and they went straight to my head. They inflated my ego. I actually felt somewhat superior to my fellow designers.

The casualties? My design stagnated. Its evolution, which is what I evolved, has stagnated.

I felt so supremely confident in my abilities that I effectively stopped researching and discovering. When my first instinct was to sketch concepts or iterate ideas in lead, I instead leaped right into Photoshop. I drew my inspiration from the smallest of sources ( and with blinders on ). My peers frequently vehemently disapproved of any criticism of my work. The most tragic loss: I had lost touch with my values.

My ego almost destroyed some of my friendships and blossoming professional relationships. I was toxic in talking about design and in collaboration. However, thankfully, those same friends gave me a priceless gift: sincerity. They called me out on my unhealthy behavior.

It’s true, I initially didn’t accept it, but after much reflection, I was able to accept it. I was soon able to accept, and process, and course correct. Although the re-awakening was necessary, the realization let me down. I let go of the “reward” of adulation and re-centered upon what stoked the fire for me in art school. Most importantly, I returned to my fundamental values.

Always Students

Following that temporary decline, my personal and professional design journey advanced. And I could self-reflect as I got older to facilitate further growth and course correction as needed.

Let’s use the Large Hadron Collider as an example. The LHC was designed” to help answer some of the fundamental open questions in physics, which concern the basic laws governing the interactions and forces among the elementary objects, the deep structure of space and time, and in particular the interrelation between quantum mechanics and general relativity”. Thank you, Wikipedia.

Around fifteen years ago, in one of my earlier professional roles, I designed the interface for the application that generated the LHC’s particle collision diagrams. These diagrams are the depiction of what is actually happening inside the Collider during any given particle collision event and are frequently regarded as works of art by themselves.

Designing the interface for this application was a fascinating process for me, in that I worked with Fermilab physicists to understand what the application was trying to achieve, but also how the physicists themselves would be using it. In order to accomplish this, this role requires,

I cut my teeth on usability testing, working with the Fermilab team to iterate and improve the interface. To me, their language and the topics they discussed seemed to me to be foreign languages. And by making myself humble and working under the mindset that I was but a student, I made myself available to be a part of their world to generate that vital connection.

I also had my first ethnographic observational experience, which involved visiting the Fermilab location and observing how the physicists used the tool in their own environments, on their own terminals. For example, one takeaway was that due to the level of ambient light-driven contrast within the facility, the data columns ended up using white text on a dark gray background instead of black text-on-white. They could read through a lot of data at once and relieve their strain in the process. And Fermilab and CERN are government entities with rigorous accessibility standards, so my knowledge in that realm also grew. Another crucial form of communication was the barrier-free design.

So to those core drivers of my visual problem-solving soul and ultimate fulfillment: discovery, exposure to new media, observation, human connection, and evolution. Before I entered those values, I checked my ego before entering the door.

An evergreen willingness to listen, learn, understand, grow, evolve, and connect yields our best work. I want to pay attention to the phrases “grow” and “evolve” in particular. If we are always students of our craft, we are also continually making ourselves available to evolve. Yes, we have years of practical design experience behind us. Or the focused lab sessions from a UX bootcamp. or the work portfolio with monograms. Or, ultimately, decades of a career behind us.

However, with all that being said, experience does not make one an “expert.”

As soon as we close our minds via an inner monologue of’ knowing it all’ or branding ourselves a” #thoughtleader” on social media, the designer we are is our final form. The artist we can be will never be there.

I am imaginative. Alchemy is what I do. It’s a puzzle. I prefer to let it be done through me rather than through me.

I have a creative side. This brand 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 perception, and I regard it. Perhaps I also have a little bit of fear for them. However, my thinking and being are unique.

It distracts one to apologize and qualify in progress. That’s what my head does to destroy me. I’ll leave it alone for today. I may forgive and be qualified at any time. After I’ve said what I originally said. which is difficult enough.

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

Sometimes it does. Maybe I have to create something right away. I’ve learned to avoid saying it right away because they think you don’t work hard enough when you realize that sometimes the idea really comes along and it is the best plan and you know it is 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. Maybe I get so excited about something that just happened that I blurt it out and didn’t stop myself. like a child who discovered a reward in a box of Cracker Jacks. I occasionally manage to get away with this. Yes, that is the best plan, per some observers. They don’t usually, and I regret losing my joy.

Passion should be saved for the meeting, where it will matter. Certainly the informal get-together that comes before that meeting with two more discussions. Nobody understands why these discussions occur. We keep saying we’re going to get rid of them, but we end up really trying to. They occasionally also excel. Sometimes they detract from the real work, though. Depending on what you do and where you do it, the ratio between when conferences are valuable and when they are a sad distraction vary. And who you are and how you go about doing it. I’ll go over it once more. I am imaginative. That is the topic.

Often, a lot of hours of diligent and diligent work ends up with something that is rarely useful. Maybe I have to take that and move on to the next task.

Don’t inquire about the procedure. I am imaginative.

I have a creative side. My dreams are not in my power. And I have no power over my best tips.

I may hammer away and often find it useful to surround myself with images or information. I can go for a move, which occasionally works. There is no connection between sizzling fuel and bubbling pots, and I may be making dinner. I frequently have a plan for action when I wake up. The idea that may have saved me disappears almost as frequently as I become aware and a part of the world once more as a thoughtless wind of oblivion. For imagination, in my opinion, comes from that other planet. the one that we enter in ambitions and, possibly, before and after suicide. I’m not a writer, so that’s up to authors to think about. I am imaginative. Theologians are encouraged to build massive armies in their artistic world, which they insist is true. But that is yet another diversion. And a miserable one. Possibly on a much bigger issue than whether or not I am creative. But that’s not how I came around, though.

Often the result is evasion. And suffering. Do you know the actor who is tortured by the cliché? Even when the artist ( this place that noun in quotes ) attempts to write a sweet drink jingle, a call in a worn-out comedy, or a budget ask, it’s true.

Some individuals who detest being called artistic perhaps been closeted artists, but that’s between them and their gods. No offence intended. Your assertions are also accurate. My needs are own, though.

Artists are recognized as artists.

Negatives are aware of cons, just like queers are aware of queers, just like real rappers are aware of true rappers. People have a lot of regard for designers. We respect, follow, and nearly deify the excellent ones. Of program, deifying any person is a dreadful error. We have been given warning. We are more knowledgeable. We are aware that people are really people. They argue, they are depressed, they regret their most important choices, they are weak and thirsty, they can be cruel, and they can be as terrible as we can because they are clay, just like us. But. But. However, they produce this incredible issue. They give birth to something that was unable to arise before them or otherwise. They are the inspirations ‘ mother. And since it’s only lying there, I suppose I should add that they are the inventor’s parents. Bad mee backside! That’s done, I suppose. Continue.

Creatives denigrate our personal small accomplishments because they are compared to those of the wonderful people. Wonderful graphics! I‘m not Miyazaki, though. That is glory right then. That is glory straight out of the Bible. This unsatisfied small thing I created? It essentially fell off the back of the pumpkin trailer. And the carrots weren’t actually new.

Artists is aware that they are at best Salieri. Also Mozart’s original artists believe that.

I have a creative side. I haven’t worked in advertising in 30 years, but my previous artistic managers have been the ones who make my decisions. They are correct to do that. My mind goes blank when it really counts because I’m too sluggish and complacent. No medication is available to treat innovative function.

I have a creative side. Every project I create has a goal that makes Indiana Jones appear older and snoring in a balcony head. The more I pursue my creative endeavors, the faster I progress in my work, and the more I slog through lines and gaze blankly before beginning that task.

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 only been creative for a short time in their careers. Only that I spend twice as long as they do putting the job of before I work ten times as quickly as they do. When I put my mind to it, I am so confident in my ability to do a great career. I have an addiction to the delay rush. The climb also terrifies me.

I don’t create anything.

I have a creative side. never a performer. Though as a child, I had a dream that I would one day become 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 don’t practice politicians.

I have a creative side. Despite my belief in reason and science, I make decisions based on my own senses and instincts. And bear witness to what comes next, both the successes and the disasters.

I have a creative side. Every term I’ve said these may irritate another artists who have different viewpoints. Ask a question to two artists, and three views will be formed. No matter how we does think about it, our debate, our passion for it, and our responsibility to our own truth, at least in my opinion, are the best indications that we are creative.

I have a creative side. I lament my lack of taste in the areas of human knowledge that I know quite small, that is to say about everything. And I put my taste before everything else in the things that are most important to me, or perhaps more precisely, to my obsessions. Without my passions, I had probably have to spend time staring living in the eye, which almost none of us can do for very long. No seriously. Actually, not. Because living is so difficult to handle when you really look at it.

I have a creative side. I think that when I’m gone, some of the good parts of me will stay in the head of at least one additional person, just like a family does.

Working frees me from worrying about my job.

I have a creative side. I fear that my little product will disappear without warning.

I have a creative side. 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 have a creative side. I think approach is the most amazing mystery. I think I have to consider it so strongly that I actually made the foolish decision to publish an essay I wrote without having to go through or edit. I swear I didn’t accomplish this frequently. 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 beautiful.

There. I believe I’ve said it.

I’d like you to consider this a “yes … and” piece to complement Joe’s post. Instead of refuting everything he’s saying, I’m pointing out some areas where AI may make real, positive impacts on people with disabilities. To be clear, I’m not saying that there aren’t real challenges or pressing problems with AI that need to be addressed; there are, and we’ve needed to address them, like, yesterday; instead, I want to take a moment to talk about what’s possible so that we can get it one day.

Other words

Joe’s article spends a lot of time examining how computer vision versions can create other words. He raises a number of true 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 ( which should probably have descriptions ) and those that are purely decorative ( which might not even need a description ) either. However, I still think there’s possible in this area.

As Joe points out, alt text editing via human-in-the-loop should be a given. 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 station a design to examine image usage in context, this may help us more quickly determine which images are likely to be elegant and which ones are likely to be descriptive. That will help clarify which situations require image descriptions, and it will increase authors ‘ effectiveness in making their sites more visible.

While complex images—like graphs and charts—are challenging to describe in any sort of succinct way ( even for humans ), the image example shared in the GPT4 announcement points to an interesting opportunity as well. 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 would frequently leave many unanswered questions about the data, but let’s just assume that that was the description in place. ) If your browser knew that that image was a pie chart ( because an onboard model concluded this ), imagine a world where users could ask questions like these about the graphic:

• Are there more smartphone users than feature phones?
• How many more?
• Is there a group of people that don’t fall into either of these buckets?
• What number is that?

For a moment, the chance to learn more about images and data in this way could be revolutionary for people with low vision and blindness as well as for those with various forms of color blindness, cognitive disabilities, and other issues. It could also be useful in educational contexts to help people who can see these charts, as is, to understand the data in the charts.

What if you could ask your browser to make a complicated chart simpler? What if you asked it to separate a single line from a line graph? What if you could ask your browser to transpose the colors of the different lines to work better for form of color blindness you have? What if you asked it to switch colors in favor of patterns? That seems like a possibility given the chat-based interfaces and our current ability to manipulate images in today’s AI tools.

Now imagine a purpose-built model that could extract the information from that chart and convert it to another format. Perhaps it could convert that pie chart (or, better yet, a series of pie charts ) into more usable ( and useful ) formats, like spreadsheets, for instance. That would be incredible!

Matching algorithms

When Safiya Umoja Noble chose to call her book Algorithms of Oppression, she hit the nail on the head. Although her book focused on how search engines can foster racism, I believe it’s equally true that all computer models have the potential to foster conflict, prejudice, and intolerance. Whether it’s Twitter always showing you the latest tweet from a bored billionaire, YouTube sending us into a Q-hole, or Instagram warping our ideas of what natural bodies look like, we know that poorly authored and maintained algorithms are incredibly harmful. A large portion of this is a result of a lack of diversity in the people who design and construct them. However, when these platforms are built with inclusive features in mind, there is 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. They match job seekers with potential employers using an algorithm based on more than 75 data points. 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 takes into account each work environment, communication issues relating to each job, and other factors. Mentra made the decision to change the script when it came to the typical employment websites because it was run by neurodivergent people. They use their algorithm to propose available candidates to companies, who can then connect with job seekers that they are interested in, reducing the emotional and physical labor on the job-seeker side of things.

More people with disabilities can be used to create algorithms, which can lessen the likelihood that they will harm their communities. Diverse teams are crucial because of this.

Imagine that a social media company’s recommendation engine was tuned to analyze who you’re following and if it was tuned to prioritize follow recommendations for people who talked about similar things but who were different in some key ways from your existing sphere of influence. For instance, if you followed a group of nondisabled white male academics who spoke about AI, it might be advisable to follow those who are disabled, aren’t white, or aren’t men who also speak about AI. If you followed its advice, you might be able to understand what is happening in the AI field more fully and nuancedly. 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 assist 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. In no particular order:

preservation of voice You may be aware of the voice-prescribing options from Microsoft, Acapela, or others, or you may have seen the announcement for VALL-E or Apple’s Global Accessibility Awareness Day. It’s possible to train an AI model to replicate your voice, which can be a tremendous boon for people who have ALS ( Lou Gehrig’s disease ) or motor-neuron disease or other medical conditions that can lead to an inability to talk. We need to approach this tech responsibly because it has the potential to have a truly transformative impact, which is why it can also be used to create audio deepfakes.
• voice recognition is. Researchers like those in the Speech Accessibility Project are paying people with disabilities for their help in collecting recordings of people with atypical speech. As I type, they are actively seeking out people who have Parkinson’s and related conditions, and they intend to expand this list as the project develops. 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 lead to more inclusive data sets that enable them to use their computers and other devices more effectively and with just their voices.
• Text transformation. The most recent generation of LLMs is capable of altering already-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 importance of diverse teams and data

We must acknowledge that our differences matter. The intersections of the identities we exist 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 has been written by people with a variety of disabilities in the training data.

Want a non-binary language model? You may be able to use existing data sets to build a filter that can intercept and remediate ableist language before it reaches readers. Despite this, AI models won’t be replacing human copy editors anytime soon when it comes to sensitivity reading.

Want a coding copilot who can provide you with useful recommendations after the jump? Train it on code that you know to be accessible.

I have no doubts about how dangerous AI can and will be for people today, tomorrow, and for the rest of the world. However, I also think that we can acknowledge this and make thoughtful, thoughtful, 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 supporting the development of this article, Ashley Bischoff for providing me with invaluable editorial support, and of course, Joe Dolson for the prompt.

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.

online standards were born.

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 languages like PHP, Java, and.NET overtook Perl as the predominant back-end processors, and the cgi-bin was tossed in the trash bin. With these improved server-side tools, the first era of web applications started with content-management systems (especially those used in blogs like Blogger, Grey Matter, Movable Type, and WordPress ) In the mid-2000s, AJAX opened doors for asynchronous interaction between the front end and back end. Pages now no longer needed to reload their pages ‘ content. A crop of JavaScript frameworks like Prototype, YUI, and jQuery arose to help developers build more reliable client-side interaction across browsers that had wildly varying levels of standards support. Techniques like image replacement enable skilled designers and developers to use fonts of their choosing. And technologies like Flash made it possible to add animations, games, and even more interactivity.

The industry was reenergized by these new tools, standards, and methods in many ways. Web design flourished as designers and developers explored more diverse styles and layouts. However, we still relied heavily on numerous hacks. Early CSS was a huge improvement over table-based layouts when it came to basic layout and text styling, but its limitations at the time meant that designers and developers still relied heavily on images for complex shapes ( such as rounded or angled corners ) and tiled backgrounds for the appearance of full-length columns (among other hacks ). All kinds of nested floats or absolute positioning ( or both ) were necessary for complicated layouts. Flash and image replacement for custom fonts was a great start toward varying the typefaces from the big five, but both hacks introduced accessibility and performance problems. Additionally, JavaScript libraries made it simple to add a dash of interaction to pages without having to spend the money to double or even quadruple the download size for basic websites.

The web as software platform

The interplay between the front end and the back end continued to grow, which led to the development of the current era of modern web applications. 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. Along with these tools, there were additional options, such as collaborative build automation, collaborative version control, and shared package libraries. What was once primarily an environment for linked documents became a realm of infinite possibilities.

Mobile devices increased in their capabilities as well, and they gave us access to the internet in our pockets at the same time. Mobile apps and responsive design opened up opportunities for new interactions anywhere and any time.

This fusion of potent mobile devices and potent development tools contributed to the growth of social media and other centralized tools for people to use and interact with. As it became easier and more common to connect with others directly on Twitter, Facebook, and even Slack, the desire for hosted personal sites waned. Social media made connections on a global scale, with both positive and negative outcomes.

Want a much more extensive history of how we got here, with some other takes on ways that we can improve? ” Of Time and the Web” was written by Jeremy Keith. Or check out the” Web Design History Timeline” at the Web Design Museum. A fun tour of” Internet Artifacts” is also available from Neal Agarwal.

Where we are now

It seems like we’ve reached yet another significant turning point in recent years. As social-media platforms fracture and wane, there’s been a growing interest in owning our own content again. There are many different ways to create websites, from the tried-and-true classic of hosting plain HTML files to static site generators to content management systems of all kinds. The fracturing of social media also comes with a cost: we lose crucial infrastructure for discovery and connection. The IndieWeb‘s Webmentions, RSS, ActivityPub, and other tools can assist with this, but they’re still largely underdeveloped and difficult to use for the less geeky. We can build amazing personal websites and add to them regularly, but without discovery and connection, it can sometimes feel like we may as well be shouting into the void.

Browser support for standards like web components like CSS, JavaScript, and other standards has increased, particularly with efforts like Interop. New technologies gain support across the board in a fraction of the time that they used to. I frequently find out about a new feature and check its browser support only to discover that its coverage is already over 80 %. Nowadays, the barrier to using newer techniques often isn’t browser support but simply the limits of how quickly designers and developers can learn what’s available and how to adopt it.

With a few commands and a few lines of code, we can currently prototype almost any concept. All the tools that we now have available make it easier than ever to start something new. However, as we upgrade and maintain these frameworks, we eventually pay the upfront costs that these frameworks may initially save in terms of our technical debt.

If we rely on third-party frameworks, adopting new standards can sometimes take longer since we may have to wait for those frameworks to adopt those standards. These frameworks, which once made it easier to adopt new techniques sooner, have since evolved into obstacles. These same frameworks often come with performance costs too, forcing users to wait for scripts to load before they can read or interact with pages. And when scripts fail ( whether due to poor code, network issues, or other environmental factors ), there is frequently no other option, leaving users with blank or broken pages.

Where do we go from here?

Hacks of today help to shape standards for the future. 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. So what can we do to create the future we want for the web?

Build for the long haul. Optimize for performance, for accessibility, and for the user. weigh the costs associated with those user-friendly tools. They may make your job a little easier today, but how do they affect everything else? What is the cost to the users? To future developers? to the adoption of standards? Sometimes the convenience may be worth it. Sometimes it’s just a hack that you’ve gotten used to. And sometimes it’s holding you back from even better options.

Start with the basics. Standards continue to evolve over time, but browsers have done a remarkably good job of continuing to support older standards. The same holds true for third-party frameworks, though. Sites built with even the hackiest of HTML from the’ 90s still work just fine today. The same can’t always be said of websites created with frameworks even after a few years.

Design with care. Consider the effects of each choice, whether it is your craft, which is code, pixels, or processes. The convenience of many a modern tool comes at the cost of not always understanding the underlying decisions that have led to its design and not always considering the impact that those decisions can have. Use the time saved by modern tools to think more carefully and make decisions with care rather than rushing to “move fast and break things”

Always be learning. If you’re constantly learning, you’re also developing. 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 neural connections in your brain, and the techniques you learn in one day may be used to inform different experiments in the future.

Play, experiment, and be weird! The ultimate experiment is this web we created. It’s the single largest human endeavor in history, and yet each of us can create our own pocket within it. Be brave and make new friends. Build a playground for ideas. In your own bizarre science lab, conduct absurd experiments. Start your own small business. There has never been a place where we have more room to be creative, take risks, and discover our potential.

Share and amplify. As you play, experiment, and learn, share what has 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 ahead and create.

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 incorporate our values into the products we produce, and let’s improve the world for everyone. Create that thing that only you are uniquely qualified to make. Then distribute it, improve it, re-use it, or create something new with it. Learn. Make. Share. Grow. Rinse and repeat. Everything will change whenever you believe you have mastered the web.

The personalization space is true, between the dream of getting it right and the worry of it going wrong ( like when we encounter “persofails” similar to a company’s repeated pleas for more toilet seats from regular people ). It’s an particularly confusing place to be a modern professional without a map, a map, or a strategy.

There are no Lonely Planet and some tour guides for those of you who want to personalize because successful personalization depends so much on each group’s talent, technology, and market position.

But you can ensure that your group has packed its bags rationally.

There’s a DIY method to increase your chances for victory. You’ll at least at least disarm your boss ‘ irrational exuberance. Before the group you’ll need to properly plan.

We refer to it as prepersonalization.

Behind the audio

Take into account Spotify’s DJ element, which debuted this year.

We’re used to seeing the polished final outcome of a personalization have. A personal have had to be conceived, budgeted, and prioritized before the year-end prize, the making-of-backstory, or the behind-the-scenes success chest. Before any customisation have goes live in your product or service, it lives amid a delay of valuable ideas for expressing consumer experiences more automatically.

How do you decide where to position personalization wagers? How do you design regular interactions that didn’t journey up users or—worse—breed mistrust? We’ve discovered that several budgeted programs second required one or more workshops to join key stakeholders and domestic customers of the technology in order to justify their continuous investments. Make it count.

We’ve closely observed the same evolution with our consumers, from major software to young companies. In our experience with working on small and large customisation efforts, a program’s best monitor record—and its capacity to weather tough questions, work steadily toward shared answers, and manage its design and engineering efforts—turns on how successfully these prepersonalization activities play out.

Effective workshops consistently distinguish successful future endeavors from unsuccessful ones, saving countless hours of time, resources, and overall well-being in the process.

A personalization practice involves a multiyear effort of testing and feature development. It’s not a switch-flip 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 ( like 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. These cards won’t be necessary for you. But we strongly recommend that you create something similar, whether that might be digital or physical.

Set the timer for the kitchen.

How long does it take to cook up a prepersonalization workshop? The activities we suggest including during the assessment can ( and frequently do ) last for weeks. For the core workshop, we recommend aiming for two to three days. Here are a summary of our broad approach and information on the most crucial first-day activities.

The full arc of the wider workshop is threefold:

Kickstart: This specifies the terms of engagement as you concentrate on both the potential and the team’s and leadership’s readiness and drive.
1. 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.
2. Work your plan: This stage essentially entails creating a competitive environment in which team members can individually present 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: Apt your appetite

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

Create a conversation by mentioning consumer 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 list of these in the cards. Here’s a list of 142 different interactions to jog your thinking.

It’s all about setting the tone. What are the possible paths for the practice in your organization? Here’s a long-form primer and a strategic framework for a broader perspective.

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 ). We break down connected experiences into five categories in our cards: functions, features, experiences, complete products, and portfolios. Size your own build here. This will help to draw attention to both the benefits of ongoing investment and the difference between what you currently offer and what you intend 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 crucial because it emphasizes how personalization can affect your own ways of working as well as your external customers. 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 decide where their focus should be placed for your product or service. Naturally, you can’t prioritize all of them. Here, the goal is to demonstrate how various departments may view their own advantages over the effort, which can be different from one department 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 filling in the personalization gap. Is your customer journey well documented? Will data and privacy protection be a significant challenge? Do you have content metadata needs that you have to address? It’s just a matter of acknowledging the magnitude of that need and finding a solution ( we’re fairly certain that you do ). In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six intractable stakeholder attitudes that prevent progress.

Effectively collaborating and managing expectations is critical to your success. Consider the potential obstacles to your advancement in the future. Press the participants to name specific steps to overcome or mitigate those barriers in your organization. As research has shown, personalization initiatives face a number of common obstacles.

At this point, you’ve hopefully discussed sample interactions, emphasized a key area of benefit, and flagged key gaps? You’re all set to go on, good.

Hit that test kitchen

Next, let’s take a look at what you’ll need to create personalization recipes. Personalization engines, which are robust software suites for automating and expressing dynamic content, can intimidate new customers. They give you a variety of options for how your organization can conduct its activities because of their broad and potent capabilities. This presents the question: Where do you begin when you’re configuring a connected experience?

The key here is to avoid treating the installed software like some imagined kitchen from a fantasy remodeling project ( as one of our client executives humorously 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.

Over the course of the workshop, the ultimate menu of the prioritized backlog will come together. 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 be made from recipes, which have predetermined ingredients.

Verify your ingredients

Like a good product manager, you’ll make sure you have everything ready to cook up your desired interaction ( or figure out what needs to be added to your pantry ) and that you validate with the right stakeholders present. 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 doesn’t just involve identifying requirements. Documenting your personalizations as a series of if-then statements lets the team:

1. compare findings to a common method for developing features, similar to how artists paint with the same color palette,
2. specify a consistent set of interactions that users find uniform or familiar,
3. and establish parity between all important performance indicators and performance metrics.

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.

Create your recipe.

What ingredients are important to you? Consider a who-what-when-why construct:

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

Five years ago, we created these cards and card categories. We regularly play-test their fit with conference audiences and clients. And we still come across fresh possibilities. But they all follow an underlying who-what-when-why logic.

In the cards in the accompanying photo below, you can typically follow along with right to left in three examples of subscription-based reading apps.

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: An email is sent when a new user registers to highlight the breadth of the content catalog and convert them to happy subscribers.
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.

We’ve also found that cocreating the recipes themselves can sometimes be the most effective way to start brainstorming about what these cards might be for your organization. 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.

The later stages of the workshop could be characterized as moving from focusing on a cookbook to 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 architecture is necessary for better kitchens.

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

A team overfitting: they aren’t designing with their best data, is what causes personalization to become a laugh line. Like a sparse pantry, every organization has metadata debt to go along with its technical debt, and this creates a drag on personalization effectiveness. For instance, your AI’s output quality is in fact impacted 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 withstand the heat without a doubt.

Personalization technology opens a doorway into a confounding ocean of possible designs. Only a deliberate and cooperative approach will produce the desired outcome. So banish the dream kitchen. Instead, head to the test kitchen to save time, preserve job security, and avoid imagining the creative concepts that come from the doers in your organization. There are meals to serve and mouths to feed.

This framework of the workshop gives you a strong chance at long-term success as well as solid ground. Wiring up your information layer isn’t an overnight affair. However, if you use the same cookbook and the same recipes, you’ll have solid ground for success. We designed these activities to make your organization’s needs concrete and clear, long before the hazards pile up.

Your time well spent is being able to assess your unique situation and digital skills, despite the associated costs associated with investing in this kind of technology and product design. Don’t squander it. The pudding is the proof, as they say.

I’ve been fascinated by movies since I was a child. I loved the heroes and the excitement—but most of all the stories. I aspired to be an artist. And I believed that I’d get to do the things that Indiana Jones did and go on fascinating experiences. Yet my friends and I had movie ideas to make and sun in. But they never went any farther. However, I did end up in the user experience ( UX) field. Today, I realize that there’s an element of drama to UX— I hadn’t actually considered it before, but consumer research is story. And to get the most out of customer studies, you must tell a compelling story that involves stakeholders, including the product team and decision-makers, and piques their interest in learning more.

Think of your favourite film. It more than likely follows a three-act narrative architecture: the installation, the turmoil, and the resolution. The second act shows what exists now, and it helps you get to know the figures and the challenges and problems that they face. The issue begins in Act 2, which introduces the issue. Here, difficulties grow or get worse. And the quality is the third and final work. This is where the issues are resolved and the figures learn and change. This structure, in my opinion, is also a fantastic way to think about consumer research, and it might be particularly useful for explaining user research to others.

Use story as a framework when conducting research.

It’s sad to say, but many have come to see studies as being dispensable. Research is typically one of the first things to go when expenses or deadlines are tight. Instead of investing in study, some goods professionals rely on manufacturers or—worse—their personal judgment to make the “right” options for users based on their experience or accepted best practices. That may lead some groups, but that approach can so easily miss the chance to solve clients ‘ real issues. To be user-centered, this is something we really avoid. User study improves style. It keeps it on trail, pointing to problems and opportunities. You can keep back of your competition by being aware of the problems with your goods and fixing them.

In the three-act structure, each action corresponds to a part of the process, and each part is important to telling the whole story. Let’s take a look at the various functions and how they relate to consumer study.

Act one: installation

The basic research comes in handy because the layout is all about understanding the background. Basic research ( also called conceptual, discovery, or preliminary research ) helps you understand people and identify their problems. Like in the movies, you’re learning about the difficulties users face, what options are available, and how they are affected by them. To do basic research, you may conduct cultural inquiries or journal studies ( or both! ), which may assist you in identifying both prospects and problems. It doesn’t need to get a great investment in time or money.

Erika Hall writes about the most effective anthropology, which can be as straightforward as spending 15 hours with a customer and asking them to” Walk me through your morning yesterday.” That’s it. Give that one ask. Locked up and listen to them for 15 days. Do everything in your power to keep yourself and your pursuits out of it. Bam, you’re doing ethnography”. Hall predicts that “[This ] will likely prove quite fascinating. In the very unlikely event that you didn’t learn anything new or helpful, carry on with increased confidence in your way”.

This makes sense to me in all its entirety. And I love that this makes consumer studies so visible. You can only attract participants and do it! You don’t need to create a lot of documentation. This can offer a wealth of knowledge about your customers, and it’ll help you better understand them and what’s going on in their life. That’s what action one is really all about: understanding where people are coming from.

Maybe Spool talks about the importance of basic research and how it really type the bulk of your research. If you can complement what you’ve heard in the basic studies by using any more user data that you can obtain, such as surveys or analytics, or if you can identify areas that need more investigation. Together, all this information creates a clearer picture of the state of things and all its deficiencies. And that’s the start of a gripping tale. It’s the place in the story where you realize that the principal characters—or the people in this case—are facing issues that they need to conquer. This is where you begin to develop compassion for the characters and support their success, much like in films. And finally partners are now doing the same. Their concern may be with their company, which could be losing money because people are unable to complete specific tasks. Or probably they do connect with people ‘ problems. In any case, action one serves as your main strategy to pique the interest and interest of the participants.

When stakeholders begin to understand the value of basic research, that is open doors to more opportunities that involve users in the decision-making approach. And that can influence product teams ‘ focus on improving. This benefits everyone—users, the product, and stakeholders. It’s similar to winning an Oscar for a film; it frequently results in a favorable reception and success for your product. And this can be an incentive for stakeholders to repeat this process with other products. Knowing how to tell a good story is the only way to convince stakeholders to care about doing more research, and storytelling is the key to this process.

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 typically involves conducting directional research, such as usability tests, where you evaluate a potential solution ( such as a design ) to see if it addresses the issues you identified. The issues could include unmet needs or problems with a flow or process that’s tripping users up. More problems will come up in the process, much like in the second act of a film. It’s here that you learn more about the characters as they grow and develop through this act.

Usability tests should typically consist of five participants, according to Jakob Nielsen, who found that that number of users can typically identify the majority of the issues:” 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. With fewer participants, each user’s struggles will be more easily recalled and shared with other parties when discussing 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.

Usability tests have been conducted in person for decades, but you can also conduct them remotely using software 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 might consider in-person usability tests like attending a play and remote sessions as more of a movie watching experience. There are advantages and disadvantages to each. Usability research in person is a much more extensive experience. Stakeholders can experience the sessions with other stakeholders. Additionally, you get real-time reactions, including surprises, disagreements, 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 conducting usability testing in the field is like watching a play that is staged and controlled, where any two sessions may 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 conduct your research by meeting users at their locations. 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. You have less control over how these sessions run as researchers, but this can occasionally improve your understanding of users. 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 add a level of detail that is frequently absent from remote usability tests.

That’s not to say that the “movies” —remote sessions—aren’t a good option. A wider audience can be reached through remote sessions. They allow a lot more stakeholders to be involved in the research and to see what’s going on. Additionally, they make the doors accessible to a much wider range 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 advantage of usability testing, whether conducted remotely or in person, is that you can ask real users questions to understand their reasoning and understanding of the problem. This can help you not only identify problems but also glean why they’re problems in the first place. Additionally, you can test your own hypotheses and determine whether your reasoning 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. The excitement centers on Act 2, but there are also potential surprises in that Act. This is equally true of usability tests. Unexpected things that are said by participants frequently alter how you view things, and these unexpected developments in the story can lead to unexpected turns in your perception.

Unfortunately, user research is sometimes seen as expendable. Usability testing is often the only method of research that some stakeholders believe they ever need, especially in this regard. 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 down the area of focus on without considering the needs of the users. As a result, there’s no way of knowing whether the designs might solve a problem that users have. In the context of a usability test, it’s only feedback on a particular design.

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 demonstrates the value of conducting both directional and foundational 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 encourage stakeholders to take action on the issues raised.

Act three: resolution

The third act is about resolving the issues from the first two acts, while the first two acts are about understanding the background and the tensions that can compel stakeholders to take action. 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 includes all members of the product team, including developers, UX experts, business analysts, delivery managers, product managers, and any other parties who have a say in the coming development. It allows the whole team to hear users ‘ feedback together, ask questions, and discuss what’s possible within the project’s constraints. Additionally, it enables the UX design and research teams to clarify, suggest alternatives, or provide more context for their decisions. So you can get everyone on the same page and get agreement on the way forward.

Voiceover narration of this act is typically used with audience input. 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 offer the stakeholders their suggestions and suggestions for how to create this vision.

Nancy Duarte in the Harvard Business Review offers an approach to structuring presentations that follow a persuasive story. The most effective presenters employ the same methods as great storytellers: By reaffirming the status quo and then revealing a better way, they create 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 proof for “what is “—the issues you’ve identified. And “what could be “—your recommendations on how to address them. And so forth and 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 as visual as quick sketches of a potential solution to a problem. These can help generate conversation and momentum. And this continues until the session is over when you’ve concluded by bridging the gaps and offering suggestions for improvement. This is the part where you reiterate the main themes or problems and what they mean for the product—the denouement of the story. The stakeholders will now have the opportunity to take the next steps, and hopefully the will-power to do so!

While we are nearly at the end of this story, let’s reflect on the idea that user research is storytelling. The three-act structure of user research contains all the components of a good story:

Act one: You meet the protagonists ( the users ) and the antagonists ( the problems affecting users ). This is the plot’s beginning. In act one, researchers might use methods including contextual inquiry, ethnography, diary studies, surveys, and analytics. These techniques can produce personas, empathy maps, user journeys, and analytics dashboards as output.

Act two: Next, there’s character development. The protagonists encounter problems and challenges, which they must overcome, and there is conflict and tension. In act two, researchers might use methods including usability testing, competitive benchmarking, and heuristics evaluation. Usability findings reports, UX strategy documents, usability guidelines, and best practices can be included in the output of these.

Act three: The protagonists triumph and you see what a better future looks like. Researchers may use techniques like presentation decks, storytelling, and digital media in act three. The output of these can be: presentation decks, video clips, audio clips, and pictures.

The researcher performs a number of tasks: they are the producer, the director, and the storyteller. The participants have a small role, but they are significant characters ( in the research ). And the audience are the stakeholders. But the most important thing is to get the story right and to use storytelling to tell users ‘ stories through research. In the end, the parties should leave with a goal and an eagerness to fix the product’s flaws.

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. User research is ultimately a win-win situation for everyone, and all you need to do is pique stakeholders ‘ interest in how the story ends.

It came as no surprise when YouTube legends RackaRacka, also known as Danny and Micheal Philippou, were hired to lead a fresh Street Fighter film following their enormous success with their divine young Talk to Me. It appeared that after moving into theater film, the film industry rose to prominence with its bloody, unwarranted action and horror videos.

The first article on Den of Geek: Talk to Me Executives Explain Why Their Street Fighter Movie Got KO’d was originally published by.

At South by Southwest, we spoke with a Spotify executive and two top panelists about the upcoming boom in the sector.

When two podcasters are sat in a place with a Spotify execute, their infectious enthusiasm for both long-form and short-form discussion topics will immediately make you wonder where the medium will go in the future. Similar to what happened at South by Southwest when Jordan Newman, the Spotify Senior Director of Content Partnerships, welcomed us to the Den of Geek theater along with two incredible visitors, Rachel Lindsay of Higher Learning and Morgan Absher of Two Popular Takes.

Absher and Lindsay briefly discussed how the pandemic and changing visitors choices have influenced how their displays, which are available on Spotify in both audio and video structure, have grown and changed over the past five years. Additionally, Newman chimed in with his thoughts on how blogging has evolved since its inception and where points might be headed. You won’t want to miss some of the great stories that podcasting allows them to explore, and the couple’s shared passion of the channel is on screen throughout the movie.

Adolescence has managed to become one of Netflix’s most watched shows in just three months on the streaming service.

” The limited series amassed another 30.4 % of views between March 24 and March 30, putting it at a total of 96.7 million views since its debut. That was sufficient to get you to No. 9 on the list of the Most Popular English TVs of all time, removing Bridgerton Season 2 from it altogether and pushing Stranger Items 3 to eighth spot.

Learn more at Deadline.

At CinemaCon, Sydney Sweeney and Amanda Seyfried shared a picture and the video for the movie” The Housemaid.”

” Sydney Sweeney joined chairman Paul Feig and her friend The Housemaid actors at CinemaCon to share the angry second film. On Tuesday, Amanda Seyfried and Brandon Sklenar showed up on the set of the Lionsgate film to encourage the mental thriller and show the truck, which has not yet been made available for public viewing. The film, which premieres on Christmas Day, adapts Freida McFadden’s 2022 bestseller into its own text.

Read more about The Hollywood Reporter.

Supporters of Kendrick Lamar’s comic will have to delay until 2026 before seeing Matt Stone and Trey Parker, South Park makers.

The unnamed comedy” Kendrick Lamar didn’t make its debut on America’s bday, after all. The release dates for Paramount, the studio that produced the carefully guarded film Matt Stone and Trey Parker from Lamar and South Park, have been changed from July 4, 2025 to March 20, 2026.

Learn more at Variety.

The first article on Den of Geek was Link Tank: How Music Is Changing the Nature of Podcast.