Blog

In tomorrow’s data-driven environment, it’s becoming more and more common for a UX expert to be asked to create a personal digital experience, whether it’s a common website, user portal, or local application. But while there continues to be no lack of marketing buzz around personalization systems, we also have very few defined approaches for implementing personalized UX.

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

Getting Started

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

Common scenarios for starting a personalisation task:

• Your business or client made a purchase to support personalization of 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 unclear or disjointed.
• You are running some secluded targeting strategies or A/B tests
• On the personalisation approach, stakeholders disagree.
• Mandate of customer privacy rules ( e. g. GDPR ) requires revisiting existing user targeting practices

Regardless of where you begin, a powerful personalization system will require the same key creating stones. These are the “levels” on the tower, as we’ve made them. Whether you are a UX artist, scholar, or planner, understanding the core components may help make your contribution effective.

From top to bottom, the rates include:

North Star: What larger geopolitical goal is the personalisation initiative pursuing?
1. Objectives: What are the specific, tangible benefits of the system?
2. Touchpoints: Where will you get customized service?
3. Contexts and Campaigns: What personalization information does the person view?
4. What constitutes a distinct, suitable audience? User Parts
5. Actionable Data: What dependable and credible information is captured by our professional platform to generate personalization?
6. Natural Data: What wider set of data is conceivable ( now in our environment ) to allow you to optimize?

We’ll go through each of these amounts in turn. To make this more bearable, we created a deck of cards that accompany it to show specific instances from each stage. We’ve found them helpful in customisation pondering periods, and will include cases for you here.

Starting at the Top

The parts of the pyramids are as follows:

North Star

With your personalisation plan, whether large or small, you aim for a general north star. The North Star defines the (one ) overall mission of the personalization program. What do you hope to accomplish? North Stars cast a ghost. The darkness is bigger the sun the bigger the sun. Example of North Starts may incorporate:

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

Goals

Personalization can help speed up designing with user intentions, as in any great UX design. Goals are the military and tangible metrics that may prove the entire program is effective. A good place to begin is with your existing analytics and calculation software and metrics you can standard against. In some cases, new targets may be ideal. The most important thing to keep in mind is that personalisation is not a desired outcome. It is a means to an end. Common targets include:

• Conversion
• Time spent on work
• Net promoter score ( NPS)
• Satisfaction of the customers

Touchpoints

Touchpoints are where the personalisation happens. This will be one of your biggest areas of responsibility as a UX custom. The contacts available to you will depend on how your personalization and associated technologies capabilities are instrumented, and should be rooted in improving a person’s experience at a certain point in the trip. Touchpoints can be multi-device ( mobile, in-store, website ), but they can also be more specific ( web banner, web pop-up, etc. ). Voici some illustrations:

Channel-level touchpoints

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

Wireframe-level Touchpoints

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

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

Contexts and Campaigns

Once you’ve identified some touchpoints, you can decide what kind of personalized content a user will receive. Many personalization tools will refer to these as” campaigns” ( so, for example, a campaign on a web banner for new visitors to the website ). These will be displayed programmatically to specific user segments, as defined by user data. At this stage, we find it helpful to consider two separate models: a context model and a content model. The context helps you consider whether a user is engaging with the personalization process at the moment, such as when they are simply browsing the web or engaging in a deep dive. Think of it in terms of information retrieval behaviors. The content model can then guide you in deciding what kind of personalization to use in the context ( for instance, an” Enrich” campaign that features related articles might be a good substitute for extant content ).

Personalization Context Model:

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

Content model for personalization:

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

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

User Groups

User segments can be created prescriptively or adaptively, based on user research ( e. g. via rules and logic tied to set user behaviors or via A/B testing ). You will need to think about how to treat the logged-in visitor, the guest or returning visitor for whom you may have a stateful cookie ( or another post-cookie identifier ), or the authenticated visitor who is logged in at the very least. Here are some examples from the personalization pyramid:

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

Actionable Data

Every organization with any digital presence has data. It’s a matter of examining what user data you can ethically collect, its inherent reliability and value, and how you can use it ( sometimes referred to as “data activation” ). Fortunately, the tide is turning to first-party data: a recent study by Twilio estimates some 80 % of businesses are using at least some type of first-party data to personalize the customer experience.

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

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

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

Pulling it Together

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

In assembling a card “hand”, one can begin to trace the entire trajectory from leadership focus down through a strategic and tactical execution. It is also at the heart of the way 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, what is important to note is that each colored class of card is helpful to survey in understanding the range of choices potentially at your disposal, it is threading through and making concrete decisions about for whom this decisioning will be made: where, when, and how.

Lay Down Your Cards

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

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

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

The Absurd Pate of Justin: The Tale of Justin

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

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 wanted—nay, needed—to better understand the underlying relevance of what my design decisions may think when rendered in a website.

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

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

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

For instance, this iteration of my personal portfolio site (” the pseudoroom” ) from that time was experimental if not a little overt with regard to how the idea of a living sketchbook was conveyed visually. Very skeuomorphic. This one involved sketching and then passing a Photoshop file back and forth to experiment with various user interactions with fellow designer and dear friend Marc Clancy, who is now a co-founder of the creative project organizing app Milanote. Then, I’d break it down and code it into a digital layout.

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

