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?

Mobile-first CSS may yet be the best option for your own projects, but you need to first determine 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 pyramid. 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 has been a tried-and-true method that has worked for years because it solves a trouble flawlessly.

Prioritizes the portable watch. The smart watch is the simplest and perhaps the most crucial because it covers all of the crucial user journeys and frequently accounts for more user visits ( depending on the project ) in terms of both simple and crucial aspects.

Inhibits desktop-centric growth. It can be tempting to first focus on the desktop perspective because enhancement is done using pc servers. No one wants to spend their time retrofitting a desktop-centric website to function on mobile devices, but thinking about smart from the beginning prevents us from getting stuck in the future!

Drawbacks of mobile-first

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

More richness. The more unneeded code you inherit from lower thresholds the higher up the target order you ascend.

Higher CSS sensitivity. A school name declaration with a turned default value for a style has a higher specificity today. When trying to keep the CSS candidates as simple as possible, this can cause trouble on complex projects.

Requires more analysis tests. All higher thresholds must be regression tested if CSS changes at lower views ( such as adding a new fashion ).

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

The issue of home value supersedes

Overwriting values is not necessarily essentially bad; CSS was created to do that. However, sharing incorrect values is counterproductive and can be burdensome and inadequate. When you have to replace styles to restore them to their defaults, which may cause issues after, especially if you are using a combination of bespoke CSS and power classes, it can also lead to more fashion specificity. A style with a higher specificity that has been reset won’t be able to be used with a utility class.

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. However, if it appears that Grid is much better for large screens and Flexbox is much better for mobile, both can be accomplished entirely independently when the CSS is entered into closed media query ranges. Additionally, developing simultaneously requires you to have a thorough understanding of any given component in all breakpoints right away. This can help identify issues with the design more quickly in the development process. We don’t want to travel down the rabbit hole while creating complex mobile components, only to discover that the desktop designs are just as 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 like to work on one device at a time, are comfortable with focusing on the mobile view, and have a good understanding of the requirements for other breakpoints, then you should definitely stick to the classic development order. The key is to find common styles and exceptions so that you can include them in the appropriate stylesheet, which is a manual tree-shaking procedure! Personally, I find this a little easier when working on a component across breakpoints, but that’s by no means a requirement.

Closed media query ranges 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.

separating the CSS from combining it

Back in the day, keeping the number of requests to a minimum was very important because the browser's concurrent request limit (typically around six ) was high. 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. By using a media query, we can break CSS into several files. The obvious benefit of this is that the browser can now request the CSS it currently requires with a higher priority than the CSS it doesn't. This is more effective and can shorten the amount of time a page is blocked overall.

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, go to the Network tab and check whether 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 anticipating? The HTTP/2 user support is excellent.

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.

We can see that the mobile and default CSS are loaded with" Highest" priority in the following example of a website that is visited on a mobile breakpoint, since they are currently required 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.

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

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

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

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

Moving on

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

I don't think anyone wants to return to that development model again, but it's important we don't lose sight of the issue it highlighted: that things can easily get convoluted and less efficient if we prioritize one particular device—any device—over others. For this reason, 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 to notice subtle simplifications in both the CSS and other developers', and that the work is also a little more organized and effective.

In the end, simplifying CSS rule creation whenever possible is a more effective strategy than circling around with 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. Although there is still a lot of advertising hype surrounding personalization websites, there are still very some standardized methods for implementing personalized UX.

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

Getting Started

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

Popular circumstances for launching a personalization project:

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

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

From top to bottom, the rates include:

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

We’ll go through each of these amounts sequentially. An associated deck of cards serves as an example of each level’s specific examples to make this more practical. We’ve found them useful in brainstorming about customisation, so we’ll provide examples for you here.

Starting at the top

The tower has the following elements:

North Star

What overall goal do you have with your personalization software ( big or small ) is a northern star. The personalisation program’s entire goal is described in The North Star. 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 personalisation componentry. Examples:” Cooked” notifications, advanced optimizations ( geolocation ), basic dynamic messaging, customized modules, automations, recommenders
2. Experience: Personal user experiences across many 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 encounters with personalization at their base, like the “algotorial” songs by Spotify quite as Discover Weekly.

Goals

As in any great UX design, personalization may help promote designing with client intentions. The goals serve as the military and measurable indicators of the success of the entire system. Start with your existing analytics and assessment system, as well as indicators you can benchmark against. In some cases, new targets may be suitable. The most important thing to keep in mind is that personalisation is certainly a desired outcome. It is a means to an end. Popular targets include:

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

Touchpoints

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

Channel-level Touchpoints

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

Wireframe-level Touchpoints

• Web overlay
• Web call bar
• Web symbol
• Web content wall
• Web restaurant

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

Contexts and Campaigns

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

Personalization Context Model:

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

Personalization Content Model:

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

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

User Parts

Based on customer research, user segments can be created prescriptively or dynamically ( for example, using principles and logic tied to user behavior, or through A/B testing ). You will need to think about how to treat the unidentified or first-time visitor, the guest or returning visitor for whom you may have a stateful cookie ( or an equivalent post-cookie identifier ), or the logged-in visitor who is authenticated. The personalisation tower has some of the following cases:

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

Actionable Data

