Blog

Containers are used to style CSS. In fact, the whole website is made of containers, from the website viewport to components on a webpage. However, every now and then a new element appears that prompts us to reevaluate our design philosophy.

Square features, for instance, make it fun to play with round picture areas. Mobile display holes and electronic keyboards offer issues to best manage content that stays clear of them. And having two or more portable devices forces us to reevaluate how to make the most of the available space in a variety of diverse device positions.

These latest changes to the online platform have made it both more difficult and fascinating to create products. They’re wonderful opportunities for us to break out of our triangular boxes.

I’d like to talk about a new feature similar to the above: the Window Controls Overlay for Progressive Web Apps ( PWAs ).

Liberal Web Apps are bridging the gap between websites and apps. They combine the best of both worlds. On the one hand, they are flexible, linkable, and stable, just like websites. On the other hand, they provide more effective features, work online, and read documents just like local apps.

As a style area, PWAs are really exciting because they challenge us to think about what mixing online and device-native user interface can get. We have more than 40 years of experience telling us what software may look like, especially on desktop computers, and it can be challenging to get out of this psychological design.

At the end of the day though, PWAs on desktops are constrained to the glass they appear in: a square with a name bar at the top.

What a standard desktops PWA app looks like:

Sure, as the author of a PWA, you get to choose the color of the title bar (using the Web Application Manifest theme_color home ), but that’s about it.

What if we could consider other ways and reclaim the whole window in the app? Doing so would give us a chance to create our applications more wonderful and feel more included in the operating system.

The Window Controls Overlay offers precisely this. This innovative PWA operation makes it possible to take advantage of the full floor area of the app, including where the name bar usually appears.

About the subject bar and screen controls

Let’s get started with an explanation of the subject bar and screen controls.

The title bar is the place displayed at the top of an game windows, which frequently contains the phone’s name. The controls are displayed at the top of an app’s window, along with the buttons that enable it to reduce, maximize, near, and close it.

Window Controls Overlay removes the natural barrier of the name bar and windows controls areas. The title bar and glass control buttons can be overlayed on top of the user’s internet material, allowing it to free up the entire height of the game window.

If you are reading this article on a desktop computer, take a quick look at other apps. Chances are they’re already doing something similar to this. In fact, the web browser you are using uses the top area to display tabs.

Spotify displays album artwork to the top of the application window all the way up.

Microsoft Word uses the available title bar space to display the auto-save and search functionalities, and more.

The whole point of this feature is to allow you to make use of this space with your own content while providing a way to account for the window control buttons. And it makes it possible to offer this modified experience across a variety of platforms without having a negative impact on browsers or other devices that don’t support Window Controls Overlay. After all, PWAs are all about progressive enhancement, so this feature is a chance to enhance your app to use this extra space when it’s available.

Let’s use the feature.

For the rest of this article, we’ll be working on a demo app to learn more about using the feature.

The demo app is called 1DIV. Users can create designs using CSS and a single HTML element in a simple CSS playground.

The app has two pages. The first lists your existing CSS designs:

The second page enables you to create and edit CSS designs:

We can install the app as a PWA on the desktop because I added a straightforward web manifest and service worker. Here is what it looks like on macOS:

And on Windows:

Our app is looking good, but the white title bar in the first page is wasted space. It would be really nice if the design area reached the top of the app window on the second page.

Let’s use the Window Controls Overlay feature to improve this.

Enabling Window Controls Overlay

The feature is still experimental at the moment. To try it, you need to enable it in one of the supported browsers.

It has currently been incorporated into Chromium as a result of a collaboration between Microsoft and Google. We can therefore use it in Chrome or Edge by going to the internal about: //flags page, and enabling the Desktop PWA Window Controls Overlay flag.

Using the overlay of window controls

To use the feature, we need to add the following display_override member to our web app’s manifest file:

{ "name": "1DIV", "description": "1DIV is a mini CSS playground", "lang": "en-US", "start_url": "/", "theme_color": "#ffffff", "background_color": "#ffffff", "display_override": [ "window-controls-overlay" ], "icons": [ ... ]}

On the surface, the feature is really simple to use. The only thing we need to change is this manifest change, which will make the title bar disappear and convert the window controls into an overlay.

However, to provide a great experience for all users regardless of what device or browser they use, and to make the most of the title bar area in our design, we’ll need a bit of CSS and JavaScript code.

Here is how the app currently looks:

Our logo, search field, and NEW button are now partially obscured by the window controls because our layout now begins at the top of the window, which is what we wanted.

It’s similar on Windows, with the difference that the close, maximize, and minimize buttons appear on the right side, grouped together with the PWA control buttons:

Using CSS to keep clear of the window controls

New CSS environment variables have also been introduced along with the feature:

• titlebar-area-x
• titlebar-area-y
• titlebar-area-width
• titlebar-area-height

You use these variables with the CSS env ( ) function to position your content where the title bar would have been while ensuring it won’t overlap with the window controls. Our header, which includes the logo, search bar, and NEW button, will be placed using two of the variables in our case.

header { position: absolute; left: env(titlebar-area-x, 0); width: env(titlebar-area-width, 100%); height: var(--toolbar-height);}

The titlebar-area-x variable gives us the distance from the left of the viewport to where the title bar would appear, and titlebar-area-width is its width. (Remember, this is not equivalent to the width of the entire viewport, just the title bar portion, which as noted earlier, doesn’t include the window controls.)

