# experience design Published articles for experience design. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How You as a Lone Designer Can Change the World DevFeed: [How You as a Lone Designer Can Change the World]() Original publisher: [Read original article]() Author: Rikke Friis Dam Published: 2026-08-13T14:00:00Z Content type: article Language: en Sources: [UX Daily - User Experience Daily]() Topics: [User Experience](), [User experience (UX)]() Tags: [design](), [experience-design](), [interaction-design](), [learn](), [skills](), [user-experience](), [user-experience-design](), [ux](), [ux-design]() ### AI overview This video article explains how lone designers can use their design expertise to address major societal issues. Don Norman recommends joining organizations already working on these issues, gaining authority within an existing company, or joining a legally structured corporation such as a B Corp. ### Source excerpt Has Don Norman convinced you to work on important societal issues? As a lone designer, what can you do? If you are a new designer who has just graduated from design school, an experienced designer, or a designer who would like to shift your company's path toward helping the world, there are ways to make these things happen. In this video, Don shares his wisdom on how you can accomplish it by joining an organization or company that is already working on these issues, by gaining authority in your current company, or by joining a type of corporation--such as a "b-corp" in the US--that is actually set up legally to address some important societal issues. "If you want to work on the major societal... ## The 4 Types of Designers Who Will Thrive in 2030 (And the One Most Schools Still Ignore) DevFeed: [The 4 Types of Designers Who Will Thrive in 2030 (And the One Most Schools Still Ignore)]() Original publisher: [Read original article]() Author: Rikke Friis Dam Published: 2026-08-13T14:00:00Z Content type: article Language: en Sources: [UX Daily - User Experience Daily]() Topics: [user experience design](), [User Experience]() Tags: [design](), [education](), [experience-design](), [user-experience]() ### AI overview Don Norman outlines four kinds of design challenges that designers may face in the 21st century and the skills needed to address them. The article presents design as a way of thinking that can help tackle complex societal issues, while also describing performance and systemic challenges. ### Source excerpt What is the future of design? Which skills will you need in the 21st century? In this video, Don Norman gives four examples of the tasks that designers might be doing in the 21st century, and the four types of designers that will be needed."So there you are. Four different kinds of design problems, each of them requiring different skills and different change from the traditional design of designers of craft."-- Don Norman: Father of User Experience design, author of the legendary book The Design of Everyday Things, co-founder of the Nielsen Norman Group, and former VP of the Advanced Technology Group at Apple.Don Norman is trying to mobilize the current and next generations of designers to us... ## The End of Prompting: Why the Future of AI Experience Design Is Constraint-First DevFeed: [The End of Prompting: Why the Future of AI Experience Design Is Constraint-First]() Original publisher: [Read original article]() Author: Yves Binda Published: 2026-04-17T04:57:58Z Content type: opinion Language: en Sources: [UX Magazine]() Topics: [User experience (UX)](), [Artificial Intelligence](), [Prompt Engineering](), [Language models]() Tags: [ai](), [experience-design](), [interface](), [prompting](), [systems](), [ux]() ### AI overview This commentary argues that prompting should not be treated as the primary interface or design philosophy for AI systems. It presents constraint-first design--embedding verification, scope boundaries, and escalation paths into system architecture--as a more reliable approach for high-stakes and regulated workflows, because authoritative-sounding language does not guarantee accuracy or compliance. ### Source excerpt There is a point in each technology cycle when the workaround turns into the product. We saw it when spreadsheets displaced paper ledgers and then became the planning tool. Emails supplanted memos, which then became the management layer. And now we're watching that happen with prompting. Prompting was never meant to be the interface. It The post The End of Prompting: Why the Future of AI Experience Design Is Constraint-First appeared first on UX Magazine. ## What they're not teaching in design class--and what you can do about it DevFeed: [What they're not teaching in design class--and what you can do about it]() Original publisher: [Read original article]() Author: Michelle Liu; Valerie Wong Published: 2025-06-12T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [User Experience](), [user experience design](), [Microsoft](), [Netflix]() Tags: [business](), [community](), [customer](), [design](), [education](), [experience-design](), [figma](), [management](), [microsoft](), [netflix](), [product](), [product-design](), [product-sense]() ### AI overview The article argues that design education often underemphasizes business fundamentals. Figma Campus Leaders explain that designers need business fluency and product sense to connect user experience, stakeholder needs, and creative decisions to tangible business outcomes. ### Source excerpt Designers don't just shape experiences--they shape businesses. But with so many design programs lacking in business fundamentals, these Figma Campus Leaders argue that students should go extracurricular. ## Why cultivating a prototyping culture will help you build better products DevFeed: [Why cultivating a prototyping culture will help you build better products]() Original publisher: [Read original article]() Author: Nikolas Klein; Garrett Miller Published: 2023-12-08T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [ide]() Tags: [design](), [development](), [experience-design](), [experimentation](), [figma](), [innovation](), [product-development](), [prototyping](), [user-testing](), [workflow]() ### AI overview The article explains how cultivating a prototyping culture improves product development. Interactive prototypes help teams identify navigation and usability issues early, test and validate ideas rapidly, save engineering time, streamline workflows, and help designers communicate proposals and gain organizational support. ### Source excerpt Prototyping, once an eleventh-hour nice-to-have, has risen to become a critical tool at multiple points in the product development workflow. ## FIT's principles for fostering a collaborative classroom DevFeed: [FIT's principles for fostering a collaborative classroom]() Original publisher: [Read original article]() Author: Miggi Cardona Published: 2021-08-25T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [user experience design]() Tags: [best-practices](), [collaboration](), [design](), [digital-design](), [experience-design](), [figma](), [projects](), [skills](), [ui](), [user-experience](), [user-experience-design](), [workflows]() ### AI overview Professors at the Fashion Institute of Technology share principles for creating a collaborative virtual classroom in Figma. The article describes organizing courses into teams, projects, and files while encouraging open feedback and the development of design skills. ### Source excerpt Best practices from professors at the Fashion Institute of Technology on how to construct a virtual classroom in Figma. ## Human-centered Software Development DevFeed: [Human-centered Software Development]() Original publisher: [Read original article]() Author: Headspace Published: 2021-05-27T20:52:21Z Content type: opinion Language: en Sources: [Stories by Headspace on Medium]() Topics: [Development](), [User Experience](), [Software Engineering](), [interfaces](), [Code](), [App]() Tags: [developers](), [development](), [end-user-experience](), [engineering](), [experience-design](), [interfaces](), [software](), [software-development](), [software-engineer](), [user-experience](), [user-experience-design]() ### AI overview The article argues that software development should be human-centered because developers are users of the code and systems they build. It applies user-experience principles to the development process, emphasizing code readability, maintainability, and attention to engineers' human factors. ### Source excerpt Build stronger software by designing for human interaction Author: Edward Park, Senior Software Engineer Creating software is a human-centered endeavor. The software that we build is used directly by human users. Whether we're building a mobile application, service, or tool, the cumulative moments of delight (or abhorrence) that our human users experience determine the efficacy of the software we build. For this reason, software organizations invest in user experience design, in addition to the nuts-and-bolts of the technology under the hood. Product designers leverage their expertise in interaction psychology to create user flows that are useful, familiar, and discoverable. Designers understand that application interfaces are only as effective as their users find them to be useful. Therefore, the best user experiences incorporate visual components that facilitate task completion while working with the psychological heuristics that humans intuitively employ. Humans seek sensory cues and constraints to navigate a deluge of stimuli and process large amounts of information, and we do so while interacting with computing interfaces as well as the real world. In essence, software organizations are constantly trying to optimize how humans interact with computers. Today, the practice of using design to hone user experience is predominantly applied to visual interfaces. These are commonly the front ends of applications, where humans interact with the visually rendered software (in a browser or mobile app). What about the act of software development itself? OUR FELLOW DEVELOPERS ARE USERS, TOO Most observers would think that software development strives to translate human instructions into machine-understandable directives in a reductive, one-way communication flow. We are "programming" computers to do our bidding, and we do so with cold, logical artifacts composed of code modules. While the software itself is mostly evaluated against human experiences, we compartmentalize th