Category: Blog

Humility, a writer’s most important quality, has a great circle to it. What about sincerity, an business manager’s important value? Or a surgeon’s? Or a student’s? They all have fantastic sounds. When humility is our guiding light, the course is usually available for fulfillment, development, relation, and commitment. We’ll 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. Along the way, I’m going to render myself a little vulnerable. I call it:

The Absurd Pate of Justin: A Tale

When I was coming out of arts school, a long-haired, goateed novice, write was a known quantity to me, design on the web, however, was riddled with complexities to understand and learn, a problem to be solved. Although I had formal training in typography, layout, and creative design, what piqued my interest was how these traditional skills could be applied to a young modern landscape. This theme may 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 design existed in the late 1990s and the early 2000s. Manufacturers at the time were all figuring out how to use layout and visual connection to the online environment. What were the guidelines? How may we break them and also engage, entertain, and present information? How was my values, which include modesty, respect, and connection, coincide with that on a more general level? I was eager to find out.

Those are classic factors between non-career relationships and the world of design, even though I’m talking about a different time. What are your main passions, or ideals, that elevate medium? The main themes are the same, basically the same as what we previously discussed on the primary parallels between what fulfills you, independent of the physical or digital realms.

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

Along with pattern book pieces, the site even offered free downloads for Mac OS customizations: desktop wallpapers that were successfully design experimentation, custom-designed typefaces, and desktop icons.

GUI Galaxy was a design, pixel art, and Mac-centric news portal that graphic designer friends and I developed from 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 as designers had changed and developed a bandwidth-sensitive, award-winning, much more accessibility-conscious website. Still ripe with experimentation, yet more mindful of equitable engagement. Below are some content panes that show general news (tech, design ) and news centered on Mac. We also offered many of the custom downloads I cited before as present on my folio site but branded and themed to GUI Galaxy.

The presentation layer of the website’s backbone was made up of global design + illustration + news author collaboration. The backbone was a homegrown CMS. And the collaboration effort here, in addition to experimentation on a’ brand’ and content delivery, was hitting my core. We were creating 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.

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

First of all, there’s a reason for the nostalgia for the” Wild West” era of design that so many personal portfolio and design portals sprang from the past. Ultra-finely detailed pixel art UI, custom illustration, bespoke vector graphics, all underpinned by a strong design community.

The web design industry has experienced 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 there are selections that vaguely relate to their respective content in an icon library.

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

Pixel Issues

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

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

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

So I started doing my homework and conducting 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. Problem-solving Again, these core connection-based values are agnostic of medium.

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

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

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

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

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

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

I felt so supremely confident in my abilities that I effectively stopped researching and discovering. When I used to lead myself to iterate through concepts or sketches, I leaped right into Photoshop. I drew my inspiration from the smallest of sources ( and with blinders on ). Any criticism of my work from my fellow students was frequently vehemently dissented. 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. However, thankfully, those same friends gave me a priceless gift: sincerity. 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 re-awakening was necessary, the realization let me down. I let go of the “reward” of adulation and re-centered upon what stoked the fire for me in art school. Most importantly, I returned to my fundamental values.

Always Students

Following that temporary regression, I was able to advance in both my personal and professional design. And I could self-reflect as I got older to facilitate further growth and course correction as needed.

Let’s 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, in this role,

I cut my teeth on usability testing, working with the Fermilab team to iterate and improve the interface. To me, their language and the topics they discussed seemed 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 communication was the barrier-free design.

So to those core drivers of my visual problem-solving soul and ultimate fulfillment: discovery, exposure to new media, observation, human connection, and evolution. 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 phrases “grow” and “evolve” in particular. If we are always students of our craft, we are also continually making ourselves available to evolve. Yes, we have years of practical design experience behind us. Or the focused lab sessions from a UX bootcamp. Or the monogrammed portfolio of our work. Or, ultimately, decades of a career behind us.

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

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

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

That’s where we come in. After completing tens of personalisation projects over the past few years, we gave ourselves a purpose: could you make a systematic personalization platform especially for UX practitioners? The Personalization Pyramid is a designer-centric framework for establishing human-centered personalization initiatives that cover data, classification, content delivery, and overall objectives. 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 building stones. These are the “levels” on the tower, as we’ve made them. Whether you are a UX artist, scholar, or planner, understanding the core components may help make your contribution effective.

From top to bottom, the amounts include:

North Star: What larger corporate goal is driving the personalization system?
1. Objectives: What are the specific, tangible benefits of the system?
2. Touchpoints: Where will you get customized service?
3. Contexts and Campaigns: What personalization information does the person view?
4. What constitutes a distinct, accessible market according to consumer 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 brainstorming periods, and will include cases for you here.

Starting at the Top

The tower has the following elements:

North Star

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

Function: Personalized based on fundamental person inputs. Examples:” Raw” messages, basic search effects, system user settings and settings options, general flexibility, basic improvements
1. Feature: Self-contained personalisation component. Examples:” Cooked” notifications, advanced optimizations ( geolocation ), basic dynamic messaging, customized modules, automations, recommenders
2. User experience: 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 aid in accelerating designing with user intentions, as in any great UX design. Goals are the military and quantifiable metrics that may prove the entire program is effective. Start with your existing analytics and assessment system, as well as metrics that you can benchmark against. In some cases, new targets may be suitable. The most important thing to keep in mind is that personalisation is never a desired outcome. It is a means to an end. Popular targets include:

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

Touchpoints

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

Channel-level Points

• 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 at specific touchpoints, as defined by user data. At this stage, we find it helpful to consider two separate models: a context model and a content model. The context helps you consider the user’s level of engagement at the personalization moment, such as when they are casually browsing information or deep-dive. Think of it in terms of information retrieval behaviors. The content model can then guide you in deciding what kind of personalization to use in the context ( for instance, an” Enrich” campaign that features related articles might be a good substitute for extant content ).

Personalization Context Model:

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

Personalization Content Model

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

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

User Groups

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

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

Actionable Data

Every organization with any digital presence has data. It’s important to inquire about how to use the data you can ethically collect on users, its inherent reliability and value, and how to 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 for the user experience, including being relatively simple to collect, more likely to be accurate, and less susceptible to the” creep factor” of third-party data. So a key part of your UX strategy should be to determine what the best form of data collection is on your audiences. Here are a few illustrations:

There is a progression of profiling when it comes to recognizing and making decisioning about different audiences and their signals. As 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 content repository and data backbone. But these approaches should be considered as part of the larger roadmap and may indeed help accelerate the organization’s overall progress. 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 multi-faceted method of profiling that is adaptable.

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 serves as the foundation for the workshops that both co-authors have conducted to build a program backlog, which would make a good article topic.

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

Lay Down Your Cards

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

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 fascinating experiences. Yet my friends and I had movie ideas to make and sun in. But they never went any farther. However, I did end up 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 more than likely follows a three-act construction that’s frequently seen in movies: the installation, the conflict, and the resolution. The second act shows what exists now, and it helps you get to understand the characters and the challenges and problems that they face. Act two sets the scene for the fight and the action begins. Here, issues grow or get worse. The solution is the third and final work. This is where the issues are resolved and the figures learn and change. This structure, in my opinion, is also a fantastic way to think about customer research, and it might be particularly useful for explaining user research to others.

Use story as a framework for conducting research

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

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

Act one: installation

