Blog

Humility, a writer’s most important quality, has a great circle to it. What about sincerity, an business manager’s vital value? Or a doctor’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 section.

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

The Ludicrous Pate of Justin: The Tale of Justin

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

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

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

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

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

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

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

We 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. There are a few content panes here, with both Mac-focused news and general news (tech, design ) to be seen. We also offered many of the custom downloads I cited before as present on my folio site but branded and themed to GUI Galaxy.

The presentation layer consists of international design, illustration, and news author collaboration, and the backbone of the website 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, there’s a reason for the nostalgia for that design era ( the” Wild West” era, as I put it ): the inherent exploration, personality, and creativity that dominated many design portals and personal portfolio websites. Ultra-finely detailed pixel art UI, custom illustration, bespoke vector graphics, all underpinned by a strong design community.

The web design industry has experienced 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 Mac OS 7.5 is available, 8 and 9 are not very different.

How could any single icon, at any point, stand out and grab my attention, fascinated me? In this example, the user’s desktop is tidy, but think of a more realistic example with icon pandemonium. 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, in my opinion, was the embodiment of digital visual communication under such absurd constraints. And often, ridiculous restrictions can yield the purification of concept and theme.

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

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

These are some of my creations that made use of ResEdit, the only program I had at the time, to create icons. ResEdit was a clunky, built-in Mac OS utility not really made for exactly what we were using it for. Research is at the center of all of this endeavor. Challenge. 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. With its pixel art-fueled presentation, attention to detail paid to every aspect of every detail, and many of the more well-known designers of the time who were invited to be news authors on the site, well… it was the place to be, my friend. With respect where respect is due, GUI Galaxy’s concept was inspired by what these folks were doing.

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

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

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

The victims? My design stagnated. My evolution has stagnated, as is my evolution.

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

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

It was a gift I initially did not accept but which I, on the whole, was able to reflect on in depth. I was soon able to accept, and process, and course correct. Although the realization made me feel uneasy, the re-awakening was necessary. I let go of the “reward” of adulation and re-centered upon what stoked the fire for me in art school. Most importantly, I returned to my fundamental values.

Always Students

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

Let’s 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 often regarded as works of art by themselves because they depict what is actually happening inside the Collider during any given particle collision event.

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, how they spoke and what they talked about was like an alien tongue. And by making myself humble and working under the mindset that I was but a student, I made myself available to be a part of their world to generate that vital connection.

I also had my first ethnographic observational experience, which involved visiting the Fermilab location and observing how the physicists used the tool in their own environments, on their own terminals. For example, one takeaway was that due to the level of ambient light-driven contrast within the facility, the data columns ended up using white text on a dark gray background instead of black text-on-white. This made it easier for them to pore over a lot of data during the day and lessen their strain on their eyes. 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 words “grow” and “evolve” in particular in that statement. If we are always students of our craft, we are also continually making ourselves available to evolve. Yes, we have years of practical design experience under our belt. Or the focused lab sessions from a UX bootcamp. Or the monogrammed portfolio of our work. Or, ultimately, decades of a career behind us.

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

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

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

I have a creative side. No all creative people approve of this brand. No everyone sees themselves in this way. Some innovative people practice technology in their work. I value their assertion, which is true. Perhaps I even have a small envy for them. However, my method is unique; my being is unique.

It distracts one to apologize and qualify in progress. My mind uses that to destroy me. I put it off for the moment. I may regret and then qualify. after I’ve said what I should have. which is difficult enough.

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

Sometimes it does. Maybe what I need to make arrives in a flash. 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.

Maybe I just keep working until the thought strikes me. Maybe it arrives right away, but 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 medal in one of his Cracker Jacks. Often I get away with this. Yes, that is the best plan, per some observers. They don’t usually, and I regret losing my joy.

Passion should be saved for the meeting, where it will matter. Certainly the informal get-together that comes before that meeting with two more meetings. Nobody understands why these discussions occur. We keep saying we’re going to get rid of them, but we just keep trying to find different ways to get them. They occasionally also are good. But occasionally they detract from the actual labor. Depending on what you do and where you do it, the ratio between when conferences are valuable and when they are a sad distraction vary. also who you are and what you do. I’ll go over it once more. I have a creative side. That is the design.

Often, a lot of hours of diligent and diligent work ends up with something that is barely 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 control over my goals. And I have no power over my best tips.

I may hammer away and often find it useful to surround myself with images or information. I can go for a move, which occasionally works. There is a Eureka, which has nothing to do with boiling pots and sizzling oil, and I may be making dinner. I frequently have a plan for action when I wake up. The idea that may have saved me disappears almost as frequently as I become aware and a part of the world once more as a senseless wind of oblivion. For ingenuity, in my opinion, originates in that other world. the one that we enter in ambitions and, possibly, before and after suicide. But authors should be asking this, and I am not a writer. I have a creative side. Theologians are encouraged to build massive armies in their artistic 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 not how I came around, though.

Often the result is mitigation. And suffering. You are familiar with the adage” the tortured designer”? Even when the artist is trying to write a soft drink song, a call in a worn-out comedy, or a budget ask, that word is correct.