Every business has access to data, regardless of its online existence. It’s important to inquire about how to use the data you can ethically collect on users, its inherent reliability and value, and how to use it ( sometimes referred to as “data activation” ). Fortunately, the tide is turning to first-party information: a recent study by Twilio estimates some 80 % of companies are using at least some type of first-party information 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. Therefore, determining which method of data collection is best for your audiences should be a crucial component of your UX strategy. Here are some examples:

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

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

Pulling it Together

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

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

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

Lay Down Your Cards

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

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 teacher’s? They all good wonderful. When humility is our guiding light, the course is usually available for fulfillment, development, relation, and commitment. In this section, 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. Along the way, I’m going to render myself a little vulnerable. 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. In the end, this topic may determine my career’s direction.

But I drained HTML and JavaScript books until the early hours of the morning and self-taught myself how to code during my freshman year rather than student and go into write like many of my friends. I needed to understand what my design choices would ultimately think when rendered in a website, which I did not want to do.

The later ‘ 90s and early 2000s were the so-called” Wild West” of web design. The modern landscape was being studied by designers at the time as they attempted to incorporate design and visual communication. 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 looking for information.

Even though I’m referring to a different time, those are amazing factors between non-career relationships and the world of layout. What are your main passions, or ideals, that elevate medium? The main themes remain the same, much like the clear parallels between what fulfills you, who is independent of the physical or digital worlds.

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

For 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. On this one, we would first sketch and then pass a Photoshop file back and forth to trick things out and play with various user interactions. I co-founded the creative project organizing app Milanote and my dear friend, fellow designer Marc Clancy. 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 provided many of the custom downloads I previously mentioned as being accessible on my folio website but with a GUI Galaxy theme and branding.

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 creating a larger-than-anyone experience and establishing a global audience.

Collaboration and connection transcend media in their impact, which have been extremely satisfying for me as a designer.

Why am I going down this design memory lane with you, now? 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. There’s a good chance you’ve seen a website with a hero image, a banner with text overlays, perhaps with a lovely rotating carousel of images ( laying the snark on heavy there ), three columns of sub-content directly beneath, and three columns of sub-content, according to the theory. Perhaps there are selections that vaguely relate to their respective content in an icon library.

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

Pixel Problems

Websites built during this time were frequently built using Macs whose desktops and OS 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. Under such absurd constraints, this seemed to me to be the embodiment of digital visual communication. And frequently, ridiculous limitations can lead to 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. These absurd restrictions imposed a clarity of concept and presentation that I found incredibly appealing. I was thrown the digital gauntlet, and that challenge fueled my determination. And so, in my dorm room into the wee hours of the morning, I toiled away, bringing conceptual sketches into mini mosaic fruition.

These are some of my creations that made use of ResEdit, the only program I had at the time, to create icons. ResEdit was a clunky, built-in Mac OS utility that wasn’t really designed for 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.

One more design portal that I want to mention also serves as the second reason for my story to connect this all.

This is K10k, short for Kaliber 1000. Michael Schmidt and Toke Nygaard founded K10k in 1998, which was the design news website during that time. 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. The idea for GUI Galaxy was inspired by what these people were doing, respect where respect is due.

For my part, the combination of my pixel art and web design work started to gain me some notoriety in the design community. K10k eventually figured out and added me as one of their very limited group of news writers to add content to the website.

Amongst my personal work and side projects —and now with this inclusion—in the design community, this put me on the map. Additionally, my design work has started to appear on other design news portals, as well as be published in various printed collections, in domestic and international magazines, and in various printed collections. 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 praise and the press immediately surpassed what I needed to fulfill, and they did just that. They inflated my ego. I actually felt a little better than my fellow designers.

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

I effectively stopped researching and discovering because I felt so incredibly confident in my abilities. When my first instinct was to sketch concepts or iterate ideas in lead, I instead leaped right into Photoshop. I got my inspiration from the tiniest of sources ( while wearing a blindfold ). My peers frequently vehemently disapproved of any criticism of my work. The most tragic loss: I had lost touch with my values.

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

It was a gift I initially did not accept but which I, on the whole, was able to reflect on in depth. I was soon able to accept, and process, and course correct. The realization laid me low, but the re-awakening was essential. I let go of the “reward” of admiration and turned my attention to the issues that had plagued my art school career. 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 as I grew older, I could reflect on myself to help with further development and course correction.

As an example, let’s talk about the Large Hadron Collider. The LHC was created” to help answer some of the fundamental open questions in physics, which concern the fundamental laws governing the interactions and forces between the elementary objects, the deep structure of space and time, and in particular the interrelation between general relativity and quantum mechanics.” Thanks, Wikipedia.

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

I had a fascinating experience designing the interface for this application because I collaborated with Fermilab physicists to understand both how the application was intended to use it and how the physicists themselves would use it. To that end, in this role,

Working with the Fermilab team to iterate and make improvements to the interface, I cut my teeth on usability testing. To me, their language and the topics they discussed seemed to me to be foreign languages. And by accepting that I was just a student and working with the mindset that I was only a student, I made myself available to them in order to form that crucial bond.

I also had my first ethnographic observational experience, which involved visiting the Fermilab location and observing how the physicists used the tool in their own environments, on their own terminals. One takeaway was that the data columns ended up using white text on a dark gray background rather than black text-on-white because of the facility’s level of ambient light-driven contrast. This made it easier for them to pore over a lot of data during the day and lessen their strain on their eyes. Additionally, since Fermilab and CERN are government entities with stringent accessibility requirements, my knowledge expanded. 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. Before I entered those values, I had to check my ego before entering it, which opened the door to those values.