By doing this, we make sure our content remains fully visible. We’re also defining fallback values (the second parameter in the env() function) for when the variables are not defined (such as on non-supporting browsers, or when the Windows Control Overlay feature is disabled).

Now our header adapts to its surroundings, and it doesn’t feel like the window control buttons have been added as an afterthought. The app appears much more like a native app.

Changing the window controls background color so it blends in

Now let’s take a closer look at our second page: the CSS playground editor.

Not very good. Our CSS demo area does go all the way to the top, which is what we wanted, but the way the window controls appear as white rectangles on top of it is quite jarring.

We can fix this by changing the app’s theme color. There are a few ways to define it:

PWAs can define a theme color in the web app manifest file using the theme_color manifest member. The OS then uses this color in various ways. On desktop platforms, it is used to provide a background color to the title bar and window controls.
• Websites can use the theme-color meta tag as well. It’s used by browsers to customize the color of the UI around the web page. For PWAs, this color can override the manifest theme_color.

In our case, we can set the manifest theme_color to white to provide the right default color for our app. The OS will read this color value when the app is installed and use it to make the window controls background color white. This color works great for our main page with the list of demos.

The theme-color meta tag can be changed at runtime, using JavaScript. So we can do that to override the white with the right demo background color when one is opened.

Here is the function we’ll employ:

function themeWindow(bgColor) { document.querySelector("meta[name=theme-color]").setAttribute('content', bgColor);}

With this in place, we can imagine how using color and CSS transitions can produce a smooth change from the list page to the demo page, and enable the window control buttons to blend in with the rest of the app’s interface.

Dragging the window

Now, getting rid of the title bar entirely does have an important accessibility consequence: it’s much more difficult to move the application window around.

Users can drag and click their way to a sizable area in the title bar, but when using the Window Controls Overlay feature, they are limited to where the control buttons are, and must carefully place their fingers in between these buttons to move the window.

Fortunately, this can be fixed using CSS with the app-region property. This property is, for now, only supported in Chromium-based browsers and needs the -webkit- vendor prefix. 

We can use the following to animate any aspect of the app so that the window can drag it toward any point:

-webkit-app-region: drag;

It is also possible to explicitly make an element non-draggable:

-webkit-app-region: no-drag; 

These choices might be beneficial to us. We can make the entire header a dragging target, but make the search field and NEW button within it non-draggable so they can still be used as normal.

However, because the editor page doesn’t display the header, users wouldn’t be able to drag the window while editing code. Let’s take a different approach, then. We’ll create another element before our header, also absolutely positioned, and dedicated to dragging the window.

...

.drag { position: absolute; top: 0; width: 100%; height: env(titlebar-area-height, 0); -webkit-app-region: drag;}

With the above code, we’re making the draggable area span the entire viewport width, and using the titlebar-area-height variable to make it as tall as what the title bar would have been. This way, our draggable area is aligned with the window control buttons as shown below.

And, now, to make sure our search field and button remain usable:

header .search,header .new { -webkit-app-region: no-drag;}

Users can now click and drag the title bar back into the above code. It is an area that users expect to be able to use to move windows on desktop, and we’re not breaking this expectation, which is good.

Adapting to window resize

It may be useful for an app to know both whether the window controls overlay is visible and when its size changes. In our situation, there wouldn’t be enough room for the search field, logo, and button to fit because the user made the window very narrow. We would want to push them a little lower.

The Window Controls Overlay feature comes with a JavaScript API we can use to do this: navigator.windowControlsOverlay.

Three intriguing things are provided by the API:

• navigator.windowControlsOverlay.visiblelets us know whether the overlay is visible.
• navigator.windowControlsOverlay.getBoundingClientRect()lets us know the position and size of the title bar area.
• navigator.windowControlsOverlay.ongeometrychangeenables us to determine changes in size or visibility.

Let’s use this to be aware of the size of the title bar area and move the header down if it’s too narrow.

if (navigator.windowControlsOverlay) { navigator.windowControlsOverlay.addEventListener('geometrychange', () => { const { width } = navigator.windowControlsOverlay.getBoundingClientRect(); document.body.classList.toggle('narrow', width < 250); });}

In the example above, we set the narrow class on the body of the app if the title bar area is narrower than 250px. We could do something similar with a media query, but using the windowControlsOverlay API has two advantages for our use case:

• It’s only fired when the feature is supported and used, we don’t want to adapt the design otherwise.
• We can see the title bar area on different operating systems, which is great because Mac and Windows have different title bar sizes. Using a media query wouldn’t make it possible for us to know exactly how much space remains.

.narrow header { top: env(titlebar-area-height, 0); left: 0; width: 100%;}

When the window is too small, we can use the above CSS code to move our header down and the thumbnails down in accordance with this.

Thirty pixels of exciting design opportunities

Our straightforward demo app was transformed into something that felt much more connected to desktop devices by using the Window Controls Overlay feature. Something that reaches out of the usual window constraints and provides a custom experience for its users.

In reality, this feature only gives us about 30 more pixels of room and presents challenges when using the window controls. And yet, this extra room and those challenges can be turned into exciting design opportunities.

More devices of all shapes and forms get invented all the time, and the web keeps on evolving to adapt to them. To make it easier for us, web authors, to integrate more and more deeply with those devices, new features are added to the web platform. From watches or foldable devices to desktop computers, we need to evolve our design approach for the web. We can now think outside the rectangular box when building for the web.

So let’s embrace this. Let’s use the standard technologies already at our disposal, and experiment with new ideas to provide tailored experiences for all devices, all from a single codebase!

