Here are the adoption curves for a handful of major technologies in the United States. There are big differences in the speeds at which these technologies were absorbed. Landline telephones took about 86 years to hit 80% adoption.Flush toilets took 96 years to hit 80% adoption.Refrigerators took about 25 years.Microwaves took 17 years.Smartphones took just 12 years.Why these wide differences in adoption speed? Conformability with existing infrastructure. Flush toilets required the build-out of water and sewage utility systems. They also meant adding a new room to the house—the bathroom—and running new water and sewage lines underneath and throughout the house. That’s a lot of systems to line up. By contrast, refrigerators replaced iceboxes, and could fit into existing kitchens without much work. Microwaves could sit on a countertop. Smartphones could slip into your pocket.

One of the most impactful uses of LLM technology lies in content rewriting, which naturally capitalizes on these systems’ robust capabilities for generating and refining text. This application is a logical fit, helping users enhance their content while engaging with a service.

Similar to summarization but incorporating an element of judgment, features like Microsoft Team CoPilot’s call transcript summaries distill extensive discussions into essential bullet points, spotlighting pivotal moments or insights.

The ability to ‘understand’ nuanced language through summarization extends naturally into advanced search functionalities. ServiceNow does this by enabling customer service agents to search tickets for recommended solutions and to dispel jargon used by different agents.

Rather than merely focusing on content creation or manipulation, emerging applications of these systems provide new perspectives and predict outcomes based on accumulated human experiences. The actual value of these applications lies not merely in enhancing efficiency but in augmenting effectiveness, enabling users to make more informed decisions.

In the first approach, the primary interface affordance is an input that directly (for the most part) instructs an AI model(s). In this paradigm, people are authoring prompts that result in text, image, video, etc. generation. These prompts can be sequential, iterative, or un-related. Marquee examples are OpenAI's ChatGPT interface or Midjourney's use of Discord as an input mechanism. Since there are few, if any, UI affordances to guide people these systems need to respond to a very wide range of instructions. Otherwise people get frustrated with their primarily hidden (to the user) limitations.

The second approach doesn't include any UI elements for directly controlling the output of AI models. In other words, there's no input fields for prompt construction. Instead instructions for AI models are created behind the scenes as people go about using application-specific UI elements. People using these systems could be completely unaware an AI model is responsible for the output they see.

The third approach is application specific UI with AI assistance. Here people can construct prompts through a combination of application-specific UI and direct model instructions. These could be additional controls that generate portions of those instructions in the background. Or the ability to directly guide prompt construction through the inclusion or exclusion of content within the application. Examples of this pattern are Microsoft's Copilot suite of products for GitHub, Office, and Windows.

they could be overlays, modals, inline menus and more. What they have in common, however, is that they supplement application specific UIs instead of completely replacing them.

By Katharine Schwab4 minute ReadOver the last year, Ideo’s philosophy of “design thinking“–a codified, six-step process to solve problems creatively–has come under fire. It’s been called bullshit, the opposite of inclusive design, and a failed experiment. It’s even been compared to syphilis.Ideo as an institution has rarely responded to critiques of design thinking or acknowledged its flaws. But at the Fast Company Innovation Festival, Ideo partner and leader of its Cambridge, Massachusetts, office Michael Hendrix had a frank conversation with Co.Design senior writer Mark Wilson about why design thinking has gotten so much flack.“I think it’s fair to critique design thinking, just as it’s fair to critique any other design strategy,” Hendrix says. “There’s of course many poor examples of design thinking, and there’s great examples. Just like there’s poor examples of industrial design and graphic design and different processes within organizations.”Part of the problem is that many people use the design thinking methodology in superficial ways. Hendrix calls it the “theater of innovation.” Companies know they need to be more creative and innovative, and because they’re looking for fast ways to achieve those goals, they cut corners.“We get a lot of the materials that look like innovation, or look like they make us more creative,” Hendrix says. “That could be anything from getting a bunch of Sharpie markers and Post-its and putting them in rooms for brainstorms, to having new dress codes, to programming play into the week. They all could be good tools to serve up creativity or innovation, they all could be methods of design thinking, but without some kind of history or strategy to tie them together, and track their progress, track their impact, they end up being a theatrical thing that people can point to and say, ‘oh we did that.'”