Fundamental analysis comes in handy because the layout is all about comprehending the background. Basic research ( also called conceptual, discovery, or preliminary research ) helps you understand people and identify their problems. Just like in the movies, you’re learning about the problems users face, what options are available, and how those challenges impact them. To do basic research, you may conduct cultural inquiries or journal studies ( or both! ), which may assist you in identifying both problems and opportunities. It doesn’t need to get a great investment in time or money.

Erika Hall discusses 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. Provide that one ask. Opened up and listen to them for 15 days. Do everything in your power to keep yourself and your pursuits out of it. Bam, you’re doing ethnography”. 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 sense to me in all its entirety. And I love that this makes consumer studies so visible. You can simply attract participants and carry out the recruitment process without having to create 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 what work one is really all about: understanding where people are coming from.

Maybe Spool talks about the importance of basic research and how it really type the bulk of your research. If you can substitute what you’ve heard in the fundamental research by using more customer information that you can obtain, such as surveys or analytics, or to highlight areas that need more research. Together, all this information creates a clearer picture of the state of things and all its inadequacies. 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 concern may be with their company, which may be losing money because people are unable to complete specific tasks. Or probably they do connect with 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 help product teams become more user-centric. This benefits everyone—users, the product, and stakeholders. It’s similar to winning an Oscar for a film; it frequently results in a favorable reception and success for your product. And this can be an incentive for stakeholders to repeat this process with other products. Knowing how to tell a good story is the only way to convince stakeholders to care about doing more research, and storytelling is the key to this process.

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

Act two: conflict

Act two is all about digging deeper into the problems that you identified in act one. This typically involves conducting directional research, such as usability tests, where you evaluate a potential solution ( such as a design ) to see if it addresses the issues you identified. The issues could include unmet needs or problems with a flow or process that’s tripping users up. Additional problems will arise in the course of act two of a film. It’s here that you learn more about the characters as they grow and develop through this act.

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

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

Usability tests have been conducted in person for decades, but you can also do them remotely using software like Microsoft Teams, Zoom, or other teleconferencing software. This approach has become increasingly popular since the beginning of the pandemic, and it works well. You might interpret in-person usability tests as a form of theater watching as opposed to remote testing. There are advantages and disadvantages to each. Usability research in person is a much more extensive experience. Stakeholders can experience the sessions with other stakeholders. 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 meet users at their location to conduct your research. With either option, you get to see how things work in context, things come up that wouldn’t have in a lab environment—and conversion can shift in entirely different directions. You have less control over how these sessions 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. A wider audience can be reached through remote sessions. They allow a lot more stakeholders to be involved in the research and to see what’s going on. Additionally, they make 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.

You can ask real users questions to understand their thoughts and understanding of the solution as a result of usability testing, whether it is conducted remotely or in person. This can help you not only identify problems but also glean why they’re problems in the first place. Additionally, you can test your own hypotheses and determine whether your reasoning is correct. By the end of the sessions, you’ll have a much clearer picture of how usable the designs are and whether they work for their intended purposes. The excitement is in the second act, but there are also potential surprises in the third. This is equally true of usability tests. Unexpected things that are said by participants frequently alter how you view things, and these unexpected developments in the story can lead to unexpected turns in your perception.

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

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

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

Act three: resolution

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

Voiceover narration of this act is typically used with audience input. The researcher is the narrator, who paints a picture of the issues and what the future of the product could look like given the things that the team has learned. They provide the stakeholders with their suggestions and direction for developing 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.

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 everything by summarizing the key points and offering suggestions for a solution. This is the part where you reiterate the main themes or problems and what they mean for the product—the denouement of the story. This stage provides stakeholders with the next steps, and hopefully, the motivation to take those steps as well!

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

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

Act two: Next, there’s character development. The protagonists face 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 plays a variety of roles, including producer, director, and storyteller. The participants have a small role, but they are significant characters ( in the research ). And the audience is one of the stakeholders. But the most important thing is to get the story right and to use storytelling to tell users ‘ stories through research. In the end, the parties should leave with a goal and an eagerness to fix the product’s flaws.

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

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

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

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

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

We refer to it as prepersonalization.

Behind the audio

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

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

How do you decide where to position customisation wagers? How do you design regular interactions that hasn’t journey up users or—worse—breed mistrust? We’ve found that for many well-known budgeted programs to support their continued investments, they initially required one or more workshops to join vital technologies users and stakeholders. Make it matter.

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

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

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

