Blog

The mobile-first style approach is great—it focuses on what really matters to the consumer, it’s well-practiced, and it’s been a popular style design for years. But developing your CSS mobile-first should also be fantastic, too…right?

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

On your own tasks, mobile-first CSS may yet be the best tool for the job, but first you need to assess just how ideal 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.

Benefits of mobile-first

Some of the points to enjoy with mobile-first CSS creation —and why it’s been the de facto growth strategy for thus long—make a lot of feeling:

Development order. One thing you definitely get from mobile-first is a great development hierarchy—you only focus on the cellular view and get developing.

Tried and tested. 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 smart watch is the simplest and probably the most important, as it encompasses all the important person journeys, and typically accounts for a higher proportion of user visits ( depending on the project ).

Prevents desktop-centric development. As development is done using desktop computers, it can be tempting to initially focus on the desktop view. But thinking about mobile from the start prevents us from getting stuck later on, no one wants to spend their time retrofitting a desktop-centric site to work on mobile devices!

Disadvantages of mobile-first

Setting style declarations and then overwriting them at higher breakpoints can lead to undesirable ramifications:

More complexity. The farther up the breakpoint hierarchy you go, the more unnecessary code you inherit from lower breakpoints.

Higher CSS specificity. Styles that have been reverted to their browser default value in a class name declaration now have a higher specificity. This can be a headache on large projects when you want to keep the CSS selectors as simple as possible.

Requires more regression testing. Changes to the CSS at a lower view ( like adding a new style ) requires all higher breakpoints to be regression tested.

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.

The problem of property value overrides

There is nothing inherently wrong with overwriting values, CSS was designed to do just that. Still, inheriting incorrect values is unhelpful and can be burdensome and inefficient. It can also lead to increased style specificity when you have to overwrite styles to reset them back to their defaults, something that may cause issues later on, especially if you are using a combination of bespoke CSS and utility classes. We won’t be able to use a utility class for a style that has been reset with a higher specificity.

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

This approach opens up some opportunities, as you can look at each breakpoint as a clean slate. If a component’s layout looks like it should be based on Flexbox at all breakpoints, it’s fine and can be coded in the default style sheet. But if it looks like Grid would be much better for large screens and Flexbox for mobile, these can both be done entirely independently when the CSS is put into closed media query ranges. Also, developing simultaneously requires you to have a good understanding of any given component in all breakpoints up front. This can help surface issues in the design 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!

Though this approach isn’t going to suit everyone, I encourage you to give it a try. There are plenty of tools out there to help with concurrent development, such as Responsively App, Blisk, and many others.

Having said that, I don’t feel the order itself is particularly relevant. If you are comfortable with focusing on the mobile view, have a good understanding of the requirements for other breakpoints, and prefer to work on one device at a time, then by all means stick with the classic development order. The important thing is to identify common styles and exceptions so you can put them in the relevant stylesheet—a sort of manual tree-shaking process! 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 in practice

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

• smaller than 768
• from 768 to below 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 due to the browser's limit of concurrent requests (typically around six ). As a consequence, the use of image sprites and CSS bundling was the norm, with all the CSS being downloaded in one go, as one stylesheet with 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. This allows us to separate the CSS into multiple files by media query. The clear benefit of this is the browser can now request the CSS it currently needs with a higher priority than the CSS it doesn't. This is more performant and can reduce the overall time page rendering is blocked.

Which HTTP version are you using?

To determine which version of HTTP you're using, go to your website and open your browser's dev tools. Next, select the Network tab and make sure the Protocol column is visible. If "h2" is listed under Protocol, it means HTTP/2 is being used.

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

Also, if your site is still using HTTP/1... WHY?!! What are you waiting for? There is excellent user support for HTTP/2.

Splitting the CSS

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

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

With bundled CSS, the browser will have to download the CSS file and parse it before rendering can start.

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. 

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

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 uptake of mobile-first CSS was a really important milestone in web development, it has helped front-end developers focus on mobile web applications, rather than developing sites on desktop and then 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, focusing on the CSS in its own right, always mindful of what is the default setting and what's an exception, seems like the natural next step. I've started noticing small simplifications in my own CSS, as well as other developers', and that testing and maintenance work is also a bit more simplified and productive.

In general, simplifying CSS rule creation whenever we can is ultimately a cleaner approach than going around in circles of overrides. But whichever methodology you choose, it needs to suit the project. Mobile-first may—or may not—turn out to be the best choice for what's involved, but first you need to solidly understand the trade-offs you're stepping into.

As a UX skilled in today’s data-driven landscape, it’s extremely likely that you’ve been asked to design a personal digital experience, whether it’s a common website, user portal, or local application. But 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 come in. 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? The Personalization Pyramid is a designer-centric model for standing up human-centered personalisation programs, spanning information, classification, content delivery, and general goals. By using this strategy, you will be able to understand the core elements of a modern, UX-driven personalization system ( or at the very least understand enough to get started ).

Getting Started

For the sake of this article, we’ll suppose you’re already familiar with the basics of online personalization. A nice guide can be found these: Website Personalization Planning. While Graphic jobs in this area can take on several different forms, they usually stem from identical starting positions.

Common scenarios for starting a personalisation task:

• Your organization or client purchased a content management system ( CMS ) or marketing automation platform ( MAP ) or related technology that supports personalization
• The CMO, CDO, or CIO has identified personalisation as a target
• User data is disjointed or confusing
• You are running some secluded targeting strategies or A/B tests
• Partners disagree on personalization technique
• 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. We’ve captured these as the “levels” on the tower. Whether you are a UX artist, scholar, or planner, understanding the core components may help make your contribution effective.

From top to bottom, the amounts include:

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

We’ll go through each of these amounts in turn. To help make this practical, we created an following deck of cards to demonstrate specific examples from each degree. We’ve found them helpful in customisation pondering periods, and will include cases for you here.

Starting at the Top

The parts of the pyramids are as follows:

North Star

A northern star is what you are aiming for total with your personalization system ( big or small ). The North Star defines the (one ) overall mission of the personalization program. What do you wish to achieve? North Stars cast a ghost. The bigger the sun, the bigger the dark. Example of North Starts may incorporate:

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

Goals

As in any good UX design, personalization can help accelerate designing with customer intentions. Goals are the tactical and measurable metrics that will prove the overall program is successful. A good place to start is with your current analytics and measurement program and metrics you can benchmark against. In some cases, new goals may be appropriate. The key thing to remember is that personalization itself is not a goal, rather it is a means to an end. Common goals include:

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