“If you make something rigid and formulaic, it could absolutely fail,” he says. “You want to rely on milestones in the creative process, but you don’t want it to be a reactive process that loses its soul.”

“There is a real need to build respect for one another and trust in the safety of sharing ideas so you can move forward,” Hendrix says. “Knowing when to bring judgments is important. Cultures that are highly judgy, that have hierarchy, that are rewarding the person who is the smartest person in the room, don’t do well with this kind of methodology.”

There are a multitude of viable culprits behind this revenue drop. Robson himself pointed to the pandemic and tightened global budgets while arguing that “the widespread adoption of design thinking . . . has reduced demand for our services.” (Ideo was, in part, its own competition here since for years, it sold courses on design thinking.) It’s perhaps worth noting that, while design thinking was a buzzword from the ’90s to the early 2010s, it’s commonly met with all sorts of criticism today.

“People were like, ‘We did the process, why doesn’t our business transform?'” says Cliff Kuang, a UX designer and coauthor of User Friendly (and a former Fast Company editor). He points to PepsiCo, which in 2012 hired its first chief design officer and opened an in-house design studio. The investment has not yielded a string of blockbusters (and certainly no iPhone for soda). One widely promoted product, Drinkfinity, attempted to respond to diminishing soft-drink sales with K-Cup-style pods and a reusable water bottle. The design process was meticulous, with extensive prototyping and testing. But Drinkfinity had a short shelf life, discontinued within two years of its 2018 release.

“Design is rarely the thing that determines whether something succeeds in the market,” Kuang says. Take Amazon’s Kindle e-reader. “Jeff Bezos henpecked the original Kindle design to death. Because he didn’t believe in capacitive touch, he put a keyboard on it, and all this other stuff,” Kuang says. “Then the designer of the original Kindle walked and gave [the model] to Barnes & Noble.” Barnes & Noble released a product with a superior physical design, the Nook. But design was no match for distribution. According to the most recent data, Amazon owns approximately 80% of the e-book market share.

The rise of mobile computing has forced companies to create effortless user experiences—or risk getting left behind. When you hail an Uber or order toilet paper in a single click, you are reaping the benefits of carefully considered design. A 2018 McKinsey study found that companies with the strongest commitment to design and the best execution of design principles had revenue that was 32 percentage points higher—and shareholder returns that were 56 percentage points higher—than other companies.

As the construction industry matured, and best practices were commodified, the percentage of buildings requiring the direct involvement of architects plummeted. Builders can now choose from an array of standard layouts that cover most of their needs; materials and design questions, too, have been standardized, and reflect economies of scale more than local or unique contextual realities.

Cities have lots of rules and regulation about how things can be designed and built, reducing the need for and value of creativity

The situation is similar in our field. In 2009, companies might ask a designer to “imagine the shoe-shopping experience on mobile,” and such a designer would need to marshal a considerable number of skills to do so: research into how such activity happens today and how it had been attempted online before and the psychology of people engaged in it; explorations of many kinds of interfaces, since no one really knew yet how to present these kinds of information on smartphones; market investigations to determine e.g. “what % of prospective shoppers have which kinds of devices, and what designs can accommodate them all”; testing for raw usability: can people even figure out what to do when they see these screens? And so on.In 2023, the scene is very different. Best practices in most forms of software and services are commodified; we know, from a decade plus of market activity, what works for most people in a very broad range of contexts. Standardization is everywhere, and resources for the easy development of UIs abound.