1. customer experience optimization ( CXO, also known as A/B testing or experimentation )
2. always-on automations ( whether rules-based or machine-generated )
3. mature features or standalone product development ( 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 require these cards. But we strongly recommend that you create something similar, whether that might be digital or physical.

Set the timer for your kitchen.

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

The full arc of the wider workshop is threefold:

Kickstart: This specifies the terms of your engagement as you concentrate on both your team’s and your team’s readiness and drive.
1. Plan your work: This is the heart of the card-based workshop activities where you specify a plan of attack and the scope of work.
2. Work your plan: This stage consists of making it possible for team members to individually pitch their own pilots that each include a proof-of-concept project, business case, and operating model.

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

Kickstart: Apt your appetite

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

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

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

Assess each example that you discuss for its complexity and the level of effort that you estimate that it would take for your team to deliver that feature ( or something similar ). In our cards, we break down connected experiences into five categories: functions, features, experiences, complete products, and portfolios. Size your own build here. This will help to draw attention to the benefits of ongoing investment as well as the difference between what you deliver right now 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 crucial because it emphasizes how personalization can affect your own ways of working as well as your external customers. It’s also a reminder ( which is why we used the word argument earlier ) of the broader effort beyond these tactical interventions.

Each team member should decide where they would like to place your company’s emphasis on your product or service. Naturally, you can’t prioritize all of them. Here, the goal is to show how various departments may view their own benefits from the effort, which can vary from one department to the next. Documenting your desired outcomes lets you know how the team internally aligns across representatives from different departments or functional areas.

The third and final kickstart activity is about filling in the personalization gap. Is your customer journey well documented? Will data and privacy protection be a significant challenge? Do you have content metadata needs that you have to address? ( We’re pretty sure you do; it’s just a matter of recognizing the need’s magnitude and its solution. ) In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six protracted behavior that is harmful to the development of our country.

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

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

Hit that test kitchen

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

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

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

Recipes have ingredients in them, and those recipes have ingredients.

Verify your ingredients

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

This is not just about identifying needs. Documenting your personalizations as a series of if-then statements lets the team:

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

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

Create a recipe.

What ingredients are important to you? Consider the construct “what-what-when-why”

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

Five years ago, we developed these cards and card categories for the first time. We regularly play-test their fit with conference audiences and clients. And there are still fresh possibilities. But they all follow an underlying who-what-when-why logic.

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

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

We’ve also found that sometimes this process comes together more effectively by cocreating the recipes themselves, so a good preworkshop activity might be to think about what these cards might be for your organization. Start with a set of blank cards, and begin labeling and grouping them through the design process, eventually distilling them to a refined subset of highly useful candidate cards.

The workshop’s later stages could be characterized as shifting from focusing on a cookbook to a more nuanced customer-journey mapping. Individual” cooks” will pitch their recipes to the team, using a common jobs-to-be-done format so that measurability and results are baked in, and from there, the resulting collection will be prioritized for finished design and delivery to production.

Better architecture is required for better kitchens.

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

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

You can’t stand the heat, in fact…

Personalization technology opens a doorway into a confounding ocean of possible designs. Only a disciplined and highly collaborative approach can achieve the necessary concentration and intention. So banish the dream kitchen. Instead, head to the test kitchen to burn off the fantastical ideas that the doers in your organization have in store for time, to preserve job satisfaction and security, and to avoid unnecessary distractions. There are meals to serve and mouths to feed.

You have a better chance of lasting success and sound beginnings with this workshop framework. Wiring up your information layer isn’t an overnight affair. However, if you use the same cookbook and the same recipe combination, you’ll have solid ground for success. We designed these activities to make your organization’s needs concrete and clear, long before the hazards pile up.

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

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 requirements 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 techniques (especially those used in blogs like Blogger, Grey Matter, Movable Type, and WordPress ) In the mid-2000s, AJAX opened gates for sequential interaction between the front end and back finish. Websites now no longer needed to refresh their pages ‘ content. A grain of Script frameworks like Prototype, YUI, and ruby arose to aid developers develop more credible client-side conversation across browsers that had wildly varying levels of standards support. Techniques like picture alternative enable the use of fonts by skilled developers and developers. And technology like Flash made it possible to include movies, sports, and even more engagement.

These new methods, requirements, and solutions greatly reenergized the sector. Web style flourished as manufacturers and designers explored more different styles and designs. However, we also relied heavily on numerous exploits. Early CSS was a huge improvement over table-based layouts when it came to basic layout and text styling, but its limitations at the time meant that designers and developers still relied heavily on images for complex shapes ( such as rounded or angled corners ) and tiled backgrounds for the appearance of full-length columns (among other hacks ). All kinds of nested floats or absolute positioning ( or both ) were necessary for complicated layouts. Display and photo substitute for specialty styles was a great start toward varying the designs from the big five, but both tricks introduced convenience and efficiency issues. Additionally, JavaScript libraries made it simple to add a dash of interaction to pages without having to spend the money to double or even quadruple the download size for basic websites.

The web as software platform

The 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 shared package libraries, build automation, and collaborative version control. 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 user interaction and consumption. 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 positive and negative outcomes.

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

Where we are now

It seems like we’ve 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. The IndieWeb‘s Webmentions, RSS, ActivityPub, and other tools can assist with this, but they’re still largely underdeveloped and difficult to use for the less geeky. We can build amazing personal websites and add to them regularly, but without discovery and connection, it can sometimes feel like we may as well be shouting into the void.

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

We can prototype almost any idea today with just a few commands and a few lines of code. All the tools that we now have available make it easier than ever to start something new. However, as the initial cost of these frameworks may be saved in the beginning, it eventually becomes due as their upkeep and maintenance becomes a component of our technical debt.

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

Where do we go from here?

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

Build for the long haul. Optimize for performance, for accessibility, and for the user. weigh the costs associated with those user-friendly tools. They may make your job a little easier today, but how do they affect everything else? What is the 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. Not all third-party frameworks are the same. Sites built with even the hackiest of HTML from the’ 90s still work just fine today. The same can’t be said about websites created with frameworks even after a few years.

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

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

Play, experiment, and be weird! This website we created is the most incredible experiment. 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. Share what you think has worked for you as you experiment, play, and learn. Write on your own website, post on whichever social media site you prefer, or shout it from a TikTok. Write something for A List Apart! But take the time to amplify others too: find new voices, learn from them, and share what they’ve taught you.

Go ahead and create a masterpiece.

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.

I’d like you to consider this a “yes … and” piece to complement Joe’s post. Instead of refuting everything he’s saying, I’m pointing out some areas where AI may produce real, positive impacts on people with disabilities. 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 word. He raises a lot of appropriate points regarding the state of the world 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 ( should probably have descriptions ) and those that are purely decorative ( couldn’t possibly need a description ) either. Nonetheless, I still think there’s possible in this area.

As Joe points out, alt text editing via human-in-the-loop should be a given. And if AI can intervene to provide a starting place for alt text, even if the swift might say What is this BS? That’s not correct at all … Let me try to offer a starting point— I think that’s a gain.

If we can specifically station a design to examine image usage in context, this may help us more quickly determine which images are likely to be elegant and which ones are likely to be descriptive. That will clarify which situations require image descriptions, and it will increase authors ‘ effectiveness in making their sites more visible.

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

• Are there more smartphone users than have devices?
• How many more are there?
• Is there a group of people that don’t fall into either of these containers?
• How many people are that?

For a moment, the chance to learn more about graphics and data in this way could be innovative for people who are blind and low vision as well as for those with different types of color blindness, cognitive impairments, and other issues. Putting aside the challenges of large language model ( LLM) hallucinations. 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 demanded that the line graph be isolated into just one line? 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 demanded that it switch colors in favor of patterns? That seems like a possibility given the chat-based interfaces and our current ability to manipulate images in modern 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 put her book Algorithms of Oppression, she hit the nail on the head. Although her book focused on the ways that search engines can foster racism, I believe it to be equally accurate to say that all computer models have the potential to amplify conflict, bias, and intolerance. Whether it’s Twitter always showing you the latest tweet from a bored billionaire, YouTube sending us into a Q-hole, or Instagram warping our ideas of what natural bodies look like, we know that poorly authored and maintained algorithms are incredibly harmful. A large portion of this is attributable to the lack of diversity in those who create and shape them. There is real potential for algorithm development when these platforms are built with inclusive features in, though.

Take Mentra, for example. They serve as a network of employment for people who are neurodivers. They employ an algorithm to match job seekers with potential employers 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 typical employment websites because it was run by neurodivergent people. They use their algorithm to propose available candidates to companies, who can then connect with job seekers that they are interested in, reducing the emotional and physical labor on the job-seeker side of things.

When more people with disabilities are involved in developing algorithms, this can lower the likelihood that these algorithms will harm their communities. Diverse teams are crucial because of this.

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

Other ways that AI can assist people with disabilities

I’m sure I could go on and on about using AI to assist people with disabilities, but I’m going to make this last section into a bit of a lightning round if I weren’t trying to put this together in between other tasks. In no particular order:

preservation of voice You might have heard about the voice-preserve offerings from Microsoft, Acapela, or others, or have seen the VALL-E paper or Apple’s Global Accessibility Awareness Day announcement. It’s possible to train an AI model to replicate your voice, which can be a tremendous boon for people who have ALS ( Lou Gehrig’s disease ) or motor-neuron disease or other medical conditions that can lead to an inability to talk. This technology can also be used to create audio deepfakes, so we need to approach it 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 currently hiring people with Parkinson’s and related conditions, and they intend to expand this list as the project develops. More people with disabilities will be able to use voice assistants, dictation software, and voice-response services, as well as to use only their voices to control computers and other devices, according to this research.
• Text transformation. 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 the importance of our differences. The intersections of the identities that we exist in have an impact on our lived experiences. These lived experiences—with all their complexities ( and joys and pain ) —are valuable inputs to the software, services, and societies that we shape. Our differences must be reflected in the data we use to develop new models, and those who provide it need to be compensated for doing so. Stronger models can be created using inclusive data sets, which lead to more equitable outcomes.

Want a model that doesn’t demean or patronize or objectify people with disabilities? Make sure that 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 doesn’t speak in ableist language? You may be able to use existing data sets to build a filter that can intercept and remediate ableist language before it reaches readers. Despite this, AI models won’t be replacing human copy editors anytime soon when it comes to sensitivity reading.

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

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

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.

I have a creative side. What I do involves chemistry. 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. No everyone sees themselves in this way. Some innovative individuals practice technology in their work. I value their assertion, which is true. Perhaps I also have a little bit of envy for them. However, my method is different; my being is unique.

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

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

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

Sometimes I just work until the plan strikes me. Maybe it arrives right away and I don’t remind people for three days. Maybe I get so excited about something that just happened that I blurt it out and didn’t stop myself. like a child who discovered a reward in a box of Cracker Jacks. Often I get away with this. Yes, that is the best plan, but sometimes another people disagree. The majority of the time, they don’t, and I regret that passion has faded.

Joy should only be saved for the meet, when it will matter. not the informal gathering that two different gatherings precede that appointment. Nobody understands why these discussions occur. We keep saying we’re getting rid of them, but we keep discovering new ways to get them. They occasionally yet are good. But occasionally they are a hindrance to the actual job. Depending on what you do and where you do it, the ratio between when conferences are valuable and when they are a sad distraction vary. And who you are and how you go about doing it. I’ll go back and forth once more. I have a creative side. That is the style.

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

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

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

I can nail ahead, fill in the blanks, or use images or information, which occasionally works. I can go for a move, which occasionally works. There is a Eureka that has nothing to do with sizzling crude and flowing pots. I may be making dinner. I frequently know what to do when I awaken. The idea that may have saved me disappears almost as frequently as I become aware and a part of the world once more as a thoughtless wind of oblivion. For inventiveness, in my opinion, originates in that other world. The one that we enter in ambitions and, possibly, before and after death. But authors should be asking this, and I am not one of them. I have a creative side. Theologians are encouraged to build massive armies in their artistic globe, which they insist is genuine. That is yet another tangent, though. And one that is miserable. Possibly on a much bigger issue than whether or not I am creative. But that’s also a step backwards from what I’m trying to say.

Often the result is mitigation. And suffering. Do you know the actor who is tortured by the cliché? Even when the artist attempts to create a soft drink song, a callback in a worn-out sitcom, or a budget request, that noun is real.

Some individuals who detest being called artistic perhaps been closeted artists, but that’s between them and their gods. No offence intended. Yours is also real. 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. People have a lot of regard for designers. We respect, follow, and nearly deify the excellent ones. Of course, deifying any person is a horrible error. We’ve been given a warning. We are more knowledgeable. We are aware that people are really people. They argue, they are depressed, they regret their most important choices, they are weak and 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 was unable to arise before them or otherwise. They are the inspirations of thought. And I suppose I should add that they are the mother of technology because it’s just lying it. Ba ree 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, though. Greatness is then that. That is brilliance directly from God’s heart. This meagre much creation that I made? It essentially fell off the back of the pumpkin trailer. The carrots weren’t actually new, either.

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

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. My mind goes blank when it really counts because I’m too sluggish and complacent. No medication is available to treat artistic function.

I have a creative side. Every project I create has a goal that makes Indiana Jones appear older and snoring in a deck 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 work.

I can move ten times more quickly than those who aren’t innovative, those who have only had a short-cut of creativity, and those who have just had a short-cut of creativity for work. Only that I spend twice as long as they do putting the job off before I work ten times as quickly as they do. When I put my mind to it, I am so confident in my ability to do a great career. I have an addiction to the delay rush. I’m also so scared of jumping.

I don’t create art.

I have a creative side. never a musician. Though as a child, I had a dream that I would one day become that. Some of us like and criticize our talents because we are not Michelangelos and Warhols. That is narcissism, but at least we aren’t in elections.

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

I have a creative side. Every word I’ve said these may irritate other artists who see things differently. Ask two artists a topic and find three opinions. 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 that I know very little about. And I put my preference before all other things in the areas that are most dear to my soul, 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 actually. No truly. Because a lot of living is intolerable if you really look at it.

I have a creative side. I think that when I leave, a small portion of me will stay in someone else’s head, just like a parent does.

Working frees me from worrying about my job.

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

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

I have a creative side. I think there is the greatest secret in the process. I think so strongly that I am actually foolish enough to post an essay I wrote into a small machine without having to go through or edit it. I swear I didn’t accomplish this frequently. But I did it right away because I was even more scared of forgetting what I was saying because I was as worried as I might be of you seeing through my sad gestures toward the gorgeous.

There. I believe I’ve said it.

David Tennant, the director of the television series Tenth Doctor, Fourteenth Doctor, and Metacrisis Doctor, has a unique radio called David Tennant Does a Podcast With…, and this week he added his former boss Russell T Davies as a guest. You’d get disappointed if you had hoped for Frost/Nixon. [ ] ] This was cozy.

