# Web Strategy Published articles for Web Strategy. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Design for Amiability: Lessons from Vienna DevFeed: [Design for Amiability: Lessons from Vienna]() Original publisher: [Read original article]() Author: by Mark Bernstein Published: 2025-10-15T15:35:00Z Content type: article Language: en Sources: [A List Apart: The Full Feed]() Topics: [Web](), [Computer science](), [Math and Logic]() Tags: [community](), [community-industry-state-of-the-web-web-strategy](), [design](), [history](), [industry](), [math](), [research](), [state-of-the-web](), [web](), [web-strategy]() ### AI overview The article examines how amiable design can improve web environments and uses the Vienna Circle and the origins of computer science in Vienna as a historical case study. It connects the quality of interaction in research communities with the design of welcoming online spaces. ### Source excerpt Today's web is not always an amiable place. Sites greet you with a popover that demands assent to their cookie policy, and leave you with Taboola ads promising "One Weird Trick!" to cure your ailments. Social media sites are tuned for engagement, and few things are more engaging than a fight. Today it seems that people want to quarrel; I have seen flame wars among birders. These tensions are often at odds with a site's goals. If we are providing support and advice to customers, we don't want those customers to wrangle with each other. If we offer news about the latest research, we want readers to feel at ease; if we promote upcoming marches, we want our core supporters to feel comfortable and we want curious newcomers to feel welcome. In a study for a conference on the History of the Web, I looked to the origins of Computer Science in Vienna (1928-1934) for a case study of the importance of amiability in a research community and the disastrous consequences of its loss. That story has interesting implications for web environments that promote amiable interaction among disparate, difficult (and sometimes disagreeable) people. The Vienna Circle Though people had been thinking about calculating engines and thinking machines from antiquity, Computing really got going in Depression-era Vienna. The people who worked out the theory had no interest in building machines; they wanted to puzzle out the limits of reason in the absence of divine authority. If we could not rely on God or Aristotle to tell us how to think, could we instead build arguments that were self-contained and demonstrably correct? Can we be sure that mathematics is consistent? Are there things that are true but that cannot be expressed in language? The core ideas were worked out in the weekly meetings (Thursdays at 6) of a group remembered as the Vienna Circle. They got together in the office of Professor Moritz Schlick at the University of Vienna to discuss problems in philosophy, math, and language. The i ## Design Dialects: Breaking the Rules, Not the System DevFeed: [Design Dialects: Breaking the Rules, Not the System]() Original publisher: [Read original article]() Author: by Michel Ferreira Published: 2025-09-26T16:48:12Z Content type: article Language: en Sources: [A List Apart: The Full Feed]() Topics: [Web](), [systems]() Tags: [component](), [design](), [design-design-systems-web-strategy-workflow-tools](), [design-systems](), [systems](), [web](), [web-strategy](), [workflow-tools]() ### AI overview The article argues that design systems should function as living languages rather than rigid component libraries. It introduces design dialects: systematic adaptations that preserve core principles while allowing context-specific patterns, helping teams solve user problems without sacrificing the system's essential grammar. ### Source excerpt "Language is not merely a set of unrelated sounds, clauses, rules, and meanings; it is a totally coherent system bound to context and behavior." -- Kenneth L. Pike The web has accents. So should our design systems. Design Systems as Living Languages Design systems aren't component libraries--they're living languages. Tokens are phonemes, components are words, patterns are phrases, layouts are sentences. The conversations we build with users become the stories our products tell. But here's what we've forgotten: the more fluently a language is spoken, the more accents it can support without losing meaning. English in Scotland differs from English in Sydney, yet both are unmistakably English. The language adapts to context while preserving core meaning. This couldn't be more obvious to me, a Brazilian Portuguese speaker, who learned English with an American accent, and lives in Sydney. Our design systems must work the same way. Rigid adherence to visual rules creates brittle systems that break under contextual pressure. Fluent systems bend without breaking. Consistency becomes a prison The promise of design systems was simple: consistent components would accelerate development and unify experiences. But as systems matured and products grew more complex, that promise has become a prison. Teams file "exception" requests by the hundreds. Products launch with workarounds instead of system components. Designers spend more time defending consistency than solving user problems. Our design systems must learn to speak dialects. A design dialect is a systematic adaptation of a design system that maintains core principles while developing new patterns for specific contexts. Unlike one-off customizations or brand themes, dialects preserve the system's essential grammar while expanding its vocabulary to serve different users, environments, or constraints. When Perfect Consistency Fails At Booking.com, I learned this lesson the hard way. We A/B-tested everything--color, copy, button sh ## From Beta to Bedrock: Build Products that Stick. DevFeed: [From Beta to Bedrock: Build Products that Stick.]() Original publisher: [Read original article]() Author: by Liam Nugent Published: 2025-04-23T18:04:31Z Content type: article Language: en Sources: [A List Apart: The Full Feed]() Topics: [bedrock](), [Security]() Tags: [bedrock](), [business](), [business-industry-usability-user-experience-user-research-web-strategy](), [development](), [finance](), [industry](), [security](), [usability](), [user-experience](), [user-research](), [web-strategy]() ### AI overview The article argues that financial products should be built around a stable bedrock of clear customer value rather than an accumulation of features. It discusses the risks of feature-first development, the role of a Minimum Viable Product, and the need to resist internal pressures that can produce confusing, bloated experiences. ### Source excerpt As a product builder over too many years to mention, I've lost count of the number of times I've seen promising ideas go from zero to hero in a few weeks, only to fizzle out within months. Financial products, which is the field I work in, are no exception. With people's real hard-earned money on the line, user expectations running high, and a crowded market, it's tempting to throw as many features at the wall as possible and hope something sticks. But this approach is a recipe for disaster. Here's why: The pitfalls of feature-first development When you start building a financial product from the ground up, or are migrating existing customer journeys from paper or telephony channels onto online banking or mobile apps, it's easy to get caught up in the excitement of creating new features. You might think, "If I can just add one more thing that solves this particular user problem, they'll love me!" But what happens when you inevitably hit a roadblock because the narcs (your security team!) don't like it? When a hard-fought feature isn't as popular as you thought, or it breaks due to unforeseen complexity? This is where the concept of Minimum Viable Product (MVP) comes in. Jason Fried's book Getting Real and his podcast Rework often touch on this idea, even if he doesn't always call it that. An MVP is a product that provides just enough value to your users to keep them engaged, but not so much that it becomes overwhelming or difficult to maintain. It sounds like an easy concept but it requires a razor sharp eye, a ruthless edge and having the courage to stick by your opinion because it is easy to be seduced by "the Columbo Effect"... when there's always "just one more thing..." that someone wants to add. The problem with most finance apps, however, is that they often become a reflection of the internal politics of the business rather than an experience solely designed around the customer. This means that the focus is on delivering as many features and functionalities as pos ## The Wax and the Wane of the Web DevFeed: [The Wax and the Wane of the Web]() Original publisher: [Read original article]() Author: by Ste Grainer Published: 2024-02-29T14:45:00Z Content type: opinion Language: en Sources: [A List Apart: The Full Feed]() Topics: [Web Development]() Tags: [browsers](), [css](), [design](), [developers](), [hacks](), [state-of-the-web](), [state-of-the-web-web-strategy](), [web](), [web-standards](), [web-strategy]() ### AI overview A reflective article on the web's recurring shifts in design and development practices. It contrasts early table-based layouts, font tags, spacer GIFs, and CGI scripts with the rise of web standards and broader CSS adoption. ### Source excerpt I offer a single bit of advice to friends and family when they become new parents: When you start to think that you've got everything figured out, everything will change. Just as you start to get the hang of feedings, diapers, and regular naps, it's time for solid food, potty training, and overnight sleeping. When you figure those out, it's time for preschool and rare naps. The cycle goes on and on. The same applies for those of us working in design and development these days. Having worked on the web for almost three decades at this point, I've seen the regular wax and wane of ideas, techniques, and technologies. Each time that we as developers and designers get into a regular rhythm, some new idea or technology comes along to shake things up and remake our world. How we got here 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 birth of web standards At the turn of the century, a new cycle started. Crufty code littered with table layouts and font tags waned, and a push for web standards waxed. Newer technologies like CSS got more widespread adoption by browsers make ## Sustainable Web Design, An Excerpt DevFeed: [Sustainable Web Design, An Excerpt]() Original publisher: [Read original article]() Author: by Tom Greenwood Published: 2021-08-05T14:00:00Z Content type: article Language: en Sources: [A List Apart: The Full Feed]() Topics: [Web](), [web design](), [App](), [Benchmark]() Tags: [apps](), [benchmark](), [design](), [design-web-strategy](), [reduce](), [standards](), [tools](), [web](), [web-design](), [web-strategy]() ### AI overview This excerpt argues that establishing clear performance benchmarks can expand what developers believe is possible for websites. It introduces sustainable web design, noting that websites and apps lack broadly established environmental standards and that its primary goal is to reduce carbon emissions. ### Source excerpt In the 1950s, many in the elite running community had begun to believe it wasn't possible to run a mile in less than four minutes. Runners had been attempting it since the late 19th century and were beginning to draw the conclusion that the human body simply wasn't built for the task. But on May 6, 1956, Roger Bannister took everyone by surprise. It was a cold, wet day in Oxford, England--conditions no one expected to lend themselves to record-setting--and yet Bannister did just that, running a mile in 3:59.4 and becoming the first person in the record books to run a mile in under four minutes. This shift in the benchmark had profound effects; the world now knew that the four-minute mile was possible. Bannister's record lasted only forty-six days, when it was snatched away by Australian runner John Landy. Then a year later, three runners all beat the four-minute barrier together in the same race. Since then, over 1,400 runners have officially run a mile in under four minutes; the current record is 3:43.13, held by Moroccan athlete Hicham El Guerrouj. We achieve far more when we believe that something is possible, and we will believe it's possible only when we see someone else has already done it--and as with human running speed, so it is with what we believe are the hard limits for how a website needs to perform. Establishing standards for a sustainable web In most major industries, the key metrics of environmental performance are fairly well established, such as miles per gallon for cars or energy per square meter for homes. The tools and methods for calculating those metrics are standardized as well, which keeps everyone on the same page when doing environmental assessments. In the world of websites and apps, however, we aren't held to any particular environmental standards, and only recently have gained the tools and methods we need to even make an environmental assessment. The primary goal in sustainable web design is to reduce carbon emissions. However, it's almos