It’s also the case that if a designer adds 15% to a design’s quality but increases cycle time substantially, is another cook in the kitchen, demands space for ideation or research, and so on, the trade-off will surely start to seem debatable to many leaders, and that’s ignoring FTE costs! We can be as offended by this as we want, but the truth is that the ten millionth B2B SaaS startup can probably validate or falsify product-market-fit without hiring Jony Ive and an entire team of specialists.

We design apps downstream of how Apple designs iOS. There’s just not that much room for innovating in UI at the moment

Today, for a larger-than-ever percentage of projects, some good libraries and guidelines like Apple’s HIG can get non-designers where they need to go. Many companies could probably do very well with1 designer to do native design + create and maintain a design systemPMs and executives for ideationFront-end engineers working off of the design system / component library to implement ideasSo even where commodification doesn’t mean no designers, it still probably means fewer designers.

If, for example, they land AR / VR, we will once again face a world of businesses who need to figure out how their goods and services make sense in a new context: how should we display Substack posts in AR, for example? Which metaphors should persist into the new world? What’s the best way to shop for shoes in VR? What affordances empower the greatest number of people?

But there will at least be another period when engineers who “just ship” will produce such massively worse user interfaces that software designers will be important again.

“design process” and “design cycles” are under pressure and may face much more soon. Speed helps, and so too does a general orientation towards working with production however it’s happening. This basically sums to: “Be less precious, and try to fit in in whatever ways help your company ship.”

being capable of more of the work of making software can mean becoming better at strategy and ideation, such that you’re ever executive’s favorite collaborative partner; you listen well, you mock fast (maybe with AI), and you help them communicate; or it can mean becoming better at execution, learning, for example, to code.

With the comprehensive application of Artificial Intelligence into the creation and post production of images, it seems questionable if the resulting visualisations can still be considered ‘photographs’ in a classical sense – drawing with light. Automation has been part of the popular strain of photography since its inception, but even the amateurs with only basic knowledge of the craft could understand themselves as author of their images. We state a legitimation crisis for the current usage of the term. This paper is an invitation to consider Synthography as a term for a new genre for image production based on AI, observing the current occurrence and implementation in consumer cameras and post-production.

In recent years Sketch’s Mac-ness has become a liability. Requiring every person in a large design organization to use a Mac is not an easy sell. Plus, a new generation of “internet native” users expect different things from their software than old-school Mac connoisseurs: Multiplayer editing, inline commenting, and cloud sync are now table-stakes for any successful creative app.

At the time of Sketch’s launch most UX designers were using Photoshop or Illustrator. Both were expensive and overwrought, and neither were actually created for UX design. Sketch’s innovation wasn’t any particular feature — if anything it was the lack of features. It did a few things really well, and those were exactly the things UX designers wanted. In that way it really embodied the Mac ethos: simple, single-purpose, and fun to use.

Apple pushed hard to attract artists, filmmakers, musicians, and other creative professionals. It started a virtuous cycle. More creatives using Macs meant more potential customers for creative Mac software, which meant more developers started building that software, which in turn attracted even more customers to the platform.And so the Mac ended up with an abundance of improbably-good creative tools. Usually these apps weren’t as feature-rich or powerful as their PC counterparts, but were faster and easier and cheaper and just overall more conducive to the creative process.

Apple is still very interested in selling Macs — precision-milled aluminum computers with custom-designed chips and “XDR” screens. But they no longer care much about The Mac: The operating system, the software platform, its design sensibilities, its unique features, its vibes.

The term-of-art for this style is “skeuomorphism”: modern designs inspired by their antecedents — calculator apps that look like calculators, password-entry fields that look like bank vaults, reminders that look like sticky notes, etc.This skeuomorphic playfulness made downloading a new Mac app delightful. The discomfort of opening a new unfamiliar piece of software was totally offset by the joy of seeing a glossy pixel-perfect rendition of a bookshelf or a bodega or a poker table, complete with surprising little animations.

