Look a week ahead: Towards the end of a week, I’ll start to take a look at what meetings I have the following week. For any that I’m responsible for, I’ll start pulling together some information for attendees. Sometimes this means updating the calendar invite with an agenda; other times this means starting a Google Doc for what we need to run through during the meeting, and I share it with edit rights for all attendees. Use meeting goals: If the meeting has a bunch of people in it (like, more than two), especially if those people typically have full schedules, then I’ll write down goals for the meeting. Often, I’ll put those goals in the calendar item, and I’ll mention them at the beginning of the meeting. That means that if we get off-track during our time together, I can hit pause and recenter on the goals, asking folks to continue that other conversation afterward. Find a plant: Once in awhile, it’s helpful to “seed” the meeting somehow. For example, in one meeting where there’s an “open questions” time and I want people to ask anything, I’ve asked a buddy to think up a super weird one to demonstrate to others that it’s a safe space. Don’t surprise people in the meeting: Additionally, I do a lot of prep to make sure there’s no surprises in my meetings, at least none coming from me. This usually means that I let a handful of people know about a big announcement ahead of time (or had a tough conversation), usually one-on-one, so they wouldn’t be surprised in front of a lot of other people. Gain consensus 1:1 beforehand, if possible: My goal with any decision-making meeting is to already have a sense, going in, of what issues people have, what their opinion is, and what they might need to come to agreement. I do as much legwork in advance as possible, so that the whole group is ready to make that decision more quickly in the room.

Few things bog down meetings more than an unclear process, or a lack of clarity about how people in attendance are supposed to participate. By sharing the goals of the meeting and a high-level overview of what we’re going to do there, I hope to make it clear what’s expected of folks in the room.

Setting up a form for people to add their questions to - including people in the shared physical space - so that the facilitator can run through them rather than prioritize the voices in the room

I cancel meetings if they’re unwarranted. I check-in every few months to see if a meeting’s goal still makes sense; I ask attendees how they’re feeling about the length of the meeting, how often it happens, and what we do during it. I iterate on meetings to make sure they’re still effective, or even necessary.

Swelling trade tensions and the rise of “direct-to-consumer” platforms were bound to heighten the scrutiny on the import of mass media cultural products. But it’s also notable that the Marvel movies that did gain admittance in China were led by six heroes (The Avengers), five of whom were employed by the American military (with the sole outlier being an extraterrestrial) and all of whom were white. The current, rejected leads are more diverse in vocation, American allegiance, and ethnicity (among other attributes).

In 2017, Disney began a marketing integration with aerospace and defense giant Northrop Grumman encouraging those who use Google to research American defense contractor Stark Industries to join something like the real thing.

Avatar’s unprecedented achievements require us to examine not just its technological innovations, but also its narrative. The film’s “protagonist humans” are classic Western archetypes such as the taciturn soldier and the driven scientist. The villains are archetypes as well, but they are also particularly close to foreign caricatures of evil Americans: the tough-as-nails, violence-prone colonel and pillage-the-earth corporate executive. Furthermore, Avatar’s overarching message is one of collectivism, spiritualism, and alignment with nature. At the end of the movie, each of the Western heroes literally shed their individual identities (and white bodies) to become part of the cooperative aboriginal mind and save the day.

Not all design work is done in code, prototyping tools, or sketches. Likewise, not all engineering work is done in code or technical diagrams. Natural language, text, and conversations should be some of your primary mediums for creative work.

one of the most important sub-skills for writing and conversation as a design medium is learning how to create great analogies. Douglas Hofstadter thinks that analogies are actually the core of cognition, which I buy.

the web has some amazing advantages for launching new projects, which include (but aren’t limited to): Super fast distribution and updates Cross platform Huge tooling ecosystems Enormous, worldwide community If you’re into games, awesome! If you’re into mobile or native development, that’s cool too. There are lots of platform-specific toolkits and environments to make those. There’s also a lot of effort in creating cross platform tools and community-driven projects for both domains (like Unity and Flutter). They all have their advantages, but to me, nothing beats the portability and speed of launching new websites and using web tech to get ideas out the door.

using web tech for 80-90% of my projects has a lot of skill transfer effects. Since I’m using similar tools for lots of different projects, I can still refine my core skillset no matter what I’m making. If I’m making a drawing tool concept, a game, or a text editor— I’ll can still probably build all three with React. Of course there are specific libraries or APIs I might need to learn to make each kind of project, but there’s enough in common between all the projects that I can focus on the new content instead of yakshaving and deliberating over unnecessary details.

There are also market pressures that imply focusing on web will have long term payoff, like the rise of wasm, new browsers, and collaborative apps becoming the norm.

Something with no visual interface sounds amazing until you realize it is impossible to know its boundaries. You can ask for a translation to one language and it will work perfectly, but a different language is not translatable. A command that activates some smart home gadget may not work the same way for a different device.

By creating a character who can’t be written off as another predictably problematic man, “Tár” draws our attention to how Lydia learned to become one. And, by following Lydia closely, the film relieves the audience of a neurotic cultural obsession with the artistic legacies of real-life powerful figures, focussing instead on their tools. In lieu of asking “Can you separate the art from the artist?” or “But what will happen to these poor, bad men?,” “Tár” asks, “What does power look like, feel like, not only within an institution but within an individual psyche?”