Some individuals who detest being called artistic perhaps been closeted artists, but that’s between them and their gods. No act here. Yours is also real. However, mine is for me.

Artists are recognized as artists.

Disadvantages are aware of cons, just like queers are aware of queers, just like real rappers are aware of actual rappers are aware of cons. People have a lot of regard for artists. 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 of this. They argue, they are depressed, they regret their most critical decisions, they are weak and hungry, they can be violent, and they can be as ridiculous as we can if, like us, they are clay. But. But. However, they produce something incredible. They give birth to something that was unable to arise before them or otherwise. They are thought’s founders. And I suppose I should add that they are the mother of technology because it’s just lying it. Ba ho backside! Okay, that’s all said and done. Continue.

Because we compare our personal small accomplishments to those of the great ones, artists denigrate our own. Wonderful video I‘m not Miyazaki, though. Greatness is then that. That is glory straight out of the mouth of God. This unsatisfied small thing I created? It essentially fell off the pumpkin vehicle. And the carrots weren’t actually new.

Artists is aware that they are at best Some. Yet Mozart’s original artists believe that.

I have a creative side. I haven’t worked in advertising in 30 times, but my former artistic managers are the ones who make my hallucinations. And they are correct to do so. When it really counts, my brain goes flat because I am too lazy and simplistic. No medication is available to treat innovative function.

I have a creative side. Every project I create has a goal that makes Indiana Jones appear to be a retiree snoring in a balcony head. The more I pursue creativity, the faster I can complete my work, and the longer I obsess over my ideas and whizz around in circles before I can complete that task.

I can move ten times more quickly than those who aren’t innovative, those who have just been creative for a short while, and those who have just had a short time of creative work. Only that I work twice as quickly as they do, putting the work away, just before I do it, When I put my mind to it, I am so confident in my ability to do a wonderful career. I have an addiction to the delay rush. I’m also so scared of jumping.

I am hardly a painter.

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

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

I have a creative side. Every term I’ve said these may irritate another artists who see things differently. Ask two artists a problem and find three opinions. No matter how we perhaps think about it, our debate, our passion for it, and our responsibility to our own truth, at least in my opinion, are the best indications that we are artists.

I have a creative side. I lament my lack of taste in the areas of human knowledge that I know quite small, that is to say about everything. And I put my ego before everything else in the areas that are most important to me, or perhaps more precisely, to my obsessions. Without my addictions, I’d probably have to spend the majority of our time looking ourselves in the eye, which is something that almost none of us can do for very long. No seriously. No actually. Because living is so difficult to handle when you really look at it.

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

Working frees me from worrying about my job.

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

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 frightened of forgetting what I was saying because I was afraid of you seeing through my sad movements toward the wonderful.

There. I believe I said it correctly.

I’d like you to consider this a “yes … and” piece to complement Joe’s post. Instead of refuting everything he’s saying, I’m pointing out some areas where AI may make real, positive impacts on people with disabilities. I want to take some time to talk about what’s possible in hope that we’ll get there one day. I’m no saying that there aren’t real challenges or pressing problems with AI that need to be addressed; there are.

Other words

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

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

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

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

• Are there more smartphone users than feature phones?
• How many more?
• Is there a group of people that don’t fall into either of these buckets?
• What number is that?

For a moment, the chance to learn more about images and data in this way could be revolutionary for people who are blind and low vision as well as for those with various forms of color blindness, cognitive disabilities, and other issues. Putting aside the realities 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 call 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’s equally true that all computer models have the potential to foster conflict, prejudice, and intolerance. Whether it’s Twitter always showing you the latest tweet from a bored billionaire, YouTube sending us into a Q-hole, or Instagram warping our ideas of what natural bodies look like, we know that poorly authored and maintained algorithms are incredibly harmful. A large portion of this is a result of a lack of diversity in the people who design and construct them. However, when these platforms are built with inclusive features in mind, there is real potential for algorithm development to help people with disabilities.

Take Mentra, for example. They serve as a network of people with disabilities. 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 the 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.

More people with disabilities can be used to create algorithms, which can lessen the likelihood that they 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 followed a group of nondisabled white male academics who spoke about AI, it might be advisable to follow those who are disabled, aren’t white, or aren’t men who also speak about AI. If you followed its 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

If I weren’t attempting to combine this with other tasks, I’m sure I could go on and on, giving various examples of how AI could be used to assist people with disabilities, but I’m going to make this last section into a bit of a lightning round. In no particular order:

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 it’s something we need to approach responsibly, but the technology has truly transformative potential.
• voice recognition Researchers like those in the Speech Accessibility Project are paying people with disabilities for their help in collecting recordings of people with atypical speech. As I type, they are 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 quite capable of changing existing text without giving off hallucinations. This is incredibly empowering for those who have cognitive disabilities and who may benefit from text summaries or simplified versions, or even text that has been prepared for bionic reading.

The importance of diverse teams and data

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

Want a model that doesn’t demean or patronize or objectify people with disabilities? Make sure that you include information about disabilities that has been written by people with a variety of disabilities in the training data.

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

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

