Blog

I have a creative side. Alchemy is what I do. It is a secret. I prefer to let it be done through me rather than through me.

I am imaginative. This brand is not appropriate for all creatives. No everyone see themselves in this manner. Some innovative persons incorporate technology into their work. That is their perception, and I regard it. Perhaps I have a little bit of fear for them. However, my thinking and being are unique.

Apologizing and qualifying in advance is a diversion. My head uses that to destroy me. I’ll leave it alone for today. I may regret and then qualify. after I’ve said what I should have. Which is too difficult.

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

Sometimes it does go that approach. 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 work and work and work until the thought strikes me. Maybe it arrives right away and I don’t remind people for three days. Sometimes I blurt out the plan so quickly that I didn’t stop myself. like a child who discovered a reward in a box of Cracker Jacks. I occasionally manage to get away with this. Yes, that is the best idea, but sometimes another persons disagree. The majority of the time, they don’t, and I regret that joy has faded.

Passion should only be saved for the meet, when it will matter. Certainly the informal get-together that comes before that meeting with two more discussions. Nothing understands why we hold these gatherings. We keep saying we’re getting rid of them, but we keep discovering new ways to get them. They occasionally yet excel. But occasionally they are a hindrance to the real job. Depending on what you do and where you do it, the ratio between when conferences are valuable and when they are a sad distraction vary. And who you are and how you go about doing it. I’ll go over it once more. I have a creative side. That is the style.

Often, a lot of hours of diligent and diligent work ends up with something that is barely useful. Maybe I have to take that and move on to the next task.

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

I am imaginative. I have no control over my desires. And I have no power over my best tips.

I may hammer apart 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 that has nothing to do with sizzling fuel and flowing pots. I may be making dinner. I frequently know what to do when I awaken. The idea that may have saved me disappears almost as frequently as I become aware and a part of the world once more as a senseless wind of oblivion. For imagination, 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 world, which they insist is true. But that is yet another diversion. And a miserable one. Possibly on a much bigger issue than whether or not I am creative. But that’s also a step backwards from what I’m trying to say.

Often the result is avoidance. And suffering. Do you know the designer who is tortured by the cliché? 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 offence intended. Your wisdom is also true. My needs are own, though.

Creatives identify artists.

Disadvantages are aware of cons, just like queers are aware of queers, just like real rappers are aware of genuine rappers are aware of cons. Designers are highly revered by people in the world. We revere, follow, and nearly deify the great types. Of course, it is horrible to revere any person. We’ve been given a warning. We are more knowledgeable. We are aware that people are really people. Because they are clay, like us, they squabble, they are depressed, they regret making the most important decisions, they are weak and hungry, they can be cruel, and they can be as ridiculous as we can. But. But. However, they produce this incredible issue. They give birth to something that may not occur without them and did not exist before them. They are the inspirations of thought. And I suppose I should add that they are the mother of technology because it’s just lying it. Bad mee backside! Okay, that’s all done. Continue.

Because we compare our personal small accomplishments to those of the great ones, designers denigrate them. Wonderful graphics I‘m not Miyazaki, though. That is glory right then. That is glory straight out of the mouth of God. This unsatisfied small factor I created? It essentially fell off the turnip truck’s up. The carrots weren’t actually new, either.

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

I am imaginative. In my hallucinations, my former artistic managers are the ones who judge me because I haven’t worked in advertising in 30 times. And they are correct to do so. When it really matters, my brain goes flat because I am too stupid and complacent. No medication is available to treat innovative function.

I am imaginative. Every project I create has a goal that makes Indiana Jones appear to be a retiree snoring in a deck 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 creative, those who have just been creative for a short while, and those who have just been creative for a short time in their careers. Only that I spend twice as long as they do putting the job of before I work ten times as quickly as they do. When I put my mind to it, I am so confident in my ability to do a great career. I have an addiction to the delay rush. I’m also so scared of jumping.

I don’t create anything.

I am imaginative. hardly a musician. Though as a child, I had a dream that I would one day become that. Some of us criticize our abilities and like our own selves because we are not Michelangelos and Warhols. That is narcissism, but at least we don’t practice politicians.

I am imaginative. 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 am imaginative. Every term I’ve said these may irritate another artists who see things differently. Ask a question to two artists, and three thoughts will be formed. Our dispute, our interest in it, and our responsibility to our own wisdom, at least in my opinion, are the proof that we are creative, no matter how we does think about it.

I am imaginative. I lament my lack of taste in almost all of the areas of human understanding, which I know very little about. And I put my preference before all other things in the areas that are most dear to my soul, or perhaps more precisely, to my passions. Without my passions, I may probably have to spend time staring living in the eye, which almost none of us can do for very long. No actually. No truly. Because a lot of living is intolerable if you really look at it.

I am imaginative. 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 am imaginative. I worry that my little product will disappear unexpectedly.

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

I am imaginative. I think method is the most amazing secret. I think it is so important that I’m actually foolish enough to publish an essay I wrote into a small machine without having to go through or edit it. I swear I didn’t accomplish this frequently. But I did it right away because I was even more scared of forgetting what I was saying because I was as worried as I might be of you seeing through my sad gestures toward the gorgeous.