Touchpoints

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

Channel-level Touchpoints

• Email: Role
• Email: Time of open
• In-store display ( JSON endpoint )
• Native app
• Search

Wireframe-level Touchpoints

• Web overlay
• Web alert bar
• Web banner
• Web content block
• Web menu

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

Contexts and Campaigns

Once you’ve outlined some touchpoints, you can consider the actual 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 programmatically be shown at certain touchpoints to certain user segments, as defined by user data. At this stage, we find it helpful to consider two separate models: a context model and a content model. The context helps you consider the level of engagement of the user at the personalization moment, for example a user casually browsing information vs. doing a deep-dive. Think of it in terms of information retrieval behaviors. The content model can then help you determine what type of personalization to serve based on the context ( for example, an” Enrich” campaign that shows related articles may be a suitable supplement to 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 extensively about each of these models elsewhere, so if you’d like to read more you can check out Colin’s Personalization Content Model and Jeff’s Personalization Context Model.

User Segments

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 ). At a minimum you will likely need to consider how to treat the unknown or first-time visitor, the guest or returning visitor for whom you may have a stateful cookie ( or equivalent post-cookie identifier ), or the authenticated visitor who is logged in. Here are some examples from the personalization pyramid:

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

Actionable Data

Every organization with any digital presence has data. It’s a matter of asking what data you can ethically collect on users, its inherent reliability and value, as to how can you use it ( sometimes known as “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 represents multiple advantages on the UX front, including being relatively simple to collect, more likely to be accurate, and less susceptible to the” creep factor” of third-party data. So a key part of your UX strategy should be to determine what the best form of data collection is on your audiences. Here are some examples:

There is a progression of profiling when it comes to recognizing and making decisioning about different audiences and their signals. It tends to move towards more granular constructs about smaller and smaller cohorts of users as time and confidence and data volume grow.

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 a strong data backbone and content repository is a prerequisite for optimization. But these approaches should be considered as part of the larger roadmap and may indeed help accelerate the organization’s overall progress. Typically at this point you will partner with key stakeholders and product owners to design a profiling model. The profiling model includes defining approach to configuring profiles, profile keys, profile cards and pattern cards. A multi-faceted approach to profiling which makes it scalable.

Pulling it Together

While the cards comprise the starting point to an inventory of sorts ( we provide blanks for you to tailor your own ), a set of potential levers and motivations for the style of personalization activities you aspire to deliver, they are more valuable when thought of in a grouping.

In assembling a card “hand”, one can begin to trace the entire trajectory from leadership focus down through a strategic and tactical execution. It is also at the heart of the way both co-authors have conducted workshops in assembling a program backlog—which is a fine subject for another article.

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 sustainable personalization strategy must consider near, mid and long-term goals. 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. That said, there is a common grammar to all personalization activities, just like every sentence has nouns and verbs. These cards attempt to map that territory.

Humility, a writer’s necessary value—that has a good ring to it. What about sincerity, an business manager’s necessary value? Or a doctor’s? Or a student’s? They all good wonderful. When humility is our guiding light, the course is usually available for fulfillment, development, relation, and commitment. In this book, we’re going to discuss about why.

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 private one, and I’m going to make myself a little prone along the way. I call it:

The Tale of Justin’s Preposterous Pate

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. Though I had been fully trained in graphic design, font, and design, what fascinated me was how these classic skills may be applied to a budding online landscape. This style would eventually form the rest of my profession.

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

The later ‘ 90s and early 2000s were the so-called” Wild West” of website design. Manufacturers at the time were all figuring out how to use layout and visual connection to the online environment. What were the laws? How may we break them and also engage, entertain, and present information? At a more micro level, how was my values, inclusive of modesty, admiration, and link, coincide in combination with that? I was eager to find out.

Though I’m talking about a diverse time, those are amazing factors between non-career connections and the world of style. What are your main passions, or ideals, that elevate medium? It’s basically the same idea we discussed previously on the immediate parallels between what fulfills you, independent of the visible or electronic realms, the primary themes are all the same.

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 example, this iteration of my personal portfolio site (” the pseudoroom” ) from that era was experimental, if not a bit heavy- handed, in the visual communication of the concept of a living sketchbook. Very skeuomorphic. I collaborated with fellow designer and dear friend Marc Clancy ( now a co-founder of the creative project organizing app Milanote ) on this one, where we’d first sketch and then pass a Photoshop file back and forth to trick things out and play with varied user interactions. Then, I’d break it down and code it into a digital layout.

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

From around the same time, GUI Galaxy was a design, pixel art, and Mac-centric news portal some graphic designer friends and I conceived, designed, developed, and deployed.

Design news portals were incredibly popular during this period, featuring ( what would now be considered ) Tweet-size, small-format snippets of pertinent news from the categories I previously mentioned. If you took Twitter, curated it to a few categories, and wrapped it in a custom-branded experience, you’d have a design news portal from the late 90s / early 2000s.

We as designers had evolved and created a bandwidth-sensitive, web standards award-winning, much more accessibility-conscious website. Still ripe with experimentation, yet more mindful of equitable engagement. You can see a couple of content panes here, noting general news (tech, design ) and Mac-centric news below. 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 site’s backbone was a homegrown CMS, with the presentation layer consisting of global design + illustration + news author collaboration. And the collaboration effort here, in addition to experimentation on a’ brand’ and content delivery, was hitting my core. We were designing something bigger than any single one of us and connecting with a global audience.

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

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

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

Today’s web design has been in a period of stagnation. 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. Maybe an icon library is employed with selections that vaguely relate to their respective content.

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 responsive presentation that meets human beings wherever they’re engaging from. 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 Problems

Websites during this period were often designed and built on Macs whose OS and desktops looked something like this. This is Mac OS 7.5, but 8 and 9 weren’t that different.

Desktop icons fascinated me: how could any single one, at any given point, stand out to get my attention? In this example, the user’s desktop is tidy, but think of a more realistic example with icon pandemonium. Or, say an icon was part of a larger system grouping ( fonts, extensions, control panels ) —how did it also maintain cohesion amongst a group?

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

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

Expanding upon the notion of exploration, I wanted to see how I could push the limits of a 32×32 pixel grid with that 256-color palette. Those ridiculous constraints forced a clarity of concept and presentation that I found incredibly appealing. The digital gauntlet had been tossed, and that challenge fueled 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, utilizing the only tool available at the time to create icons called ResEdit. ResEdit was a clunky, built-in Mac OS utility not really made for exactly what we were using it for. At the core of all of this work: Research. Challenge. Problem- solving. Again, these core connection-based values are agnostic of medium.

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

This is K10k, short for Kaliber 1000. K10k was founded in 1998 by Michael Schmidt and Toke Nygaard, and was the design news portal on the web during this period. With its pixel art-fueled presentation, ultra-focused care given to every facet and detail, and with many of the more influential designers of the time who were invited to be news authors on the site, well… it was the place to be, my friend. 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. Eventually, K10k noticed and added me as one of their very select group of news authors to contribute content to the site.

Amongst my personal work and side projects —and now with this inclusion—in the design community, this put me on the map. My design work also began to be published in various printed collections, in magazines domestically and overseas, and featured on other design news portals. With that degree of success while in my early twenties, something else happened:

I evolved—devolved, really—into a colossal asshole ( and in just about a year out of art school, no less ). The press and the praise became what fulfilled me, and they went straight to my head. They inflated my ego. I actually felt somewhat superior to my fellow designers.

The casualties? My design stagnated. Its evolution—my evolution — stagnated.

I felt so supremely confident in my abilities that I effectively stopped researching and discovering. When previously sketching concepts or iterating ideas in lead was my automatic step one, I instead leaped right into Photoshop. I drew my inspiration from the smallest of sources ( and with blinders on ). Any critique of my work from my peers was often vehemently dismissed. The most tragic loss: I had lost touch with my values.

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

Admittedly, it was a gift I initially did not accept but ultimately was able to deeply reflect upon. I was soon able to accept, and process, and course correct. The realization laid me low, but the re-awakening was essential. I let go of the “reward” of adulation and re-centered upon what stoked the fire for me in art school. Most importantly: I got back to my core values.

Always Students

Following that short-term regression, I was able to push forward in my personal design and career. And I could self-reflect as I got older to facilitate further growth and course correction as needed.

As an example, let’s talk about the Large Hadron Collider. 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”. Thanks, 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 rendering of what’s actually happening inside the Collider during any given particle collision event and are often considered works of art unto 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. To that end, in this role,

I cut my teeth on usability testing, working with the Fermilab team to iterate and improve the interface. How they spoke and what they spoke about was like an alien language to me. 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 observation experience: going to the Fermilab location and observing how the physicists used the tool in their actual environment, on their actual 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. This enabled them to pore over reams of data during the day and ease their eye strain. And Fermilab and CERN are government entities with rigorous accessibility standards, so my knowledge in that realm also grew. The barrier-free design was another essential form of connection.

So to those core drivers of my visual problem-solving soul and ultimate fulfillment: discovery, exposure to new media, observation, human connection, and evolution. What opened the door for those values was me checking my ego before I walked through it.

An evergreen willingness to listen, learn, understand, grow, evolve, and connect yields our best work. In particular, I want to focus on the words’ grow’ and ‘ evolve’ in that statement. If we are always students of our craft, we are also continually making ourselves available to evolve. Yes, we have years of applicable design study under our belt. Or the focused lab sessions from a UX bootcamp. Or the monogrammed portfolio of our work. Or, ultimately, decades of a career behind us.

But all that said: experience does not equal “expert”.

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

I am a artistic. What I do is alchemy. It is a secret. I do not so many do it, since let it be done through me.

I am a artistic. Certainly all creative people like this brand. Certainly all see themselves this method. Some creative individuals see knowledge in what they do. That is their reality, and I regard it. Sometimes I even envy them, a minor. But my approach is different—my becoming is unique.

Apologizing and qualifying in advance is a diversion. That’s what my head does to destroy me. I set it aside for today. I may come back later to forgive and qualify. After I’ve said what I came to say. Which is challenging enough.

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

Sometimes it does come that approach. Maybe what I need to build comes in an instant. I have learned not to say it at that time, because if you admit that sometimes the plan only comes and it is the best idea and you know it is the best idea, they think you don’t work hard enough.

Maybe I work and work and work until the plan comes. Often it comes suddenly and I don’t tell people for three weeks. Maybe I’m so excited by the idea that came quickly that I blurt it out, can’t help myself. Like a child who found a medal in his Cracker Jacks. Maybe I get away with this. Maybe another persons agree: yes, that is the best idea. Most times they don’t and I regret having given way to joy.

Passion is best saved for the conference where it will make a difference. Certainly the casual get-together that accompanies that gathering by two different meetings. Anyone knows why we have all these sessions. We keep saying we’re doing away with them, but then only finding different ways to include them. Sometimes they are also great. But other days they are a distraction from the actual labor. The percentages between when conferences are important, and when they are a sad distraction, vary, depending on what you do and where you do it. And who you are and how you do it. Suddenly I digress. I am a artistic. That is the style.

Often many hours of hard and persistent work produce something that is rarely serviceable. Maybe I have to accept that and move on to the next task.

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

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

I can nail aside, surround myself with information or photos, and maybe that works. I can go for a walk, and occasionally that functions. I may be making breakfast and there’s a Eureka having nothing to do with sizzling oil and boiling pots. Usually I know what to do the moment I wake up. And then, nearly as often, as I become aware and part of the world once, the idea that may have saved me turns to vanishing sand in a senseless storm of nothingness. For imagination, I believe, comes from that other world. The one we enter in aspirations, and possibly, before conception and after death. But that’s for writers to know, and I am not a writer. I am a innovative. And it’s for theologians to large forces about in their artistic world that they insist is true. But that is another diversion. And a miserable one. Even on a much more important issue than whether I am a inventive or not. But nevertheless a tangent from what I came here to say.

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

Some people who hate being called artistic may be closeted artists, but that’s between them and their angels. No offence meant. Your reality is correct, too. But mine is for me.

Creatives identify artists.

Creatives identify creatives like faggots recognize queers, like true rappers recognize true performers, like cons know cons. Creatives feel enormous regard for creatives. We love, respect, emulate, and nearly deify the excellent ones. To revere any man is, of course, a horrible mistake. We have been warned. We know much. We know people are really people. They dispute, they are depressed, they regret their most critical decisions, they are weak and thirsty, they can be cruel, they can be just as terrible as we can, if, like us, they are clay. But. But. But they make this wonderful issue. They beginning things that did not exist before them, and could not occur without them. They are the mother of tips. And I suppose, since it’s only lying it, I have to put that they are the mother of technology. Ba ho bum! Okay, that’s done. Continue.

Creatives belittle our personal small successes, because we compare them to those of the wonderful people. Wonderful video! Also, I‘m no Miyazaki. Now THAT is glory. That is brilliance directly from the mind of God. This half-starved small item that I made? It more or less fell off the back of the pumpkin trailer. And the carrots weren’t actually new.

Creatives knows that, at best, they are Salieri. Yet the creatives who are He think that.

I am a innovative. I haven’t worked in advertising in 30 years, but in my hallucinations, it’s my previous artistic managers who judge me. And they are appropriate to do so. I am very lazy, overly simplistic, and when it actually counts, my mind goes blank. There is no supplement for innovative function.

I am a artistic. Every date I make is an experience that makes Indiana Jones look like a retiree snoring in a balcony seat. The longer I remain a artistic, the faster I am when I do my job and the longer I brood and move in circles and gaze blankly before I do that job.

I am also 10 times faster than people who are not artistic, or people who have just been imaginative a short while, or people who have just been properly imaginative a short while. It’s just that, before I work 10 times as fast as they do, I spend twice as long as they do putting the work out. I am that confident in my ability to do a great task when I put my mind to it. I am that attached to the excitement scramble of delay. I am also that scared of the climb.

I am not an actor.

I am a artistic. Not an actor. Though I dreamed, as a boy, of eventually being that. Some of us disparage our products and like ourselves because we are not Michelangelos and Warhols. That is narcissism—but at least we aren’t in elections.

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

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

I am a artistic. I lament my lack of taste in the places about which I know quite small, which is to say almost all areas of human knowledge. And I trust my preference above all other items in the regions closest to my soul, or perhaps, more precisely, to my passions. Without my passions, I would probably have to spend my time looking career in the eye, and virtually none of us can do that for longer. No seriously. No truly. Because many in existence, if you really look at it, is terrible.

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

Working saves me from worrying about job.

I am a artistic. I live in horror of my little present immediately going ahead.

I am a artistic. I am very active making the next thing to spend too much time seriously considering that almost nothing I make does come anywhere near the glory I awkwardly aspire to.

I am a artistic. I believe in the greatest mystery of operation. I believe in it so much, I am actually foolish enough to submit an article I dictated into a small machine and didn’t take time to evaluate or update. I won’t do this often, I promise. But I did it just now, because, as afraid as I might be of your seeing through my pitiful gestures toward the beautiful, I was even more afraid of forgetting what I came to say.

There. I think I’ve said it.

I’d like you to consider this a “yes … and” piece to complement Joe’s post. I’m not trying to reject any of what he’s saying but instead provide some awareness to projects and possibilities where AI can generate substantial differences for people with disabilities. To be clear, I’m not saying that there aren’t true threats or pressing problems with AI that need to be addressed—there are, and we’ve needed to address them, like, yesterday—but I want to take a little time to talk about what’s possible in hope that we’ll get there one day.

Other text

Joe’s part spends a lot of time talking about computer-vision types generating other words. He highlights a ton of true issues with the current state of things. And while computer-vision concepts continue to improve in the quality and complexity of information in their information, their effects aren’t wonderful. As he rightly points out, the current state of image analysis is pretty poor—especially for certain image types—in large part because current AI systems examine images in isolation rather than within the contexts that they’re in ( which is a consequence of having separate “foundation” models for text analysis and image analysis ). Today’s models aren’t trained to distinguish between images that are contextually relevant ( that should probably have descriptions ) and those that are purely decorative ( which might not need a description ) either. Still, I still think there’s potential in this space.

As Joe mentions, human-in-the-loop authoring of alt text should absolutely be a thing. And if AI can pop in to offer a starting point for alt text—even if that starting point might be a prompt saying What is this BS? That’s not right at all … Let me try to offer a starting point— I think that’s a win.

Taking things a step further, if we can specifically train a model to analyze image usage in context, it could help us more quickly identify which images are likely to be decorative and which ones likely require a description. That will help reinforce which contexts call for image descriptions and it’ll improve authors ‘ efficiency toward making their pages more accessible.

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 suppose that you came across a chart whose description was simply the title of the chart and the kind of visualization it was, such as: Pie chart comparing smartphone usage to feature phone usage among US households making under$ 30, 000 a year. ( That would be a pretty awful alt text for a chart since that would tend to leave many questions about the data unanswered, but then again, let’s suppose that that was the description that was in place. ) If your browser knew that that image was a pie chart ( because an onboard model concluded this ), imagine a world where users could ask questions like these about the graphic:

• Do more people use smartphones or feature phones?
• How many more?
• Is there a group of people that don’t fall into either of these buckets?
• How many is that?

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

Taking things a step further: What if you could ask your browser to simplify a complex chart? What if you could ask it to isolate a single line on 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 could ask it to swap colors for patterns? Given these tools ‘ chat-based interfaces and our existing ability to manipulate images in today’s AI tools, that seems like a possibility.

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

Matching algorithms

Safiya Umoja Noble absolutely hit the nail on the head when she titled her book Algorithms of Oppression. While her book was focused on the ways that search engines reinforce racism, I think that it’s equally true that all computer models have the potential to amplify conflict, bias, 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 lot of this stems from a lack of diversity among the people who shape and build them. When these platforms are built with inclusively baked in, however, there’s real potential for algorithm development to help people with disabilities.

Take Mentra, for example. They are an employment network for neurodivergent people. They use an algorithm to match job seekers with potential employers based on over 75 data points. On the job-seeker side of things, it considers each candidate’s strengths, their necessary and preferred workplace accommodations, environmental sensitivities, and so on. On the employer side, it considers each work environment, communication factors related to each job, and the like. As a company run by neurodivergent folks, Mentra made the decision to flip the script when it came to typical employment sites. 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.

When more people with disabilities are involved in the creation of algorithms, that can reduce the chances that these algorithms will inflict harm on their communities. That’s why diverse teams are so important.

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 example, if you were to follow a bunch of nondisabled white male academics who talk about AI, it could suggest that you follow academics who are disabled or aren’t white or aren’t male who also talk about AI. If you took its recommendations, perhaps you’d get a more holistic and nuanced understanding of what’s happening in the AI field. These same systems should also use their understanding of biases about particular communities—including, for instance, the disability community—to make sure that they aren’t recommending any of their users follow accounts that perpetuate biases against (or, worse, spewing hate toward ) those groups.

Other ways that AI can helps people with disabilities

If I weren’t trying to put this together between other tasks, I’m sure that I could go on and on, providing all kinds of examples of how AI could be used to help people with disabilities, but I’m going to make this last section into a bit of a lightning round. In no particular order:

Voice preservation. You may have seen the VALL-E paper or Apple’s Global Accessibility Awareness Day announcement or you may be familiar with the voice-preservation offerings from Microsoft, Acapela, or others. It’s possible to train an 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. This is, of course, the same tech that can also be used to create audio deepfakes, so it’s something that we need to approach responsibly, but the tech has truly transformative potential.
• Voice recognition. Researchers like those in the Speech Accessibility Project are paying people with disabilities for their help in collecting recordings of people with atypical speech. As I type, they are actively recruiting people with Parkinson’s and related conditions, and they have plans to expand this to other conditions as the project progresses. This research will result in more inclusive data sets that will let more people with disabilities use voice assistants, dictation software, and voice-response services as well as control their computers and other devices more easily, using only their voice.
• Text transformation. The current generation of LLMs is quite capable of adjusting existing text content without injecting hallucinations. This is hugely empowering for people with cognitive disabilities who may benefit from text summaries or simplified versions of text or even text that’s prepped for Bionic Reading.

The importance of diverse teams and data

We need to recognize that our differences matter. Our lived experiences are influenced by the intersections of the identities that we exist in. 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 need to be represented in the data that we use to train new models, and the folks who contribute that valuable information need to be compensated for sharing it with us. Inclusive data sets yield more robust models that foster more equitable outcomes.

Want a model that doesn’t demean or patronize or objectify people with disabilities? Make sure that you have content about disabilities that’s authored by people with a range of disabilities, and make sure that that’s well represented in the training data.

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

Want a coding copilot that gives you accessible recommendations from the jump? Train it on code that you know to be accessible.

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

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

The same applies for those of us working in design and development these times. 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. Each day that we as developers and designers get into a regular rhythm, some innovative idea or technology comes down to shake things up and copy our world.

How we got below

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

The beginning of website standards

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

Server-side languages like PHP, Java, and.NET overtook Perl as the predominant back-end processors, and the cgi-bin was tossed in the trash bin. With these better server-side tools came the first era of web applications, starting with content-management systems ( particularly in the blogging space with tools like Blogger, Grey Matter, Movable Type, and WordPress ). In the mid-2000s, AJAX opened doors for asynchronous interaction between the front end and back end. Suddenly, pages could update their content without needing to reload. A crop of JavaScript frameworks like Prototype, YUI, and jQuery arose to help developers build more reliable client-side interaction across browsers that had wildly varying levels of standards support. Techniques like image replacement let crafty designers and developers display fonts of their choosing. And technologies like Flash made it possible to add animations, games, and even more interactivity.

These new technologies, standards, and techniques reinvigorated the industry in many ways. Web design flourished as designers and developers explored more diverse styles and layouts. But we still relied on tons of hacks. Early CSS was a huge improvement over table-based layouts when it came to basic layout and text styling, but its limitations at the time meant that designers and developers still relied heavily on images for complex shapes ( such as rounded or angled corners ) and tiled backgrounds for the appearance of full-length columns (among other hacks ). Complicated layouts required all manner of nested floats or absolute positioning ( or both ). Flash and image replacement for custom fonts was a great start toward varying the typefaces from the big five, but both hacks introduced accessibility and performance problems. And JavaScript libraries made it easy for anyone to add a dash of interaction to pages, although at the cost of doubling or even quadrupling the download size of simple websites.

The web as software platform

The symbiosis between the front end and back end continued to improve, and that led to the current era of modern web applications. Between expanded server-side programming languages ( which kept growing to include Ruby, Python, Go, and others ) and newer front-end tools like React, Vue, and Angular, we could build fully capable software on the web. Alongside these tools came others, including collaborative version control, build automation, and shared package libraries. What was once primarily an environment for linked documents became a realm of infinite possibilities.

At the same time, mobile devices became more capable, and they gave us internet access in our pockets. Mobile apps and responsive design opened up opportunities for new interactions anywhere and any time.

This combination of capable mobile devices and powerful development tools contributed to the waxing of social media and other centralized tools for people to connect and consume. 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 offered connections on a global scale, with both the good and bad that that entails.

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

Where we are now

In the last couple of years, it’s felt like we’ve begun to reach another major inflection point. 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 make a website, from the tried-and-true classic of hosting plain HTML files to static site generators to content management systems of all flavors. The fracturing of social media also comes with a cost: we lose crucial infrastructure for discovery and connection. Webmentions, RSS, ActivityPub, and other tools of the IndieWeb can help with this, but they’re still relatively underimplemented and hard to use for the less nerdy. We can build amazing personal websites and add to them regularly, but without discovery and connection, it can sometimes feel like we may as well be shouting into the void.

Browser support for CSS, JavaScript, and other standards like web components has accelerated, especially through efforts like Interop. New technologies gain support across the board in a fraction of the time that they used to. I often learn about a new feature and check its browser support only to find that its coverage is already above 80 percent. 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.

Today, with a few commands and a couple of lines of code, we can prototype almost any idea. All the tools that we now have available make it easier than ever to start something new. But the upfront cost that these frameworks may save in initial delivery eventually comes due as upgrading and maintaining them becomes a part 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 used to let us adopt new techniques sooner—have now become hindrances instead. 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 through poor code, network issues, or other environmental factors ), there’s often no alternative, leaving users with blank or broken pages.

