#typography / MacOS Catalina users have access to premium typography.

What better way to kick off a new week than with free, amazing type? I wish more Monday’s started off this way.

Apple has recently licensed fonts from type foundries such as Commercial Type, Klim Type Foundry and Mark Simonson Studio to be used as system fonts on Mac OS Catalina. But since these fonts are an optional download, many users of Mac OS X are not even aware they have access to them for free.

Over-saturation of Domaine, Produkt, and Publico is imminent.

#donotwant

My friend Abdullah Shaikh. He was one of a kind.

As far as meeting a new co-worker goes, being introduced to Abdullah Shaikh was one of the strangest moments to date. We were both hired into a new team with a mission to create a better incubation program at IBM Design. The program’s purpose was to prepare further brand new designers (young people right out of college, many of whom had never had a job before) to work at IBM and the many worlds of Enterprise computing, storage, education, health, governance, and technology. The incubator program was a six-week project that was the culmination of all the things they learned through other onboarding programs. After they left our care, IBM needed them to be able to interact with other professionals, work with executives, validate Enterprise-grade problems, and create higher caliber solutions than IBM was creating at the time.

I had been on the job for about a month, by myself for most of that time. While the expectations of the outcomes were clear, I was still trying to wrap my brain around IBM, a company of four hundred thousand people working in almost every country on the planet. And here I was on the morning of inheriting twenty designers who I had never met before, so I could lead them through a project to help IBM win in the marketplace (or at the very least help them avoid spending millions to lose in the marketplace). I was pretty anxious.

And then I met Abdullah. He showed up the morning the incubator program started calm and cool as a cucumber. I was glad he was there because I knew plenty about leading teams through projects, but I knew nothing about working at a place like IBM. I used to have clients in similar Enterprise-class companies, and they were always running behind, checking email, and generally not enjoying their job. I thought it just came with working in a place that assigns people a serial or employee number. Abdullah had worked at Microsft for several years and that experience proved to be invaluable.

During that first cohort, Abdullah brought humanity to the program. He helped us all learn to take our anxiety down a notch and enjoy the work at hand. And he did this primarily through doughnut diplomacy. About mid-way through the six weeks, while we were all trying to figure out heads from tails, Abdullah came in one day with ten to twelve boxes of doughnuts and placed them in a common area. He told one team, who told the next, and so on. I was on the other side of the studio, and you could hear the wave of sound-to-silence from one side to the next as designers leaped up and raced to get a treat. With a doughnut in hand, everyone calmed down, and the reduction in anxiety across the studio was palpable.

It became an incubator program tradition combined with the second thing Abdullah loved about the program: The pivot. After the first and second cohort, it was clear to Abdullah and I that every team was very likely to hit a moment when they had to pivot. For some, this happened near the end of research when the team could not validate the program handed to them by an executive. That didn’t mean they could quit and hang out for another month. Instead, they had to dig into their data and come back with an alternative, a course correction that would produce a worthwhile outcome. This happened with such regularity that we sought to make it happen in each project because it taught a few valuable lessons.

  1. Executives are not always right.
  2. If you talk to enough users, they will illuminate the right path forward.
  3. Pivoting means progress, not a failure.

When we started to map out future cohorts, it became a tradition to schedule the pivot celebration, with more than enough doughnuts for everyone.

Abdullah was a smart guy, and his talents and background were different than my own. We made a good team, helping each other where needed, but also giving each other enough space to be our own leader and co-owner of the program. There was overlap in our stories, but that was mostly around former business ownership and life experience. We both enjoyed working with young folks, helping guide them through career (and sometimes life decisions). We both played the role of coach.

While we didn’t talk much about our lives, Abdullah loved to talk about the Delta frequent filer program, specifically the Delta Lounge. If you could live there full time, he would have pushed all of his chips in. Damn, he loved that lounge and mentioned it any time some related topic came up. A few years back, I took a first-class trip to Shanghai. I tried to tell everyone at work the story, “It was on a 787, the plane with the blackout windows. They served a five-course meal paired with French wines…” That’s about as far as I got before Abdullah would break in and say something like, “Yeah, at the Delta Lounge…”

Eventually, we got a third partner when Erin Hauber joined the team. Her perspective and immersive knowledge about design thinking and education helped us make even more improvements. The three of us worked well together, a true testament to diverse teams. I left the Incubator program a year later. I admit being a bit emotional about it, considering how much we had done to improve the program and the outcomes. To this day, our work on the incubator program is one of my proudest achievements.

Abdullah loved the Incubator program and wanted to run it, but eventually, that responsibility was given to someone else, and it didn’t go well. Changes were made without consideration for the work, the improvements that we made. The new owner didn’t have the same heart for the designers and the work as Abdullah did, and it became a point of resentment. I always felt bad about that time because it was a bit like taking Christmas away from Santa Claus. He loved that program and working with young people that much.