GUI Galaxy was a design, pixel art, and Mac-centric news portal that my friends and I conceptualized, designed, developed, and deployed around the same time.

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

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

The presentation layer, which included global design, illustration, and news author collaboration, was the backbone of the website. And the collaboration effort here, in addition to experimentation on a’ brand’ and content delivery, was hitting my core. We were creating something bigger than just one of us and establishing a global audience.

Collaboration and connection transcend medium in their impact, immensely fulfilling 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 put it ): the inherent exploration, personality, and creativity that dominated many design portals and personal portfolio websites. Ultra-finely detailed pixel art UI, custom illustration, bespoke vector graphics, all underpinned by a strong design community.

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

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

Pixel Issues

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

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

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

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

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

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

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

This is the Kaliber 1000, or K10k, abbreviated. K10k was founded in 1998 by Michael Schmidt and Toke Nygaard, and was the design news portal on the web during this period. With its pixel art-fueled presentation, attention to detail paid to every aspect of every detail, and many of the more well-known designers of the time who were invited to be news authors on the site, well… it was the place to be, my friend. With respect where respect is due, GUI Galaxy’s concept was inspired by what these folks were doing.

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

Amongst my personal work and side projects —and now with this inclusion—in the design community, this put me on the map. Additionally, my design work has started to appear on other design news portals, as well as 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 actually changed into a colossal asshole in about a year of school, not less. The press and the praise became what fulfilled me, and they went straight to my head. My ego was inflated by them. I actually felt somewhat superior to my fellow designers.

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

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

Some of my friendships and blossoming professional relationships almost ended up being destroyed by my ego. I was toxic in talking about design and in collaboration. But thankfully, 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. Although the realization made me feel uneasy, the re-awakening was necessary. I let go of the “reward” of adulation and re-centered upon what stoked the fire for me in art school. Most importantly, I returned to my fundamental values.

Always Students

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

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

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

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

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

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

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

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

However, remember that “experience” does not equate to “expert.”

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

I am imaginative. What I do is alchemy. It is a secret. I prefer to let it be done through me rather than through me.

I have a creative side. No all creative people approve of this brand. Not all people see themselves in this manner. Some innovative people practice scientific in their work. That is their perception, and I regard it. Perhaps I have a little bit of fear for them. However, my method is different; my being is unique.

It distracts you to apologize and qualify in progress. My brain uses that to destroy me. I’ll leave it alone for today. I may regret and then define. after I’ve said what I should have. which is sufficient.

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

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

Maybe I work and work and work until the thought strikes me. It occasionally arrives right away, but I don’t remind people for three weeks. Sometimes I get so excited about something that just happened that I blurt it out and didn’t stop myself. like a child who discovered a prize in one of his Cracker Jacks. I occasionally manage to escape this. Yes, that is the best idea, but sometimes another people disagree. The majority of the time, they don’t, and I regret that joy has faded.

Passion should only be saved for the meet, when it matters. Certainly the informal get-together that comes before that meeting with two more meetings. Nothing understands why we hold these gatherings. 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. Sometimes they detract from the real function, though. Depending on what you do and where you do it, the ratio between when conferences are valuable and when they are a sad distraction vary. And who you are and how you go about doing it. Once, I digress. I am imaginative. That is the design.

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

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

I have a creative side. I have no power over my goals. And I have no control over my best tips.

I can chisel aside, surround myself with information or photos, and occasionally that works. Often going for a walk is what I may do. There is no connection between sizzling fuel and flowing pots, and I may be making dinner. I frequently have a sense of direction when I awaken. The idea that may have saved me disappears almost as frequently as I become aware and a part of the world once more as a thoughtless wind of oblivion. For imagination, in my opinion, comes from that other planet. The one that we enter in goals, and possibly before and after death. I’m not a writer, so that’s up to authors to think about. I am imaginative. Theologians are encouraged to build massive armies in their artistic world, which they insist is true. But that is yet another diversion. And a sad one. Possibly on a much bigger issue than whether or not I am creative. But this is still a departure from what I said when I came around.

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

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

Artists are recognized as designers.

Negatives are aware of cons, just like queers are aware of queers, just like real rappers are aware of true rappers are aware of cons. Artists are highly revered by people in the world. We revere, follow, and almost deify the great types. Of course, it is dreadful to revere any person. We’ve been given a warning. We are more knowledgeable. We are aware that people are simply people. They argue, they are depressed, they regret their most important choices, they are weak and hungry, they can be violent, and they can be as terrible as we can because they are clay, just like us. But. But. However, they produce this incredible issue. They give birth to something that may not occur without them and did not exist before them. They are the inspirations ‘ mother. And I suppose I should add that they are the mother of technology because it’s just lying it. Bad mee backside! Okay, that’s all said and done. Continue.

Creatives denigrate our personal small accomplishments because they are compared to those of the wonderful people. Wonderful video! I‘m not Miyazaki, so I‘m not. Greatness is then that. That is glory straight out of the Bible. I created this drained small thing. It essentially fell off the turnip truck’s up. And the carrots weren’t actually new.

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

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

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

I can move ten times more quickly than those who aren’t imaginative, those who have just been creative for a short while, and those who have just had a short time of creative work. Only that I 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 wonderful career. I have an addiction to the delay rush. I also have a fear of the climb.