An evergreen willingness to listen, learn, understand, grow, evolve, and connect yields our best work. In particular, I want to focus on the words’ grow’ and ‘ evolve’ in that statement. If we constantly practice our craft, we are also making ourselves more and more adaptable. Yes, we have years of practical design experience under our belt. Or the focused lab training from a bootcamp for UX. or the work portfolio with monograms. Or, ultimately, decades of a career behind us.

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

The designer we are is our final form as soon as we close our minds through an inner monologue of “knowing it all” or branding ourselves a” #thoughtleader” on social media. There will never be a designer like us.

I am a innovative. What I do is alchemy. It is a secret. I don’t perform it as much as I let it be done by me.

I am a artistic. This brand is never appropriate for all creatives. No everyone sees themselves in this way. Some innovative individuals incorporate technology into their work. That is their reality, and I respect it. Sometimes I even envy them, a minor. But my approach is different—my becoming is unique.

Apologizing and qualifying in progress is a diversion. My brain uses that to destroy me. I’ll leave it alone for today. I may forgive and be qualified at any time. After I’ve said what I originally said. Which is challenging enough.

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

Sometimes it does. Maybe I have to make something right away. I’ve learned to avoid saying it right away because people think you don’t work hard enough when you know it’s the best idea when you’re on the go and you know it’s the best idea.

Sometimes I just work until the thought strikes me. Maybe it arrives right away, but I don’t remind people for three weeks. Maybe I get so excited about an idea that just came along that I blurt it out and didn’t stop myself. like a child who discovered a medal in one of his Cracker Jacks. I occasionally manage to get away with this. Maybe other people agree: yes, that is the best plan. Most times they don’t and I regret having given way to passion.

Passion should only be saved for the meet, when it matters. not the informal gathering that two different gatherings precede that meeting. Anyone knows why we have all these sessions. We keep saying we’re going to get rid of them, but we just keep trying to find different ways to get them. They occasionally yet excel. But occasionally they are a hindrance to the 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 go about doing it. Suddenly I digress. I am a artistic. That is the topic.

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

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

I am a innovative. I don’t handle my desires. 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 works. There is a Eureka, which has nothing to do with boiling pots and sizzling oil, and I may be making dinner. I frequently know what to do when I awaken. The idea that may have saved me disappears almost as frequently as I become aware and a part of the world once more as a senseless wind of oblivion. For imagination, I believe, comes from that other planet. The one we enter in aspirations, and possibly, before conception and after death. But that’s for authors to know, and I am not a writer. I am a innovative. Theologians should circulate large armies throughout their artistic globe, which they claim to be true. But that is another diversion. And one that is miserable. Possibly on a much bigger issue than whether or not I am creative. But that’s also a step backwards from what I’m trying to say.

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

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

Creatives understand artists.

Disadvantages are aware of cons, just like queers are aware of queers, just like real rappers are aware of genuine rappers are aware of 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 dreadful mistake. We have been warned. We know much. We know people are simply people. They dispute, they are depressed, they regret their most critical decisions, they are weak and thirsty, they can be cruel, they can be just as terrible as we can, if, like us, they are clay. But. But. However, they produce this incredible point. They give birth to something that was unable to occur before them or otherwise. They are thought’s founders. And I suppose, since it’s only lying it, I have to put that they are the mother of technology. Ba ho 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 brilliance. That is brilliance straight out of the mouth of God. This half-starved small item that I made? It essentially fell off the back of the pumpkin trailer. And the carrots weren’t even clean.

Creatives knows that, at best, they are Salieri. Yet Mozart’s original artists hold that opinion.

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. They are correct in doing so. I am very lazy, overly simplistic, and when it actually counts, my mind goes blank. There is no supplement for innovative function.

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

I can move ten times more quickly than those who aren’t creative, those who have simply been creative for a short while, and those who have just been creative for a short time in their careers. Only that I spend twice as long putting the job off as they do before I work ten times as quickly as they do. When I put my mind to it, I am so confident in my ability to do a great career. I am that attached to the excitement scramble of delay. The climb also terrifies me.

I am not an actor.

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

I am a artistic. Though I believe in reason and science, I decide by intelligence and desire. And sit with what follows—the disasters 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 debate, 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 almost all of the areas of human understanding that I know very little about. 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 may probably have to spend time staring living in the eye, which almost none of us can do for very long. No seriously. No truly. Because many in existence, if you really look at it, is terrible.

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

Working frees me from worrying about my job.

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

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

I am a artistic. I think that method is the greatest mystery. I think I have to think it so strongly that I actually made the foolish decision to publish an essay I wrote without having to go through or edit. I didn’t do this generally, I promise. But I did it right away because I was even more frightened of forgetting what I was saying because I was afraid of you seeing through my sad movements toward the beautiful.

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 just trying to contradict what he’s saying, but I’m just trying to give some context to initiatives and opportunities where AI can make a difference 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 words

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

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

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

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

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

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

What if you could request your website to make a complicated map simpler? What if you demanded that the line curve be isolated into just one collection? What if you could request your computer to transform the different lines ‘ colors so they match your color blindness better? What if you could request it to switch shades for habits? Given these resources ‘ chat-based interface and our existing ability to manipulate photos in today’s AI devices, that seems like a chance.

Now imagine a specially designed model that could take the data from that map and turn 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 awesome!

Matching systems

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

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

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

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

Other ways that AI can helps people with disabilities