You can report bugs to the spec’s repository if you have the chance to try the Window Controls Overlay feature and have feedback on it. It’s still early in the development of this feature, and you can help make it even better. You can also check out this demo app and its source code, or the feature’s existing documentation.

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 projects that had worked well for me, such as using checklists, notion 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 ethics. And it’s remarkably easy! However, we must first focus out to understand what we’re going through.

Control the structure

Unfortunately, the capitalist system, which promotes consumerism and inequality, 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. Our well-meaning human-centered mentality has been transformed into a powerful device that encourages ever-higher levels of consumption over the past ten years due to these objectives. 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 can begin by acting on the appropriate level of the system. A program thinker named Donna H. Meadows after outlined ways to influence a system in terms of effectiveness. When you apply these to architecture, you get:

You can change things like usability results or the number of layout criticism at the lowest level of effectiveness. 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 improve its ability to achieve its goals. But that doesn’t alter the goals themselves, which means that the business will also work against your ethical-design ideals.
• The change of moral methods, toolkits, articles, conferences, workshops, and so on is what most ethical-design initiatives are currently focused on at the next level, info flows. This is also where social style has remained largely theoretical. We’ve been focusing on the wrong level of the system all this day.
• Get rules, for instance; they consistently defeat 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 income, frequently revealed through comments like” the customer didn’t ask for it” or “don’t make it too big” can smother social style.
• Changing the rules without holding formal power is extremely difficult. That’s why the next stage is so significant: self-organization. Research, bottom-up initiatives, interest projects, self-steering teams, and other such self-organization techniques all contribute to a company’s resilience and creativity. It’s precisely this diversity of viewpoints that’s needed to functionally address major structural issues like materialism, money injustice, and climate change.
• But goals and metrics are even more powerful than self-organization. Our businesses want to make more money, which means that everything and everyone in the business does their best to… make the company more income. And when I realized that income is nothing more than a measurement, I understood how important a very particular, defined measurement may be toward pushing a company in a particular 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:

The means are feasibility and desire, and viability is the aim. 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: Italian speakers are completely unaware of the distinction between feasibility and viability; both terms 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 them “imputability, 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 individual’s goal on the individual level clarifies what success entails in contrast to the typical user-centric focus on usability and satisfaction, taking into account factors like how much time and effort are required of 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.

We must consider our impact beyond the user, expanding our focus to the economy, communities, and other indirect stakeholders, as a result of having an objective on the societal level. 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 solutions promote the circular economy by generating value from waste, reusing products, and giving priority to sustainable choices. 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, it is still necessary to define these goals. 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.

This overview provides examples of metrics you can use 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 provided 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. If we set an objective to create a calm interface, we might still end up with a screen that makes people anxious, even if we set 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.

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. Making the decision to” simply” use your imagination and pick one of the many resources and knowledge resources 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 brief illustration suffice, or should you go with that enticing video? Which typeface is the most calm and inclusive? What brand-new equipment and techniques 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 impacted by decisions are present when they are made? How can you measure our effects?

The definition of success will fundamentally alter what it means to do good design.

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. It consists of two main steps: 1 ) the alignment of expectations and 2 ) the definition of success.

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. Discussion and assumptions are raised. 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 conducted an online kickoff with the client, a subject-matter expert, and two other designers for a recent freelance project that aimed to design a digital platform that facilitates US student advisors ‘ documentation and communication. 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 having respect for its desirability, viability, feasibility, and ethics is just as crucial as expressing expectations. What are the objectives in each dimension?

You need to be sure that you can trust success at this early stage because it will determine the project’s future. 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. To create a successful product, we agreed in our first meeting that a diverse user group that includes A and B is necessary. 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. A set of outer rings is used to measure the objectives, as well as an inner ring that is intended to capture ideas for those objectives. 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: What is the purpose of 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, procedure, 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

How do I get started with ethical design, many of my coworkers have questioned me over the past year? 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 design in an ethical, responsible way.

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, your first step should be to understand how your industry contributes to consumerism and inequality, how finance drives business, and how to think about how to use the system to exert the most influence. 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 to set design goals for sustainability, well-being, and equity. 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” Wouldn’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 colleagues 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 we need to get started. 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 design approach is excellent because it concentrates on what the customer truly needs, is well-practiced, and has become a standard design practice for years. But developing your CSS mobile-first should also be wonderful, 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 working on. 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.

merits of mobile-first technology

Some of the benefits of mobile-first CSS growth, and why it’s been the de facto growth practice 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 ) ).

Inhibits desktop-centric growth. It can be tempting to first focus on the desktop perspective because enhancement is done using pc servers. However, considering mobile from the beginning prevents us from getting stuck eventually; no one wants to spend their day getting a site that is focused on desktops to work on mobile devices!

Drawbacks of mobile-first

Kind declarations can be set at lower breakpoints and therefore overwritten at higher breakpoints:

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

higher CSS precision A school name declaration’s default style has then a higher specificity that has been returned to the browser’s default value. 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 CSS changes at lower views ( such as adding a new fashion ).

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.

Home value issue is overruled by the issue.

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 have to replace styles to restore them back to their defaults, which may cause issues after, especially if you are using a combination of bespoke CSS and power classes, it can also lead to more fashion precision. We won’t be able to use a power school 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 blank slate, this technique opens up some opportunities. If a product’s layout appears to be based on Flexbox at all baselines, that is acceptable and can be coded in the definition style sheet. 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 design flaws earlier 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!