At nineteen, I wrote in a private journal that “the knowledge that anything I feel has already been expressed in a work of art” was my version of feeling watched over by a higher power.

I do not mean to suggest that art works can be divorced from social context, only that our reactions to them are not, in themselves, public statements, acts of harm, or good deeds.

the desire to ship quickly was counterbalanced by a demanding, comprehensive perfectionism. Most commercial projects are driven by commercial values, where the goal is to maximize profits by outperforming your competition. In contrast, the Macintosh was driven more by artistic values, oblivious to competition, where the goal was to be transcendently brilliant and insanely great.

Unlike other parts of Apple, which were becoming more conservative and bureaucratic as the company grew, the early Mac team was organized more like a start-up company. We eschewed formal structure and hierarchy, in favor of a flat meritocracy with minimal managerial oversight, like the band of revolutionaries we aspired to be.

You need to make your case for what the problem or opportunity is—most often validated with at least directional data and/or research insights—and why your specific solution could work. You need to ensure it weaves into broader company initiatives as well as goals for your team and org. And you need a plan to get your product out there in a timely manner along with ways you'll further learn and validate your approach. An executive team won't be thrilled to hear you want to spend a year building something based solely on a hunch.

People hire services not just based on what they can do but how it makes them feel. Quality has a direct relationship to that. Quality products can take your users from "I'm merely using this thing to accomplish a task" to "this is something I love using and I'm telling everyone I know about it."

To maintain a shared, company-wide understanding of the company's specific stance is on quality, how does quality get rewarded, celebrated and prioritized? Is there a process in place for delaying a release and having a retro when the quality bar slips? Who decides when quality has slipped? Who's accountable for addressing it?

What does quality mean to them? How does it tie into the career ladder, promotions and prioritization frameworks? Do they focus more on execution speed over quality?

Is quality baked into the normal product development process, or is it often relegated to low priority "polish" tickets that pile up.

Do different roles (like engineering, product, design) have different motivations for getting their work done? This, again, ladders up to what the org thinks about quality.

Liberal use of "MVP" or "it's just an experiment". Does the team use those terms to skirt around typical quality standards and ship something subpar? Does everything worked on, even experiments, demand the same care as a more mainstream release that goes out to all users? That's a slippery slope because it's all too easy to simply ramp up that experiment to 100% of your users if it performs well, without addressing quality issues that were neglected prior to shipping to that initial set of users. No one wants a slice of cake that is just a piece of the bottom layer. You need to have a taste of each layer with each bite, including the icing. So even if it’s not your entire vision, it has all the right pieces involved. Ditch the term MVP and use SLC (Simple, Lovable, Complete).

I’m not saying designers, PMs and engineers should be holding up their projects for months to “get it right”. I'm saying that teams should be working in a way where everything is considered and there's a framework for identifying, discussing and prioritizing quality-related issues so that quality is a bit less of a sisyphian task.

Does your team have the skills and incentives to identify and adequately fix those issues? Does the organization continually reinforce and celebrate work that ladders up to quality, craft and great design?

have worked for myself over the 25+ years since, and similarly straddled design and development up until recently.Something I've found challenging is that in my projects and pricepoints, it's felt like there is no time for craft. Always harried, always spread thin. Never enough budget to do much more than burn through code. And working with clients who barely know what they expect, so it's hard to confidently spend time on design polish while the chance of concepts being rejected on a whim seems quite random.

Bikeshed refers to topics which have never recieved concensus and are likely to generate side-discussions and flames unless all participants are well-read on all the past history. It stems from the idea that big changes (like the building of a power plant) go through quickly, since everyone assumes that someone else has checked it out, while simple changes (like building a bikeshed) often get mired in bureaucracy, since everyone has an opinion on it.

When asked how often they decide not to post on social media out of fear of it being using against them, older teen girls stand out. For example, half of 15- to 17-year-old girls say they often or sometimes decide not to post something on social media because they worry others might use it to embarrass them, compared with smaller shares of younger girls or boys.

While 9% of teens think social media has had a mostly negative effect on them personally, that share rises to 32% when the same question is framed about people their age.

this survey reveals that only a minority of teens say they have been civically active on social media in the past year via one of the three means asked about at the time of the survey. One-in-ten teens say they have encouraged others to take action on political or social issues that are important to them or have posted a picture to show their support for a political or social issue in the past 12 months.

larger shares of Democrats than Republicans say they have posted pictures or used hashtags to show support for a political or social issue in the past year. In total, Democratic teens are twice as likely as Republican teens to have engaged in any of these activities during this time (20% vs. 10%).

Not only do small shares of teens participate in these types of activities on social media, relatively few say these platforms play a critical role in how they interact with political and social issues.

18% of Democratic teens say social media is extremely or very important to them when it comes to exposing them to new points of view, compared with 8% of Republican teens.

Despite feeling a lack of control over their data being collected by social media companies, teens are largely unconcerned. A fifth of teens (20%) say they feel very or extremely concerned about the amount of their personal information social media companies might have. Still, a notable segment of teens – 44% – say they have little or no concern about how much these companies might know about them.

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.

the monetary pressure of maintaining the American dream of homeownership is as powerful a weight on people’s psyches as the threat of being overcome by malignant spirits.