I’m sure I could go on and on about using AI to assist people with disabilities, but I’m going to make this last section into a bit of a lightning round. In no particular order:

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

The value of various teams and sources of data

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

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

Want a model that doesn’t use ableist language? Before ableist language reaches readers, you might be able to use already-existing data sets to create a filter that can intercept and correct it. That being said, when it comes to sensitivity reading, AI models won’t be replacing human copy editors anytime soon.

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

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

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

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

How we got below

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

The beginning of website standards

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

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

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

The internet as technology platform

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

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

This fusion of potent portable devices and potent creation tools contributed to the growth of social media and other centralized resources for people to use and interact with. As it became easier and more popular to interact with others immediately on Twitter, Facebook, and yet Slack, the need for held private websites waned. Social media made links on a global level, with both positive and negative outcomes.

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

Where we are now

In the last couple of years, it’s felt like we’ve begun to achieve another big tone place. As social-media programs bone and fade, there’s been a growing interest in owning our personal information again. From the tried-and-true classic of hosting plain HTML files to static site generators and content management systems of all kinds, there are many different ways to create websites. Social media fracturing also has a price: we lose essential 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 create incredible personal websites and update them frequently, but without discovery and connection, it can feel as though we could as well be yelling into the void.

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

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

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

Where do we go from here?

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

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

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

Design with care. Whether your craft is code, pixels, or processes, consider the impacts of each decision. Many modern tools have the convenience of having the ability to always understand the decisions that underlie their creation and to never consider the effects those decisions may have. Use the time saved by modern tools to consider more carefully and design with consideration rather than rush to “move fast and break things”

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

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

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

Go forth and make

As designers and developers for the web ( and beyond ), we’re responsible for building the future every day, whether that may take the shape of personal websites, social media tools used by billions, or anything in between. Let’s imbue our values into the things that we create, and let’s make the web a better place for everyone. Create something special for yourself that you are only qualified to create. 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.

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

There are no Lonely Planet and some tour guides for those of you who want to personalize because powerful customisation is so dependent on each group’s talent, technology, and market position.

However, you can make sure your team has properly packed its carriers.

There’s a DIY method to increase your chances for achievement. You’ll at least at least disarm your boss ‘ irrational exuberance. You’ll need to properly plan before the celebration.

We call it prepersonalization.

Behind the audio

Take into account the DJ have on Spotify, which was introduced last year.

We’re used to seeing the polished final outcome of a personalization have. A personal have had to be conceived, budgeted, and prioritized before the year-end prize, the making-of-backstory, or the behind-the-scenes success chest. Before any customisation function is implemented in your product or service, it lives among a long list of thought-provoking concepts that can be used to enhance customer experience more automatically.

So how do you understand where to position your personalization bet? How can you create regular interactions that hasn’t irritate users or worse, breed trust? We’ve discovered that several budgeted programs second required one or more workshops to join key stakeholders and domestic customers of the technology in order to justify their continuing investments. Create it count.

We’ve witnessed the same evolution up near with our clients, from big tech to budding companies. How successfully these prepersonalization actions work out, based on our experience working on small and large customisation initiatives, and how successful these programs are.

Time and again, we’ve seen successful workshops individual coming success stories from fruitless efforts, saving many time, resources, and social well-being in the process.

A personalization process involves a year-long process of testing and characteristic creation. It’s never a technical load switch-flip. It’s ideal managed as a queue that usually evolves through three actions:

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

We think there is a basic language, a set of “nouns and verbs” that your business can use to create experiences that are personalized, personalized, or automated, which is why we created our democratic personalization platform and why we’re field-testing an following deck of cards. You didn’t require these accounts. But we highly recommend that you create something similar, whether that might be online or natural.

Set the timer for the house.

How long does it take to prepare a factory on prepersonalization? The surrounding assessment activities that we recommend including can ( and often do ) span weeks. We suggest aiming for two to three days for the primary workshop. Here are a description of our broad strategy and information on the most crucial first-day activities.

The whole episode of the wider studio is twofold:

Kickstart: This specifies the terms of relationship as you concentrate on the potential, the preparation and drive of your group, and your leadership.
1. Plan your function: This is where the card-based factory activities take place, giving you a work plan and the work scope.
2. Work your plan: This stage is all about creating a competitive environment for staff participants to singularly pitch their personal pilots that each contain a proof-of-concept task, its business situation, and its operating model.

Give yourself at least two days, divided into two long time periods, to work through those initial two phases more effectively.

Kickstart: Apt your appetite

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

Give examples of connected experience interactions that you admire, find familiar, or even dislike, as examples of consumer and business-to-business examples. This should cover a representative range of personalization patterns, including automated app-based interactions ( such as onboarding sequences or wizards ), notifications, and recommenders. We have a list of these in the cards. To jog your mind, here is a list of 142 different interactions.

This is all about setting the table. What are the potential paths the practice could take in your organization? Here’s a long-form primer and a strategic framework for a broader view.

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 break down connected experiences into five categories: functions, features, experiences, complete products, and portfolios. Build your own size 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.

The following 2 2 grid, which lists the four enduring justifications for a personalized experience, should be used as the starting point for each idea. This is crucial because it emphasizes how personalization can affect your own methods of working as well as your external customers. It’s also a reminder ( which is why we used the word argument earlier ) of the broader effort beyond these tactical interventions.

