My paraphrasing of Zeynep Tufekci’s tweet from October 2017:
My paraphrasing of Zeynep Tufekci’s tweet from October 2017:
This is day 15 of 15 in a short series on inclusive design. If you missed any of the earlier posts, see day 1 here or view the full list below.
Resources, notes, and links to recap the 15-day series on inclusive design, where I shared what I’m learning about inclusive design with you.
I hope you’ve enjoyed following along and have learned something new. I welcome your comments and back-links to share your stories and resources, so I can learn what inclusive design means to you.
This content will live on in the form of a continually updated page: sensible.blog/inclusive.
About this Inclusive Design series — Today (February 16, 2018) I’m giving a talk on inclusive design at WordCamp Phoenix 2018. Leading up to the conference I’ve been publishing notes on voices, stories, products, and other resources: everything I’m learning about this emerging practice. Read more about the series.
This is day 14 of 15 in a short series on inclusive design. If you missed any of the earlier posts, see day 1 here or view the full list.
Inclusive and diverse teams make better, stronger teams — and these teams make better decisions. Because our work and thought patterns are influenced by our background and biases, working with a diverse group means not only fresh, new ideas, but we also counterbalance the tendency to design for people just like ourselves. A higher standard.
And that is why representation matters, not just to those who are represented, but to all of us. Because it expands our sense of what’s possible, and what we have reason to expect. —Cate Huston
For maximum learning and a broader perspective, not limiting yourself to your immediate team or company; seeking out a wide variety of inputs from mentors, coaches, and other advisors.
If your team is limited and you don’t have the ability to expand, actively seek out people with other perspectives to consult or act as project advisors, and give special consideration to their feedback.
I learned from Sara VanSlyke and Trace Byrd at Atlassian that it also matters how a diverse team is represented, in their article “Illustrating Balanced and Inclusive Teams.”
As a company that wants to unleash the potential in every team, depicting people is especially important. How we represent the people who make up teams should be just as important. We’ve always known that the best teams are balanced; made of a diverse group of people with different backgrounds and perspectives, but our illustrations haven’t always reflected that.
The authors found that even though their team aspired to be more inclusive, how they represented themselves visually wasn’t keeping pace with the true diversity of the team.
Promoting diversity and inclusion within our brand is a persistent and multi-faceted effort. And it’s a challenge to depict diversity without it feeling merely perfunctory or symbolic until the reality of our industry truly represents the customers we serve and the world at large. More needs to be done outside of the brand to promote an inclusive workplace, but we’ve found that the results of constant vigilance and open conversation are worth the time and energy.
To truly represent our customers is something Automattic is improving — we still have a long way to go. If you missed the story about updating the WordPress.com brand illustrations to be more diverse, see Inclusive Design, Day 5/15: To See Yourself in Imagery — with illustrator Alice Lee and my designer colleague Joan Rho.
See also this YouTube series introducing Automattic employees from all walks of life. A diverse group! I’m proud to work with them every day.
For a thorough treatment of this topic, I highly recommend reading and bookmarking “On Improving Diversity in Hiring” from my Automattic colleague Cate Huston. In this in-depth article, she shares her hiring expertise to build diverse teams, everything from onboarding and recruiting to specific tips and tricks during interviews.
This rule of thumb about stopping the behavior before someone is hired hit home with me as this is something I need to improve on personally. An off-color joke here, a comment there; I’m learning to speak up more when I notice these things.
A good rule for inclusion pre-work to diversity is to stop doing things you would have to change if the demographics of your team better reflected the demographics of the world. —Cate Huston
One practical tip shared by Cate that I’ve put to good use is Textio, a service to help make job descriptions more inclusive. I used it in 2016 to update the Excellence Wrangler job posting, replacing phrases like triage ruthlessly with triage efficiently.
Cate’s influence in the last year or so has helped me improve my hiring to be more inclusive, both in mindset and in practice. She’s inspired me to read more broadly, and think more openly.
In closing, a word from Scott Page via his Aeon article titled “Why hiring the ‘best’ people produces the least creative results:”
When building a forest, you do not select the best trees as they tend to make similar classifications. You want diversity.
(Scott has a new book out on this topic: The Diversity Bonus, How Great Teams Pay Off in the Knowledge Economy. I haven’t read it yet.)
For day 15 of 15 of inclusive design, the last day, I’ll share a recap of all the inclusive design learnings I’ve shared in this series so far.
About this Inclusive Design series — Tomorrow I’ll give a talk on inclusive design at WordCamp Phoenix 2018. Leading up to the conference I’ve been publishing notes on voices, stories, products, and other resources: everything I’m learning about this emerging practice. This is day 14 of 15. Read more about the series.
This is day 13 of 15 in a short series on inclusive design. If you missed any of the earlier posts, see day 1 here or view the full list.
Speed and connectivity should be considered be a major factor in exclusion. Just ride the BART in San Francisco. 😀
Joking aside, much of the world does not enjoy the wonders of high-speed bandwidth yet. Like William Gibson famously said, “The future is here, but it’s not evenly distributed.” Kansas City Google Fiber gigabit on one end, on the other Tegucigalpa less-than-Edge with wires hanging off a string.
As evidence of the disparity consider the “lite”* apps built by tech giants for markets where they want to drive adoption. The need for a reduced-weight experience in places with low-speed wired broadband and tenuous mobile broadband highlights the case of exclusion. Where large populations are left out of the “modern web” due to connectivity limitations, cost of entry, archaic device types, and many more reasons both cultural and political. (*Side note: what the heck is with that spelling?)
One story I noticed recently that mentioned speed as a leading tech market indicator involved WhatsApp’s growth in India even as Facebook lags behind them, via The Economist, January 27, 2018. Sluggish web app performance is a factor in Facebook’s lack of adoption in India. People who pay by the megabyte or gigabyte prefer to use a service that is leaner, faster, less bloated. They’re voting with their app choices.
In more ways than one, WhatsApp is the opposite of Facebook… whereas Facebook requires a fast connection, WhatsApp is not very data-hungry.
As a result [of this and other reasons], WhatsApp has become a social network to rival Facebook in many places, particularly in poorer countries. Of the service’s more than 1.3bn monthly users, 120m live in Brazil and 200m in India.
On the plus side, designing for speed brings about broad improvements to everyone else in the world. People should love the simpler interface with fewer settings and menus, alongside the bandwidth savings and reduced footprint for the app’s data storage needs.
Logically, “Design for low bandwidth” is on the Automattic Inclusive Design Checklist under “Bringing inclusion into designs.”
Back to the trend of tech giants creating lighter versions of their apps. When I take a closer look at the apps like “Twitter Lite” and “Facebook Lite” — at first they appear to be primarily designed for speed on slow connections. Yet the changes bring a new and different experience to many people who are mobile-first or non-technical.
The design enhancements resulting in a simpler and more intuitive app extends the benefit to a wide variety of people. For example, better readability from larger text size and the usability win from simpler navigation and clearer labels. That sounds like something the AARP crowd would all buy or click on or subscribe to.
If you’re curious about the “lites” — here’s further reading.
Facebook Lite came out two years earlier: Announcing Facebook Lite (June 2015).
With Facebook Lite, our goal is to provide the best possible Facebook experience to everyone, no matter their device or connection. And we hope that by sharing how we built the app, we can encourage more people to build for the next billion coming online. — via How we built Facebook Lite for every Android phone and network
The next billion coming online! Ambitious.
Goal: Calypso is the WordPress Lite.
Calypso designers also pay attention to the user interface, of course — recently we’ve made the text size larger and improved the color contrast for readability. My team at WordPress.com is now digging into label changes and interactions needed for a refreshed, simpler navigation for managing WordPress websites.
For those curious, we track speed improvements in Calypso on this data-rich website: iscalypsofastyet.com. And, we’re hoping to improve both the mobile web performance and the usability of the app even more in 2018.
In a blog post Speed is a key design attribute John Maeda highlights two strong voices in recent web history — speaking out on the value of speed and performance: Marissa Mayer and Lara Hogan. They’ve both been preaching this same topic for years. I’m sure today no one argues the pivotal role of speed in Google’s early success and how it led them to market dominance.
Testing bandwidth limitations even on a fast network is a great empathy challenge. I’m grateful to John Maeda for sharing two ways to do this: Chrome has a throttling setting in developer options to try out slower speeds with your site or web app, and the Network Link Conditioner for XCode 9.2 for macOS.
I’ve felt this slowness most times I travel, even in the US — in airports, hotels, taxis, trains. Most definitely when in other countries, because I’m limited by my data plan’s built-in speed limitation. Or, as when I visited a WordCamp in Nicaragua, the slow mobile “broadband” is the reality for everyone living there.
Keeping in mind much of the world now sees the web only through a mobile device. Which brings us to a message from Wapuu: Mind the mobile!
For day 14 of 15 of inclusive design, I’ll share behind-the-scenes details of the work Automattic designers put into our inclusive guide and checklist.
About this Inclusive Design series — In 2 days I’ll give a talk on inclusive design at WordCamp Phoenix 2018. Leading up to the conference I’m publishing notes on voices, stories, products, and other resources: everything I’m learning about this emerging practice. This is day 13 of 15. Read more about the series.
This is day 12 of 15 in a short series on inclusive design. If you missed any of the earlier posts, see day 1 here or view the full list.
I’d like to share another example of solving for one case, extending to many. This one comes from my team at Automattic. We’re called “Delta” — and we focus on making the editing–publishing flow for WordPress.com as smooth and pain-free as possible.
From our own experience, we know that publishing content to the entire world can be nerve-wracking! This “publishing confidence” experience started out with a specific case in mind: the WordPress.com announcements blog. With 43 million email subscribers as of the latest count, the authors at Automattic writing for this English-language blog never want to accidentally hit that “Publish” button before a new announcement is polished and ready to go.
That’d be a total disaster, right?
alert() dialog intended to add a quick warning before publishing. Developed for use on high-end client sites running on WordPress.com, it looks like this:
Fast-forward to 2017 — the Delta team starts revamping these same publishing flows as we upgrade many of the key features in the new WordPress.com interface. As we researched the pain points in the experience, we realized that this same feeling of anxiety could be shared by many other people. In fact, our customers often wrote in to request this exact thing for their own blogs.
There needs to be an “Are You Sure” button on the publish section, I’ve accidentally published a blog post too early so many times. — A WordPress mobile app user, writing it to support in 2017.
What if we could make a product change to reduce that same anxiety for everyone? Well, yes — it makes sense. The team also upgraded the blog post preview pane to add in a switcher for screen sizes — mobile, tablet, and desktop — to further improve the confidence in the end result.
Solving this in the WordPress.com editor experience means making it much harder to accidentally publish on any blog. The change enables all of our customers to breathe easier. Like us with the WordPress.com announcements blog — they can now feel more confident that the changes they’re sharing are ready for the world.
See also Publishing on WordPress.com for a project-level report on improving this publishing experience written by colleague Shaun Andrews.
For day 13 of 15 of inclusive design, we’ll look at speed and connectivity as an exclusion example. How the trend of “Lite” apps built for certain markets to drive adoption brings needed improvements to everyone.
About this Inclusive Design series — In 3 days I’ll give a talk on inclusive design at WordCamp Phoenix 2018. Leading up to the conference I’m publishing notes on voices, stories, products, and other resources: everything I’m learning about this emerging practice. This is day 12 of 15. Read more about the series.
This is day 11 of 15 in a short series on inclusive design. If you missed earlier posts, see day 1 here or view the full list.
The “OXO Good Grips Story” is an astounding example of inclusive design, solving for one and extending to many. An opportunity that grew from one person’s kitchen solution into a $60 million business.
Sam Farber — who created Copco enamel cast-iron cookware in 1960 — later developed what is now the quintessential OXO kitchen peeler from seeing his wife struggle with the classic shape and size of metal kitchen tools. He solved her pain by creating an ergonomic and comfortable grip that even people with arthritis could use. Turns out everyone else loves it, too.
The idea was always, from the start, to make useful products for people of all ages and levels of dexterity. We can improve every day life for people, without them even knowing or thinking about it. — Sam Farber
Watch the video, “Objectified: Smart Design OXO Good Grips Story,” for a behind-the-scenes look at OXO’s product development process and inclusive mindset.
Read more history in a case study from The Center for Universal Design: OXO International Becomes a Universal Design Icon (2000).
For day 12 of 15 of inclusive design, I’ll share about reduced anxiety when publishing to WordPress.com websites. A problem solved originally for one use case by adding an extra step for confidence.
About this Inclusive Design series — In 4 days I’ll give a talk on inclusive design at WordCamp Phoenix 2018. Leading up to the conference I’m publishing notes on voices, stories, products, and other resources: everything I’m learning about this emerging practice. This is day 11 of 15. Read more about the series.
This is day 10 of 15 in a short series on inclusive design. If you missed earlier posts, see day 1 here or view the full list.
Making your app accessible to visually impaired users benefits all your users. — Ayesha Zafar on the Invision blog
Taking the principles of inclusive design from idea to action means changing how and what we design. A reminder that technical details matter as much as the intention.
Via the design.blog/inclusive checklist under “Building inclusion into designs” we see how this relates to accessibility, “There’s no inclusion without accessibility.”
The amazing thing about doing the hard work for universal access is that the changes benefit everyone. Design for slow bandwidth? It’ll load faster for all people.
Here’s the full text for this checklist section, for reference:
There’s no inclusion without accessibility. Accessible designs will present differently depending on the medium you’re working in; consider physical, visual, auditory, financial, and other factors as well as an individual’s temporary or permanent limitations to accessing each. Is your video accessible to someone with hearing impairment? Is your website accessible to someone with a low internet bandwidth? Is your copy readable by individuals with different education levels, for whom the text is in a second language, or who are new to the subject matter? The more contexts you consider, the more accessible and inclusive your designs will be.
For a real-life example, I love this in-depth look at providing an accessible mobile app experience for visually impaired users by product designer Ayesha Zafar. Written for Invision, makers of software for digital designers. To understand inclusive design at both the highest level, the why — means you then need to deliver at the detail level, the what and how.
Read the full article to learn about: How to Design Mobile App Experiences for the Visually Impaired.
Ayesha also wrote a similar guide — focused instead on blind users — that’s also full of accessibility tips and inclusive design principles: How to design accessible mobile experiences for the blind.
On a digital product team it is everyone’s responsibility to have empathy for users and thus all users, no matter their ability, should be considered in the design process. — Ayesha Zafar on the Willow Tree Apps blog
Thank you, Ayesha. 💯
For day 11 of 15 of inclusive design, another example of “solve for one, extend to many — accessibility and usability considered first in the design: the story of “OXO Good Grips.”
About this Inclusive Design series — In 5 days I’ll give a talk on inclusive design at WordCamp Phoenix 2018. Leading up to the conference I’m publishing notes on voices, stories, products, and other resources: everything I’m learning about this emerging practice. This is day 10 of 15. Read more about the series.
This is day 9 of 15 in a short series on inclusive design. If you missed earlier posts, see day 1 here or view the full list.
Today I’d like to pause, take a deep breath, and review the principles of inclusive design as I’ve come to understand them.
Here’s the working draft we’re using in Automattic, with a nod to Kat Holmes’s work on Microsoft’s inclusive design toolkit.
1. Recognize exclusion.
2. Broaden perspectives and build empathy.
3. Bring diversity into teams and processes.
4. Solve inclusively for one, extend to many.
Kat herself describes these principles of inclusive design superbly in this brief video, from an O’Reilly design conference in March 2017.
For day 10 of 15 of inclusive design, I’ll share a story about making an app accessible to visually impaired users — which then benefits all users.
About this Inclusive Design series — In 6 days I’ll give a talk on inclusive design at WordCamp Phoenix 2018. Leading up to the conference I’m publishing notes on voices, stories, products, and other resources: everything I’m learning about this emerging practice. This is day 9 of 15. Read more about the series.
This is day 8 of 15 in a short series on inclusive design. If you missed earlier posts, see day 1 here or view the full list.
Adopting inclusive design isn’t just about being a good person. It’s a solid foundation for good business — focused on solving real needs for real people.
Barclays Bank understands this and is putting it into practice. Thanks to Beatriz Lonskis for pointing me to this example of smart business and good design.
We’re committed to inclusive design and accessible services — using new technology to make banking easier for you. — “Barclays Access” statement
The full case study is in The Guardian — Barclays Bank learned that embracing inclusive design, starting with accessibility, creates a better solution for all their customers. It’s a commercial opportunity when meeting a real need — not an expensive compliance issue.
Another Barclays accessibility piece in The Times, Smarter technology is improving the lives of disabled people.
Today, I manage all my financial affairs by smartphone,” she says. “It has genuinely transformed my life, cutting out all those frustrating trips to the bank.” — June Maylin (a blind customer of the bank).
June’s story provides an insight into how the technologies designed to make banking easier for everyone can be particularly effective for people with disabilities, and are steadily giving people much more control over their money. Even small, relatively low-tech initiatives can make a big difference.
By the way, I love this aspiration for leadership in this emerging practice on the Barclays Access Twitter profile: “One of our ambitions is to become the most accessible & inclusive FTSE org. Tweets about accessibility & disability issues.”
Small changes make a big impact, and inclusive design can have a major impact on revenue and business success by solving for one and extending to many.
For day 9 of inclusive design, we’ll review the principles discussed so far: 1/ Start with exclusion, 2/ Broaden your perspective to gain empathy, 3/ Bring diversity into teams and processes and 4/ Solve inclusively for one, extend to many.
About this Inclusive Design series — In 1 week I’ll give a talk on inclusive design at WordCamp Phoenix 2018. Leading up to the conference I’m publishing notes on voices, stories, products, and other resources: everything I’m learning about this emerging practice. This is day 8 of 15. Read more about the series.
This is day 7 of 15 in a short series on inclusive design. If you missed earlier posts, see day 1 here or view the full list.
“Solve for one, extend to many” is a key principle of inclusive design which I learned from Kat Holmes and her work with Microsoft.
Via fellow WordPresser Leo Postovoit, I learned more about how Roku followed this principle to achieve commercial success. “From a small hardware start-up to a publicly listed company with an estimated 2017 revenue of $500 million and a $5 billion market cap,” according to Variety.
Roku is successful because of how user-friendly everything is. Along with Apple TV, Chromecast, Android TV, and others — the experience is a big improvement over traditional TVs.
CEO Anthony Wood explains in Variety:
Roku’s original user interface was anything but flashy. Wood instead aimed for simplicity, banning all but the most essential buttons from Roku’s remote control, and calling apps “channels” to help TV viewers in their transition to the new medium. “Companies commonly overdesign something and make it kind of pretty, but not easy,” he says. “Customers, what they really want is easy.”
Here’s what people love about Roku:
— The minimal interface takes full advantage of “10-Foot UI” principle by using simple, intuitive navigation based on a grid. Large and readable from ten feet because you have no mouse/keyboard, viewing from the couch. (The navigations options are limited to left, right, up, down — click to select). Requires no fancy 100-button or huge user manual. Setup is a breeze.
— A trimmed down TV remote with programmable buttons; plus dedicated buttons for popular streaming services like Netflix. No menus to scroll through, go straight to viewing.
— Voice commands to search via the remote, and the search matches available content quickly from your input. Leo says: “My favorite feature is the universal search, where it actually queries every channel for listings, fuzzy searches too. You can find every “Batman” movie, including the Dark Knight!”
— Packaged as low-cost hardware — basic streaming kit sell for $29 — Roku positions itself as an attractive alternative to regular TVs that require a cable or satellite subscription. Streaming requires WiFi, and increasing broadband speeds boost the value of high-quality, always available content.
— One of my favorite features is the earphone jack in the remote control — great for private listening and for those who need a little extra hearing assistance.
[More about the 10-foot UI, if you’re curious like me: Wikipedia article and a user design guide.]
Though I couldn’t find evidence for it, the person Roku seems to have in mind in solving the typical TV problems is a cost-conscious, non-technical person over a certain age. Your grandparent might prefer a simple gadget that does one thing well, for example.
Fewer cords to plug in. No need to tinker or walk through endless steps of complicated menus to set up the TV. They certainly don’t love or wish to understand how to operate 100-button remote controls. [That’s why they call you over! “Fix my TV again, please.”]
The beauty of “solve for one, extend to many” is that the same elegant UI and intuitive remote works well for seniors and the elderly — but also works great for everyone else.
As Leo told me, “It benefits all people.”
Erica Manfred explains her love for Roku as a hard-of-hearing senior citizen: Aging With Geekitude: Why Roku is My New Crush:
Roku has terrific little feature, a headset jack on the remote so you can listen to your favorite shows and movies without bothering anyone. For a hearing aid wearer like me this is a godsend. The Roku also supports closed captioning, another huge benefit for the hearing impaired and anyone who can’t understand current slang.
(Leo notes 30-40 percent of Roku content still isn’t captioned.)
Roku proves to me that simple and inclusive hardware+software is good design and good business.
For day 8 of 15 of inclusive design, I’ll share a business success story — how to expand your market by solving for one, extending to many. Because inclusive design is great for business.
About this Inclusive Design series — Coming up next week I’ll give a talk on inclusive design at WordCamp Phoenix 2018. Leading up to the conference I’m publishing notes on voices, stories, products, and other resources: everything I’m learning about this emerging practice. This is day 7 of 15. Read more about the series.