Where do we go from here?

Today’s hacks help to shape tomorrow’s standards. And there’s nothing inherently wrong with embracing hacks —for now—to move the present forward. Problems only arise when we’re unwilling to admit that they’re hacks or we hesitate 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 developer-friendly tools. They may make your job a little easier today, but how do they affect everything else? What’s the cost to users? To future developers? To standards adoption? Sometimes the convenience may be worth it. Sometimes it’s just a hack that you’ve grown accustomed to. And sometimes it’s holding you back from even better options.

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

Design with care. Whether your craft is code, pixels, or processes, consider the impacts of each decision. 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. Rather than rushing headlong to “move fast and break things”, use the time saved by modern tools to consider more carefully and design with deliberation.

Always be learning. If you’re always learning, you’re also growing. Sometimes it may be hard to pinpoint what’s worth learning and what’s just today’s hack. You might end up focusing on something that won’t matter next year, even if you were to focus solely on learning standards. ( Remember XHTML? ) But constant learning opens up new connections in your brain, and the hacks that you learn one day may help to inform different experiments another day.

Play, experiment, and be weird! This web that we’ve built is the ultimate experiment. It’s the single largest human endeavor in history, and yet each of us can create our own pocket within it. Be courageous and try new things. Build a playground for ideas. Make goofy experiments in your own mad science lab. Start your own small business. There has never been a more empowering place to be creative, take risks, and explore what we’re capable of.

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