Although this strategy won’t work for everyone, I urge you to try it. There are plenty of tools 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. Stick to the classic development order if you like to concentrate on the mobile view, understand the requirements for other breakpoints, and prefer to work on multiple devices at once. The key is to find common styles and exceptions so that you can include them in the appropriate stylesheet, which is a 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.

Closed media query ranges are used in real life

We overwrite the styles in the traditional mobile-first CSS, but media query ranges can be used to prevent this. 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 the dev tools in your browser 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... WHHY!! What are you waiting for? Excellent user support exists for HTTP/2.

CSS should be split.

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 need to be later, but with" Lowest" priority.

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

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 development milestone 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 of my own and that of other developers, and that testing and maintenance work is also a little more effective and streamlined.

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

In today’s data-driven environment, it’s becoming more common for a UX expert to be asked to create a personal digital experience, whether it be a common website, consumer portal, or native 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.

That’s where we begin. 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 elements of a modern, UX-driven personalization system ( or at the very least know 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 projects 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 support personalization with a content management system ( CMS ), marketing automation platform ( MAP ), or other related technology.
• The CMO, CDO, or CIO has identified personalisation as a target
• Consumer data is unclear or disjointed.
• You are running some secluded targeting strategies or A/B tests
• On the personalisation method, stakeholders 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 creating stones. These are the “levels” on the tower, which we have identified. Whether you are a UX artist, scholar, or planner, understanding the core components may help make your contribution effective.

From top to bottom, the amounts 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 you get a customized experience?
3. Contexts and Campaigns: What personalization information does the person view?
4. What constitutes a distinct, suitable audience? User Parts
5. Actionable Data: What dependable and credible information is captured by our professional platform to generate personalization?
6. What wider set of data is conceivable ( now in our environment ) to allow you to optimize?

We’ll go through each of these amounts in change. An associated deck of cards was created to highlight specific examples from each level to make this more practical. We’ve found them helpful in customisation pondering periods, and will include cases for you here.

Starting at the Top

The tower has the following elements:

North Star

What overall goal do you have with your personalization program ( big or small ) is a northern star. The North Star defines the (one ) overall mission of the personalization program. What do you hope to accomplish? North Stars cast a ghost. The darkness is bigger the sun, the star, and so on. Example of North Starts may include:

Function: Personalized based on fundamental consumer sources. Examples:” Raw” messages, basic search effects, system user settings and settings options, general flexibility, basic improvements
1. Feature: Self-contained personalisation component. Examples:” Cooked” notifications, advanced optimizations ( geolocation ), basic dynamic messaging, customized modules, automations, recommenders
2. Experience: Individualized customer experiences across a variety of interactions and customer flows. Examples: Email campaigns, landing pages, advanced messaging ( i. e. C2C chat ) or conversational interfaces, larger user flows and content-intensive optimizations ( localization ).
3. Solution: Highly distinctive, personalized solution experiences. Example: Standalone, branded encounters with personalization at their base, like the “algotorial” songs by Spotify quite as Discover Weekly.

Goals

Personalization can aid in accelerating designing with user intentions, as in any great UX design. Goals are the military and tangible metrics that may prove the entire program is effective. Start with your existing analytics and measurement system, as well as metrics that you can benchmark against. In some cases, fresh targets may be ideal. The most important thing to keep in mind is that personalisation is certainly a desired outcome. Popular targets include:

• Conversion
• Time spent on work
• Net promoter score ( NPS)
• achievement of the client

Touchpoints

Touchpoints are where the personalisation happens. One of your main responsibilities as a UX artist will be in this area. The connections available to you will depend on how your personalization and associated technology features are instrumented, and should be rooted in improving a person’s experience at a certain point in the trip. Touchpoints can be multi-device ( mobile, in-store, website ), but they can also be more specific ( web banner, web pop-up, etc. ). Here are a few illustrations:

Channel-level touchpoints

• Email: Role
• Email: When is the email open?
• In-store display ( JSON endpoint )
• Native app
• Search

Wireframe-level Touchpoints

• Web overlay
• Web alert bar
• Web banner
• Web content block
• menu on the web

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, context, 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 whether a user is engaging with the personalization process at the moment, such as when they are simply browsing the web or engaging in a deep dive. Think of it in 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

Personalization Content Model

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

We’ve written a lot more in depth about each of these models elsewhere, so be sure to 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 think about how to treat the unidentified or first-time visitor, the guest or returning visitor for whom you may have a stateful cookie ( or an equivalent post-cookie identifier ), or the logged-in visitor who is authenticated. Here are some examples from the personalization pyramid:

• Unknown
• Guest
• Authenticated
• Default
• Referred
• Role
• Cohort
• Unique Identification Number

Actionable Data

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 for the user experience, 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. Here are a few illustrations:

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 content repository and data backbone. 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 key 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 multi-faceted method of profiling that is adaptable.

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 strategy 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, every personalization activity has a common grammar, just like every sentence has 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 necessary value? Or a surgeon’s? Or a student’s? They all have fantastic sounds. 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 book.

That said, this is a guide for developers, and to that conclusion, I’d like to begin with a story—well, a voyage, actually. It’s a personal one, and I’m going to make myself a little prone along the way. I call it:

The Absurd Pate of Justin: The Tale of Justin

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, how could these fundamental skills be applied to a developing electric landscape was what piqued my interest. 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 design 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 modesty, respect, and connection, coincide with that on a more general level? I was eager to find out.

Those are amazing 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 clear 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. Quite skeuomorphic. On this one, I worked with fellow artist and dear buddy Marc Clancy, who is now a co-founder of the creative task organizing app Milanote, to outline and then play with various user interactions. Finally, I’d break it down and protocol it into a modern layout.

Along with pattern book pieces, the site even offered free downloads for Mac OS customizations: pc wallpapers that were successfully 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 had evolved into a bandwidth-sensitive, award-winning, much more accessibility-conscious website using web standards. 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 of the website’s backbone was made up of global design + illustration + news author collaboration. The backbone 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.

Why am I taking you on this journey of design memory lane, now? Two reasons.

First of all, there’s a reason for the nostalgia for the” Wild West” era of design that so many personal portfolio and design portals sprang from the past. 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 an icon library is used with selections that only vaguely relate to their respective content is used.

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 connects with people 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 this is Mac OS 7.5, 8 and 9 aren’t all that 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. How did it maintain cohesion among the group, for example, if an icon was a part of a larger system grouping ( fonts, extensions, control panels )?

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 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 use that 256-color palette to push the boundaries of a 32×32 pixel grid, expanding upon the idea of exploration. Those ridiculous constraints forced a clarity of concept and presentation that I found incredibly appealing. The challenge of throwing the digital gauntlet had been thrown at me. 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 made use of 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 endeavor. Challenge. solving problems. 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 place to be, my friend, with its pixel art-fueled presentation, ultra-focused care given to every aspect of every detail, and many of the more influential designers of the time who were invited to be news authors on the site. 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 figured out that I was one of their very limited group of news writers who could contribute content to the website.

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 really changed into a colossal asshole in just about a year of 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 victims? 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 I used to lead myself to iterate through concepts or sketches, I 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.

Some of my friendships and blossoming professional relationships almost ended up being destroyed by my ego. I was toxic in talking about design and in collaboration. But thankfully, candor was a gift from those same friends. They called me out on my unhealthy behavior.

It was a gift I initially did not accept but which I, on the whole, was able to reflect on in depth. I was soon able to accept, and process, and course correct. Although the realization made me feel uneasy, the re-awakening was necessary. 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 regression, I was able to advance in both my personal and professional design. 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, in this role,

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 foreign. 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 had to check my ego before entering it, which opened the door to those values.

An evergreen willingness to listen, learn, understand, grow, evolve, and connect yields our best work. I want to pay attention to the words “grow” and “evolve” in that statement in particular. If we are always students of our craft, we are also continually making ourselves available to evolve. Yes, we have completed years of design research. 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 equate to “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. There will never be a designer like us.

I have a creative side. Alchemy is what I do. It’s a puzzle. I don’t perform it as much as I let it be done by me.

I am imaginative. Certainly all creative people approve of this brand. Not everyone see themselves in this manner. Some innovative persons incorporate technology into their work. I value their assertion, which is true. Perhaps I even have a small fear for them. However, my thinking and being are unique.

It distracts one to apologize and qualify in progress. That’s what my mind does to destroy me. I’ll leave it alone for today. I may come back later to make amends and count. After I’ve said what I originally said. which is sufficient.

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

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

Maybe I work and work and work until the thought strikes me. Maybe it arrives right away and I don’t remind people for three weeks. Sometimes I blurt out the plan so quickly that I didn’t stop myself. like a child who discovered a medal in one of his Cracker Jacks. I occasionally manage to escape this. Yes, that is the best idea, but sometimes another people disagree. They don’t usually, and I regret losing my joy.

Joy should be saved for the meeting, where it will matter. Certainly the informal get-together that comes before that meeting with two more meetings. Nobody understands why these discussions occur. We keep saying we’re going to get rid of them, but we just keep trying to find different ways to get them. They occasionally yet are good. But occasionally they detract from the actual job. 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. also who you are and what you do. Once, I digress. I have a creative side. That is the design.

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

Don’t inquire about the procedure. I have a creative side.

I am imaginative. I have no power over my goals. And I have no power over my best tips.

I can nail ahead, fill in the blanks, or use images or information, which occasionally works. I can go for a move, which occasionally works. There is a Eureka, which has nothing to do with boiling pots and sizzling petrol, and I may be making dinner. I frequently have a sense of direction when I awaken. The idea that may have saved me disappears almost as frequently as I become aware and a part of the world once more as a senseless 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 death. But writers should be asking this, and I am not a writer. I have a creative side. Theologians are encouraged to build massive armies in their artistic world, which they insist is true. That is yet another tangent, though. And one that is miserable. Possibly on a much bigger issue than whether or not I am creative. But that’s also a step backwards from what I’m trying to say.

Often, the outcome is evasion. also suffering. Do you know the actor who is tortured by the cliché? Even when the artist is trying to write a soft drink song, a call in a worn-out comedy, or a budget ask, that word is correct.

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

Creatives understand artists.

Disadvantages are aware of cons, just like queers are aware of queers, just like real rappers are aware of actual rappers. People have a lot of regard for designers. We respect, follow, and nearly deify the excellent ones. Of course, it is dreadful to revere any person. We’ve been given a warning. We are more knowledgeable. We are aware of this. Because they are clay, like us, they squabble, they are unhappy, they regret making the most important decisions, they are weak and hungry, they can be cruel, and they can be as ridiculous as we can. But. But. However, they produce this incredible point. They give birth to something that may not exist without them and did not exist before them. They are the inspirations ‘ mother. And I suppose I should add that they are the mother of technology because it’s just lying it. Ba ho backside! Okay, that’s all said and done. Continue.

Because we compare our personal small accomplishments to those of the great ones, designers denigrate them. Wonderful graphics I‘m not Miyazaki, so I‘m not. Greatness is then that. That is glory directly from God’s heart. This unsatisfied small thing I created? It essentially fell off the turnip trailer. The carrots weren’t actually new, either.

Artists is aware that they are at best Some. That is what Mozart’s artists do, also.

I am imaginative. In my hallucinations, my former innovative managers are the ones who judge me because I haven’t worked in advertising in 30 times. And they are correct to do so. When it really counts, my mind goes flat because I am too lazy and simplistic. There is no treatment for artistic mania.

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

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 hurry. I also have a fear of the climb.

I don’t create art.

I am imaginative. Never a performer. Though as a boy, 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 aren’t in elections.

I am imaginative. Despite my belief in reason and science, I make decisions based on my own senses and instincts. and sit in the aftermath of both the successes and disasters.

I am imaginative. Every word I’ve said these may irritate another artists who see things differently. Ask a question to two artists, and three thoughts will be formed. Our dispute, our interest in it, and our commitment to our own truth, at least in my opinion, are the proof that we are creative, no matter how we does think about it.

I am imaginative. I lament my lack of taste in the areas of human knowledge that I know quite little, that is to say about everything. And I 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, no. Because living is so difficult to handle when you really look at it.

I am imaginative. 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 am imaginative. I fear that my little present will disappear.

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

I am imaginative. I think that method is the greatest secret. I think so strongly that I am actually foolish enough to post an essay I wrote into a small machine without having to go through or edit it. I swear I didn’t do 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 wonderful.

There. I believe I said it correctly.

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 produce real, positive impacts on people with disabilities. I want to take some time to talk about what’s possible in hope that we’ll get there one day. I’m no saying that there aren’t real challenges or pressing problems with AI that need to be addressed; there are.

Other words

Joe’s article spends a lot of time examining how computer vision models 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. As he rightly points out, the state of image research is currently very poor, especially for some graphic types, in large part due to the lack of context for which AI systems look at images ( which is a result of having separate “foundation” models for words analysis and picture analysis ). Today’s models aren’t trained to distinguish between images that are contextually relevant ( should probably have descriptions ) and those that are purely decorative ( couldn’t possibly need a description ) either. Nonetheless, I still think there’s possible in this area.

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

If we can specifically teach a design to consider image usage in context, it might be able to help us more swiftly distinguish between images that are likely to be attractive and those that are more descriptive. That will 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 description of the chart’s title and the type of representation it was: Pie map comparing smartphone usage to have phone usage in US households earning 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 website knew that that picture was a pie graph ( because an ship model concluded this ), imagine a world where people could ask questions like these about the creative:

• Are there more smartphone users than have phones?
• How many more?
• Is there a group of people that don’t fall into either of these pots?
• That number, how some?

For a moment, the chance to learn more about graphics and data in this way could be innovative for people who are blind and low vision as well as for those with various types of color blindness, cognitive impairments, and other issues. Putting aside the challenges of large language model ( LLM) hallucinations, where a model only makes up plausible-sounding “facts,” 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 write 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 attributable to the lack of diversity in those who create and shape them. There is still a lot of potential for algorithm development when these platforms are built with inclusive features in mind.

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. It takes into account the workplace, the communication environment, and other factors. Mentra made the decision to change the script when it came to traditional 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. That’s why diverse teams are so crucial.

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 follow a group of white men who are not white or aren’t white and who also discuss AI, it might be wise to follow those who are also disabled or who are not white. If you followed its recommendations, you might learn more about what’s happening in the AI field. These same systems should also use their understanding of biases about particular communities—including, for instance, the disability community—to make sure that they aren’t recommending any of their users follow accounts that perpetuate biases against (or, worse, spewing hate toward ) those groups.

Other ways that AI can 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 if I weren’t trying to put this together in between other tasks. In no particular order:

Voice preservation You might have heard about the voice-preserve offerings from Microsoft, Acapela, or others, or have seen the VALL-E paper or Apple’s Global Accessibility Awareness Day announcement. 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 currently hiring people with 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 well as to use only their voices to control computers and other devices, according to this research.
• Text transformation. LLMs of the current generation are quite capable of changing text without creating hallucinations. This is incredibly empowering for those who have cognitive disabilities and who may benefit from text summaries, simplified versions, or even text that has been prepared for Bionic Reading.

The importance of diverse teams and data

Our differences must be acknowledged as important. The intersections of the identities we live in have an impact on our lived experiences. These lived experiences—with all their complexities ( and joys and pain ) —are valuable inputs to the software, services, and societies that we shape. Our differences must be reflected in the data we use to develop new models, and those who provide that valuable information must be compensated for doing so. Stronger models can be created using inclusive data sets, which lead to more equitable outcomes.

Want a model that doesn’t demean or patronize or objectify people with disabilities? Make sure that the training data includes information about disabilities written by people with a range of disabilities.

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 soon replace human copy editors when it comes to sensitivity reading.

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

I have no doubts about how dangerous AI will be for people today, tomorrow, and for the rest of the world. However, I think we should also acknowledge this and make thoughtful, thoughtful, and intentional changes to our approaches to AI that will also reduce harm over time with an emphasis on accessibility ( and, in general, inclusion ). 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 get into a routine pattern, a brand-new concept or technology emerges to shake things up and completely alter our planet.

How we got below

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

the development of internet requirements

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

Server-side language like PHP, Java, and.NET took Perl as the primary back-end computers, and the cgi-bin was tossed in the garbage bin. With these improved server-side software, the first period of internet programs started with content-management techniques (especially those used in blogs like Blogger, Grey Matter, Movable Type, and WordPress ) In the mid-2000s, AJAX opened gates for sequential interaction between the front end and back close. Pages was now revise their content without having to reload. A grain of Script frameworks like Prototype, YUI, and ruby arose to aid developers develop more credible client-side conversation across browsers that had wildly varying levels of standards support. Techniques like photo alternative enable the use of fonts by skilled developers and developers. And technology like Flash made it possible to include movies, sports, and even more engagement.

These new methods, requirements, and systems greatly boosted the sector’s growth. Web style flourished as creators and designers explored more different styles and designs. However, we also relied heavily on exploits. 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. Display and photo substitute for specialty styles was a great start toward varying the designs from the big five, but both tricks introduced convenience and efficiency issues. And JavaScript libraries made it simple for anyone to add a dash of interaction to pages, even at the expense of double, even quadrupling, the download size of basic websites.

The web as software platform

The front-end and back-end symbiosis continued to improve, leading to the development of the modern web application. 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. Additionally, Neal Agarwal takes a fascinating tour of” Internet Artifacts.”

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 a website, from the tried-and-true classic of hosting plain HTML files to static site generators to content management systems of all varieties. The fracturing of social media also comes with a cost: we lose crucial infrastructure for discovery and connection. Webmentions, RSS, ActivityPub, and other IndieWeb tools can be useful in this regard, 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.

Especially with efforts like Interop, browser support for CSS, JavaScript, and other standards like web components has increased. New technologies gain support across the board in a fraction of the time that they used to. When I first learn about a new feature, I frequently discover that its coverage is already over 80 % when I check the browser support. 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.

We can prototype almost any idea today with just a few commands and a few lines of code. All the tools that we now have available make it easier than ever to start something new. However, as the initial cost of these frameworks may be saved in the beginning, it eventually becomes due as their upkeep and maintenance becomes a component 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 previously 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 ), users frequently have no choice but to use 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 of those user-friendly tools. They may make your job a little easier today, but how do they affect everything else? What does each user pay? 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. Even after a few years, the same can’t be said about websites created with frameworks.