I am hardly a painter.

I have a creative side. Never a performer. Though as a child, I had a dream that I would one day become that. Some of us criticize our abilities and fear our own accomplishments because we are not Michelangelos and Warhols. That is narcissism, but at least we don’t practice politicians.

I have a creative side. Despite my belief in reason and science, my decisions are based on my own senses. and accept both the successes and the calamities that come with them.

I have a creative side. Every term I’ve said these may irritate another artists who have different viewpoints. Ask a question to two designers, and you’ll find three responses. Our dispute, our interest in it, and our commitment to our own truth, at least in my opinion, are the proof that we are creative, no matter how we does think about it.

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

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

Working frees me from worrying about my job.

I have a creative side. I fear that my little present will disappear.

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

I have a creative side. I think there is the greatest secret in the process. I think I have to consider it so strongly that I actually made the foolish decision to publish an essay I wrote without having to go through or edit. I swear I didn’t accomplish this frequently. But I did it right away because I was even more frightened of forgetting what I was saying because I was afraid of you seeing through my sad gestures toward the beautiful.

There. I believe I said it correctly.

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

Other words

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

As Joe points out, human-in-the-loop editing of ctrl text should definitely be a factor. And if AI can intervene and provide a starting point for alt text, even if the swift 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 station a design to examine image usage in context, it might help us more quickly determine which images are likely to be elegant and which ones are likely to need a description. That will clarify which situations require image descriptions, and it will increase authors ‘ effectiveness in making their sites more visible.

While complex images—like graphs and charts—are challenging to describe in any sort of succinct way ( even for humans ), the image example shared in the GPT4 announcement points to an interesting opportunity as well. Let’s say you came across a map that was simply the name of the table and the type of visualization it was: Pie table comparing smartphone use to have phone use among US households making under$ 30, 000 annually. ( That would be a pretty bad alt text for a chart because it would frequently leave many unanswered questions about the data, but let’s just assume that that was the description in place. ) If your browser knew that that image was a pie chart ( because an onboard model concluded this ), imagine a world where users could ask questions like these about the graphic:

• Do more people use smartphones or other types of smartphones?
• How many more?
• Is there a group of people that don’t fall into either of these buckets?
• That number, how many?

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

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

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

Matching algorithms

When Safiya Umoja Noble chose to write her book Algorithms of Oppression, she hit the nail on the head. Although her book focused on how search engines can foster racism, I believe it’s equally true that all computer models have the potential to foster conflict, prejudice, and intolerance. Whether it’s Twitter always showing you the latest tweet from a bored billionaire, YouTube sending us into a Q-hole, or Instagram warping our ideas of what natural bodies look like, we know that poorly authored and maintained algorithms are incredibly harmful. A large portion of this is a result of a lack of diversity in the people who design and construct them. However, when these platforms are built with inclusive features in mind, there is real potential for algorithm development to help people with disabilities.

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

More people with disabilities can be used to create algorithms, which can lessen the likelihood that they will harm their communities. That’s why diverse teams are so crucial.

Imagine that a social media company’s recommendation engine was tuned to analyze who you’re following and if it was tuned to prioritize follow recommendations for people who talked about similar things but who were different in some key ways from your existing sphere of influence. For instance, if you followed a group of nondisabled white male academics who spoke about AI, it might be advisable to follow those who are disabled, aren’t white, or aren’t men who also speak about AI. If you followed its recommendations, you might learn more about what’s happening in the AI field. These same systems should also use their understanding of biases about particular communities—including, for instance, the disability community—to make sure that they aren’t recommending any of their users follow accounts that perpetuate biases against (or, worse, spewing hate toward ) those groups.

Other ways that AI can assist people with disabilities

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

Voice preservation You may be aware of the voice-prescribing options from Microsoft, Acapela, or others, or you may have seen the announcement for VALL-E or Apple’s Global Accessibility Awareness Day. It’s possible to train an AI model to replicate your voice, which can be a tremendous boon for people who have ALS ( Lou Gehrig’s disease ) or motor-neuron disease or other medical conditions that can lead to an inability to talk. This technology can also be used to create audio deepfakes, so it’s something we need to approach responsibly, but the technology has truly transformative potential.
• Voice recognition. Researchers like those in the Speech Accessibility Project are paying people with disabilities for their help in collecting recordings of people with atypical speech. As I type, they are actively seeking out people who have Parkinson’s and related conditions, and they intend to expand this list as the project develops. More people with disabilities will be able to use voice assistants, dictation software, and voice-response services as a result of this research, which will result in more inclusive data sets that will enable them to use their computers and other devices more easily and with just their voices.
• Text transformation. The most recent generation of LLMs is capable of altering already-existing text without giving off hallucinations. This is incredibly empowering for those who have cognitive disabilities and who may benefit from text summaries, simplified versions, or even text that has been prepared for Bionic Reading.

The importance of diverse teams and data

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

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

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

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

I have no doubts about how dangerous AI can and will be for people today, tomorrow, and for the rest of the world. However, I also think we should acknowledge this and make thoughtful, thoughtful, and intentional changes to our approaches to AI that will reduce harm over time as well. Today, tomorrow, and well into the future.