Go forth and make

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

Between the dream of getting it right and the fear of it going wrong—like when we encounter “persofails” in the vein of a company constantly imploring daily consumers to buy more toilet seats—the personalization gap is true. It’s an particularly confusing place to be a modern professional without a map, a map, or a strategy.

For those of you venturing into customisation, there’s no Lonely Planet and some tour guides because powerful personalization is so specific to each group’s skills, systems, and market place.

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

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

We call it prepersonalization.

Behind the music

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

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

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

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

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

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

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

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

Set your kitchen timer

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

The full arc of the wider workshop is threefold:

Kickstart: This sets the terms of engagement as you focus on the opportunity as well as the readiness and drive of your team and your leadership..
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 phase is all about creating a competitive environment for team participants to individually pitch their own pilots that each contain a proof-of-concept project, its business case, and its operating model.

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

Kickstart: Whet your appetite

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

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

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

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

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

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

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

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

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

Hit that test kitchen

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

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

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

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

Verify your ingredients

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

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

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

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

Compose your recipe

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

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

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

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

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

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

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

Better kitchens require better architecture

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

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

You can definitely stand the heat …

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

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

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

Always since I was a child, I’ve been fascinated with movies. I loved the figures and the excitement—but most of all the reports. I wanted to be an actor. And I believed that I’d get to do the things that Indiana Jones did and go on exciting activities. I also dreamed up suggestions for videos that my friends and I could create and sun in. But they never went any farther. I did, however, end up working in user experience ( UX). 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 to get the most out of consumer research, you need to show a good account where you bring stakeholders—the solution team and choice makers—along and getting them interested in learning more.