I have no doubt that AI has the potential to harm people today, tomorrow, and long into the future. However, I think we should also acknowledge this and make thoughtful, thoughtful, and intentional changes to our approaches to AI that will also reduce harm over time with an emphasis on accessibility ( and, in general, inclusion ). Today, tomorrow, and well into the future.

Many thanks to Kartik Sawhney for supporting the development of this article, Ashley Bischoff for providing me with invaluable editorial support, and, of course, Joe Dolson for the prompt.

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

How we got below

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

the development of online standards

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

Server-side language like PHP, Java, and.NET took Perl as the primary back-end computers, and the cgi-bin was tossed in the garbage bin. The first age of internet programs started with content-management systems (especially those used in blogs like Blogger, Grey Matter, Movable Type, and WordPress ), with these better server-side equipment. In the mid-2000s, AJAX opened gates for sequential interaction between the front end and back close. Websites now no longer needed to reload 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 photo replacement enable skilled manufacturers and designers to use fonts of their choosing. And technology like Flash made it possible to include movies, sports, and even more engagement.

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

The web as software platform

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

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

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

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

Where we are now

It seems like we’ve reached yet another significant turning point in the last couple of years. As social-media platforms fracture and wane, there’s been a growing interest in owning our own content again. There are many different ways to create a website, from the tried-and-true classic of hosting plain HTML files to static site generators to content management systems of all varieties. The fracturing of social media also comes with a cost: we lose crucial infrastructure for discovery and connection. Webmentions, RSS, ActivityPub, and other IndieWeb tools can be useful in this regard, but they’re still largely underdeveloped and difficult to use for the less geeky. We can build amazing personal websites and add to them regularly, but without discovery and connection, it can sometimes feel like we may as well be shouting into the void.

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 has already exceeded 80 %. Nowadays, the barrier to using newer techniques often isn’t browser support but simply the limits of how quickly designers and developers can learn what’s available and how to adopt it.

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

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

Where do we go from here?

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

Build for the long haul. Optimize for performance, for accessibility, and for the user. weigh the price of those user-friendly tools. They may make your job a little easier today, but how do they affect everything else? What is the cost 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 the basics. Standards continue to evolve over time, but browsers have done a remarkably good job of continuing to support older standards. The same isn’t always the case with third-party frameworks. Sites built with even the hackiest of HTML from the’ 90s still work just fine today. The same can’t always be said of websites created with frameworks even after a few years.

Design with care. Consider the effects of each choice, whether your craft is code, pixels, or processes. The convenience of many a modern tool comes at the cost of not always understanding the underlying decisions that have led to its design and not always considering the impact that those decisions can have. Use the time saved by modern tools to 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! The ultimate experiment is this web we created. It’s the single largest human endeavor in history, and yet each of us can create our own pocket within it. Be brave and try something new. Build a playground for ideas. Create absurd experiments in your own crazy science lab. 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 go through testing, playing, and learning. Write on your own website, post on whichever social media site you prefer, or shout it from a TikTok. Write something for A List Apart! But take the time to amplify others too: find new voices, learn from them, and share what they’ve taught you.

Make a move and make it happen.

As designers and developers for the web ( and beyond ), we’re responsible for building the future every day, whether that may take the shape of personal websites, social media tools used by billions, or anything in between. Let’s give everything we produce a positive vibe by infusing our values into everything we do. 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 have mastered the web.

The personalization space is real, between the dream of getting it right and the fear of it going wrong ( like when we encounter “persofails” in the spirit of a company that regularly asks regular people to buy more toilet seats ). 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 carriers reasonably.

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

We refer to it as prepersonalization.

Behind the song

Take into account Spotify’s DJ feature, which was introduced last month.

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

How do you decide where to position customisation wagers? How do you design regular interactions that didn’t journey up users or—worse—breed mistrust? We’ve discovered that several budgeted programs second required one or more workshops to join key stakeholders and domestic customers of the technology in order to justify their continuing investments. Create it count.

We’ve closely observed the same evolution with our consumers, from major software to young companies. In our experience with working on small and large customisation efforts, 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 separate successful future endeavors from unsuccessful ones, saving countless hours of time, resources, and overall well-being.

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 ( like 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. These cards won’t be necessary for you. But we strongly recommend that you create something similar, whether that might be digital or physical.

Set the timer for the 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. Details on the essential first-day activities are included in a summary of our broad approach.

The full arc of the wider workshop is threefold:

Kickstart: This specifies the terms of engagement as you concentrate on the potential, the readiness and drive of your team, and your leadership.
1. Plan your work: This is the heart of the card-based workshop activities where you specify a plan of attack and the scope of work.
2. Work your plan: This stage essentially entails creating a competitive environment in which team members can individually present their own pilots that each contain a proof-of-concept project, its business case, and its operating model.

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

Kickstart: Apt your appetite

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

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

The table must be set up for this. What are the possible paths for the practice in your organization? Here’s a long-form primer and a strategic framework for a broader perspective.

Assess each example that you discuss for its complexity and the level of effort that you estimate that it would take for your team to deliver that feature ( or something similar ). 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 currently offer and what you intend to offer 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 their focus should be placed for 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 acknowledging the magnitude of that need and finding a solution. ) In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six intractable behaviors that prevent progress.