Thanks to Kartik Sawhney for assisting me with writing this article, 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.

online standards were born.

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

Server-side language like PHP, Java, and.NET took Perl as the primary back-end computers, and the cgi-bin was tossed in the garbage bin. With these improved server-side equipment, the first period of internet programs started with content-management methods (especially those used in blogs like Blogger, Grey Matter, Movable Type, and WordPress ) In the mid-2000s, AJAX opened gates for sequential interaction between the front end and back finish. Pages had now revise their content without having to reload. A grain of Script frameworks like Prototype, YUI, and ruby arose to aid developers develop more credible client-side interaction across browsers that had wildly varying levels of standards support. Techniques like image replacement enable skilled designers and developers to display fonts of their choosing. And technologies like Flash made it possible to add animations, games, and even more interactivity.

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

The web as software platform

The front-end and back-end symbiosis continued to improve, leading to the development of the modern web application. Between expanded server-side programming languages ( which kept growing to include Ruby, Python, Go, and others ) and newer front-end tools like React, Vue, and Angular, we could build fully capable software on the web. Along with these tools, there were additional options, such as collaborative build automation, collaborative version control, and shared package libraries. What was once primarily an environment for linked documents became a realm of infinite possibilities.

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

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

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

Where we are now

It seems like we’ve been at a new significant inflection point over the past couple of years. As social-media platforms fracture and wane, there’s been a growing interest in owning our own content 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. The fracturing of social media also comes with a cost: we lose crucial infrastructure for discovery and connection. Webmentions, RSS, ActivityPub, and other IndieWeb tools can be useful in this regard, but they’re still largely underdeveloped and difficult to use for the less geeky. We can build amazing personal websites and add to them regularly, but without discovery and connection, it can sometimes feel like we may as well be shouting into the void.

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

With a few commands and a few lines of code, we can currently prototype almost any concept. All the tools that we now have available make it easier than ever to start something new. However, 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.

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

Where do we go from here?

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

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

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

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

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

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

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

Make a move and make it happen.

As designers and developers for the web ( and beyond ), we’re responsible for building the future every day, whether that may take the shape of personal websites, social media tools used by billions, or anything in between. Let’s incorporate our values into the products we produce, and let’s improve the world for everyone. Create that thing that only you are uniquely qualified to make. Then distribute it, improve it, re-use it, or create something new with it. Learn. Make. Share. Grow. Rinse and repeat. Everything will change whenever you believe you’ve mastered the web.

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

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

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

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

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

We call it prepersonalization.

Behind the music

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

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

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

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

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

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

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

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

Set your kitchen timer

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

The full arc of the wider workshop is threefold:

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

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

Kickstart: Whet your appetite

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

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

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

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

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

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

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

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

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

Hit that test kitchen

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

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

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

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

Verify your ingredients

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

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

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

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

Compose your recipe

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

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

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

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

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

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

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

Better kitchens require better architecture

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

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

You can definitely stand the heat…

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

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

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

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

Think of your favourite film. It probably follows a three-act narrative architecture: the installation, the conflict, and the resolution, which is prevalent in literature. The second act shows what exists now, and it helps you get to know the figures and the challenges and problems that they face. Act two sets the scene for the fight and the activity begins. Here, difficulties grow or get worse. The solution comes in the third and final action. This is where the issues are resolved and the figures learn and change. This architecture, in my opinion, is also a fantastic way to think about consumer research, and it might be particularly useful for introducing user research to others.

Use story as a framework when conducting study.

It’s sad to say, but many have come to view studies as being inconsequential. Research is typically one of the first things to go when expenses or deadlines are tight. Instead of investing in study, some goods professionals rely on manufacturers or—worse—their personal judgment to make the “right” options for users based on their experience or accepted best practices. That may 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. User study improves pattern. It keeps it on trail, pointing to problems and opportunities. You can keep back of your competition by being aware of the problems with your goods and fixing them.

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

Act one: installation

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

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

This makes perfect sense to me. And I love that this makes consumer research so visible. 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. That’s exactly what work one is all about: understanding where people are coming from.

Maybe Spool talks about the importance of basic research and how it really type the bulk of your research. If you can supplement what you’ve heard in the fundamental studies by using any more user data that you can obtain, such as surveys or analytics, to make recommendations that may need to be investigated further, you might as well use those that can be drawn from those that you can obtain. Together, all this information creates a clearer picture of the state of things and all its deficiencies. And that’s the start of a gripping tale. It’s the place in the story where you realize that the principal characters—or the people in this case—are facing issues that they need to conquer. This is where you begin to develop compassion for the characters and support their success, much like in films. And maybe partners are now doing the same. Their business may lose money because users can’t finish specific tasks, which may be their love. Or probably they do connect with customers ‘ problems. In either case, action one serves as your main strategy to pique the interest and interest of 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 influence product groups ‘ focus on improving. This gains everyone—users, the goods, and partners. It’s similar to winning an Oscar for a film; it frequently results in a favorable reception and success for your item. And this can be an opportunity for participants to repeat this process with different items. Knowing how to show a good story is the only way to convince partners to worry about doing more research, and story is the key to this method.

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

Act two: issue

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

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