Think of your favorite film. More than likely it follows a three-act construction that’s frequently seen in story: the layout, the fight, and the quality. The second act shows what exists now, and it helps you get to know the characters and the challenges and problems that they face. Act two introduces the fight, where the activity is. Here, difficulties grow or get worse. And the third and final work is the solution. This is where the issues are resolved and the figures learn and change. I believe that this architecture is also a great way to think about customer study, and I think that it can be particularly helpful in explaining person exploration to others.

Use story as a framework to complete research

It’s sad to say, but many have come to see studies as being inconsequential. If finances or timelines are strong, analysis tends to be one of the first points to go. 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 get clubs some of the way, but that strategy is so easily miss out on solving people ‘ real problems. To be user-centered, this is something we really avoid. User studies puts style. It keeps it on record, pointing to problems and opportunities. Being aware of the issues with your product and reacting to them can help you stay 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 look at the different functions and how they align with customer study.

Act one: installation

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

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

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

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

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

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

Act two: conflict

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

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

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

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

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

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

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

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

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

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

Act three: resolution

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

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

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

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

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

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

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

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

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

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

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

Weekend Favs March 29th written by John Jantsch read more at Duct Tape Selling

My trip blog post program includes posting references to a handful of equipment or great glad I ran across during the week. I don’t go into detail about the sees, but I encourage you to check them out if they sound exciting. The pictures in the article is a favourite for the week from an online ]…]