There. I believe I’ve said it.

I’d like you to consider this a “yes … and” piece to complement Joe’s post. I’m not trying to reject any of what he’s saying, but rather to give some context to initiatives and options where AI may produce real, positive impacts on people with disabilities. To be clear, I’m not saying that there aren’t real challenges or pressing problems with AI that need to be addressed; there are, and we’ve needed to address them, like, yesterday; instead, I want to take a moment to talk about what’s possible so that we can find it one day.

Other text

Joe’s article spends a lot of time examining how computer vision models can create other word. 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 ( which should probably have descriptions ) and those that are purely decorative ( which might not even need a description ) either. However, I still think there’s possible in this area.

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

If we can specifically station a design to examine image usage in context, it might help us more quickly determine which images are likely to be elegant and which ones are likely to need a description. That will help 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 merely stated the chart’s name and the type of representation it was:” Pie chart comparing smartphone use to have phone usage in US households making under$ 30, 000 annually.” ( That would be a pretty bad alt text for a chart because it frequently leaves many unanswered questions about the data, but let’s just assume that was the description in place. ) If your website knew that that picture was a pie graph ( because an onboard model concluded this ), imagine a world where people could ask questions like these about the creative:

• 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?
• That number, how many?

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, where a model just makes up plausible-sounding “facts,” It could also be useful in educational contexts to help people who can see these charts, as is, to understand the data in the charts.

What if you could ask your browser to make a complicated chart simpler? What if you asked it to separate a single line from a line graph? What if you could ask your browser to transpose the colors of the different lines to work better for form of color blindness you have? What if you asked it to 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. For instance, it might be able to convert that pie chart (or, better yet, a number of pie charts ) into more usable ( and useful ) formats, like spreadsheets. That would be incredible!

Matching algorithms

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

Take Mentra, for example. They serve as a network of employment for people who are neurodivers. Based on more than 75 data points, they match job seekers with potential employers using an algorithm. On the job-seeker side of things, it considers each candidate’s strengths, their necessary and preferred workplace accommodations, environmental sensitivities, and so on. On the employer side, it takes into account each work environment, communication strategies for 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.

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

Imagine that a social media company’s recommendation engine was tuned to analyze who you’re following and if it was tuned to prioritize follow recommendations for people who talked about similar things but who were different in some key ways from your existing sphere of influence. For instance, if you followed a group of nondisabled white male academics who spoke about AI, it might be advisable to follow those who are disabled, aren’t white, or aren’t men who also speak about AI. If you followed its 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:

Voice preservation 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 is. Researchers like those in the Speech Accessibility Project are paying people with disabilities for their help in collecting recordings of people with atypical speech. As I type, they are actively recruiting people with Parkinson’s and related conditions, and they intend to expand this to other conditions as the project develops. More people with disabilities will be able to use voice assistants, dictation software, and voice-response services as a result of this research, which will result in more inclusive data sets that will enable them to use their computers and other devices more easily and with just their voices.
• Text transformation. The most recent generation of LLMs is 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

We must acknowledge the importance of our differences. 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. Stronger models can be created using inclusive data sets, which lead to more equitable outcomes.

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

Want a model that 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 soon replace human copy editors when it comes to sensitivity reading.

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

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

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 systems or idea 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 internet requirements

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

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

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

The web as software platform

The 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 shared package libraries, build automation, and collaborative version control. What was once primarily an environment for linked documents became a realm of infinite possibilities.

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

This fusion of potent mobile devices and potent development tools contributed to the growth of social media and other centralized tools for user interaction and consumption. As it became easier and more common to connect with others directly on Twitter, Facebook, and even Slack, the desire for hosted personal sites waned. Social media provided connections on a global scale, with both 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 recent 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 websites, from the tried-and-true classic of hosting plain HTML files to static site generators to content management systems of all kinds. The fracturing of social media also comes with a cost: we lose crucial infrastructure for discovery and connection. The IndieWeb‘s Webmentions, RSS, ActivityPub, and other tools can assist with this, but they’re still largely underdeveloped and difficult to use for the less geeky. We can build amazing personal websites and add to them regularly, but without discovery and connection, it can sometimes feel like we may as well be shouting into the void.

Especially with efforts like Interop, browser support for CSS, JavaScript, and other standards like web components has increased. New technologies gain support across the board in a fraction of the time that they used to. When I first learn about a new feature, I frequently discover that its coverage is already over 80 % when I check the browser support. 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 we upgrade and maintain these frameworks, we eventually pay the upfront costs that these frameworks may initially save in terms 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 frequently, when scripts fail ( whether due to poor code, network problems, or other environmental factors ), users are left with blank or broken pages.

Where do we go from here?

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

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

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

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

Play, experiment, and be weird! This website we created is the most incredible experiment. It’s the single largest human endeavor in history, and yet each of us can create our own pocket within it. Be brave and try something new. Build a playground for ideas. Create absurd experiments in your own crazy science lab. Start your own small business. There is no better place for being more creative, risk-taking, and expressing our creativity.

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