The first article on Den of Geek: Doctor Who’s Mix of Laughter and Worry Has Always Been Its Power appeared initially.

Kate Mara is a little bit knowledgeable about spaceflight. Mara continues to have aspects of that expertise with her, including the costume, as one of the stars of Ridley Scott &#8216’s 2015 hit, The Martian. She admits with a laugh while inside the Den of Geek theater,” I have my journey coat from The Martian,” and that she is also wearing one.

However, Mara&#8217’s new film The Astronomer is about a storage traveler feeling abandoned at house, unlike that Scott film that focused on a man abandoned in place. I am alone for a lot of the picture, and for the most part, &#8221, Mara says of her figure, the eponymous astronaut Sam. &#8220, It&#8217, s just me and my thoughts. That, plus whatever definitely is out there going nudge in the evening after Mara&#8217, s Captain Sam Walker results to Earth. She also had a remarkable thanksgiving, as she managed to survive a perplexing spacecraft. She was later found in the ocean with a glowing water on her face and no remembrance of what transpired. She is aware of the existence of a problem when darkness appear in her field of vision while she is quarantined in the wilderness.

Mara did a lot of research to get ready for her Sam position, but she didn’t need to go all out to try to replicate the isolation she felt from everyone she loves. That is only a part of being an artist.

There is always a sort of re-entry time after you picture someone intensive, especially if you’re not filming anywhere you live, which is really 99 percent of the time. Even if you have your home with you, as I did when we were filming this, you can always adapt to what life is like when you don’t have a very particular place to go every day and have to become someone else. For example, I had my children with me in Ireland while filming this. Although that component of an astronaut’s work is admirable, it is much more powerful and upbeat than being an actor. &#8221,

Writer and director Jess Varley expands Mara’s personal encounter with the real-world study she conducted into room and, in her case, anti-gravity dreams, which true astronauts have experienced after returning home.

I looked at actual signs that pilots have, according to Varley’s report. In order to keep everything as grounded as possible, I wanted her state to feel natural, like it was unfolding before our eyes in a true method, so that it never felt prosthetic-heavy or overly stylized. In the beginning of the movie, Sam crash lands, but I felt like there was some license we could get with bruising, spreading on her body. I made an effort to keep it as a grounded as possible. &#8221,

Despite this, Varley did take inspiration from other movies, particularly one about a woman going through a crisis of identity and the men doubting her every step of the way.

&#8220, I love Black Swan, &#8221, she says of the 2010 Darren Aronofsky movie. That was actually a bit of an inspiration for The Astronaut, according to &#8220. We have this unreliable narrator and a few other things that might be a little spoilery, so I won’t say. However, it’s fun to create these red-herring situations where we’re not sure if we can trust Sam. &#8221,

Varley adds, &#8220, She&#8217, s not sure if she can trust herself, and it helps us sort of enjoy the ride, but also leaves enough room for us to hopefully be shocked at where the movie ultimately goes. &#8221,

Producer Brad Fuller points to the thrill ride as one of the main draws for a movie like The Astronaut. He explains,” People go to the movie theaters to have a shared experience,” and” #8221. And genre films really give everyone in the theater the incredible chance to scream. &#8221,