Eventually, Abdullah moved on to run different teams, and I moved on to another company. From time to time we would get together for an old fashioned or two followed by giant steaks and bottles of wine. We both loved the steakhouse atmosphere and had plenty of stories of previous experiences to share. And we in touch through Instagram, where he was always posting photos of all the fantastic food he cooked and baked. I honestly don’t know why he didn’t open a food truck or a restaurant because he loved to cook for people. He loved to entertain and provide new experiences for his friends.

Abdullah was an old soul, a friend I would have had for life. Unfortunately, he passed away unexpectedly last Saturday night. While he had no immediate family of his own, Abdullah is survived by hundreds of IBM designers who he coached and fed doughnuts over the years.

#utopia

Ballast—004.

  • After two months of sheltering in place, the walls are starting to feel like they are closing in. Last week we drove a few miles out of town to pick up a delivery and kept ongoing. It felt good to see something different, something new. About forty-five minutes out, we got to a small town where it became apparent that other folks needed to get out too. I’m not in a hurry for quarantine to be over, but I’ll be glad when it is. Thankfully we managed to get our outdoor furniture, which means we can live outside for part of the day, and that’s helped a lot. I have to admit I started to envy the folks who have driveways and backyards.

  • I had no idea how many millions of Darwin worshippers there are on the planet. So many just carrying on like nothing is happening—pandemic, what?! Hanging out in parks, getting together with friends (outside a bubble), and inviting the neighbors over for BBQ! The funny thing is, I bet most of these folks would never lay down $100 on a Blackjack table in Vegas, but they’re quick to gamble their lives. Talk about the ultimate face-palm; now I understand why Jesus did what he did. After a few years roaming the Earth and he knew humans didn’t have it in them to make it through on their own.

  • Zoom has been both a blessing and a curse. Turns out that “Zoom fatigue” is real. National Geographic published an interesting piece on how too much video conferencing is “taxing the brain.” While the quality of video conferencing under Zoom has been phenomenal, the future workforce is going to need more ways to interact and stay connected. I’ve started to use the Phone app on my iPhone instead of Slacking a Zoom link, and that’s been helpful. Also, I’m surprised to find that most people don’t know you can do both audio and video chats within Slack. The toolset is not meant to compete with Zoom’s features that make it perfect for meetings and events like webinars, but it’s quick and works quite well for small group conversations.

  • I got into the Valorant closed beta this week. It has been a long time since playing a game on a PC (In my case, a dual booted a MacBook Pro equipped with a Radeon Pro 560x, it does the job). Going from controller to keyboard and mouse has been weird but not as challenging as I thought it would be. Valorant hasn’t made the transition easy. One of the core tenants of the game is gun accuracy. Meaning the games doesn’t provide aim assistance. It’s still fun and reminds me of playing Return to Wolfenstein many, many years ago.

  • I posted this to Twitter earlier this week, but it’s worth repeating here, I don’t know who the design team is at Riot Games, but they are killing it with their web design right now. I love the art direction, page compositions, color palettes, type choices—all of it. Very nice work.

  • While I still intend to pick up the Cyberpunk 2077 Xbox (because it’s so damn cool looking), I’m not sure about buying into the next generation of consoles later this year and instead might switch to a Razer laptop.

  • Lastly, I enjoyed reading Ethan’s article on the gluttony of frameworks (my words, not his). Whatever trade-offs we’ve made by moving into the frequent use of these systems, it seems clear that the costs have been pushed to the user in loss of time and a severe increase in data usage. There’s another cost in the energy and materials resources it takes to push and pull all of that data. One website might not be a big deal, but look at the numbers with a million sites, and my guess is we’d need a serious forest of trees to offset the carbon generated by all of this extra code. Another keen observation about these frameworks—none of them are geared for accessibility or performance.

Be well y’all and don’t leave the house without a facemask on!

#nerdvsgeek / An oral history behind the Star Trek episode that saved "Next Generation."

A fun read with a kicker!

As great as “Yesterday’s Enterprise” is, it is a source of some regret for one of its key creative architects.

“I wish we did this as the plot for Generations,” Moore says, referencing the first Star Trek feature film featuring The Next Generation crew that he co-wrote with Brannon Braga. “If we hadn’t have done that episode, then [the movie] would have been the Enterprise-A coming through that wormhole, and you’d have Spock and Kirk and everyone on that ship, we’d play the same story. They — the original crew — they had to go back to their deaths. And Guinan knew Kirk, and Guinan knew Picard, and that would have been an amazing movie.”

Can you imagine? I agree with Brannon, this plot would have made a fantastic film. There is a lot behind this one storyline that a cinematic format could have addressed so much better.