Make a move and make it happen.

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

The personalization space is true, between the dream of getting it right and the worry of it going wrong ( like when we encounter “persofails” similar to a company’s constant plea to regular people to purchase additional bathroom 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 bags rationally.

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

It’s known as prepersonalization.

Behind the song

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

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 personalization wagers? How do you design regular interactions that didn’t journey up users or—worse—breed mistrust? We’ve discovered that several budgeted programs foremost needed one or more workshops to join key stakeholders and domestic customers of the technology to justify their continuing investments. Make it matter.

We’ve witnessed the same evolution up near with our clients, from big tech to budding companies. In our experience with working on small and large personalization work, a program’s best monitor record—and its capacity to weather tough questions, work steadily toward shared answers, and manage its design and engineering efforts—turns on how successfully these prepersonalization activities play out.

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

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

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

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

Set the timer for your kitchen.

How long does it take to cook up a prepersonalization workshop? The evaluation activities that we suggest include can last for a number of weeks ( and frequently do ). 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 consists of making it possible for team members to individually present their own pilots, which each include a proof-of-concept project, business case, and operating model.

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

Kickstart: Apt your appetite

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

Give examples of connected experience interactions that you admire, find familiar, or even dislike, as examples of consumer and business-to-business examples. This should cover a representative range of personalization patterns, including automated app-based interactions ( such as onboarding sequences or wizards ), notifications, and recommenders. 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 ). We categorize connected experiences in our cards according to their functions, features, experiences, complete products, and portfolios. Size your own build here. This will help to draw attention to the benefits of ongoing investment as well as the difference between what you deliver right now and what you want to deliver in the future.

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

Each team member should decide where they would like to place your company’s emphasis on your product or service. Naturally, you can’t prioritize all of them. Here, the goal is to demonstrate how various departments may view their own advantages over the effort, which can be different 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 ensuring data and privacy is a major challenge too much? Do you have content metadata needs that you have to address? ( We’re pretty sure you do; it’s just a matter of recognizing the need’s magnitude and its solution. ) In our cards, we’ve noted a number of program risks, including common team dispositions. For instance, our Detractor card lists six protracted behavior that is harmful to the development of our country.

Effectively collaborating and managing expectations is critical to your success. Consider the potential obstacles to your progress in the future. Press the participants to name specific steps to overcome or mitigate those barriers in your organization. According to research, 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 ready 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.

The dishes will be made from recipes, which have predetermined ingredients.

Verify your ingredients

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

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 strategy 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 of a who-what-when-why

• Who are your key audience segments or groups?
• What kind of content will you provide for 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 there are still fresh possibilities. But they all follow an underlying who-what-when-why logic.

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

1. Nurture personalization: When a guest or an unknown visitor interacts with a product title, a banner or alert bar appears that makes it easier for them to encounter a related title they may want to read, saving them time.
2. Welcome automation: An email is sent when a new user registers 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. Beware of anyone who contradicts your advice. With that being said,” Complicated problems can be hard to solve, but they are addressable with rules and recipes“.

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

You can’t stand the heat, unquestionably…

Personalization technology opens a doorway into a confounding ocean of possible designs. Only a disciplined and highly collaborative approach will produce the necessary concentration and intention for success. So banish the dream kitchen. Instead, head to the test kitchen to save time, preserve job security, and avoid imagining the creative concepts that come from your organization’s masters. There are meals to serve and mouths to feed.

This organizational framework gives you a fighting chance at long-term success as well as solid ground. Wiring up your information layer isn’t an overnight affair. However, you’ll have solid ground for success if you use the same cookbook and the same recipes. We designed these activities to make your organization’s needs concrete and clear, long before the hazards pile up.

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

I’ve been fascinated by movies since I was a child. I loved the heroes and the excitement—but most of all the reports. I aspired to be an artist. And I believed that I’d get to do the things that Indiana Jones did and go on fascinating experiences. Yet my friends and I had movie ideas to make and sun in. But they never went any farther. However, I did end up in the user experience ( UX) field. Today, I realize that there’s an element of drama to UX— I hadn’t actually considered it before, but consumer research is story. And you must show a compelling story to entice stakeholders, such as the product team and decision-makers, to learn more in order to get the most out of consumer research.

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

Use story as a framework for conducting analysis

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

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

Act one: installation

The fundamental research comes in handy because the layout is all about understanding the background. Basic research ( also called relational, discovery, or preliminary research ) helps you understand people and identify their problems. You’re learning about the difficulties people face now, what options are available, and how those challenges impact them, just like in the films. To do basic research, you may conduct cultural inquiries or journal studies ( or both! ), which can assist you in identifying both prospects and issues. It doesn’t need to get a great investment in time or money.

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

This makes perfect sense to me. And I love that this makes consumer studies so visible. You don’t need to make a lot of paperwork; you can only attract people and do it! This can offer a wealth of knowledge about your customers, and it’ll help you better understand them and what’s going on in their life. That’s exactly what work one is all about: understanding where people are coming from.