Build a Brand Gen Z Wants to Work ( and Buy ) From written by Jarret Redding read more at Duct Tape Marketing

The Duct Tape Marketing Podcast with Len Silverman

In this instance of the Duct Tape Marketing Podcast, I interviewed Len Silverman, a former professional, past Learning Center landlord, and creator of Mesh: Aligning Your Personal Brand with Gen Z. With over 30 years of experience and firsthand information into the Gen Z labor, Len offers a clear strategy for businesses struggling to interact with this rising generation of employees and customers.

Len stock why just labeling Gen Z as “lazy” or “hard to control” is a huge misstep. Rather, businesses need to know Gen Z traits and align their business culture and company brand with what this generation really values—authenticity, flexibility, purpose, and opportunity. Whether you &#8217, re hiring Gen Z workers or advertising to them, the essential lies in understanding the intersection of specific brand and company personality.

Len Silverman’s insights are a wake-up contact for any business that wants to be appropriate, both in the hiring industry and in customer wedding. If you want your company to relate with the next century, it starts with getting real about who you are —and who they are.

Important Restaurants:

• Understand the Gen Z Workforce: Gen Z isn’t scared to spirit employers—but it’s usually due to broken hiring experience, not disillusionment. Modify, understand, and customize your process.
• Personal Branding Matters: Gen Z expects companies to have a brand identity that mirrors their personal values. They’re looking for position, not just a money.
• Company Culture Is Everything: This technology wants mentoring, not micromanagement. They crave situations where input is empty, and function drives work.
• Consider Employee Journey, Not Really Customer Journey: Gen Z sees work as part of their life experience. Treat recruitment and retention like a well-crafted selling funnels.
• Authenticity Wins: Theatrical brand won’t last. Gen Z may visit it out. Make sure your principles show up in your leadership, deeds, and contacts.
• Mentorship Over Management: Help Gen Z through gaze mentors or structured applications to link actions, aspirations, and professional advancement.
• Generational Understanding Builds Trust: Bridging the gap between Gen X management and Gen Z workers starts with emotion, open dialogue, and shared value.

Chapters:

• ]00: 09 ] Introduction to Len Silverman
• ]00: 53] What is the Personal Brand of Gen Z
• ]02: 56] Common Stereotypes of Genz
• ]04: 16 ] The Old Ways Aren&#8217, t Going to Work
• ]06: 39] The Employee Journey
• ]08: 35] Importance of Cultural Consistency
• ]10: 39] Changing Mindsets
• ]12: 44] Gen Z Customers
• ]14: 19] Common Mistakes Trying to Align with Gen Z
• ]17: 11] Turning Gen Z into A Players

More About Len Silverman:

Check out Len Silverman&#8217, s Website
• Connect with Len Silverman on LinkedIn
• Read MESH: Aligning the Personal Brand of Gen Z with your Company Culture by Len Silverman

This essay contains Death of a Unicorn clues. ” You know what? We really had placed more stock in art story”. This is a spiritual reality that should be repeated. It also, perhaps, is a thought that flashed through the mind of Odell Leopold ( Richard E. Grant ) right before a unicorn’s horn also smashed into that ]… ]

The article Death of a Unicorn: The True Medieval Lore and Tapestries Explained by the Director appeared first on Den of Geek.

This essay contains Death of a Unicorn clues.