Each team member should vote on where they see your product or service putting its emphasis. Naturally, you can’t give them all a prioritization. Here, the goal is to show how various departments may view their own benefits from the effort, which can vary from one department to the next. Documenting your desired outcomes lets you know how the team internally aligns across representatives from different departments or functional areas.

The third and final KickStart activity is about filling in the personalization gap. Is the customer journey well documented in your business? Will data and privacy compliance be too big of a challenge? Do you have to address any issues with content metadata? ( We’re pretty sure you do; it’s just a matter of acknowledging the magnitude of that need and finding a solution. ) In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six intractable stakeholder attitudes that prevent progress.

It is crucial to your success to work together and manage expectations. Consider the potential barriers to your future progress. Ask the participants to list specific actions you can take to help your organization overcome or reduce those obstacles. As research has shown, personalization initiatives face a number of common obstacles.

You should have, at this point, discussed sample interactions, emphasized a significant benefit, and identified significant gaps. Good—you’re ready to continue.

Hit the test kitchen

What will you need next to bring your personalized recipes to life. Personalization engines, which are robust software suites for automating and expressing dynamic content, can intimidate new customers. They give you a variety of options for how your organization can conduct its activities because of their broad and potent capabilities. This raises the question: When creating a connected experience, where do you start?

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 creating, testing, and improving the snacks and meals that will be a part of your personalizedization program’s constantly evolving menu.

Over the course of the workshop, the ultimate menu of the prioritized backlog will come together. And by creating “dishes,” you can expect individual team members to create personalized interactions that either satisfy their or others ‘ needs.

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

Verify your ingredients

You’ll ensure that you have everything you need to create your desired interaction ( or that you can determine what needs to be added to your pantry like a good product manager ) and that you have validated with the right stakeholders present. These elements include the audience you’re targeting, content and design elements, the interaction’s context, and your idea of how it’ll come together.

This isn’t just about discovering requirements. The team can: Identify your personalizations as a series of if-then statements by documenting them as a series of if-then statements.

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

As a result, you can deliver a common palette of the main themes of your personalized or automated experience while reducing the number of technical efforts required.

Compose your recipe

What elements are significant to you? Consider the construct “what-what-when-why”

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

We first developed these cards and card categories five years ago. We regularly test their compatibility with clients and audience members at conferences. And there are still fresh possibilities. But they all follow an underlying who-what-when-why logic.

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

1. When a visitor or an unidentified visitor interacts with a product title, a banner or alert bar appears that makes it simpler for them to find a related title they might like 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. A user receives an email requesting a promotional offer to suggest they reconsider renewing or to remind them to renew before their subscription expires or after a recent failed renewal.

We’ve also found that cocreating the recipes themselves can sometimes be the most effective way to start brainstorming about what these cards might be for your organization. Start with a set of blank cards, and begin labeling and grouping them through the design process, eventually distilling them to a refined subset of highly useful candidate cards.

The workshop’s later stages, which shift from focusing on cookbooks to focusing on customers, might seem more nuanced. Individual” cooks” will pitch their recipes to the team using a standard jobs-to-be-done format, which will allow for measurement and outcomes, and from there, the resulting collection will be prioritized for finished design and production delivery.

Better kitchens require better architecture

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

When a team overfits: they aren’t designing with their best data, personalization turns into a laughing line. Every organization has metadata debt to go along with its technical debt, which causes a drag on the effectiveness of personalization, much like a sparse pantry. Your AI’s output quality, for example, is indeed limited by your IA. Before they acquired a seemingly modest metadata startup that now powers its underlying information architecture, Spotify’s poster-child prowess today was unfathomable.

You can withstand the heat without a doubt.

Personalization technology opens a doorway into a confounding ocean of possible designs. Only a disciplined and highly collaborative approach will produce the necessary concentration and intention for success. Banish your ideal 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. Both food and mouths must be fed.

You have a better chance of lasting success and sound beginnings with this workshop framework. Wiring up your information layer isn’t an overnight affair. However, if you use the same cookbook and the same recipe combination, you’ll have solid ground for success. We created these activities to ensure that your organization’s needs are clear and concise before the risks start to accumulate.

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 waste it. The pudding is the proof, as they say.

I’ve been fascinated by shows since I was a child. I loved the figures and the excitement—but most of all the reports. I aspired to be an artist. And I backed up the idea that I would get to do the points Indiana Jones did and have interesting adventures. I also dreamed up suggestions for videos that my friends and I could render and sun in. But they never advanced. However, I did end up working in user experience ( UI). Today, I realize that there’s an element of drama to UX— I hadn’t actually considered it before, but consumer analysis is story. And to get the most out of customer studies, you must tell a compelling story that involves stakeholders, including the product team and decision-makers, and piques their interest in learning more.

Think about 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 provides an overview of the current events and allows you to understand the characters, their difficulties, and difficulties. Act two sets the scene for the fight and introduces the behavior. Here, issues grow or get worse. The solution is the third and final work. This is where the problems are resolved and the figures grow 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 for conducting analysis

Unfortunately, some people now believe that study is unprofitable. If finances or timelines are small, analysis tends to be one of the first points to go. Some goods managers rely on designers or, worse, their own mind to make the “right” decisions for users based on their own knowledge or accepted best practices rather than investing in research. That may get groups a little bit out of the way, but that approach is therefore easily miss out on resolving people ‘ real issues. To be user-centered, this is something we really avoid. Design is enhanced by consumer study. It keeps it on track by pointing out issues and options. Being aware of the issues with your product and reacting to them can help you stay away of your competition.