Maybe Spool talks about the importance of basic research and how it may type the bulk of your research. If you can supplement what you’ve heard in the basic studies by using any more user data that you can obtain, such as surveys or analytics, to make recommendations that may need to be investigated further, you might as well use those that can be drawn from those that you can obtain. Together, all this information creates a clearer picture of the state of things and all its inadequacies. And that’s the start of a gripping tale. It’s the place in the story where you realize that the principal characters—or the people in this case—are facing issues that they need to conquer. This is where you begin to develop compassion for the characters and support their success, much like in films. And finally participants are now doing the same. Their business may lose money because users didn’t finish particular tasks, which may be their love. Or probably they do connect with people ‘ problems. In any case, action one serves as your main strategy to pique the interest and interest of the participants.

When partners begin to understand the value of basic research, that is open doors to more opportunities that involve users in the decision-making approach. And that can help goods team become more user-centric. This gains everyone—users, the goods, and partners. It’s similar to winning an Oscar for a film; it frequently results in a favorable reception and success for your item. And this can be an opportunity for participants to repeat this process with different products. The secret to this method is storytelling, and knowing how to tell a compelling story is the only way to entice participants to do more research.

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

Act two: fight

Act two is all about digging deeper into the issues that you identified in action one. This typically involves conducting vertical research, such as accessibility tests, where you evaluate a potential solution ( such as a design ) to see if it addresses the problems you identified. The issues may include unfulfilled needs or problems with a circulation or procedure that’s tripping users away. Additional problems will arise in the course of action two of a film. It’s here that you learn more about the figures as they grow and develop through this work.

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

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

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

If conducting usability testing in the field is like watching a play that is staged and controlled, where any two sessions may be very different from one another. You can take usability testing into the field by creating a replica of the space where users interact with the product and then conduct your research there. Or you can conduct your research by meeting users at their locations. With either option, you get to see how things work in context, things come up that wouldn’t have in a lab environment—and conversion can shift in entirely different directions. You have less control over how these sessions end as researchers, but this can occasionally help you understand users even better. Meeting users where they are can provide clues to the external forces that could be affecting how they use your product. Usability tests in person offer a level of detail that is frequently absent from remote testing.

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

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

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

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

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

Act three: resolution

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

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

Nancy Duarte in the Harvard Business Review offers an approach to structuring presentations that follow a persuasive story. The most effective presenters” set up a conflict that needs to be resolved” using the same methods as great storytellers, Duarte writes. ” That tension helps them persuade the audience to adopt a new mindset or behave differently”.

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

You can reinforce your recommendations with examples of things that competitors are doing that could address these issues or with examples where competitors are gaining an edge. Or they can be visual, like quick sketches of how a new design could function to solve a problem. These can help generate conversation and momentum. And this continues until the session is over when you’ve concluded by bridging the gaps and offering suggestions for improvement. This is the part where you reiterate the main themes or problems and what they mean for the product—the denouement of the story. This stage provides stakeholders with the next steps and, hoped, the motivation 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. The three-act structure of user research contains all the components for a good story:

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

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

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

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

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

I’ve lost count of the times I’ve watched promising thoughts go from zero to warrior in a few days before failing to deliver within weeks as a product developer for very long.

Financial items, which is the industry in which I work, 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 fatalities of feature-first growth

It’s simple 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 apps. They may believe,” If I may only add one more thing that solves this particular person problem, they’ll enjoy me”! What happens, however, when you eventually encounter a roadblock caused by your safety team? don’t like it? When a difficult-fought film fails to win over viewers or fails due to unanticipated difficulty?

The concept of Minimum Viable Product ( MVP ) comes into play in this area. Even if Jason Fried doesn’t usually refer to this concept, his book Getting Real and his audio Redo frequently discuss it. An MVP is a product that offers only enough significance to your users to keep them interested without becoming too hard or frustrating to use. Although the idea seems simple, it requires a razor-sharp eye, a ruthless edge, and the courage to stand up for your position because it is easy to fall for” the Columbo Effect” when there is always” just one more thing …” to add.

The issue with most fund apps is that they frequently turn out to be reflections of the company’s internal politics rather than an 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 item that really matters to customers. It serves as the foundation for the fundamental building block that creates price and maintains relevance over time.

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

The key is in identifying the main tasks that individuals want to complete and therefore persistently striving to make them simple, reliable, and trustworthy.

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

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

Functional methods for creating financially successful items

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

1. What issue are you attempting to resolve first, and why? For whom? Before beginning any construction, make sure your vision is completely clear. Make certain it also aligns with the goals of your business.
2. Avoid the temptation to put too many characteristics at once and focus on getting that right first. Choose one that actually adds price, and work from that.
3. When it comes to financial goods, clarity is often more important than difficulty. Eliminate unwanted details and concentrate solely on what matters most.
4. Accept constant iteration as Bedrock is a powerful process rather than a fixed destination. Continuously collect customer opinions, make product improvements, and advance in that direction.
5. Halt, look, and listen: You don’t just have to test your product during the delivery process; you must also test it frequently in the field. Use it for yourself. Move the A/B testing. User opinions on Gear. Speak to the users of it and make adjustments accordingly.

The “bedrock conundrum”