Design with care. Consider the effects of each choice, whether your craft 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 constantly learn, you also develop. 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, and the techniques you learn in one day may be useful for guiding future experiments.

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 try something new. Build a playground for ideas. In your own bizarre science lab, perform bizarre 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. Share what you think has worked for you as you experiment, play, and learn. 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.

Make a move and make it happen.

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, share it, improve it, re-create it, or create something new. Learn. Make. Share. grow. Rinse and repeat. Everything will change whenever you believe you’ve mastered the web.

The personalization gap is real, 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 powerful personalization depends so much on each group’s talent, technology, and market position.

But you can ensure that your group has packed its carriers reasonably.

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 developed, budgeted, and given priority 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 customisation 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 continuing investments. Create 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 personalization work, 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.

Successful seminars consistently save time, money, and overall well-being by separating successful potential endeavors from unsuccessful ones.

A personalization training involves a protracted work of testing and function development. It’s never a switch-flip in your software load. It’s ideal managed as a delay that usually evolves through three actions:

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 democratic personalization platform and why we’re field-testing an following deck of cards: we believe that there’s a foundation grammar, a set of “nouns and verbs” that your organization can use to style 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 your kitchen.

How long does it take to cook up a prepersonalization workshop? The evaluation activities that we suggest include can last for a number of weeks ( and frequently do ). 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 the potential, the readiness and drive of your team, and your leadership.
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 in your company. A connected experience, in our parlance, is any UX requiring the orchestration of multiple systems of record on the backend. A marketing-automation platform and a content-management system could be used together. It could be a digital-asset manager combined with a customer-data platform.