Fuller also points out that Mara and Varley’s portrayal of The Astronaut isn’t pure escapism, despite the fact that it lacks the same level of realism. &#8220, It&#8217, s about something that could actually really happen. We&#8217 are looking at things that aren’t so outrageous that the audience thinks, well, that could never happen when Fuller and his producing partners are looking at scripts. If you believe this could occur to you, horror is scarier. &#8221,

The play’s performance as Sam&#8217’s husband Mark is further influenced by the relatable quality of Gabriel Luna.

According to Luna, the narrative is about families that are based on a love that transcends blood. You make the leap to embrace something other than yourself. You can see how powerful they are at the very core. Our relationship places the foundation of the entire narrative on people, Luna explains, citing the difficulties Mark and Sam face before the sci-fi element is introduced. There is a lot of turbulence in their relationship, just due to the distance and having to deal with the separation and raising a child. &#8221,

The commonplace relationship issues that Luna discusses at Varley &#8217, the film’s objectives and its reception get. She says,” I hope that people can relate to the messy things that we all do,” and that she hopes they too. We don’t always see that on screen, and there’s something very human and frequently very private about that. Hopefully The Astronaut makes it known more so that people can feel a little less alone in their journeys and transformations. &#8221,

And what about Mara’s journey from The Martian astronaut to astronaut at home in The Astronaut? She admits that it’s always nice to have information from another movie that you can use in whatever way. I certainly carried some of that with me, but there was undoubtedly much more to learn. &#8221,

But at least she wasn’t required to re-instruct herself how to wear a flight suit.

At SXSW, The Astronaut made its debut on March 7.

The first post on Den of Geek was Kate Mara putting a twist on the Alien Invasion movie in The Astronaut.

We agree: the computer-generated eyes could be a great fit for personas—but not for the purpose you might think. Ironically, the website highlights the core issue of this very common design method: the person ( a ) does not exist. Personas are deliberately created, just like in the photos. Knowledge is taken out of natural environment and recombined into an isolated preview that’s detached from reality.

However, oddly enough, manufacturers use personalities to inform their designs for the real world.

Personas: A action up

Most manufacturers have created, used, or come across personalities at least once in their profession. The Interaction Design Foundation defines profile as “fictional characters that you create based on your research in order to represent the various consumer types that might use your company, product, blog, or brand,” according to their article” Personas- A Simple Introduction.” In their most complete expression, personas typically consist of a name, profile picture, quotes, demographics, goals, needs, behavior in relation to a certain service/product, emotions, and motivations ( for example, see Creative Companion’s Persona Core Poster ). According to design firm Designit, the goal of personas is to “make the research relateable, ]and ] easy to communicate, digest, reference, and apply to product and service development.”

The decontextualization of personalities

Personas are common because they make “dry” research information more realistic, more people. However, this approach places a cap on the study’s data research, making it impossible for the investigated users to be excluded from their particular contexts. As a result, personalities don’t describe important factors that make you realize their decision-making method or allow you to connect to users ‘ thoughts and behavior, they lack stories. You are aware of the persona’s actions, but you lack the knowledge to know why. You end up with depictions of people that are really less people.

This “decontextualization” we see in identities happens in four way, which we’ll discuss below.

People are assumed to be dynamic, according to people.

Although many companies still try to box in their employees and customers with outdated personality tests ( referring to you, Myers-Briggs ), here’s a painfully obvious truth: people are not a fixed set of features. Depending on how you feel, how you act, think, and experience, you go about doing things. You appear distinct to different people, you may act pleasant to some, tough to others. And you change your mind all the time about judgments you’ve taken.

Current psychologists concur that while individuals typically act in accordance with specific patterns, how people act and make decisions is influenced by a combination of both history and environment. The context—the atmosphere, the effect of other people, your feelings, the whole story that led up to a situation—determines the kind of person you are in each particular time.

Personas do not account for this variation in their attempt to reduce reality; instead, they present a consumer as a set of features. Like personality tests, personas seize people away from real existence. Even worse, individuals are reduced to a brand and categorized as” that kind of guy” with no means to practice their inherent flexibility. This behavior lowers variety, reinforces stereotypes, and doesn’t indicate reality.

Personas rely on people, not the setting

You’re designing for a perspective, not an individual, in the real world. Each individual lives in a community, a group, an habitat, where there are environmental, social, and cultural factors you need to consider. A pattern is not meant for a single customer. Instead, you create a product that is intended to be used by a certain number of people. Personas, yet, show the customer alone rather than explain how the consumer relates to the environment.

Would you choose the exact course of action repeatedly? Maybe you’re a dedicated vegan but also decide to buy some meats when your family are coming across. As they depend on various situations and characteristics, your decisions—and behavior, thoughts, and comments —are no absolute but extremely contextual. Because it doesn’t explain the circumstances under which you make your decisions, the persona that “represents” you doesn’t take into account this interdependence. It doesn’t provide a rationale of why you act the way you do. People practice the well-known attribution error, which states that they too often attribute others ‘ behavior to their personalities and not to the circumstances.

As mentioned by the Interaction Design Foundation, identities are often placed in a situation that’s a” specific environment with a problem they want to or have to solve “—does that mean environment actually is considered? However, what frequently happens is that you take a hypothetical figure and based on that fiction decide how this character may deal with a particular situation. How could you possibly understand how someone you want to represent behave in new circumstances if you hadn’t even fully investigated and understood the current context of the people you want to represent?

Personas are meaningless averages

A persona is depicted as a specific person in Shlomo Goltz’s introduction to Smashing Magazine, according to Shlomo Goltz’s introduction article. It is instead made up of observations from numerous people. A well-known critique to this aspect of personas is that the average person does not exist, as per the famous example of the USA Air Force designing planes based on the average of 140 of their pilots ‘ physical dimensions and not a single pilot actually fitting within that average seat.

The same limitation applies to mental aspects of people. Have you ever heard a famous person say something like,” They took what I said out of context!” They used my words, but I didn’t mean it like that”. Although the celebrity’s statement was literally reported, the reporter failed to explain the context of the statement and to explain the non-verbal expressions. As a result, the intended meaning was lost. You do the same when you create personas: you collect somebody’s statement ( or goal, or need, or emotion ), of which the meaning can only be understood if you provide its own specific context, yet report it as an isolated finding.

However, personas go a step further, combining a decontextualized finding with another decontextualized finding from someone else. The resulting set of findings often does not make sense: it’s unclear, or even contrasting, because it lacks the underlying reasons on why and how that finding has arisen. It lacks any significance. And the persona doesn’t give you the full background of the person ( s ) to uncover this meaning: you would need to dive into the raw data for each single persona item to find it. What, then, is the usefulness of the persona?

The validity of personas can be deceiving.

To a certain extent, designers realize that a persona is a lifeless average. Designers invent and add “relatable” details to personas to make them resemble real people in order to overcome this. Nothing captures the absurdity of this better than a sentence by the Interaction Design Foundation:” Add a few fictional personal details to make the persona a realistic character”. In other words, you add non-realism in an attempt to create more realism. You purposefully understate the fact that” John Doe” is an abstract representation of research findings, but wouldn’t it be much more responsible to emphasize that John is only an abstraction? If something is artificial, let’s present it as such.

After accepting that people’s personalities are fixed, ignored the importance of their environment, and hidden meaning by joining isolated, non-generalizable findings, designers create new context to create ( their own ) meaning. In doing so, as with everything they create, they introduce a host of biases. As phrased by Designit, as designers we can” contextualize]the persona ] based on our reality and experience. We make connections that are well-known to us. This practice reinforces stereotypes, doesn’t reflect real-world diversity, and gets further away from people’s actual reality with every detail added.