This is an intriguing conundrum: sacrificing some of the potential for short-term progress in favor of long-term stability is at play. But the reward is worthwhile because products built with a focus on rock will outlive and surpass their rivals over time and provide users with long-term value.

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

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

This is the lovely, sometimes messy fact of having both a Design Manager and a Guide Designer on the same group. And 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 clear traces on an organizational chart. The Design Manager handles persons, the Lead Designer handles art. Problem is fixed, isn’t it? Except that clear com charts are fantasy. In fact, both roles care greatly about crew health, style quality, and shipping great work.

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

The biology of a good design team

Here’s what I’ve learned from years of being on both sides of this formula: consider of your design team as a living organism. The layout manager is guided by the group dynamics, emotional security, and career growth. The Lead Designer is more focused on the body ( the user-generated design standards, the handcrafted skills ), than the hands-on work that is done.

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

When we look at how good team really function, three critical devices emerge. Each requires the collaboration of both jobs, but one must assume the lead role in maintaining that system sturdy.

Individuals & Psychology: The Nervous System

Major caretaker: Design Manager
Supporting duties: Guide Custom

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 state, making sure feedback loops are good, and creating the environment for growth. They’re hosting job meetings, managing task, and making sure no single burns out.

However, a significant enabling role is played by the Lead Designer. They’re offering visual feedback on build development requirements, identifying stagnant design skills, and assisting with the design manager’s potential growth opportunities.

Design Manager tends to:

• development planning and job conversations
• mental stability and dynamics of the group
• Job management and resource planning
• Performance evaluations and opinions mechanisms
• Providing learning options

Direct Custom supports by:

• Providing craft-specific evaluation of team member creation
• identifying opportunities for growth and style talent gaps
• Providing style mentorship and assistance
• indicating when staff people are prepared for more challenging problems.

The Muscular System: Design & Execution

Major custodian: Lead Designer
Supporting position: Design Manager

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

The Lead Designer is in charge of everything here. They are establishing design standards, offering craft instruction, and making sure that shipping work meets the required standards. They’re the ones who can tell you if a design decision is sound or if we’re solving the right problem.

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

Lead Designer tends to:

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

Design Manager supports by:

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

The Circulatory System: Strategy &amp, Flow

Both the lead designer and the design manager were caretakers.

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.

True partnership occurs in this context. Although both roles are responsible for keeping the circulation strong, they both bring in different viewpoints.

Lead Designer contributes:

• User requirements are satisfied with the finished product
• 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
• Management of stakeholders and alignment
• Inter-functional team accountability
• Strategic business initiatives

Both parties work together on:

• Co-creation of strategy with 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 work hard on the wrong things.

Be Specific About the System You’re Defending.

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

This is not about staying in your 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 wholesome 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.”

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

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 specific craft execution ( muscular system ).

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

Stay curious and not territorial.

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

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

When the Organism Gets Sick

Even with clear roles, this partnership can go wrong. What 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 only concentrates on the muscular system. Both people retreat to their comfort zones and stop collaborating.

The signs: Team members receive conflicting messages, work conditions suffer, and morale declines.

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

Poor Circulation

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

The signs: 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

The other person’s expertise makes them feel threatened. 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 sucked into the middle.

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

The Payoff

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

The best of both worlds can be found in the combination of strong people leadership and deep craft expertise. When one person is ill, taking a vacation, or overburdened, the other can support the team’s health. When a decision requires both the people perspective and the craft perspective, you’ve got both right there in the room.

The framework has a balance, which is crucial. You can apply the same system thinking to fresh challenges as your team expands. Need to launch a design system? Both the muscular system and the nervous system are more prevalent in the work environment and communication, and the design manager is more focused on the implementation and change management.

Bottom Line

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

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

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

Ninjas have a certain awesome quality, whether it’s in movies or on television. That charm has undoubtedly persisted in the video game industry since its inception. Whether it’s the numerous ninja soldiers in Mortal Kombat and Dead or Alive or the numerous hack-and-slash game featuring warrior characters and the dark fighting designer […]…

The first article on Den of Geek was The Best Ninja Video Games Ranked.

Robert Redford did become remembered as a cherished professional from the New Hollywood time now that he has been informed that he passed away at the age of 89. Although obituaries may be accurate in describing Redford’s beautiful screen presence, dedication to intriguing roles, and contributions to separate cinema, they perhaps overlook an unanticipated and forgotten fact about him: that he was not generally regarded as an actor. He was criticized as very attractive by people of the &#8217, 60s, and &#8217, 70s, a position frequently held by the renowned irreverent and prominent writer Pauline Kael.

We are able to identify Redford as a classic film actor who knew how to use his attractive on-screen image to create powerful figures now. His insecure movies All the President&#8217, s Men and Three Days of the Condor employ his attraction to give the anxiety a new lease of life. His operate alongside Paul Newman in Butch Cassidy and the Sundance Kid and The Sting is hailed as an example of the late-’60s design. Yet the part that is well-known to younger people in Captain America: The Winter Soldier, a clip featuring him nodding in assent in 1972&#8217, s Jeremiah Johnson, demonstrates his acting prowess.