Each action corresponds to a stage of the process in the three-act structure, and each stage is crucial to telling the complete story. Let’s take a look at the various functions and how they relate to consumer research.

Act one: layout

Fundamental analysis comes in handy because the layout is all about comprehending the background. Basic research ( also known as conceptual, discovery, or preliminary research ) aids in understanding users and identifying their issues. You’re learning about what exists now, the obstacles people have, and how the problems affect them—just like in the videos. You can conduct contextual inquiries or diary studies ( or both! ) to conduct foundational research. ), which may assist you in identifying both problems and opportunities. It doesn’t need to get a great investment in time or money.

What is the least practical ethnography that Erika Hall can do is spend fifteen minutes with a consumer and say,” Walk me through your day yesterday. That is it. Provide that one ask. Locked up and spend fifteen minutes listening. Do everything in your power to protect both your objectives and yourself. Bam, you’re doing ethnography”. Hall predicts that “[This ] will definitely prove quite fascinating. In the unlikely event that you don’t learn anything new or helpful, move on with more self-assurance in your direction.

This makes total sense to me. And I adore how consumer research is made so simple. You can simply attract participants and carry out the recruitment process without having to make a lot of paperwork! This can offer a wealth of knowledge about your customers, and it’ll help you better understand them and what’s going on in their life. Understanding where people are coming from is what action one is really all about.

Jared Spool discusses the significance of basic research and how it does make up the majority of your study. If you can pick from any further user data that you can get your hands on, such as surveys or analytics, that can complement what you’ve heard in the fundamental studies or even time to areas that need more research. All of this information helps to reveal both the state of items and its flaws more clearly. And that’s the start of a gripping tale. It’s the place in the story where you realize that the principal characters—or the people in this case—are facing issues that they need to conquer. This is where you begin to develop compassion for the characters and support their success, much like in films. And hey, it looks like everyone else is doing the same. Their love may be with their company, which could be losing wealth because people didn’t complete certain tasks. Or perhaps they have empathy for people ‘ problems. In either case, action one serves as your main strategy for piqueing interest and investment from the participants.

When partners begin to understand the value of basic research, that is open doors to more opportunities that involve users in the decision-making approach. And that can help product teams become more user-centric. Everyone benefits from this, including the product, users, and stakeholders. It’s like winning an Oscar in movie terms—it often leads to your product being well received and successful. And this might encourage stakeholders to carry out this process with additional products. Knowing how to tell a good story is the only way to convince stakeholders to care about doing more research, and storytelling is the key to this process.

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

Act two: conflict

Act two is all about approving the issues you raised 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. Unmet needs or issues with a flow or process that is causing users to flee could be the causes. More problems will come up in the process, much like in the second act of a film. It’s here that you learn more about the characters as they grow and develop through this act.

According to Jakob Nielsen, five users should be typically in usability tests, which means that this number of users can typically identify the majority of the issues:” You learn less and less as you add more and more users because you will keep seeing the same things over and over again… After the fifth user, you are wasting your time by repeatedly observing the same findings but not learning much new.”

The plot may get lost if you try to tell a story with too many characters, which also applies to storytelling. 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 to convey the problems that need to be addressed while also highlighting the significance of conducting initial research.

Usability tests have been conducted in person for decades, but you can also conduct them remotely using software like Microsoft Teams, Zoom, or other teleconferencing software. This approach has become increasingly popular since the beginning of the pandemic, and it works well. You might consider in-person usability tests like watching a movie as opposed to remote testing like attending a play. Each has advantages and disadvantages. In-person usability research is a much richer experience. The sessions are conducted with other stakeholders in mind. Additionally, you get real-time reactions, including surprises, disagreements, and discussions about what they’re seeing. Much like going to a play, where audiences get to take in the stage, the costumes, the lighting, and the actors ‘ interactions, in-person research lets you see users up close, including their body language, how they interact with the moderator, and how the scene is set up.

If conducting usability testing in the field is like watching a play that is staged and controlled, where any two sessions may be very different from one another. You can conduct usability testing in real life by creating a replica of the product’s user interface and conducting research there. Or you can go out to meet users at their location to do your research. With either option, you can see how things work in context, how things develop in ways that wouldn’t have in a lab setting, and how conversion can occur in completely different ways. You have less control over how these sessions end as researchers, but this can occasionally 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 add a level of detail that remote usability tests frequently lack.

That’s not to say that the “movies” —remote sessions—aren’t a good option. Remote sessions can reach a wider audience. They make it possible for much more people to participate in the research and to observe what is happening. Additionally, they make the doors accessible to a much wider range of users. But with any remote session there is the potential of time wasted if participants can’t log in or get their microphone working.

The advantage of usability testing, whether conducted remotely or in person, is that you can ask real users questions to understand their reasoning and understanding of the problem. This can help you identify issues as well as understand why they were initially issues. Furthermore, you can test hypotheses and gauge whether your thinking is correct. By the end of the sessions, you’ll have a much clearer understanding of how useful the designs are and whether or not they fulfill their intended purpose. The excitement centers on Act 2, but there are also potential surprises in that Act. This is equally true of usability tests. Unexpected things that are said by participants frequently alter how you view things, and these unexpected developments in the story can lead to unexpected turns in your perception.