Give examples of connected experience interactions that you admire, find familiar, or even dislike, as examples of consumer and business-to-business examples. This should cover a representative range of personalization patterns, including automated app-based interactions ( such as onboarding sequences or wizards ), notifications, and recommenders. These cards contain a catalog, which we have. 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 methods 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 they would like to place your company’s emphasis on your product or service. Naturally, you can’t prioritize all of them. Here, the goal is to show how various departments may view their own benefits from the effort, which can vary 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 ensuring data and privacy is a major challenge too much? Do you have content metadata needs that you have to address? ( We’re pretty sure you do; it’s just a matter of recognizing the need’s magnitude and its solution. ) In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six protracted behavior that is harmful to the development of our country.

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. According to research, 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

What will you need next to bring your personalized recipes to life. Personalization engines, which are robust software suites for automating and expressing dynamic content, can intimidate new customers. Their capabilities are broad and potent, and they give you a variety of ways to organize your company. This presents the question: Where do you begin when you’re configuring a connected experience?

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

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

You’ll ensure that you have everything you need to create your desired interaction ( or that you can determine what needs to be added to your pantry like a good product manager ) and that you have validated 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 strategy 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 a 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 newly registered user is a subscriber and is able to highlight the breadth of the content catalog.
3. Winback automation: Before their subscription lapses or after a recent failed renewal, a user is sent an email that gives them a promotional offer to suggest that they reconsider renewing or to remind them to renew.