One of his best appearances is overlooked throughout this job review. In the 1992 drama Clothing, Redford excels among an outfit cast of oddballs, which is where they are.

A Charming Snippet

After a cold opening, Sneakers begins with a group of professional thieves attempting to pull off a bank heist. It depicts activist hacker Martin Brice ( portrayed by Twin Peaks &#8216, Gary Hershberger in the past ). A tightly-wound former CIA agent ( Sidney Poitier ), a blind telecommunications specialist ( David Strathairn ), a young, idealistic hacker ( River Phoenix ), and a conspiracy-minded technician ( Dan Aykroyd ) are the sequence’s main characters. A sizable sum of money is later transferred into Martin’s account as he is older and now referred to as Martin Bishop ( Redford ).

The final scene’s return highlights Redford’s acting prowess. Director Phil Alden Robinson travels to the following morning to finish the attack, where Bishop is closing his bank accounts and receiving the enormous sum he transferred in dollars. In a single, continuous chance, we watch as Martin accepts the charges, passes a security guard, and travels up a table space where he returns the funds to waiting professionals and assesses the institution’s safety procedures.

As a secretary in the next scene says,” People hire you to break into their places… make sure no one can break into their places,” as she writes as she fills out a check as legal payment for Martin &#8217, s services, &#8220, as she writes in the next scene. &#8221,

The magic of the scene is heightened by Redford’s slightly embarrassed shrug when Martin responds, &#8220, It&#8217, s a living. Redford has played Martin as calm and collected up until that point. Martin is even keeled and cool, whereas the rest of his team is either prattling on about covert assassinations or letting their nerves rule them. When he tells a teller inquiring about his decision to close his account that he” just doesn’t feel safe” with that bank, he betrays nothing, and he continues to be confident in his appeal when he demands payment before providing further analysis.

However, when the secretary points out the absurdity of his job and when she makes a buck about how little he gets paid, Martin starts to feel shaky, and Redford reveals a drop in confidence in his performance. He opens his mouth in defense, as if he knew a man so handsome and fashionable ought to make a comeback, but he walks away silently, his jaw still sagging.

Redford shrugs off the romance of Martin as a 90s hacker in that moment. Redford instead permits him to be a human.

acting human

Sneakers are driven by Redford’s ability to juggle Hollywood charisma with human vulnerability. Following its debut with a place-setting opening, Sneakers follows Martin&#8217’s team as they are re-coerced by what appear to be NSA agents to steal a brilliant mathematician ( Donal Logue, when he could be cast against type ) from a brilliant mathematician ( Dan Logue ). The team attempts their goal by getting drawn further into post-Cold War intrigue and coming face-to-face with a surprising mastermind ( Ben Kingsley ), along with assistance from Martin&#8217, his sometime girlfriend Liz ( Mary McDonnell ).

Some people complained that Redford was being asked to play in his beats from his 1970s paranoid films because Sneakers didn’t challenge him. With two decades of experience on him, Redford was even better suited to strike a balance between his charisma and humanity. Reddy’s ability to ground Bishop and his wacky pals made Sneakers stand out even more as the era’s thrillers grew more slick, with big stakes and fancy technology ( Enemy of the State, Mission: Impossible, The Long Kiss Goodnight ), made slickness of the era and rediscoverability, making his slickness make Sneakers stand out even more.

Sneakers keep insisting that Martin is fundamentally a good man against strong forces, that he has remarkable hacking skills, and that he&#8217 is fundamentally a good man against strong forces. And Redford is able to show off those admirable qualities. However, Redford manages to keep Martin human throughout the movie by slightly lowering his shoulders when Liz reminds him of how badly his relationship with Liz turned out, and by tightening his jaw as he tries to decide whether his friends will accept a risky job that will clear his record.

Robert Redford was a movie star, remarkably handsome, and blessed with endless charisma, as Sneakers repeatedly demonstrates. However, Sneakers also demonstrates that Redford was a decent actor who could remain a human even when portrayed as an idol. By pairing him with oddball character actors and having him play a real person in a heightened story.

The first post Sneakers Remains Robert Redford&#8217, s Most Underappreciated Performance appeared on Den of Geek.

Has the Dark Knight grown very black? If a recent report on pop culture changes for the next generation is any indication, the truth may be sure. Another good question for kids might be,” Who’s Batman once?” According to a recent scientific poll, Gen Alpha ( children born between 2010 and 2025 ) surprisingly enjoy going [ …].

The article Have We Forgotten Batman Is for Children’s Use? second appeared on Den of Geek.

Robert Redford, 89, will be remembered as a cherished professional from the New Hollywood time now that he has been informed of his passing. Although obituaries may be accurate in describing his magnificent display presence, interest in intriguing roles, and contributions to separate cinema, they may ignore a shocking and oft-forgotten fact about Redford: he was not always regarded as an actor. He was criticized as very attractive by people of the &#8217, 60s, and &#8217, 70s, a position frequently held by Pauline Kael, a reportedly irreverent and influenteer.

Today, Redford is regarded as a classic film star who knew how to use his attractive on-screen image to generate powerful characters. His insecure movies All the President&#8217, s Men and Three Days of the Condor employ his attraction to give the anxiety a new lease of life. His operate alongside Paul Newman in Butch Cassidy and the Sundance Kid and The Sting is hailed as an example of the late-’60s design. Yet the part that most younger people are familiar with—no, not playing a HYDRA adviser in Captain America: The Winter Soldier, but the clip of him nodding in assent in 1972&#8217, s Jeremiah Johnson, demonstrates his ability to command the camera.

One of his best appearances, however, is overlooked throughout this job review. In the 1992 drama Clothing, Redford excels among an outfit cast of oddballs, which is where they are.

A Charming Snippet

Sneakers begins with a group of professional thieves pulling off a bank heist following a cold open showing how activist hacker Martin Brice ( portrayed by Twin Peaks &#8216, s Gary Hershberger in the past ) was nearly captured by police in 1969. A tightly-wound former CIA agent ( Sidney Poitier ), a blind telecommunications specialist ( David Strathairn ), a young, idealistic hacker ( River Phoenix ), and a conspiracy-minded technician ( Dan Aykroyd ) are the sequence’s main characters. The heist ends with Martin, who is now known as Martin Bishop ( Redford ), depositing a sizable sum of money into his account.

The reward of the scene demonstrates Redford’s acting prowess. Director Phil Alden Robinson travels to the following morning to finish the attack, where Bishop is closing his bank accounts and receiving the enormous sum he transferred in dollars. We watch as Martin accepts the charges, passes a security guard, and travels to a table room where he returns the funds to the waiting managers and assesses the institution’s safety procedures in a single, uninterrupted shot.

As a secretary in the next scene says,” People hire you to break into their places… make sure no one can break into their places,” as she writes as she fills out a check as legal payment for Martin&#8217, s services, &#8220, as she writes in the next scene. &#8221,

The moment’s magic is captured in the scene when Redford pulls a slightly embarrassed shrug when Martin responds, “It’s a living. Redford has played Martin as calm and collected up until that point. Martin is even keeled and cool, even when the rest of his team is either prattling on about secret assassinations or letting their nerves take over. When he tells a teller inquiring about his decision to close his account that he simply doesn’t feel safe with that bank, he betrays nothing, and he maintains his confidence in his appeal even after demanding payment before providing further analysis.

However, when the secretary points out the absurdity of his job and when she makes a buck about how little he gets paid, Martin starts to feel shaky, and Redford reveals a drop in confidence in his performance. He opens his mouth in rebuttal, as if he knew a person so attractive and cool ought to have a comeback, but he walks away without saying anything, his jaw still slack.

Redford shrugs off the romance of Martin as a 90s hacker in that situation. Redford permits him to be a human, not the opposite.

acting human

Sneakers are driven by Redford’s ability to juggle Hollywood charisma with human vulnerability. Following its debut with a place-setting opening, Sneakers follows Martin&#8217’s team as they are re-coerced by what appear to be NSA agents to steal a brilliant mathematician ( Donal Logue, when he could be cast against type ) from a brilliant mathematician ( Dan Logue ). The team attempts their goal by getting drawn further into post-Cold War intrigue and coming face-to-face with a surprising mastermind ( Ben Kingsley ), along with assistance from Martin&#8217, his sometime girlfriend Liz ( Mary McDonnell ).

Some people at the time criticized Sneakers for failing to challenge Redford and for asking him to repeat beats from his &#8217, 70s paranoid films. With two decades of experience on him, Redford was even better suited to strike a balance between his charisma and humanity. Reddy’s ability to ground Bishop and his wacky pals made Sneakers stand out even more as the era’s thrillers grew more slick, with high stakes and fancy technology ( Enemy of the State, Mission: Impossible, The Long Kiss Goodnight, etc. ).

Sneakers keep insisting that Martin is fundamentally a good man who can defeat strong opponents and that he has remarkable hacking abilities. Redford can also exhibit those admirable qualities. However, Redford discovers ways to keep Martin human throughout the movie, such as the slight sagging in his shoulders when Liz reminds him of how badly his relationship with Liz and the tightening in his jaw as he ponders whether his friends will accept a risky job that would clear his record, and the slight inclination to accept his identity once he realizes the mastermind&#8217.

Robert Redford was a movie star, remarkably handsome, and blessed with endless charisma, as Sneakers repeatedly demonstrates. However, Sneakers also demonstrates that Redford was a decent actor who could remain a human even when portrayed on screen by pairing him with oddball character actors and having him play a real person in a heightened story.

The first post Sneakers Remains Robert Redford&#8217, s Most Underappreciated Performance appeared on Den of Geek.

Robert Redford, 89, will be remembered as a cherished professional from the New Hollywood time now that he has been informed of his passing. While obituaries may be accurate in describing Redford’s beautiful screen presence, dedication to intriguing roles, and contributions to separate cinema, they may neglect a shocking and frequently forgotten fact: […]

The second article Shoes Remains Robert Redford’s Most Underappreciated Performance appeared on Den of Geek.

Robert Redford, 89, will be remembered as a cherished professional from the New Hollywood time now that he has been informed of his passing. Although obituaries may be accurate in describing Redford’s magnificent display presence, dedication to intriguing roles, and contributions to separate cinema, they may ignore a shocking and oft-forgotten fact about him: that he was not generally regarded as an actor. He was criticized as very attractive by people of the &#8217, 60s, and &#8217, 70s, a position frequently held by the renowned irreverent and prominent writer Pauline Kael.

Today, we all recognize Redford as a classic movie celebrity who knew how to use his dazzling on-screen image to make powerful characters. His insecure movies All the President&#8217, s Men and Three Days of the Condor employ his attraction to give the anxiety a new lease of life. His operate alongside Paul Newman in Butch Cassidy and the Sundance Kid and The Sting is hailed as an example of the late-’60s design. Even the part that most younger audiences are familiar with—no, not playing a HYDRA agent in Captain America: The Winter Soldier, but the gif of him nodding in approval in 1972&#8217, s Jeremiah Johnson, demonstrates his ability to command the screen.

One of his best performances is overlooked throughout this career review. In the 1992 thriller Sneakers, Redford excels among an ensemble cast of oddballs, which is where they are.

A Charming Snippet

Sneakers begins with a group of professional thieves pulling off a bank heist following a cold open showing how activist hacker Martin Brice ( portrayed by Twin Peaks &#8216, s Gary Hershberger in the past ) was nearly captured by police in 1969. A tightly-wound former CIA agent ( Sidney Poitier ), a blind telecommunications specialist ( David Strathairn ), a young and idealistic hacker ( River Phoenix ), and a conspiracy-minded technician ( Dan Aykroyd ) are the characters in the sequence. The heist ends with Martin, who is now known as Martin Bishop ( Redford ), depositing a sizable sum of money into his account.

The final scene’s payoff highlights Redford’s acting prowess. After the heist is over, director Phil Alden Robinson, who co-wrote the script with Lawrence Lasker and Walter Parkes, heads to the next day, where Bishop is closing his bank account and receiving the enormous sum he transferred in cash. In a single, unbroken shot, we watch as Martin accepts the bills, passes a security guard, and travels up a board room where he returns the funds to waiting executives and assesses the institution’s security procedures.

As a secretary in the next scene says,” People hire you to break into their places… to make sure no one can break into their places,” as she writes in the next scene. &#8221,

When Martin responds,” It’s a living, It’s a living,” Redford pulls a slightly embarrassed shrug from the scene to add magic. Redford has played Martin as calm and collected up until that point. Martin is even keeled and cool, whereas the rest of his team is either prattling on about covert assassinations or letting their nerves rule them. When he tells a teller inquiring about his decision to close his account that he” just doesn’t feel safe” with that bank, he betrays nothing, and he continues to be confident in his appeal when he demands payment before providing further analysis.

However, when the secretary makes a comedic comment about how little money he gets paid, Martin starts to feel shaky, and Redford reveals a drop in confidence in his performance. He opens his mouth in defense, as if he knew a man so handsome and fashionable ought to make a comeback, but he walks away silently, his jaw still sagging.

Redford dismisses Martin’s romantic relationship as awesome and a 90s hacker in that situation. Redford permits him to be a human, not the other way around.

Acting Human

Redford’s ability to juggle Hollywood charisma with human vulnerability is what motivates Sneakers. Following its debut with a place-setting opening, Sneakers follows Martin&#8217’s team as they are re-coerced by what appear to be NSA agents to steal a brilliant mathematician ( Donal Logue, when he could be cast against type ) from a brilliant mathematician ( Dan Logue ). The team attempts their goal by duping a gullible scientist ( Stephen Tobolowsky ), getting drawn further into post-Cold War intrigue, and coming face-to-face with a surprising mastermind ( Ben Kingsley ), along with assistance from Martin&#8217, s sometime girlfriend Liz ( Mary McDonnell ).

Some people complained that Redford was being asked to play in his beats from his 1970s paranoid films because Sneakers didn’t challenge him. With two decades of experience on him, Redford was even better suited to strike a balance between his charisma and humanity. Reddy’s ability to ground Bishop and his wacky pals made Sneakers stand out even more as the era’s thrillers grew more slick, with big stakes and fancy technology ( Enemy of the State, Mission: Impossible, The Long Kiss Goodnight ), made slickness of the era and rediscoverability, making his slickness make Sneakers stand out even more.

Sneakers keep insisting that Martin is fundamentally a good man against strong forces and that he has remarkable hacking abilities. Redford can also exhibit those admirable qualities. However, Redford manages to keep Martin human throughout the movie by slightly lowering his shoulders when Liz reminds him of how badly his relationship with Liz turned out, and by tightening his jaw as he tries to decide whether his friends will accept a risky job that will clear his record.

Robert Redford was a movie star, remarkably handsome, and enamored of endless charisma, as Sneakers repeatedly demonstrates. However, Sneakers also demonstrates that Redford was a decent actor who could remain a human even when portrayed on screen by pairing him with oddball character actors and having him play a real person in a heightened story.

The post Den of Geek‘s Sneakers Remains Robert Redford’s Most Underappreciated Performance first appeared.