Unfortunately, user research can occasionally be viewed as unreliable. And too often usability testing is the only research process that some stakeholders think that they ever need. There isn’t much to be gained by conducting usability testing in the first place if the designs you’re evaluating in the usability test aren’t grounded in a thorough understanding of your users ( foundational research ). Because you’re narrowing the scope of what you’re receiving feedback on without understanding the needs of the users. As a result, there’s no way of knowing whether the designs might solve a problem that users have. In the context of a usability test, it’s only feedback on a particular design.

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

In act two, stakeholders will hopefully be able to observe the story develop during the user sessions, which reveal the conflict and tension in the current design’s highs and lows. And in turn, this can encourage stakeholders to take action on the issues raised.

Act three: resolution

The third act is about resolving the issues from the first two acts, while the first two acts are about understanding the background and the tensions that can compel stakeholders to take action. While it’s crucial to have an audience for the first two acts, it’s crucial that they stay 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 entire team to discuss what’s possible within the project’s constraints, ask questions, and discuss user feedback together. Additionally, it enables the UX design and research teams to clarify, suggest alternatives, or provide more context for their choices. So you can get everyone on the same page and get agreement on the way forward.

This act is primarily told in voiceover with some audience participation. The researcher serves as the narrator, who depicts the issues and what the product’s future might look like given the lessons the team has learned. They give the stakeholders their recommendations and their guidance on creating this vision.

In the Harvard Business Review, Nancy Duarte describes a method for structuring presentations that follow a persuasive narrative. The most effective presenters employ the same methods as great storytellers: they create a conflict that needs to be settled by reminding people of the status quo and then revealing a better way, according to Duarte. ” That tension helps them persuade the audience to adopt a new mindset or behave differently”.

This kind of structure is in line with research findings, particularly those from usability tests. It provides evidence for “what is “—the problems that you’ve identified. And your suggestions for how to deal with them are “what could be.” And so forth and forth.

You can reinforce your recommendations with examples of things that competitors are doing that could address these issues or with examples where competitors are gaining an edge. Or they can be visual, like quick sketches of how a new design could function to solve a problem. These can help create momentum and conversation. 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. The part where you make a second or third reference to the main themes or issues or concerns for the product is when you make the denouement of the story. The stakeholders will now have the opportunity to take the next steps, and hopefully the will-power to do so!

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

Act one: You encounter both the users ‘ protagonists and the antagonists ( the user-related issues ). This is the beginning of the plot. Researchers might employ techniques like contextual inquiry, ethnography, diary studies, surveys, and analytics in act one. These techniques can produce personas, empathy maps, user journeys, and analytics dashboards as output.

Act two: Next, there’s character development. The protagonists face problems and difficulties, which they must overcome, and there is conflict and tension. Researchers might employ heuristics evaluation, usability testing, competitive benchmarking, and other methods in act two. The output of these can include usability findings reports, UX strategy documents, usability guidelines, and best practices.

Act three: The main characters win, and the audience is shown a better future. Researchers may use techniques like presentation decks, storytelling, and digital media in act three. The output of these can be: presentation decks, video clips, audio clips, and pictures.

The researcher performs a number of tasks: they are the producer, the director, and the storyteller. Although the participants are only a small part in the study, they are significant characters. And the stakeholders are the audience. However, the most crucial thing is to get the story straight and to use storytelling to research user stories. By the end, the parties should have a goal and a desire to solve the product’s flaws.

So the next time that you’re planning research with clients or you’re speaking to stakeholders about research that you’ve done, think about how you can weave in some storytelling. User research is ultimately a win-win situation for everyone, and all you need to do is pique stakeholders ‘ interest in how the story ends.

This week, Booth Perkins makes a big step into King region by turning Stephen King’s 30-page, 1980 brief account” The Monkey” into a maniac. The film, like the original story, focuses on twin brothers named Hal and Bill ( Christian Convery as children ) who discover an old drumming monkey ]…]

The Monkey: Oz Perkins Uses a Classic Stephen King Story to Show the Funny Side of Death initially appeared on Den of Geek.

When one becomes a part of the Saturday Night Live community, it takes a lot to find excommunicated.

The most infamous case of a innovative not being invited back to NBC &#8217, s long-running comedic establishment is, of course, Sinéad O&#8217, Connor. In a 1992 show of SNL, the British singer, songwriter, and advocate concluded a handle of Bob Marley &#8217, s &#8220, War&#8221, by tearing a portrait of then-Pope John Paul II to pieces. Though O&#8217, Connor&#8217, s stated goal of protesting the Catholic Church&#8217, s story of physical, sexual and emotional abuse of adolescent congregation was also reasoned, it was perhaps to ahead of its time. She would then be criticized by numerous companies before ever being denied SNL‘s ability to return.

Following O&#8217, Connor&#8217, s dying in 2023, SNL began to loosen its attitude towards her provocative performance. The best mea culpa arrived on February 16, 2025, during the present &#8217, s sprawling, three-hour-long spread SNL50: The Celebration Special, in which Miley Cyrus and Brittany Howard covered O&#8217, Connor&#8217, s traditional &#8220, Nothing Compares 2 U. &#8221, While that was probably the biggest time of peace in SNL50, there was another, much person, example of a banished entertainer getting a cry near the end of the exclusive.

When Adrien Brody hosted Saturday Night Live for the first and only day in May 2003, he was on top of the world. Brody was eager to handle whatever SNL had put his manner, having just won a Best Artist Oscar for his amazing change in The Pianist two months prior. Unfortunately, he was very ready and to activity as the dedicated SNL inventor Lorne Michaels &#8217, saint sin: he went off script.

