The key design skill is less about beautiful all-encompassing Figma documentation with all the kinds of journey maps and personas, or mastering a “process”. It’s about being so keenly situationally aware of what unknowns are in front of you so you can pick out what tools or design activities target them precisely.

It's not helpful to think of design as process of discovering, defining, ideating and delivering (or whatever version of those double diamond steps you prefer) because following those steps often does not get you closer to a solution.

One thing I learned long ago is that people who prioritize design, UI, and UX in the software they prefer can empathize with and understand the choices made by people who prioritize other factors (e.g. raw feature count, or the ability to tinker with their software at the system level, or software being free-of-charge). But it doesn’t work the other way: most people who prioritize other things can’t fathom why anyone cares deeply about design/UI/UX because they don’t perceive it. Thus they chalk up iOS and native Mac-app enthusiasm to being hypnotized by marketing, Pied Piper style.

Those who see and value the artistic value in software and interface design have overwhelmingly wound up on iOS; those who don’t have wound up on Android. Of course there are exceptions. Of course there are iOS users and developers who are envious of Android’s more open nature. Of course there are Android users and developers who do see how crude the UIs are for that platform’s best-of-breed apps. But we’re left with two entirely different ecosystems with entirely different cultural values — nothing like (to re-use my example from yesterday) the Coke-vs.-Pepsi state of affairs in console gaming platforms.

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.

Design thinking, in a slight divergence from the original model, suggests instead that the designer herself should generate information about the problem, by drawing on her experience of the people who will be affected by the design through the empathetic connection that she forges with them

In fact, problem-solving is always messy and most solutions are shaped by political agendas and resource constraints. The solutions that win out are not necessarily the best — they are generally those that are favored by the powerful or at least by the majority.

Design thinking has allowed us to celebrate conventional solutions as breakthrough innovations and to continue with business as usual.

In much the same way that the project shelters the young, it protects nascent ideas by providing a protected space for the on-going and collaborative engagement with the ambiguity and uncertainly

the Living Breakwaters project offers an alternative to the closure built into design thinking. It illustrates a design process where the designer is dethroned and where design is less a step-by-step march through a set of stages and more of a space where people can come together and interpret the ways that changing conditions challenge the meanings, patterns, and relationships that they had long taken for granted.

It represents a commitment to a process with no clear beginning and end, with a goal that is often no more explicitly defined than imaging and articulating new ways to meet changes that are still murky and immeasurable.

Every platform has its royalty. On Instagram it's influencers, foodies, and photographers. Twitter belongs to the founders, journalists, celebrities, and comedians. On LinkedIn, it’s hiring managers, recruiters, and business owners who hold power on the platform and have the ear of the people.

On a job site, they’re the provisioners of positions and never miss the chance to regale their audience with their professional deeds: hiring a teenager with no experience, giving a stressed single mother a chance to provide for her family, or seeing past a candidate’s imperfections to give them a once-in-a-lifetime opportunity. These stories are relayed dramatically in what’s now recognizable as LinkedIn-style storytelling, one spaced sentence at a time, told by job-givers with a savior complex.

This is all build-up to my proposal for what Musk — or any other bidder for Twitter, for that matter — ought to do with a newly private Twitter. First, Twitter’s current fully integrated model is a financial failure. Second, Twitter’s social graph is extremely valuable. Third, Twitter’s cultural impact is very large, and very controversial. Given this, Musk (who I will use as a stand-in for any future CEO of Twitter) should start by splitting Twitter into two companies. One company would be the core Twitter service, including the social graph. The other company would be all of the Twitter apps and the advertising business.

TwitterServiceCo would open up its API to any other company that might be interested in building their own client experience; each company would: Pay for the right to get access to the Twitter service and social graph. Monetize in whatever way they see fit (i.e. they could pursue a subscription model). Implement their own moderation policy. This last point would cut a whole host of Gordian Knots:

A truly open TwitterServiceCo has the potential to be a new protocol for the Internet — the notifications and identity protocol; unlike every other protocol, though, this one would be owned by a private company. That would be insanely valuable, but it is a value that will never be realized as long as Twitter is a public company led by a weak CEO and ineffective board driving an integrated business predicated on a business model that doesn’t work. Twitter’s Reluctance

It creates more generic-looking interfaces that may perform well in numbers but fall short of appealing to our senses.

It’s easy to make data-driven design decisions, but relying on data alone ignores that some goals are difficult to measure. Data is very useful for incremental, tactical changes, but only if it’s checked and balanced by our instincts and common sense.

It became clear to the team in that moment that we cared about more than just clicks. We had other goals for this design: It needed to set expectations about what happens next, it needed to communicate quality, and we wanted it to build familiarity and trust in our brand.We could have easily measured how many customers clicked one button versus another, and used that data to pick an optimal button. But that approach would have ignored the big picture and other important goals.

Not everything that can be counted counts. Not everything that counts can be counted.Data is good at measuring things that are easy to measure. Some goals are less tangible, but that doesn’t make them less important.While you’re chasing a 2% increase in conversion rate you may be suffering a 10% decrease in brand trustworthiness. You’ve optimized for something that’s objectively measured, at the cost of goals that aren’t so easily codified.

Design instinct is a lot more than innate creative ability and cultural guesswork. It’s your wealth of experience. It’s familiarity with industry standards and best practices.

Overreliance on data to drive design decisions can be just as harmful as ignoring it. Data only tells one kind of story. But your project goals are often more complex than that. Goals can’t always be objectively measured.