Effectively collaborating and managing expectations is critical to your success. Consider the potential obstacles to your upcoming progress. 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? Good, you’re all set to go on.

Hit that test kitchen

Next, let’s take a look at what you’ll need to create personalization recipes. Personalization engines, which are robust software suites for automating and expressing dynamic content, can intimidate new customers. They give you a variety of options for how your organization can conduct its activities because of their broad and potent capabilities. This presents the question: Where do you begin when you’re configuring a connected experience?

The key here is to avoid treating the installed software ( as one of our client executives humorously put it ) like some sort of dream kitchen. 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

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

Not just discovering requirements, it is. Documenting your personalizations as a series of if-then statements lets the team:

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

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 your 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 created these cards and card categories. We regularly play-test their fit with conference audiences and clients. And we still come across fresh possibilities. But they all follow an underlying who-what-when-why logic.

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

1. Nurture personalization: When a guest or an unknown visitor interacts with a product title, a banner or alert bar appears that makes it easier for them to encounter a related title they may want to read, saving them time.
2. Welcome automation: An email is sent 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.

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

The 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 necessary 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“.

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

You can’t stand the heat, unquestionably…

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.

Although there are costs associated with purchasing this type of technology and product design, time well spent on sizing up and confronting your unique situation and digital skills. Don’t squander it. The pudding is the proof, as they say.

Ever since I was a boy, I’ve been fascinated with movies. I loved the characters and the excitement—but most of all the stories. I wanted to be an actor. And I believed that I’d get to do the things that Indiana Jones did and go on exciting adventures. I even dreamed up ideas for movies that my friends and I could make and star in. But they never went any further. I did, however, end up working in user experience (UX). Now, I realize that there’s an element of theater to UX—I hadn’t really considered it before, but user research is storytelling. And to get the most out of user research, you need to tell a good story where you bring stakeholders—the product team and decision makers—along and get them interested in learning more.

Think of your favorite movie. More than likely it follows a three-act structure that’s commonly seen in storytelling: the setup, the conflict, and the resolution. The first act shows what exists today, and it helps you get to know the characters and the challenges and problems that they face. Act two introduces the conflict, where the action is. Here, problems grow or get worse. And the third and final act is the resolution. This is where the issues are resolved and the characters learn and change. I believe that this structure is also a great way to think about user research, and I think that it can be especially helpful in explaining user research to others.

Use storytelling as a structure to do research

It’s sad to say, but many have come to see research as being expendable. If budgets or timelines are tight, research tends to be one of the first things to go. Instead of investing in research, some product managers rely on designers or—worse—their own opinion to make the “right” choices for users based on their experience or accepted best practices. That may get teams some of the way, but that approach can so easily miss out on solving users’ real problems. To remain user-centered, this is something we should avoid. User research elevates design. It keeps it on track, pointing to problems and opportunities. Being aware of the issues with your product and reacting to them can help you stay ahead of your competitors.

In the three-act structure, each act corresponds to a part of the process, and each part is critical to telling the whole story. Let’s look at the different acts and how they align with user research.

Act one: setup

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

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

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

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

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

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

Act two: conflict

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

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

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

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

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

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

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

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

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

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

Act three: resolution

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

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

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

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

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

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

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

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

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

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

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

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

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

The perils of feature-first creation

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

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

The issue with most funding apps is that they frequently turn out to be reflections of the company’s internal politics rather than an experience created exclusively for the customer. This implies that the priority is to provide as many features and functionalities as possible to satisfy the requirements and desires of competing inside ministries as opposed to a distinct value statement that is focused on what people in the real world actually want. These products may therefore quickly become a muddled mess of confusing, related, and finally unlovable client experiences—a feature salad, you might say.

The significance of the foundation

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

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

The rock has got to be in and around the standard cleaning journeys in the world of retail bank, which is where I work. People only look at their existing accounts once every blue sky, but they do so daily. They purchase a credit card every year or every other year, but they at least once a month assess their stability and pay their bills.

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

But how do you reach the foundation? By focusing on the” MVP” strategy, giving convenience precedence, and working incrementally toward a clear value proposition. This means avoiding pointless extras and putting your people first, making the most of them.

It also requires some fortitude, as your coworkers might not always agree on your vision at first. And in some cases, it might even mean making it clear to consumers that you won’t be coming over to their home and prepare their meal. Sometimes you may need to use the sporadic “opinionated user interface design” ( i .e. clunky workaround for edge cases ) to test a concept or to give yourself some room to work on something more crucial stuff.

Functional methods for creating stick-like economic items

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

1. What trouble are you trying to solve first, and make a distinct “why”? For whom? Make sure your goal is unmistakable before beginning any work. Make certain it also aligns with the goals of your business.
2. Avoid the temptation to put too many characteristics at once by focusing on one, key feature and focusing on getting that right before moving on to something else. Choose one that actually adds value, and work from there.
3. When it comes to financial products, simplicity is often more important than complexity. Eliminate unnecessary details and concentrate on what matters most.
4. Accept continuous iteration: Bedrock is not a fixed destination; it is a dynamic process. Continuously collect user feedback, make product improvements, and advance in that direction.
5. Stop, look, and listen: Don’t just go through with testing your product as part of the delivery process; test it repeatedly in the field. Use it for yourself. Run the A/B tests. User feedback on Gatter. Talk to those who use it, and change things up accordingly.