There are parallels with storytelling here too, if you try to tell a story with too many characters, the plot may get lost. With fewer participants, each user’s struggles will be more easily recalled and shared with other parties when discussing the research. This can help convey the issues that need to be addressed while also highlighting the value of doing the research in the first place.

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

If conducting usability testing in the field is like watching a play that is staged and controlled, where any two sessions may be very different from one another. You can take usability testing into the field by creating a replica of the space where users interact with the product and then conduct your research there. Or you can conduct your research by meeting users at their locations. With either option, you get to see how things work in context, things come up that wouldn’t have in a lab environment—and conversion can shift in entirely different directions. You have less control over how these sessions 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 training sessions can reach a wider audience. They allow a lot more stakeholders to be involved in the research and to see what’s going on. Additionally, they make access to a much wider user base geographically. But with any remote session there is the potential of time wasted if participants can’t log in or get their microphone working.

The advantage of usability testing, whether conducted remotely or in person, is that you can ask real users questions to understand their reasoning and understanding of the problem. This can help you not only identify problems but also glean why they’re problems in the first place. You can also test your own ideas and determine whether they are true. By the end of the sessions, you’ll have a much clearer picture of how usable the designs are and whether they work for their intended purposes. The excitement is in the second act, but there are also potential surprises in the third. This is equally true of usability tests. Unexpected things that participants say frequently alter the way you look at things, and these unexpected revelations can lead to unexpected turns in the narrative.

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

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

In act two, stakeholders will—hopefully—get to watch the story unfold in the user sessions, which creates the conflict and tension in the current design by surfacing their highs and lows. And in turn, this can encourage stakeholders to take action on the issues that arise.

Act three: resolution

The third act is about resolving the issues from the first two acts, whereas the first two acts are about understanding the context and the tensions that can compel stakeholders to act. While it’s important to have an audience for the first two acts, it’s crucial that they stick around for the final act. That includes all members of the product team, including developers, UX experts, business analysts, delivery managers, product managers, and any other interested parties. It allows the whole team to hear users ‘ feedback together, ask questions, and discuss what’s possible within the project’s constraints. And it gives the UX design and research teams more time to clarify, suggest alternatives, or provide more context for their choices. So you can get everyone on the same page and get agreement on the way forward.

This act is primarily told through voiceover with some audience participation. The researcher is the narrator, who paints a picture of the issues and what the future of the product could look like given the things that the team has learned. They provide the stakeholders with their suggestions and suggestions for how to create this vision.

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

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

You can reinforce your recommendations with examples of things that competitors are doing that could address these issues or with examples where competitors are gaining an edge. Or they can be visual, like quick sketches of how a new design could look that solves a problem. These can help generate conversation and momentum. And this continues until the session is over when you’ve concluded by bridging the gaps and offering suggestions for improvement. This is the part where you reiterate the main themes or problems and what they mean for the product—the denouement of the story. The stakeholders will now have the opportunity to take the next steps, and hopefully the will-power to do so!

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

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

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

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

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

So the next time that you’re planning research with clients or you’re speaking to stakeholders about research that you’ve done, think about how you can weave in some storytelling. In the end, user research is beneficial to everyone, and all parties must be interested in the conclusion.

I’ve lost count of the times when promising ideas go from being useless in a few days to being useless after working as a solution designer for too long to explain.

Financial goods, which is my area of expertise, are no exception. It’s tempting to put as many features at the ceiling as possible and hope someone sticks because people’s true, hard-earned money is on the line, user expectations are high, and a crammed market. However, this strategy is a formula for disaster. Why? How’s why:

The drawbacks of feature-first growth

It’s easy to get swept up in the enthusiasm of developing innovative features when you start developing a financial product from scratch or are migrating existing client journeys from papers or telephony channels to online bank or mobile applications. They may think,” If I may only add one more thing that solves this particular person problem, they’ll enjoy me”! What happens, however, when you eventually encounter a roadblock caused by your security team? don’t like it, right? When a battle-tested film isn’t as well-known as you anticipated or when it fails due to unforeseen difficulty?

The concept of Minimum Viable Product ( MVP ) is applied to this. Even if Jason Fried doesn’t usually refer to this concept, his book Getting Real and his radio Rework frequently discuss it. An MVP is a product that offers only enough value to your users to keep them interested, but not so much that it becomes difficult to keep up. Although the idea seems simple, it requires a razor-sharp eye, a ruthless edge, and the courage to stand up for your position because it is easy to fall for” the Columbo Effect” when there is always” just one more thing …” to add.

The issue with most fund apps is that they frequently turn out to be reflections of the company’s internal politics rather than an encounter created specifically for the customer. Instead of offering a distinct value statement that is focused on what people in the real world want, the focus should be on delivering as some features and functionalities as possible to satisfy the needs and wants of competing inside sections. These products may therefore quickly become a muddled mess of confusing, related, and finally unlovable client experiences—a feature salad, you might say.

The significance of the foundation

What is a better strategy, then? How may we create products that are user-friendly, firm, and, most importantly, stick?

The concept of “bedrock” comes into play here. Rock is the main feature of your solution that really matters to customers. It’s the fundamental building block that creates price and maintains relevance over time.