When the time came to welcome musical guest Sean Paul &#8211, which is typically a straightforward, tedious task for the host &#8211, Brody made the decision to spice things up a little. He staged himself in a dreadlocked wig and extensively vamped in a hostile Jamaican patois about &#8230, people dubbed Sean. And said &#8220, respeck mah neck&#8221, a couple of times? It was at least a little bit racist, a lot of bit incomprehensible, and most damningly for the live show, completely unplanned.

Brody has criticized the claim that he was barred from SNL in recent interviews to promote The Brutalist ( for which he will likely win another Oscar ), telling Vulture that Lorne wasn’t happy with me embellishing a little, but they allowed me to. ”Ban or no ban, Brody joined the ranks of people like O’Connor who were pointlessly never invited back to Studio 8H.

Important dates like anniversaries have a way of healing old wounds, of course. Because, while Brody didn&#8217, t receive as touching a shoutout as O&#8217, Connor did in SNL50, his inexplicable Rastaman improv did make an appearance in a hilarious compilation. Introduced by Tom Hanks, SNL50: The Anniversary Special took some time out for a special &#8220, In Memorium&#8221, segment of canceled SNL characters and moments that were no longer appropriate for the modern world.

The reasoning for many of these canceled artifacts were clear from &#8220, ethnic stereotypes &#8221, to &#8220, body shaming &#8221, to &#8220, sexual harassment. &#8221, Adrien Brody &#8217, s rasta moment, however, was accompanied by a simple &#8220, woah. &#8221, All these years later, there seems no better way to describe whatever it was that was than &#8220, woah. &#8221,

The post SNL50 Referenced Saturday Night Live&#8217, s Strangest Hosting Controversy appeared first on Den of Geek.

Most of 2016’s Steve Rogers: Captain America# 1 plays like a normal adventure starring the Sentinel of Liberty. Cap and his allies are on a rescue mission in 1926 New York, and we ultimately face traditional criminal Baron Zemo in between memories to Steve’s childhood. However, the final splash page, after Cap has defeated Zemo]… ]

The Divisive Captain America Comic That Defined Sam Wilson as Cap was the first blog to appear on Den of Geek.

When one becomes a part of the Saturday Night Live community, it takes a lot to find excommunicated.

The most infamous case of a innovative not being invited back to NBC &#8217, s long-running comedic establishment is, of course, Sinéad O&#8217, Connor. In a 1992 show of SNL, the British singer, songwriter, and advocate concluded a handle of Bob Marley &#8217, s &#8220, War&#8221, by tearing a picture of then-Pope John Paul II to pieces. Though O&#8217, Connor&#8217, s stated goal of protesting the Catholic Church&#8217, s story of physical, sexual and emotional abuse of adolescent congregation was also reasoned, it was perhaps to ahead of its time. She would then continue to receive harsh criticism from numerous companies before being permanently prohibited from ever returning to SNL.

Following O&#8217, Connor&#8217, s dying in 2023, SNL began to loosen its attitude towards her provocative performance. The best mea culpa arrived on February 16, 2025, during the present &#8217, s sprawling, three-hour-long spread SNL50: The Celebration Special, in which Miley Cyrus and Brittany Howard covered O&#8217, Connor&#8217, s typical &#8220, Nothing Compares 2 U. &#8221, While that was probably the biggest time of peace in SNL50, there was another, much person, example of a banished entertainer getting a cry near the end of the exclusive.

When Adrien Brody hosted Saturday Night Live for the first and only day in May 2003, he was on top of the world. Brody was eager to take any challenge SNL had put his manner, having just won the Best Artist Oscar for his amazing change in The Pianist two months prior. Unfortunately, he was very ready and to match as the dedicated SNL inventor Lorne Michaels &#8217, saint sin: he went off script.

Brody chose to spice things up a little when it came time to welcome musical host Sean Paul &#8211, which is typically a straightforward, trivial work for the host &#8211. He staged himself in a bearded wig and heavily vamped during a hostile Reggae patois, dubbed Sean, by the audience. And said &#8220, respeck mah neck&#8221, a couple of times? It was at least a little bit racist, a lot of little inexplicable, and most glaringly for the life present, fully unplanned.

Brody has criticized the claim that he was barred from SNL in recent interviews to promote The Brutalist ( for which he will likely win another Oscar ), telling Vulture that Lorne wasn’t happy with me embellishing a little, but they allowed me to. ”Ban or no ban, Brody joined the ranks of people like O’Connor who were pointlessly never invited back to Studio 8H.

Important dates like anniversaries have the ability to heal old wounds, of course. Because, while Brody didn&#8217, t receive as touching a shoutout as O&#8217, Connor did in SNL50, his inexplicable Rastaman improv did make an appearance in a hilarious compilation. Introduced by Tom Hanks, SNL50: The Anniversary Special took some time out for a special &#8220, In Memorium&#8221, segment of canceled SNL characters and moments that were no longer appropriate for the modern world.

The reasoning for many of these canceled artifacts were clear from &#8220, ethnic stereotypes &#8221, to &#8220, body shaming &#8221, to &#8220, sexual harassment. &#8221, Adrien Brody &#8217, s rasta moment, however, was accompanied by a simple &#8220, woah. &#8221, All these years later, there seems no better way to describe whatever it was that was than &#8220, woah. &#8221,

The post SNL50 Referenced Saturday Night Live&#8217, s Strangest Hosting Controversy appeared first on Den of Geek.