” You know what? We really had placed more stock in art story”. This is a spiritual truth that should be repeated. It also, perhaps, is a thought that flashed through the mind of Odell Leopold ( Richard E. Grant ) right before a unicorn’s horn also smashed into that soft, squishy gray matter. It might have similarly been in the back recesses of Belinda Leopold’s ( Téa Leoni ) head while another unicorn opened her belly.

They were both warned earlier in their movie by art history student Ridley Kintner ( Jenna Ortega ) that ancient masterworks tell us of the dangers posed by horned mythical creatures. She also had JPEGs of the expensive medieval tapestries to show it, with images of death by fairy disembowelment and all. But they refused to listen.

It&#8217, s a funny look befitting a film actively infused with Jurassic Park pictures as wealthy elites try and fail to control the natural world. Yet it’s not merely a joke. In fact, Death of a Unicorn writer-director Alex Scharfman extensively studied fairy folklore and tradition, telling us earlier in a Den of Geek include tale that he went back to Roman historians and the Old Testament Bible while researching the video. He also profoundly examined those pony embroideries you see in the movie. Aye, they &#8217, re true and now live in the Met Cloisters in New York City. So we just decided to sit down afterwards with Scharfman to explain how deeply these Hunt of the Unicorn tapestries informed his picture.

” I grew up around New York in the cities and went on field trips to the Cloisters Museum where those are held and maintained”, Scharfman recalls in our latest discussion about the movie and these Romanesque magic. ” They must have been buried in my incapacitated, because at some point I forgot about them but finally when researching the film, I came upon them once and I was like’ oh right, those items!'”

These vases, which were made by an unknown artist at the turn of the 16th century, and therefore resided in an aristocratic Parisian household until almost being destroyed in the French Revolution, became a North Star for everything in Death of a Unicorn. Ortega also recently told us they were a &#8220, cheat plate” for understanding their video. But meet us below as we unpack each of the seven sequences composing the Unicorn Tapestries while Scharfman explains how they influenced and shaped his man-eating pony thing feature.

The Hunters Enter the Woods

An exciting thing to note is that while the Cloisters and many craft historians place these embroideries in a normally recognized sequence—and it is the format we are using in this article—no a is exactly certain about the established order of things.

” There’s not like on the back of them a’ number one’ or a ‘ number two,'” Scharfman explains”, so people have put them in an order that seems to make sense. And I totally agree that this makes sense as the first one, but one thing that I thought was fun with the movie is they’re not necessarily in the right order.”

Still most agree this is the first composition since it distinctly lacks either a unicorn or a king and/or lord. Instead it is just dogs and kingsmen approaching a formidable wilderness.

” One thing that’s nice about this tapestry specifically is there&#8217, s just so much foliage and just this overwhelming sense of nature,” says Scharfman”. That is something people write about with the Unicorn Tapestries a lot: this sense of the way nature is depicted. ” Yet it is the humans in this specific tapestry that inspire so much of the bent of Death of a Unicorn, the movie about a CEO, or feudal lord, who summons a prospective servant, Paul Rudd‘s Elliot Kintner, to court.

” I think it’s telling that]the Lord ] is not in this one,” Scharfman says”. He sent out his minions to go get him this thing that he wants in the woods and to bring it back for him. So I totally think when you start digging into the tapestries, and more broadly most medieval unicorn mythology and lore, you end up with something that really presents itself as a class commentary in that way.”

The writer-director notes that he also modeled one of his shots of Grant leading Rudd and other characters into the wilderness while hunting a unicorn specifically after this tapestry.

The Unicorn Purifies Water

The next tableau sets the scene of a unicorn purifying the water in an enchanted fountain hidden deep within the wood. The implication is that the unicorn&#8217, s horn, and perhaps blood, has restorative magical powers, which some scholars perceive as an allusion to Christ. The myth about a unicorn’s body having healing properties long predates the tapestries and was already a key element in Scharfman&#8217, s vision for the developing movie when he rediscovered these tapestries. But this image had other significant influences on the film.

” It&#8217, s a funny thing,” Scharfman chuckles”, I don’t know why there’s this fountain in the woods. The unicorn is not purifying a stream, it’s purifying water from a fountain that’s pouring out. ” It is an odd sight, but one the director sought to recreate by placing a near replica of this fountain in the Leopold estate:” In the courtyard of the house, there’s a fountain that is exactly like that one. We modeled it pretty much as close as we could possibly get to it… and that is where the unicorn is discovered by most of the characters.”

Furthermore, this tapestry inspired even the name of the film’s villains.

Says Scharfman”, Among the other animals that are drinking from the water in this tapestry, there are a couple lions, and the Leopold family is of course the antagonists, the pharmaceutical family in the movie. ” As the director acknowledges, the name &#8220, Leopold &#8221, is an allusion to Leo the lion in astrology. The Leopolds &#8217, company sigil is also a lion.

” In a lot of unicorn mythology, lions and unicorns were enemies,” Scharfman adds. &#8220, But here they’re kind of allies, or at least the unicorn seems to be happy to let them drink from the water the unicorn has purified”. It’s a departure from the myths, as well as where Death of a Unicorn goes next….

The Unicorn Crosses a Stream

In this scene, the kingsmen fall upon the poor unicorn and begin their attack as it attempts to flee across a stream. The image sets the stage for the bigger carnage to come later, but right down to the costumes of the hunters, beginning with the gent attending to the dog in the bottom left corner, this image helped inform the look of many of&nbsp, costume designer Andrea Flesch’s creations for the film.

” There’s certainly lots of little textures and details like Will Poulter&#8217, s bathing suits”, Scharfman comments. ” There’s these really great stripes, vertical stripes on one of the characters &#8217, pants, and that was certainly an influence that we took for Will. Costume-wise, Paul wears blue throughout the movie, Jenna wears red throughout the movie. They’re kind of moving towards each other]which gives you purple ] … the Leopold family, which is played by Richard, Téa, and Will, they wear a lot of gold. Gold, white, black, that’s their palette, and when you look at the characters in these tapestries, they’re wearing red, blue, gold, and then there’s a lot of green in the background”.

Even the scientists ‘ lab coats in the film are made to mimic the high collars of late Middle Ages fashion.

The Unicorn Defends Himself

Now we get into the images that really start to influence the strange, bemused tone of Death of a Unicorn. And we are not referring to the orange tree high above the action of this scene or the red-roofed castle far off in the background. Both of those informed the look and garden of the Leopold estate, which the director is quick to point out to us. But it is the violent carnage and death in the foreground of this tapestry that immediately catches the eye.