The core must be in and around the standard servicing journeys in the retail banking industry, which is where I work. People only look at their existing account once every blue moon, but they do so every day. They sign up for a credit card every year or two, but they check their balance and pay their bill at least once a quarter.

The key is in identifying the main jobs that people want to complete and working relentlessly to render them simple, reliable, and trustworthy.

But how do you reach the foundation? By focusing on the” MVP” strategy, giving ease the top priority, and working toward a distinct value proposition. This means avoiding unnecessary characteristics and putting your customers first, and adding real value.

It also requires some nerve, as your coworkers might not always agree on your perspective right away. And dubiously, occasionally it can even suggest making it clear to customers that you won’t be coming to their house and making their breakfast. Sometimes you need to use the sporadic “opinionated user interface design” ( i .e. clunky workaround for edge cases ) to test a concept or to give yourself some more time to work on something more crucial.

Functional methods for creating reliable financial goods

What are the main learnings I’ve made from my own research and practice, then?

1. What trouble are you trying to solve first and foremost with a distinct “why”? For whom? Before beginning any project, make sure your goal is completely clear. Make certain it also aligns with the goals of your business.
2. Avoid the temptation to put too many characteristics at once and focus on getting that right first. Choose one that actually adds price, and work from that.
3. Give clarity the precedence it deserves over difficulty when it comes to financial products. Eliminate unwanted details and concentrate solely on what matters most.
4. Accept ongoing iteration: Bedrock is not a fixed destination; it is a fluid process. Continuously collect customer comments, make improvements to your product, and move toward that foundation.
5. Stop, glance, and talk: You must test your product frequently in the field rather than just as part of the shipping process. Use it for yourself. Work A/B testing. User opinions on Gear. Speak to those who use it, and change things up correctly.

The core dilemma

This is an intriguing conundrum: sacrificing some of the potential for short-term progress in favor of long-term stability is at play. But the reward is worthwhile because products created with a concentrate on core will outlive and outperform their competitors and provide people with ongoing value over time.

How do you begin your quest for rock, then? Consider it gradually. Start by identifying the underlying factors that your customers actually care about. Focus on developing and improving a second, potent have that delivers real value. And most importantly, check constantly because, whatever you think, Abraham Lincoln, Alan Kay, or Peter Drucker are all in the same boat! The best way to foretell the future is to make it, he said.

Picture this: Two people are conversing in what appears to be the same talk about the same pattern issue in a conference room at your tech company. One is talking about whether the staff has the right abilities to handle it. The other examines whether the answer really addresses the user’s issue. Similar room, the same issue, and entirely different perspectives.

This is the lovely, sometimes messy fact of having both a Design Manager and a Guide Designer on the same group. And if you’re wondering how to make this job without creating confusion, coincide, or the feared” to some cooks” situation, you’re asking the right issue.

The conventional solution has been to create clear traces on an organizational chart. The Design Manager handles persons, the Lead Designer handles art. Best, problem is fixed, best? Except that clear nonprofit charts are fantasy. In fact, both roles care greatly about crew health, style quality, and shipping great work.

When you begin to think of your style organization as a pattern organism, the magic happens when you accept collide rather than fight it.

A Healthy Design Team’s Biology

Here’s what I’ve learned from years of being on both flanks of this formula: think of your design team as a living organism. The design manager has a focus on the internal safety, career advancement, team dynamics, and other aspects. The Lead Designer is more focused on the body ( the handiwork, the design standards, the hands-on projects that are delivered to users ).

But just like mind and body aren’t totally separate systems, but, also, do these tasks overlap in significant ways. Without working in harmony with one person, you can’t have a good person. The technique is to recognize those overlaps and how to understand them gently.

When we look at how good team really function, three critical devices emerge. Each role must be combined, but one has to assume the lead role in keeping that system sturdy.

The Nervous System: Persons & Psychology

Major caretaker: Design Manager
Supporting position: Guide Custom

The anxious system is all about mental health, feedback, and signals. When this technique is good, information flows easily, people feel safe to take risks, and the staff may react quickly to new problems.

The main caretaker here is the Design Manager. They are keeping track of the team’s emotional signal, making sure feedback rings are good, and creating the conditions for people to develop. They’re hosting job meetings, managing task, and making sure no single burns out.

However, the Lead Designer has a significant supporting position. They provide visual feedback on build development requirements, identifying stagnant design skills, and assisting with the Design Manager’s potential growth opportunities.

Design Manager tends to:

• development planning and job conversations
• emotional stability and dynamics of the team
• Overhead management and resource allocation
• Performance evaluations and opinions management systems
• Providing learning options

Direct Custom supports by:

• Providing craft-specific evaluation of staff member growth
• identifying opportunities for growth and style talent gaps
• Providing style mentorship and assistance
• indicating when a crew is prepared for more challenging tasks.

The Muscular System: Design & Execution

Major custodian: Lead Designer
Supporting position: Design Manager

Power, cooperation, and skill development are the hallmarks of the skeletal system. When this technique is healthy, the team can do complicated design work with precision, maintain regular quality, and adjust their craft to fresh challenges.

The Lead Designer is the main caregiver at this place. They are raising the bar for quality work, providing craft instruction, and ensuring that shipping work is done to the highest standards. They’re the ones who can tell you if a design decision is sound or if we’re solving the right problem.