To conduct effective design research, we must report the “as-is” reality and make it relatable for our audience so that everyone can use their own empathy and formula for their own interpretation and emotional response.

Dynamic Selves: The alternative to personas

If we shouldn’t use personas, what should we do instead?

Designit suggested utilizing mindsets rather than personas. Each Mindset is a” spectrum of attitudes and emotional responses that different people have within the same context or life experience”. It challenges designers to avoid getting fixated on just one person’s way of being. Unfortunately, while being a step in the right direction, this proposal doesn’t take into account that people are part of an environment that determines their personality, their behavior, and, yes, their mindset. Therefore, Mindsets are also not absolute but change in regard to the situation. What determines a particular Mindset, remains to be seen.

Another alternative comes from Margaret P., author of the article” Kill Your Personas“, who has argued for replacing personas with persona spectrums that consist of a range of user abilities. A visual impairment may be temporary ( recovery from eye surgery ), permanent ( blindness ), or situational (screen glare ). Persona spectrums are highly useful for more inclusive and context-based design, as they’re based on the understanding that the context is the pattern, not the personality. Their limitation, however, is that they have a very functional take on users that misses the relatability of a real person taken from within a spectrum.

We want to change the traditional design process to be context-based by creating an alternative to personas. Contexts are generalizable and have patterns that we can identify, just like we tried to do previously with people. How can we identify these patterns, then? How do we ensure truly context-based design?

Understand real individuals in multiple contexts

Nothing can be more relatable and inspiring than reality. Therefore, we have to understand real individuals in their multi-faceted contexts, and use this understanding to fuel our design. We refer to this method as Dynamic Selves.

Let’s take a look at what the approach looks like, based on an example of how one of us applied it in a recent project that researched habits of Italians around energy consumption. We drafted a design research plan aimed at investigating people’s attitudes toward energy consumption and sustainable behavior, with a focus on smart thermostats.

1. Choose the right sample

We frequently get slammed for saying,” Where are you going to find a single person that encapsulates all the information from one of these advanced personas ]” when we debate personas. The answer is simple: you don’t have to. You don’t need to have information about many people for your insights to be deep and meaningful.

In qualitative research, accuracy comes from accurate sampling rather than quantity. You select the people that best represent the “population” you’re designing for. If this sample is chosen wisely and you have a deep understanding of the sampled people, you can infer how the rest of the population thinks and acts. There’s no need to study seven Susans and five Yuriys, one of each will do.

Similarly, you don’t need to understand Susan in fifteen different contexts. Once you’ve seen her in a few different settings, you’ve come to understand how Susan responds to various circumstances. Not Susan as an atomic being but Susan in relation to the surrounding environment: how she might act, feel, and think in different situations.

It becomes clear why each person should be portrayed as an individual because each already represents an abstraction of a larger group of people in similar circumstances because each person is representative of a portion of the total population you’re researching. You don’t want abstractions of abstractions! These selected people need to be understood and shown in their full expression, remaining in their microcosmos—and if you want to identify patterns you can focus on identifying patterns in contexts.

However, the question persists: how do you choose a representative sample? First of all, you have to consider what’s the target audience of the product or service you are designing: it might be useful to look at the company’s goals and strategy, the current customer base, and/or a possible future target audience.

We were creating an application for those who already have a smart thermostat in our example project. In the future, everyone could have a smart thermostat in their house. Right now, though, only early adopters own one. We had to understand the causes behind these early adopters ‘ development in order to create a sizable sample. We therefore recruited by asking people why they had a smart thermostat and how they got it. There were those who had chosen to purchase it, those who had been influenced by others, and those who had discovered it in their homes. So we selected representatives of these three situations, from different age groups and geographical locations, with an equal balance of tech savvy and non-tech savvy participants.

2. Conduct your research

After having chosen and recruited your sample, conduct your research using ethnographic methodologies. This will give you more examples and anecdotes to enrich your qualitative data. In our example project, given COVID-19 restrictions, we converted an in-house ethnographic research effort into remote family interviews, conducted from home and accompanied by diary studies.

To gain an in-depth understanding of attitudes and decision-making trade-offs, the research focus was not limited to the interviewee alone but deliberately included the whole family. With the additions or corrections made by wives, husbands, children, or occasionally even pets, each interviewee would tell a story that would then become much more engaging and precise. We also focused on the relationships with other meaningful people ( such as colleagues or distant family ) and all the behaviors that resulted from those relationships. With this extensive investigation, we were able to create vivid images of dynamic situations involving multiple actors.

It’s essential that the scope of the research remains broad enough to be able to include all possible actors. Therefore, it normally works best to define broad research areas with macro questions. Interviews should be conducted in a semi-structured manner, with follow-up questions delve into subjects that the interviewee has blatantly mentioned. This open-minded “plan to be surprised” will yield the most insightful findings. One of our participants responded,” My wife doesn’t have the thermostat’s app installed; she uses WhatsApp instead,” when we asked how his family controlled the temperature in the house. If she wants to turn on the heater and she is not home, she will text me. I am her thermostat”.

3. Analysis: Create the Dynamic Selves

You begin to represent each individual with several Dynamic Selves, each” Self” representing one of the circumstances you have examined throughout the research analysis. The core of each Dynamic Self is a quote, which comes supported by a photo and a few relevant demographics that illustrate the wider context. The research findings themselves will show which demographics are relevant to show. The key demographics were family type, number and type of homes owned, economic status, and technological maturity in our case because our research focused on families and their way of life to understand their needs for thermal regulation. ( We also included the individual’s name and age, but they’re optional—we included them to ease the stakeholders ‘ transition from personas and be able to connect multiple actions and contexts to the same person ).

Interviews must be video-recorded in order to capture precise quotes, and notes must be as much as possible taken verbatim. This is essential to the truthfulness of the several Selves of each participant. In the case of real-life ethnographic research, photos of the context and anonymized actors are essential to build realistic Selves. These photos should be taken directly from field research, but an evocative and representative image will do as well as that, as long as it’s accurate and depicts meaningful actions that you associate with your participants. For example, one of our interviewees told us about his mountain home where he used to spend every weekend with his family. We depicted him hiking with his young daughter as a result.

At the end of the research analysis, we displayed all of the Selves ‘” cards” on a single canvas, categorized by activities. Each card displayed a situation, represented by a quote and a unique photo. Each participant had several cards about themselves.

4. Identify potential designs

Once you have collected all main quotes from the interview transcripts and diaries, and laid them all down as Self cards, you will see patterns emerge. These patterns will highlight the opportunity areas for new product creation, new functionalities, and new services—for new design.

A particularly intriguing finding was made in our example project regarding the concept of humidity. We realized that people don’t know what humidity is and why it is important to monitor it for health: an environment that’s too dry or too wet can cause respiratory problems or worsen existing ones. This highlighted a significant opportunity for our client to train users about the concept and work as a health advisor.

Benefits of Dynamic Selves

When you use the Dynamic Selves approach in your research, you start to notice unique social relations, peculiar situations real people face and the actions that follow, and that people are surrounded by changing environments. One of the participants in our thermostat project, Davide, is described as a boyfriend, dog lover, and tech nut.

Davide is an individual we might have once reduced to a persona called “tech enthusiast”. However, there are also those who are wealthy or poor who are tech enthusiasts, whether they are single or have families. Their motivations and priorities when deciding to purchase a new thermostat can be opposite according to these different frames.