There are literally dozens of ways to develop cross-platform apps, including Apple’s own Catalyst — but so far, none of these tools can create anything quite as polished as native implementations.So it comes down to user preference: Would you rather have the absolute best app experience, or do you want the ability to use an acceptably-functional app from any of your devices? It seems that users have shifted to prefer the latter.

Unfortunately the appeal of native Mac software was, at its core, driven by brand strategy. Mac users were sold on the idea that they were buying not just a device but an ecosystem, an experience. Apple extended this branding for third-party developers with its yearly Apple Design Awards.

for the first time since the introduction of the original Mac, they’re just computers. Yes, they were technically always “just computers”, but they used to feel like something bigger. Now Macs have become just another way, perhaps the best way, to use Slack or VSCode or Figma or Chrome or Excel.

visionOS’s story diverges from that of the Mac. Apple is no longer a scrappy upstart. Rather, they’re the largest company in the world by market cap. It’s not so much that Apple doesn’t care about indie developers anymore, it’s just that indie developers often end up as the ants crushed beneath Apple’s giant corporate feet.

I think we’ll see a lot of cool indie software for visionOS, but also I think most of it will be small utilities or toys. It takes a lot of effort to build and support apps that people rely on for their productivity or creativity. If even the wildly-popular Mac platform can’t support those kinds of projects anymore, what chance does a luxury headset have?

Reddit is rumored to have plans to go public, but they need better leadership than the current team. Huffman has shown no leadership skills. He doesn’t know how to read the room. Most importantly, he lacks the social empathy to lead a social platform. Even more disappointing is the lack of comments or intervention from Reddit co-founder Alexis Ohanian, the always chatty — who seems to have advice for every other founder, except for his co-founder. […] In an attempt to monetize the content generated by the community, Huffman forgot that it is the people who make the platform. The community is the platform. It is something the owners of social media platforms forget. […] It happened with MySpace. It has happened with Twitter. It is now happening with Reddit. They never learn from past mistakes. They assume that because they own the platform, they own the community. Every time they forget that important thing, they erode the community’s trust. And once that trust goes, so does the unfettered loyalty. People start looking for options.

I have zero faith in Steve Huffman’s ability to lead Reddit. What kind of chief executive officer posts this comment after a massive community backlash?

closing off 3rd party API access mostly serves an IPO, not OpenAI. If Reddit merely wanted to restrict the ability to scrape its data, they could have done so without killing off clients – e.g. via licensing deals. However, perhaps if access to training data is seen as an elbows-out brawl, I could see how Reddit would be extremely protective of its data. I mean, lyrics websites, map makers, and dictionaries go to great lengths to protect their data. It would not be a giant stretch for Reddit to do so as well.

Huffman is right that, in the end, the whole situation reflects a product problem: the native Reddit apps, both on desktop and on mobile, are ugly and difficult to use. (In particular, I find the nested comments under each post bizarrely difficult to expand or collapse; the tap targets for your fingers are microscopic.) Reddit didn’t really navigate the transition to mobile devices so much as it endured it; it’s little wonder that millions of the service’s power users have sought refuge in third-party apps with more modern designs.

We still believe that "if our hope is to create software with feeling, it means inviting people in to craft it for themselves — to mold it to the contours of their unique lives and taste.” And we have a few thoughts on how to make that happen, but if you know us, you know that the prompt is almost always more interesting than the answer.

i don't even really care if the answer is right, as long as the person i'm talking to can talk about complexity cogently. if i'm interviewing for an entry-level position, i don't even really care about that, we can teach it, it's not that hard.

Anecdotally I have noticed junior engineers being increasingly difficult to work with since many of them are leetcode drones who have issues working and figuring things out on their own. They got really good at passing 'the test' but did not develop many other skills relating to technology and many times do not really have an outside interest in it beyond being able to get a job.

How they translate into 3D spaces, how they are integrated with architecture, lighting, textures & materials enables more avenues for brand expression, and often elevates the perception of a brand over time and exposure, even if the logo fades somewhat into the background.