” This was one of the first bits of unicorn violence that I had seen in any artwork”, Scharfman remembers. ” When you look in this tapestry, when you go up close and you see it, it’s stabbing this dog in the intestines. It’s a hunting dog, so I think it’s self-defense. But when you go very close or if you got a high enough resolution version of it, it is very gory with the level of detail in this wound that it’s inflicting on the dog”.

He continues,” Beyond that it’s also kicking with its hind legs, which when you go back into historical accounts of unicorns, there is a lot of violence described and there’s a lot of very violent imagery that you can find. They were not these passive creatures. They really were not afraid to bite and kick and use their horn to gore people”.

Scharfman admits that ripping out a character’s intestines like he depicted happening to poor Belinda was his own flourish, but” there are accounts of them using their teeth to bite people, so it felt like it wasn’t that big of a jump”.

The Unicorn Surrenders to a Maiden

Perhaps the most influential tapestry on all of Death of a Unicorn,” The Unicorn Surrenders to a Maiden” is as important for what it doesn’t show as for what it does.

” Jenna wears a red hoodie throughout the movie, which has a very unusual shape”, notes Scharfman. ” This actually is very much inspired by what the maiden is wearing in this, with these very kind of wide sleeves. And that was a hoodie we found from a Japanese designer that they made in gray and other colors, but we asked them to make it custom for us in red. It had this really interesting cloak kind of shape to it”.

After discovering this tapestry, it became quite indicative of how Scharfman imagined the Ridley character within the film:” It got me thinking,’ Well, what is a pure hearted maiden in 2025?’ And I started thinking it’s probably a Gen-Z leftist who’s protesting on a campus somewhere right now. Someone with very strong morals and ideals”.

However, more than just the idea of having a pure-hearted maiden, this tapestry’s incompleteness created space for Scharfman to fill in his own grisly details.

” When you look at it in real life, it’s about a third the size of the other ones”, the director points out. ” That’s because it was tremendously damaged. It was recovered after the French Revolution, so it is believed to have been damaged during the revolution, perhaps. It was used on top of a sack of potatoes to keep them warm in the winter time, and so they got totally tattered”.

What is left of the tapestry is actually torn into two pieces, and it is missing crucial information &#8230, like the maiden it is named after.

” If you look in the bottom right corner of this tapestry, just under the unicorn, you can see a woman&#8217, s hand”, says Scharfman. ” So the maiden that the unicorn is actually surrendering to is not in the tapestry, which is very confusing. This is another maiden who happens to be like a handmaiden working with the maiden who is the bait. And I thought about putting that into the movie, but I was like’ that is so confusing to try and teach people ‘—that there is a maiden in the tapestry, but that’s not the maiden it &#8217, s surrendering to. It’s surrendering to an off-screen maiden that we’ll never see”.

Nonetheless, the actual maiden’s absence gave Scharfman the creative liberty to suggest there is a fuller, more complete “lost tapestry &#8221, introduced in the film that includes so much of the monster movie mayhem that was to come.

” We had these brilliant artists do this incredible artwork to take the figures of the tapestries and the style of the tapestries, and infuse it with scenes from our movie, “he explains”. So we expanded this tapestry into this lost tapestry that includes a lot of the kills and a lot of the fun elements of the horror language that we employ in the movie, but to put it in this medieval context.”

It also allowed Scharfman to reconfigure the way the tapestries are meant to be interpreted. Whereas the following two tapestries are perceived by many historians to be the end of the story, in Scharfman&#8217, s film the actual ending is this tapestry with the maiden and unicorn resting after all the death and carnage had been carried out.

The Hunters Return to the Castle / The Unicorn Rests in a Garden

The last two actual tapestries tell an interesting if aloof conclusion to their tale: first the unicorn appears to be deceased, presumably killed by the hunters after the maiden beguiled the mythical creature long enough for them to get close—and then the creature appears to be resurrected and curiously happy in captivity.

Of the former tableau’s influences, the Lady of the Manor&#8217, s golden gown informed Leoni’s cream colored suits in the movie. Scharfman also points to the shape of the unicorn&#8217, s corpse as it lies draped over a horse in the center of the scene”. When the unicorn is killed ]and taken to ] the house in our movie, it has a similar pose where it &#8217, s kind of draped out the window of a car,” says the director. In which case, perhaps historians &#8217, interpretations of the tapestries &#8217, sequence is wrong, and this is the real first tapestry, which like Death of a Unicorn sets the stage for all the carnage that is to follow?

Either way, it &#8217, s the generally accepted final image of the story which inspires at least the oblique motivation of the film &#8217, s greediest Leopold, Will Poulter&#8217, s nepobaby Shepherd”. The unicorn in captivity, that is the vision that Will Poulter&#8217, s character is going after,” Scharfman says”. This idea that we can own this thing and possess it forever, and it will be ours within these confines. ” Yet there are multiple ways of reading the actual tapestry.

Adds the director”, What&#8217, s funny about it is when you look at it, it has a very thin chain on it. It seems like it could break out of this, but it’s not. So there are questions about the symbolic meaning there. Is it there by choice? Is it there being held as captive? Who knows? But that is his vision of the future if]Shep] can possess them and contain them. Then he will have a limitless supply of unicorns.”

Given the tone and tenor of Death of a Unicorn, we might suggest the creature’s contentment is nothing more than medieval propaganda for how they actually handle confinement. Whatever the case might be, the film ends with the beasts running free and even attacking the police vehicle that Elliot and Ridley are being driven away in. However, Scharfman doesn’t think his film’s heroes are in too much danger.

” I think they’re there to try and help Jenna and Paul’s characters,” Scharfman muses of his unicorns”, but I also think they don’t really understand how cars work or police, or how any of these things actually function, because they exist outside of society. ” Still, should either Ridley or Elliot perish in the ensuing car crash, it’s no biggie”. Worst case scenario, they can resurrect some people.”

Much like the tapestries show, when it comes to unicorns, death is more of a temporary inconvenience than a bitter fact of life. And with any luck, Death of a Unicorn might inspire some folks to learn more about the O. G. medieval roots of the pop culture creature.

” We put a lot of easter eggs from these tapestries into the movie, and I think there’s something fun about that, “muses the filmmaker”. Hopefully it adds a layer of rewatchability and maybe sends some people to the Cloisters to check out the tapestries in person. ” That would be a nice kind of enchantment.

Death of a Unicorn is playing in theaters now.

The article Death of a Unicorn: The True Medieval Lore and Tapestries Explained by the Director appeared first on Den of Geek.