A good preworkshop activity might be to consider a first draft of what these cards might be for your organization, though we’ve also found that cocreating the recipes themselves can sometimes help this process. 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.

Architecture must be improved to produce 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’t stand the heat, in fact…

Personalization technology opens a doorway into a confounding ocean of possible designs. Only a disciplined and highly collaborative approach will produce the necessary concentration and intention for success. 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 your organization’s masters. 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, you’ll have solid ground for success if you use the same cookbook and the same recipes. 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 shows since I was a child. I loved the figures and the excitement—but most of all the reports. 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 sky in. But they never went any farther. However, I did end up working in user experience ( UI). Today, I realize that there’s an element of drama to UX— I hadn’t actually considered it before, but consumer analysis is story. And you must show a compelling story to entice stakeholders, such as the product team and decision-makers, to learn more in order to get the most out of consumer research.

Think of your favorite film. It more than likely follows a three-act construction that’s frequently seen in movies: the layout, the conflict, and the resolution. The second act shows what exists now, and it helps you get to understand the characters and the challenges and problems that they face. Act two sets the scene for the fight and introduces the behavior. Here, difficulties grow or get worse. The solution comes in the third and final action. 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 introducing 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. Design is enhanced by customer research. It keeps it on trail, pointing to problems and opportunities. Being aware of problems with your goods and taking corrective actions can help you be ahead of your competition.

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 research.