However, a significant supporting role is played by the Design Manager. They are making sure the team has the resources and support they need to perform their best work, such as ensuring that an athlete receives proper nutrition and recovery time.

Lead Designer tends to:

• Definition of system usage and design standards
• Feedback on design work that meets the required standards
• Experience direction for the product
• Design choices and product-wide alignment are at stake.
• advancement of craft and innovation

Design Manager supports by:

• ensuring that all members of the team are aware of and adopting design standards
• Confirming that a direction of experience is being pursued
• Supporting practices and systems that scale without bottlenecking
• facilitating design alignment among all teams
• Providing resources and removing obstacles to outstanding craft work

The Circulatory System: Strategy &amp, Flow

Shared caretakers: Lead Designer and Design Manager, respectively.

The circulatory system is about how decisions, energy, and information flow through the team. When this system is healthy, strategic direction is clear, priorities are aligned, and the team can respond quickly to new opportunities or challenges.

This is the true partnership that occurs. Although both roles are responsible for maintaining the circulation, they both have unique perspectives to offer.

Lead Designer contributes:

• The product fulfills the user’s needs.
• overall experience and product quality
• Strategic design initiatives
• User needs for each initiative are based on research.

Contributes the design manager:

• Communication to team and stakeholders
• Stakeholder management and alignment
• Inter-functional team accountability
• Strategic business initiatives

Both parties work together on:

• Co-creation of strategy and leadership
• Team goals and prioritization approach
• organizational structure decisions
• Success frameworks and measures

Keeping the Organism Healthy

Understanding that all three systems must work together is the key to making this partnership sing. A team with excellent craftmanship but poor psychological protection will eventually burn out. A team with great culture but weak craft execution will ship mediocre work. A team that has both but poor strategic planning will work hard on the wrong things.

Be Specific About the System You’re Defending.

When you’re in a meeting about a design problem, it helps to acknowledge which system you’re primarily focused on. Everyone has context for their input.” I’m thinking about this from a team capacity perspective” ( nervous system ) or” I’m looking at this through the lens of user needs” ( muscular system ).

This is not about staying in your path. It’s about being transparent as to which lens you’re using, so the other person knows how to best add their perspective.

Create Positive Feedback Loops

The partnerships that I’ve seen have the most effective partnerships that create clear feedback loops between the systems:

Nervous system signals to muscular system:” The team is struggling with confidence in their design skills” → Lead Designer provides more craft coaching and clearer standards.

The nervous system receives the message” The team’s craft skills are progressing more quickly than their project complexity.”

We’re seeing patterns in team health and craft development that suggest we need to adjust our strategic priorities, both systems say to the circulatory system.

Handle Handoffs Gracefully

When something switches from one system to another, this partnership’s pivotal moment is. This might occur when a design standard ( muscular system ) needs to be implemented across the team ( nervous system ) or when a tactical initiative ( circulatory system ) requires specific craft execution ( muscular system ).

Make these transitions explicit. The new component standards have been defined. Can you give me some ideas on how to get the team up to speed?” or” We’ve agreed on this strategic direction. From here, I’ll concentrate on the particular user experience approach.

Stay curious and not territorial.

The Design Manager who never thinks about craft, or the Lead Designer who never considers team dynamics, is like a doctor who only looks at one body system. Great design leadership requires both parties to be concerned with the entire organism, even when they are not the primary caregiver.

This entails asking questions rather than making assumptions. ” What do you think about the team’s craft development in this area”? or” How do you think this is affecting team morale and workload”? keeps both viewpoints at the forefront of every choice.

When the Organism Gets Sick

This partnership has the potential to go wrong, even with clear roles. Which failure modes are the most prevalent in my experience:

System Isolation

The design manager ignores craft development and only concentrates on the nervous system. The Lead Designer ignores team dynamics and concentrates solely on the muscular system. Both people retreat to their comfort zones and stop collaborating.

The signs: Mixed messages are sent to team members, poor morale is attained, and there are negative things.

Reconnect with other people’s goals in the treatment. What are you both trying to achieve? It’s typically excellent design work that arrives on time from a capable team. Discover how both systems accomplish that goal.

Poor Circulation

There is no clear strategic direction, shifting priorities, or accepting responsibility for keeping information flowing.

The symptoms are: Team members are unsure of their priorities, work is duplicated or dropped, and deadlines are missed.

The treatment: Explicitly assign responsibility for circulation. Who is communicating with whom? How frequently? What’s the feedback loop?

Autoimmune Response

One person feels threatened by the other’s skill set. The Design Manager thinks the Lead Designer is undermining their authority. The Design Manager is allegedly misunderstanding the craft, according to the Lead Designer.

The signs: defensive behavior, territorial disputes, team members stifled in the middle.

The treatment: Remember that you’re both caretakers of the same organism. The entire team suffers when one system fails. The team thrives when both systems are strong.

The Payoff

Yes, communication is required for this model. Yes, it requires that both parties be confident enough to assume full responsibility for team health. But the payoff is worth it: better decisions, stronger teams, and design work that’s both excellent and sustainable.