Once you have understood Davide in multiple situations, and for each situation have understood in sufficient depth the underlying reasons for his behavior, you’re able to generalize how he would act in another situation. You can use your understanding of him to predict what he would think and act in the situations ( or scenarios ) you create.

The Dynamic Selves approach aims to dismiss the conflicted dual purpose of personas—to summarize and empathize at the same time—by separating your research summary from the people you’re seeking to empathize with. This is crucial because scale affects how we feel empathy for people and how difficult it is to do so with other people. We feel the strongest empathy for individuals we can personally relate to.

If you take a real person as inspiration for your design, you no longer need to create an artificial character. No more creating new plot devices to “realize” the character, no more implausible bias. It’s simply how this person is in real life. In fact, as we all know, personas quickly turn into nothing more than a name in our priority guides and prototype screens because we all know these characters don’t really exist.

Another powerful benefit of the Dynamic Selves approach is that it raises the stakes of your work: if you mess up your design, someone real, a person you and the team know and have met, is going to feel the consequences. It might stop you from taking shortcuts and will remind you to conduct daily checks on your designs.

Finally, real people in their specific contexts provide a better foundation for anecdotal storytelling and are thus more persuasive. Documentation of real research is essential in achieving this result. The circumstances of your design proposals resound in your mind when you encounter Alessandra. Noise, bad ergonomics, lack of light, you name it. If we go for this functionality, I’m afraid we’re going to add complexity to her life”.

Conclusion

Designit stated in their article on Mindsets that “design thinking tools offer a shortcut to deal with reality’s complexities, but this process of simplification can occasionally flatten out people’s lives into a few general characteristics.” Unfortunately, personas have been culprits in a crime of oversimplification. They fail to account for the complex nature of our users ‘ decision-making processes and don’t take into account the fact that people are immersed in environments.

Design needs simplification but not generalization. You have to look at the research elements that stand out: the sentences that captured your attention, the images that struck you, the sounds that linger. Avoid using those and use them to describe the person in all of their contexts. Both insights and people come with a context, they cannot be cut from that context because it would remove meaning.

It’s high time for design to break away from fiction and use reality as our guide and inspiration, in all of its messy, surprising, and unquantifiable beauty.

” Any post” you might have? is perhaps one of the worst ways to ask for opinions. It’s obscure and unfocused, and it doesn’t give us a sense of what we’re looking for. Getting good opinions starts sooner than we might hope: it starts with the demand.

Starting the process of receiving feedback with a question may seem counterintuitive, but it makes sense if we consider that receiving feedback can be considered a form of pattern research. In the same way that we wouldn’t perform any studies without the correct questions to get the insight that we need, the best way to ask for feedback is also to build strong issues.

Design criticism is not a one-time procedure. Sure, any great comments process continues until the project is finished, but this is especially true for layout because architecture work continues iteration after iteration, from a high level to the finest details. Each stage requires its unique set of questions.

And suddenly, as with any great research, we need to examine what we got up, get to the base of its perspectives, and take action. Iteration, evaluation, and problem. This look at each of those.

The query

Being available to input is important, but we need to be specific about what we’re looking for. Any comments,” What do you think,” or” I’d love to hear your mind” at the end of a presentation are likely to garner a lot of different ideas, or worse, to make people follow the lead of the first speaker. And next… we get frustrated because vague issues like those can change a high-level moves review into folks rather commenting on the borders of buttons. Which issue may be important, so it might be difficult to get the team to pay attention to it.

But how do we get into this scenario? A number of elements are involved. One is that we don’t often consider asking as a part of the input approach. Another is how healthy it is to keep the issue open and assume that everyone else will agree. Another is that in nonprofessional conversations, there’s usually no need to be that exact. In summary, we tend to undervalue the value of the issues, and we don’t make any improvements to them.

The work of asking good questions guidelines and focuses the criticism. It’s even a form of acceptance because it specifies what kind of feedback you’d like to receive and how you’re open to them. It puts people in the right emotional state, especially in situations when they weren’t expecting to give opinions.

There isn’t a second best method to request suggestions. It simply needs to be certain, and precision may take several shapes. The one of stage over level is a design for design criticism that I’ve found to be particularly helpful in my coaching.

” Stage” refers to each of the actions of the process—in our event, the design process. The kind of feedback changes as the consumer research moves forward to the final design. But within a single stage, one might also examine whether some assumptions are correct and whether there’s been a suitable language of the amassed input into updated designs as the job has evolved. The layers of user experience could serve as a starting point for potential questions. What do you want to know: Project objectives? user requirements? Functionality? the content Interaction design? Information architecture UI design? Navigation planning? Visual design? Branding?

Here’re a few example questions that are precise and to the point that refer to different layers:

• Functionality: Is it desirable to automate account creation?
• Interaction design: Take a look through the updated flow and let me know whether you see any steps or error states that I might’ve missed.
• Information architecture: On this page, we have two competing pieces of information. Is the structure effective in communicating them both?
• User interface design: What do you think about the top-of-the-page error counter, which makes sure you can see the next error even when the error is outside the viewport?
• Navigation design: From research, we identified these second-level navigation items, but once you’re on the page, the list feels too long and hard to navigate. Exist any recommendations for resolving this?
• Visual design: Are the sticky notifications in the bottom-right corner visible enough?

How much of a presentation’s depth would be on the other axis of specificity. For example, we might have introduced a new end-to-end flow, but there was a specific view that you found particularly challenging and you’d like a detailed review of that. This can be especially helpful when switching between iterations because it’s crucial to highlight the changes made.

There are other things that we can consider when we want to achieve more specific—and more effective—questions.

A quick fix is to get rid of the generic qualifiers from questions like “good”, “well,” “nice,” “bad,” “okay,” and” cool.” For example, asking,” When the block opens and the buttons appear, is this interaction good”? is it possible to look specific, but you can identify the “good” qualifier and make the question” When the block opens and the buttons appear, is it clear what the next action is” look like?

Sometimes we actually do want broad feedback. Although that is uncommon, it is possible. In that sense, you might still make it explicit that you’re looking for a wide range of opinions, whether at a high level or with details. Or perhaps just say,” At first glance, what do you think”? so that it’s clear that what you’re asking is open ended but focused on someone’s impression after their first five seconds of looking at it.

Sometimes the project is particularly broad, and some areas may have already been thoroughly explored. In these situations, it might be useful to explicitly say that some parts are already locked in and aren’t open to feedback. Although it’s not something I’d recommend in general, I’ve found it helpful in avoiding getting back into rabbit holes like those that could lead to even more refinement if what’s important right now isn’t.

Asking specific questions can completely change the quality of the feedback that you receive. People with less refined criticism will now be able to provide more actionable feedback, and even expert designers will appreciate the clarity and effectiveness gained from concentrating solely on what’s needed. It can save a lot of time and frustration.

The iteration

Design iterations are probably the most visible part of the design work, and they provide a natural checkpoint for feedback. Many design tools have inline commenting, but many of them only display changes as a single fluid stream in the same file. In addition, these kinds of design tools automatically update shared UI components, make conversations disappear and require designs to always display the most recent version, unless these would-be useful features were manually disabled. The implied goal that these design tools seem to have is to arrive at just one final copy with all discussions closed, probably because they inherited patterns from how written documents are collaboratively edited. That approach to design critiques is probably not the best approach, but some teams might benefit from it even if I don’t want to be too prescriptive.