Act one: layout

The setup consists entirely in comprehending the history, and that’s where basic research comes in. Basic research ( also called conceptual, discovery, or preliminary research ) helps you understand people and identify their problems. Just like in the movies, you’re learning about the difficulties users face, what options are available, and how those challenges impact them. To do basic research, you may conduct situational inquiries or journal studies ( or both! ), which may assist you in identifying both challenges and options. It doesn’t need to get a great investment in time or money.

What is the least sustainable ethnography that Erika Hall can do is spend fifteen minutes with a consumer and say,” Walk me through your day yesterday. That’s it. Current that one ask. Locked up and listen to them for 15 days. Do everything in your power to protect both your objectives and yourself. Bam, you’re doing ethnography”. According to Hall, “[This ] will probably 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”.

I think this makes sense. And I love that this makes consumer studies so visible. You don’t need to make a lot of paperwork; you can only attract people and do it! 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 work 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 supplement what you’ve heard in the fundamental studies by using any more user data that you can obtain, such as surveys or analytics, to make recommendations that may need to be investigated further, you might as well use those that can be drawn from those that you can obtain. 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 participants are now doing the same. Their concern may be with their company, which may be losing money because people are unable to complete specific tasks. Or probably they do connect with people ‘ problems. In either case, work one serves as your main strategy for piqueing interest and investment from the participants.

When partners 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 help goods team become more user-centric. This gains everyone—users, the goods, and partners. It’s similar to winning an Oscar in terms of filmmaking because it frequently results in your item receiving good reviews and success. And this can be an opportunity for participants to repeat this process with different products. Knowing how to show a good story is the only way to convince partners to worry about doing more research, and story is the key to this method.

This brings us to work two, where you incrementally review a design or idea to see whether it addresses the problems.

Act two: fight

Act two is all about digging deeper into the issues that you identified in operate one. In order to evaluate a potential alternative ( such as a design ), you typically conduct vertical research, such as usability tests, to see if it addresses the problems you identified. The issues may include unfulfilled needs or problems with a circulation or procedure that’s tripping users off. More issues may come up in the process, much like in action two of a movie. It’s ok that you learn more about the characters as they grow and develop through this work.

According to Jakob Nielsen, five users should be normally in usability tests, which means that this number of users can generally 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 second user, you are wasting your time by observing the same findings consistently 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 memorable and accessible to other stakeholders when presenting 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 watching a movie as opposed to remote testing like attending a play. 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 meet users at their location to conduct your research. With either option, you get to see how things work in context, things come up that wouldn’t have in a lab environment—and conversion can shift in entirely different directions. 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 remote usability tests frequently lack.

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

You can ask real users questions to understand their thoughts and understanding of the solution as a result of usability testing, whether it is conducted remotely or in person. 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 is in the second act, but there are also potential surprises in the third. 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 also frequently the only research technique that some stakeholders believe they ever need, and too frequently. 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. Because you’re narrowing the scope of what you’re receiving feedback on without understanding 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 interested parties. It allows the whole team to hear users ‘ feedback together, ask questions, and discuss what’s possible within the project’s constraints. And it gives the UX design and research teams more time to clarify, suggest alternatives, or provide more context for their choices. So you can get everyone on the same page and get agreement on the way forward.

This act is primarily told in voiceover with some audience participation. The researcher is the narrator, who paints a picture of the issues and what the future of the product could look like given the things that the team has learned. They 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” set up a conflict that needs to be resolved” using the same methods as great storytellers, Duarte writes. ” 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 visual, like quick sketches of how a new design could look that solves 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. This stage provides stakeholders with the next steps and, hoped, the motivation to take those steps!

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

Act one: You meet the protagonists ( the users ) and the antagonists ( the problems affecting users ). The plot begins here. 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.

Act two: Next, there’s character development. The protagonists encounter problems and difficulties, 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 storytelling, presentation decks, and digital media in act three. The output of these can be: presentation decks, video clips, audio clips, and pictures.

The researcher plays a variety of roles, including producer, director, and 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. By the end, the parties should leave with a goal and an eagerness to address 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.