The best of both worlds can be found in strong people leadership and deep craft expertise when both roles are healthy and effective together. When one person is overly sick, on vacation, or overworked, the other can help keep the team’s health. When a decision requires both the people perspective and the craft perspective, you’ve got both right there in the room.

The framework has a balance, which is crucial. You can use the same system thinking to new challenges as your team grows. Need to launch a design system? Both the muscular system ( standards and implementation ), the nervous system (team adoption and change management ), and both have a tendency to circulate ( communication and stakeholder alignment ).

The End result

The relationship between a Design Manager and Lead Designer isn’t about dividing territories. It’s about multiplying impact. Magic occurs when both roles realize they are tending to various aspects of the same healthy organism.

The mind and body work together. The team benefits from both strategic thinking and craftmanship. And most importantly, users benefit from both perspectives when they receive the work.

So the next time you’re in that meeting room, wondering why two people are talking about the same problem from different angles, remember: you’re watching shared leadership in action. And if it’s functioning well, your design team’s mind and body will both become stronger.

If you enjoy the Yautja and xenomorphs, you’re going to enjoy this summer. We’re even getting a noble Yajuta in Predator: Badlands, which Hulu and the FX series Alien: Earth have eventually brought the fronds to our home planet. One thing, for some fans, may merely improve this horde of riches: getting […]

The article Alien: Earth Showrunner Jokes About Alien vs. On Den of Geek, Predator Possibilities second appeared.

James Gunn has been hesitant to respond to too many inquiries regarding the connection between the DC Universe reboot that he and DC Studios co-head Peter Safran co-founded and the earlier universe that Zack Snyder launched with Man of Steel in 2013. There are some things from the old world that we refer to in Peacemaker time 2, he just told Den of Geek, but they’re not cannon until next.

We finally getting some good links with SDCC upon us. We catch up with Christopher Smith, aka Peacemaker ( John Cena ), when he reunites with his friends in the 11th Street Kids: Leota Adebayo ( Danielle Brooks ), Emilia Harcourt ( Jennifer Holland ), John Economos ( Steve Agee ), and Adrian Chase aka Vigilante ( Freddie Stroma ), in the most recent trailer for Peacemaker&#8216, s second season, set to &#8220, Road to

The same can’t be said for another well-known face, that of new ARGUS director Rick Flag Sr. ( Frank Grillo ), as happy as they are to see one another again. Following the death of his son Rick Flag Jr. ( Joel Kinnaman ), whom Chris murdered at the behest of Amanda Waller ( Viola Davis ), at the conclusion of The Suicide Squad, Gunn&#8217, the first DC film from 2021, Flag plans to use his new position to seek vengeance against Chris.

So far, we have been given complete assurance that The Suicide Squad‘s events are relevant in the new DCU and that it is also a cannon. That, of course, doesn’t answer every lingering question ( not even as it does with Peacemaker, which famously featured celebrities from Jason Momoa, Jason Momoa, and Aquaman in the final episode ).

However, the trailer did point out something that might give some answers to those original DC heroes. We see Chris provide a different world through a unique website throughout the video. Chris is precious in one of the different challenges we see him discovering, whereas in his house dimension, he is still a laughing stock yet after he and the 11th Street Kids stopped an alien conquest in Peacemaker‘s first season. In fact, he is loved by Auggie ( Robert Patrick ), his father, and not just by Chris killed in season 1, but also by his father, who must be very different from that person.

We see hints that Chris will spend more time in this alternate universe throughout the trailer, even stealing his counterpart’s sleek, cooler uniform ( and less cool silk shirts ). And if the footage of two John Cenas battling one another is any indication, the additional Chris has some thoughts about the perfect Chris’s attempted murder.

On the one hand, it’s a little surprising that the world is already the sole formal entry in the new DC Universe. Gunn&#8217 is certainly back away, telling panelists that Peacemaker season 2 may establish that the DC Universe has at least 100 alternative realities. This expands on earlier assertions made by Gunn that Chris ‘ sites between experiences are an extension of Lex Luthor’s in Superman.

Speaking of Superman, the SDCC board stated that the film’s next season of Peacemaker&#8216 will come a month after the film’s conclusion. That brief arc helps explain the cameos Chris can audition for the Justice Gang thanks to the contributions of Hawkgirl ( Isabela Merced ), Maxwell Lord ( Sean Gunn ), and Guy Gardner ( Nathan Fillion ). However, Chris&#8217’s conviction that he belongs with the Justice Gang straight stems from his remarkable personal development and achievements in time 1. &#8220, I don&#8217, t want to be a joke again, &#8221, Chris says in voice over in the video. &#8220, I want to get a true hero. &#8221,

Did Chris be able to develop Peacemaker into a superhero like Superman? If so, it will most likely occur in the first, sixth, and eighth incidents of Gunn’s directorial debut, Peacemaker&#8216.

Chris will undoubtedly benefit from some great technology from the universe, but he’ll first have to make amends for past transgressions. And if the trailer’s portrayal of Rick Flag Sr. is any indicator, that’s going to be a challenging task. If The Suicide Squad wasn’t a cannon, it might be much easier for Chris.

On HBO Max, Peacemaker winter 2 airs on August 12, 2025.

The first article Peacemaker Season 2 Video Completes The World and Confirms The Suicide Squad Also Canon appeared initially on Den of Geek.