The asynchronous design-critique approach that I find most effective is to create explicit checkpoints for discussion. For this, I’m going to use the term iteration post. It refers to a write-up or presentation of the design iteration followed by a discussion thread of some kind. This can be used on any platform that can accommodate this structure. By the way, when I refer to a “write-up or presentation“, I’m including video recordings or other media too: as long as it’s asynchronous, it works.

Using iteration posts has a number of benefits:

• It creates a rhythm in the design work so that the designer can review feedback from each iteration and prepare for the next.
• Decisions are made immediately available for future review, and conversations are also always available.
• It creates a record of how the design changed over time.
• It might also make it simpler to collect and act on feedback depending on the tool.

These posts of course don’t mean that no other feedback approach should be used, just that iteration posts could be the primary rhythm for a remote design team to use. And from there, other feedback techniques ( such as live critique, pair designing, or inline comments ) can emerge.

I don’t think there’s a standard format for iteration posts. However, there are a few high-level components that make sense to include as a baseline:

1. The goal
2. The layout
3. The list of changes
4. The querys

Each project is likely to have a goal, and hopefully it’s something that’s already been summarized in a single sentence somewhere else, such as the client brief, the product manager’s outline, or the project owner’s request. In other words, I would copy and paste this into every iteration post to make it work. The idea is to provide context and to repeat what’s essential to make each iteration post complete so that there’s no need to find information spread across multiple posts. The most recent iteration post will have everything I need if I want to know about the most recent design.

This copy-and-paste part introduces another relevant concept: alignment comes from repetition. Therefore, repeating information in posts is actually very effective at ensuring that everyone is on the same page.

The design is then the actual series of information-architecture outlines, diagrams, flows, maps, wireframes, screens, visuals, and any other kind of design work that’s been done. It’s any design object, to put it briefly. For the final stages of work, I prefer the term blueprint to emphasize that I’ll be showing full flows instead of individual screens to make it easier to understand the bigger picture.

It might also be helpful to have clear names on the objects since it makes them look better to refer to. Write the post in a way that helps people understand the work. It’s not much different from creating a strong live presentation.

For an efficient discussion, you should also include a bullet list of the changes from the previous iteration to let people focus on what’s new, which can be especially useful for larger pieces of work where keeping track, iteration after iteration, could become a challenge.

Finally, as mentioned earlier, it’s crucial that you include a list of the questions to help you guide the design critique in the desired direction. Doing this as a numbered list can also help make it easier to refer to each question by its number.

Not every iteration is the same. Earlier iterations don’t need to be as tightly focused—they can be more exploratory and experimental, maybe even breaking some of the design-language guidelines to see what’s possible. Then, later, the iterations begin coming to a decision and improving it until the design process is complete and the feature is ready.

I want to highlight that even if these iteration posts are written and conceived as checkpoints, by no means do they need to be exhaustive. A post might be a draft, just a concept to start a discussion, or it might be a cumulative list of all the features that have been added over the course of each iteration until the full picture is achieved.

Over time, I also started using specific labels for incremental iterations: i1, i2, i3, and so on. Although this may seem like a minor labeling tip, it can be useful in many ways:

• Unique—It’s a clear unique marker. Everyone knows where to go to review things, and it’s simple to say” This was discussed in i4″ with each project.
• Unassuming—It works like versions ( such as v1, v2, and v3 ) but in contrast, versions create the impression of something that’s big, exhaustive, and complete. Attempts must be exploratory, incomplete, or partial.
• Future proof—It resolves the “final” naming problem that you can run into with versions. No more files with the title “final final complete no-really-its-done” Within each project, the largest number always represents the latest iteration.

The wording release candidate (RC ) could be used to indicate when a design is finished enough to be worked on, even if there are some areas that still need improvement and, in turn, require more iterations, such as” with i8 we reached RC” or “i12 is an RC” to indicate when it is finished.

The review

What typically occurs during a design critique is an open discussion, with a back and forth between parties that can be very productive. This approach is particularly effective during live, synchronous feedback. However, using a different approach when we work asynchronously is more effective: adopting a user-research mindset. Written feedback from teammates, stakeholders, or others can be treated as if it were the result of user interviews and surveys, and we can analyze it accordingly.

Asynchronous feedback is particularly effective because of this shift, especially around these friction points:

1. It removes the pressure to reply to everyone.
2. It lessens the annoyance caused by swoop-by comments.
3. It lessens our personal stake.

The first friction point is having to feel pressured to respond to each and every comment. Sometimes we write the iteration post, and we get replies from our team. It’s just a few of them, it’s simple, and there isn’t much of a problem with it. But other times, some solutions might require more in-depth discussions, and the amount of replies can quickly increase, which can create a tension between trying to be a good team player by replying to everyone and doing the next design iteration. This might be especially true if the respondent is a stakeholder or someone directly involved in the project who we feel we need to speak with. We need to accept that this pressure is absolutely normal, and it’s human nature to try to accommodate people who we care about. When responding to all comments, it can be effective, but when we consider a design critique more like user research, we realize that we don’t need to respond to every comment, and there are alternatives in asynchronous spaces:

One is to let the next iteration speak for itself. The response is received when the design changes and a follow-up iteration is made. You might tag all the people who were involved in the previous discussion, but even that’s a choice, not a requirement.
• Another option is to respond politely to acknowledge each comment, such as” Understood. Thank you”,” Good points— I’ll review”, or” Thanks. These will be included in the upcoming iteration. In some cases, this could also be just a single top-level comment along the lines of” Thanks for all the feedback everyone—the next iteration is coming soon”!
• Another option is to quickly summarize the comments before moving on. Depending on your workflow, this can be particularly useful as it can provide a simplified checklist that you can then use for the next iteration.

The swoop-by comment, which is the kind of feedback that comes from a member of a team or non-project who might not be aware of the context, restrictions, decisions, or requirements, or of the discussions from earlier iterations, is the second friction point. On their side, there’s something that one can hope that they might learn: they could start to acknowledge that they’re doing this and they could be more conscious in outlining where they’re coming from. Swoop-by comments frequently prompt the simple thought,” We’ve already discussed this,” and it can be frustrating to have to keep coming back and forth.

Let’s begin by acknowledging again that there’s no need to reply to every comment. However, if responding to a previously litigated point is useful, a brief response with a link to the previous discussion for additional information is typically sufficient. Remember, alignment comes from repetition, so it’s okay to repeat things sometimes!

Swoop-by commenting has two benefits: first, they might point out something that isn’t clear, and second, they might serve as a reference point for someone who is first viewing the design. Sure, you’ll still be frustrated, but that might at least help in dealing with it.

The personal stake we might have in relation to the design could be the third friction point, which might cause us to feel defensive if the review turned out to be more of a discussion. Treating feedback as user research helps us create a healthy distance between the people giving us feedback and our ego ( because yes, even if we don’t want to admit it, it’s there ). And in the end, presenting everything in aggregated form helps us to prioritize our work more.

Always remember that while you need to listen to stakeholders, project owners, and specific advice, you don’t have to accept every piece of feedback. You must examine it and come up with a conclusion that you can support, but sometimes “no” is the best choice.

As the designer leading the project, you’re in charge of that decision. In the end, everyone has their area of expertise, and as a designer, you are the one with the most background and knowledge to make the right choice. And by listening to the feedback that you’ve received, you’re making sure that it’s also the best and most balanced decision.

Thanks to Mike Shelton and Brie Anne Demkiw for their contributions to the initial draft of this article.