The bedrock paradox

This is an intriguing paradox: sacrificing some of the potential for short-term growth in favor of long-term stability. But the payoff is worthwhile because products created with a focus on bedrock will outlive and outperform their competitors and provide users with ongoing value over time.

How do you begin your quest for bedrock, then? Take it gradually. Start by identifying the underlying factors that your users actually care about. Concentrate on developing and improving a single, potent feature that delivers real value. And most importantly, make an obsessive effort because, in the words of Abraham Lincoln, Alan Kay, or Peter Drucker ( whew! The best way to foretell the future is to create it, he said.

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

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

The conventional solution has been to create a table with clear lines. The Design Manager handles persons, the Lead Designer handles art. Problem solved, is that straight? Except for dream, fresh org charts. In fact, both roles care greatly about crew health, style quality, and shipping great work.

When you start thinking of your style organization as a style organism, the magic happens when you embrace the coincide rather than fighting it.

The biology of a good design team

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

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

When we look at how good team really function, three critical devices emerge. Each role must coexist, but one must assume primary responsibility for maintaining a solid structure.

The Nervous System: Citizens & Psychology

Major caregiver: Design Manager
Supporting position: Lead Designer

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

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

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

Design Manager tends to:

• discussions about careers and career development
• internal security and dynamics of the crew
• Job management and resource planning
• Performance evaluations and opinions management methods
• Providing learning options

Direct Custom supports by:

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

The Muscular System: Design & Execution

Major caretaker: Lead Designer
Supporting position: Design Manager

The skeletal structure focuses on developing strength, coordination, and talent development. When this technique is healthy, the team can do complicated design work with precision, maintain regular quality, and adjust their craft to fresh challenges.

The Lead Designer is in charge of everything here. They oversee the creation of quality standards, provide craft instruction, and set design standards. They’re the ones who can tell you if a design decision is sound or if we’re solving the right problem.

However, the Design Manager has a significant supporting role. They’re making sure the team has the resources and support they need to perform their best work, such as proper nutrition and time for an athlete recovering.

Lead Designer tends to:

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

Design Manager supports by:

• ensuring that design standards are understood and accepted by all members of the team
• Confirming that the right direction is being used is being done
• Supporting practices and systems that scale without bottlenecking
• facilitating design alignment among all teams
• Providing resources and removing obstacles to outstanding craft work

The Circulatory System: Strategy &amp, Flow

Shared caretakers: Lead Designer and Design Manager, respectively.

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

This is the true partnership that occurs. Although both roles are responsible for keeping the circulation strong, they both bring in different viewpoints.

Lead Designer contributes:

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

Contributes the design manager:

• Communication to team and stakeholders
• Stakeholder management and alignment
• Team accountability across all levels
• Strategic business initiatives

Both parties work together on:

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

Keeping the Organism Healthy

Understanding that all three systems must work together is the key to making this partnership sing. A team will eventually lose their way despite excellent craftmanship and poor psychological security. A team with great culture but weak craft execution will ship mediocre work. A team that has both but poor strategic planning will concentrate on the wrong things.

Be Specific About the System You’re Defending.

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

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

Create Positive Feedback Loops

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

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

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

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

Handle Handoffs Gracefully

When something switches from one system to another, this partnership’s most crucial moments occur. This might occur when a design standard ( muscular system ) needs to be implemented across the team ( nervous system ) or when a tactical initiative ( circulatory system ) requires a particular craft system ( muscular system ) rollout.

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

Stay curious and avoid being territorial.

The Design Manager who never thinks about craft, or the Lead Designer who never considers team dynamics, is like a doctor who only looks at one body system. Even when they aren’t the primary caretaker, great design leadership requires both people to be as concerned with the entire organism.

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

When the Organism Gets Sick

This partnership can go wrong even with clear roles. Here are the most typical failure modes I’ve seen:

System Isolation

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

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

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

Poor Circulation

There is no clear strategic direction, shifting priorities, or accepting responsibility for the flow of information.

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

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

Autoimmune Response

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

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

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

The Payoff

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

When both roles are well-balanced and functioning well together, you get the best of both worlds: strong people leadership and deep craft knowledge. One person can help keep the team’s health when one is sick, on vacation, or overjoyed. When a decision requires both the people perspective and the craft perspective, you’ve got both right there in the room.

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

The End result

The relationship between a Design Manager and Lead Designer isn’t about dividing territories. Multipliering impact is what is concerned with. Magic occurs when both roles are aware that they are promoting various aspects of a healthy organism.

The mind and body work together. The team benefits from both strategic thinking and craftmanship. And most importantly, the work that is distributed to users benefits both sides.

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

The internet has tones. Our style processes may also.

Designing methods as living language

Designing languages are living languages, not portion libraries. The parts are called terms, the patterns are called phrases, and the sentences are called layouts. Our goods ‘ stories are the product of the conversations we have with people.

But let’s remember that voices increase as a speech gets more fluent without losing its meaning. English in Scotland and English in Sydney are clearly different, but both are undeniably English. The terminology adapts to the situation while maintaining its fundamental message. As a Brazilian Portuguese presenter who grew up in Sydney and learned English with an American accent, this was even more apparent to me.

Our pattern processes may operate similarly. rigid systems that break under the influence of cultural pressure are the result of rigid adhesion to visual rules. Fluidic devices can bend without rupturing.

Consistent behavior turns into a captivity

Constant components may speed up development and bring together experiences, which was the promise of design systems. But as techniques evolved and products developed more sophisticated, that promise has since become a prison. Team submit hundreds of “exception” requests. Alternatively of system parts, products release with solutions. Designers devote more time promoting regularity than resolving customer issues.

Languages must be learned in our layout systems.

A pattern pronunciation is a comprehensive adaptation of a design system that maintains its core values while creating new patterns for particular circumstances. Languages maintain the state’s necessary language while expanding its vocabulary to fit various people, settings, or constraints, in contrast to one-off customizations or product themes.

When Perfect Consistency Is A Failure

I at Booking.com took this teaching without warning. Everything we A/B tested was color, version, button shapes, yet logo colors. I found this stunning as a specialist with a background in graphic design and company type guides. While people adored Airbnb’s flawless design program, Booking grew into a giant without ever taking into account physical consistency.

The conflict taught me things that persistence is not ROI, but rather solved problems are.

At Shopify Our crown jewel was Polyris ( ), a mature design language that worked well for laptop manufacturers. We were expected to follow Polaris as-is as a product staff. Then my realization group slammed an” Oh, Ship”! momentous as we had to create an app for inventory pickers using our program on shared, battered Android scanners in dark aisles, wearing heavy gloves, scanning dozens of items per second, some with only minimal English comprehension.

Task completion with the accepted Polaris of 0 %.

Every element that worked wonders for merchants entirely failed to work for pickers. Bright backgrounds produced brightness. Hand-held hands were made to look like 44px touch targets. Sentence-case brands took too long to interpret. Multi-step flows confused non-native listeners.

Polaris had to be completely abandoned, or we had to tell it inventory language.

The Birth of a Pronunciation

We favored development over trend. We created what we now refer to as a style pronunciation by adhering to Polaris’s core values of clarity, efficiency, consistency.

As a result, tasks have increased from 0 % to 100 % of the time. From three days to a single shift, onboard time has been decreased.

This was a dialect, not one of flexibility or theming; it was a rigorous translation that preserved Polaris ‘ core grammar while creating new words for a particular context. Polis had not failed; it had picked up the language of inventory.

The Flexibility Framework

Working on the Jira platform, which is a component of the larger Atlassian structure, I advocated formalizing this understanding at Atlassian. We needed organized flexibility because dozens of products shared a design language across various codebases, but we built our methods of working directly into our own. The outdated model, which required exception requests and unique approvals, was failing at scale.

To help manufacturers determine how flexible their elements should remain, we created the Flexibility Framework.

Every aspect was tied together during a transportation remodel. International search and logo remained steady. Croutons and cultural activities evolved into Flexible. Product teams could quickly identify areas where development was welcomed and where regularity was important.

The Decision Ladder

There must be boundaries for freedom. We built a straightforward staircase to determine when rules does obstruct:

Great: Include system parts that already exist. Quick, reliable, and reliable.

Better: somewhat stretch a part. Document the shift. Bring program improvements again for everyone to use.

Best to first design the best experience. Update the program to allow for user tests to verify the profit.

Which choice allows users to achieve the fastest? is the key question.

Laws are tools, not replicas.

Unity defeats consistency

Google, Drive, and Maps all speak with their own accent, but they are clearly Google. They achieve coherence through shared values rather than copied parts. About$ 30K in engineer time is spent on one additional month of box color debate.

Competency is a user outcome, while unification is a brand outcome. Part with the customer when the two fight.

Gates ‘ Gates’ Law:

How can symmetry be maintained while enabling languages? Treat your diction like a life dictionary:

Document every change, such as dialects or warehouses. director with explanations for the pictures and reasoning.

Promote shared designs: when three teams freely adopt a slang and assess its core inclusion.

Retire old idioms using flags and migration notes; this is never a big bang clean. Degrade with framework.

A living vocabulary performs better than a freezing handbook.

Your First Dialect: Start Small

Are you ready to start introducing accents? Start with a bad practice:

Get one user flow this week where great consistency prevents tasks from being completed. Users who use wireless devices might have issues with desktop-sized components or accessibility issues that their traditional patterns do not address.

What causes normal patterns to fail here? Document the context: economic restrictions person capabilities intensity of the process?

Design one consistent change: prioritize actions over looks. If gloves are the issue, bigger targets are actually serving the customer rather than “broken the method.” Create the adjustments and render them deliberate.

Assess and check: Does implementing the change make tasks more efficient? production at its peak? User pleasure

Display the savings: If that slang frees yet a second, fluency has paid for itself.

Beyond the Component Library

We’re cultivating style languages, never managing design systems anymore. language that develop along with their speakers. tones without losing any meaning in spoken language. language that prioritize the needs of people over visual ideals.

Our keys breaking the style guide didn’t matter, the warehouse personnel who went from 0 % to 100 % task execution didn’t care. They were concerned about how the keys turned out.

Your clients share your opinion. Offer your program permission to speak their speech.

The net of today is not always a welcoming area. Websites greet you with a popover that requires assent to their muffin coverage, and leave you with Taboola advertising promising” One Crazy Trick”! to treat your problems. Social media sites are tuned for wedding, and some things are more interesting than a duel. I’ve witnessed light war among birders now, and it seems like everyone wants to get into a fight.

These conflicts are often at conflict with a site’s targets. We don’t like those users to get into fights with one another if we are offering customer support and advice. If we offer information about the latest study, we want visitors to feel at ease, if we promote approaching marches, we want our core followers to feel comfortable and we want interested newcomers to experience welcome.

I looked at the origins of computer science in Vienna ( 1928-1934 ) for a case study of the significance of amiability in a research community and the disastrous effects of its demise in a study for a conference on the History of the Web. That story has interesting implications for web environments that promote amiable interaction among disparate, difficult ( and sometimes disagreeable ) people.

The Vienna Circle

Though people had been thinking about calculating engines and thinking machines from antiquity, Computing really got going in Depression-era Vienna. The people who developed the theory were interested in questioning the limits of reason in the absence of divine authority. They had no intention of creating machines. If we could not rely on God or Aristotle to tell us how to think, could we instead build arguments that were self-contained and demonstrably correct? Can we be certain that mathematics is accurate? Are there things that are true but that cannot be expressed in language?

The group known as the Vienna Circle held weekly meetings on Wednesdays at 6:00. They got together in the office of Professor Moritz Schlick at the University of Vienna to discuss problems in philosophy, math, and language. This Vienna department’s focus on the intersection of physics and philosophy had long been one of the most important achievements. Schlick’s colleague Hans Hahn was a central participant, and by 1928 Hahn brought along his graduate students Karl Menger and Kurt Gödel. Other notable speakers included philosopher Rudolf Carnap, psychologist Karl Popper, economist Ludwig von Mises ( brought by his brother Frederick, a physicist ), graphic designer Otto Neurath ( inventor of infographics ), and architect Josef Frank ( brought by his physicist brother, Phillip ). Out-of-town visitors often joined, including the young Johnny von Neumann, Alfred Tarski, and the irascible Ludwig Wittgenstein.

Participants adjourned to a nearby café for additional discussion with an even larger group of participants when Schlick’s office became too dim. This convivial circle was far from unique. The Austrian School of free-market economics was founded by an intersecting circle: Neurath, von Mises, and Oskar Morgenstern. There were theatrical circles ( Peter Lorre, Hedy Lamarr, Max Reinhardt ), and literary circles. Things actually happened in the café.

The interdisciplinarity of the group posed real challenges of temperament and understanding. Personalities were frequently difficult. Gödel was convinced people were trying to poison him. Josef Frank, an architect, relied on contracts for public housing, which Mises criticized as wasteful. Wittgenstein’s temper had lost him his job as a secondary school teacher, and for some of these years he maintained a detailed list of whom he was willing to meet. Neutrakh would yell” Metaphysics” to interrupt a speaker as he was eager to find muddled thought! The continuing amity of these meetings was facilitated by the personality of their leader, Moritz Schlick, who would be remembered as notably adept in keeping disagreements from becoming quarrels.

In the Café

The Viennese café of this era was long remembered as a particularly good place to argue with your friends, to read, and to write. With the collapse of the Empire, the cafés found themselves with too little space and fewer customers than they could have anticipated. There was no need to turn tables: a café could only survive by coaxing customers to linger. They might order another cup of coffee, or perhaps one of their friends might stop by. One could play chess, or billiards, or read newspapers from abroad. Coffee was frequently served with a glass of fresh spring water, which was a novelty in a time when most water was still considered unsafe to drink. That water glass would be refilled indefinitely.

The poet Jura Soyfer performed” The End Of The World,” a musical comedy about Professor Peep discovering a comet that is headed for earth in the basement of one cafe.

Prof. Peep: The comet is going to destroy everybody!

Hitler: It’s my business to destroy everyone.

Of course, coffee can be prepared in many ways, and the Viennese café developed a broad vocabulary to represent precisely how one preferred to drink it: melange, Einspänner, Brauner, Schwarzer, Kapuziner. The café was transformed into a warm and personal third space, a neutral ground where anyone who could afford a cup of coffee would be welcome due to the extensive customization and correspondingly esoteric conventions of service. Viennese of this era were fastidious in their use of personal titles, of which an abundance were in common use. Café waiters also gave regular customers titles, but they avoided using them to refer to their customers as a notch or two above what they deserved. A graduate student would be Doktor, an unpaid postdoc Professor. Because so many of the Circle’s members ( and so many other Viennese ) were from elsewhere: Carnap from Wuppertal, Gödel from Brno, von Neumann from Budapest, and so many others, this assurance was even more important. No one was going to make fun of your clothes, mannerisms, or accent. The pram in the hall wouldn’t bother your friends. Everyone shared a Germanic Austrian literary and philosophical culture, not least those whose ancestors had been Eastern European Jews who knew that culture well, having read all about it in books.

The café circle’s openness increased its friendliness. Because the circle sometimes extended to architects and actors, people could feel less constrained to admit shortfalls in their understanding. It was soon discovered that marble tabletops served as an improvised and accessible blackboard, making them a useful surface for pencil sketches.

Comedies like” The End Of The World” and fictional newspaper sketches or feuilletons of writers like Joseph Roth and Stefan Zweig served as a second defense against disagreeable or churlish behavior. It was certainly helped Professor Schlick stay on top of things when she was aware that a parody of one’s remarks might soon appear in Neue Freie Presse.

The End Of Red Vienna

Vienna’s city council had been Socialist, dedicated to public housing based on user-centered design, and supported ambitious programs of public outreach and adult education even though Austria’s government had drifted to the right after the War. In 1934 the Socialists lost a local election, and this era soon came to its end as the new administration focused on the imagined threat of the International Jewish Conspiracy. Von Neumann to Princeton, Neurath to Holland and Oxford, Popper to New Zealand, and Carnap to Chicago were the Circle’s most frequent members who left in less than a month. Prof. Schlick was murdered on the steps of the University by a student outraged by his former association with Jews. The author of” The End of the World,” Julia Soyfer, passed away in Buchenwald.

In 1939, von Neumann finally convinced Gödel to accept a job in Princeton. Gödel was required to pay significant fines before moving abroad. The officer in charge of these fees would look back on this as the best posting of his career, his name was Eichmann.

Design for Amiability

An impressive literature recounts those discussions and the environment that facilitated the development of computing. How can we create a comfortable environment? This is not just a matter of choosing rounded typefaces and a cheerful pastel palette. I think we might find eight distinct design constraints that work in usefully amiable ways.

Seriousness: The Vienna Circle was wrestling with a notoriously difficult book—Wittgenstein’s Tractus Logico-Philosophicus—and a catalog of outstanding open questions in mathematics. Instead of just making money off of debate, they were concerned with long-term issues. Constant reminders that the questions you are considering matter—not only that they are consequential or that those opposing you are scoundrels —help promote amity.

Empiricism: The Vienna Circle’s distinctive approach required that all knowledge be grounded in either direct observation or rigorous reasoning. Disagreement, when it arose, could be settled by observation or by proof. The situation couldn’t be resolved if neither appeared ready to help. On these terms, one can seldom if ever demolish an opposing argument, and trolling is pointless.

Abstraction: When a disagreement becomes unresolved, the argument escalates to a point where the opponent loses their face or their jobs. The Vienna Circle’s focus on theory—the limits of mathematics, the capability of language—promoted amity. Abstraction could have been merely academic without seriousness, but the limitations of reason and consistency of mathematics were obviously serious.

Formality: The punctilious demeanor of waiters and the elaborated rituals of coffee service helped to establish orderly attitudes amongst the argumentative participants. This contrasts with the contemptuous sneer that currently dominates social media.

Schlamperei: Members of the Vienna Circle maintained a global correspondence, and they knew their work was at the frontier of research. However, this was a dingy, frumpy, and old-fashioned Vienna on the edge of Europe. Many participants came from even more obscure backwaters. The majority or all of them harbored the suspicion that they were actually schleppers, and a tinge of the absurd aided in regulating tempers. The director of” The End Of The World” had to pass the hat for money to purchase a moon for the set, and thought it was funny enough to write up for publication.

Openness: Anyone could join in the discussion. There were many different kinds of people. Each week would bring different participants. Fluid borders lessen tension and give people the opportunity to expand the scope of discussion and terms of engagement. Low entrance friction was characteristic of the café: anyone could come, and if you came twice you were virtually a regular. Vienna’s cafés had no shortage of humorists, and permeable boundaries and café culture made it easier for moderating influences to draw in raconteurs and storytellers to defuse awkward moments. Openness counteracts the suspicion that promoters of amiability are exerting censorship.

Parody: The University of Chicago and the Café were unmistakably public areas. There were writers about, some of them renowned humorists. Discussion within bounds was kept from going into the possibility that one’s bad behavior or taste might be derided in print. The sanction of public humiliation, however, was itself made mild by the veneer of fiction, even if you got a little carried away and a character based on you made a splash in some newspaper fiction, it wasn’t the end of the world.

Engagement: Although the subject matter was significant to the participants, it was esoteric: neither their mothers nor their siblings were particularly interested in it. A small stumble or a minor humiliation could be shrugged off in ways that major media confrontations cannot.

I think it’s noteworthy that this setting was created to promote amiability among various voices. The café waiter flattered each newcomer and served everyone, and also kept out local pickpockets and drunks who would be mere disruptions. The discussion was kept moving and on topic thanks to Schipfl and other regulars. The fiction writers and raconteurs—perhaps the most peripheral of the participants—kept people in a good mood and reminded them that bad behavior could make anyone ridiculous. Each of these voices, naturally speaking, were human; you could understand that. Algorithmic or AI moderators, however clever, are seldom perceived as reasonable. No Moderator or central authority was present in the café circles, allowing everyone’s anger to be focused on her. Even after the disaster of 1934, what people remembered were those cheerful arguments.