Categories
Design industry Information architecture

My Liz Danzico Joke

I used to tell a joke I made up. An American goes to the Vatican on Easter Sunday, joining a huge crowd of worshippers who gaze up in awe at a raised platform. On the platform stands the Pope. Beside him is Liz Danzico.

The American turns to a nearby man and asks, “Excuse me. Who is that with the Holy Father?”

The man answers, “I don’t-a know who’s the guy in the pointy hat, but that’s-a Liz Danzico up there.”

Categories
Design industry tweets twitter

Twitter Blues

Before the present owner, I was a Twitter Blue customer, because I always pay for software—to support its creators and help prevent it from disappearing, as so many great websites and platforms have done over the years. 

It wasn’t about the Twitter Blue pro features, to be honest, because they were few and inessential.

For instance, the ability to unsend a tweet for 30 seconds turned out to be more of an annoyance than an asset. Its value could be replicated without the feature, simply by taking a few seconds to reread your post before hitting Send. Most of the time, the feature felt to me like an annoying delay before every tweet went up.

And as Twitter compulsion is closely connected to the dopamine hit of instant gratification—voila! your thought is out there in the world, quick as the firing of a synapse!—waiting 30 seconds soon came to feel like a drag on the experience, not a benefit worth paying for. Like a cigarette that takes thirty seconds to deliver nicotine when you drag on it.

Nevertheless, as long as I had the income to do so, I would have continued to pay, simply to help Twitter keep going.

Because we’ve all seen what happens to beloved platforms after they run for too long on fumes. Investors grab lifeboats. Founders sell to a new owner who rapidly enshittifies the platform. Or the product disappears. Or it lingers as an under-resourced shadow of its former self, like a loved one with a tragically wasting disease. (Something I know far too much about.)

Besides: Twitter, as a town square, was important. Leaving its future health to the mercies of subscription models and advertising was risky enough.

Just as, despite the many obstacles to true representative democracy that threaten my country, it remains my sacred duty to vote, so too—as a user and fellow creator—did it feel like my duty to vote for Twitter’s continued existence with my wallet. (Again, acknowledging the privilege of having employment and at least a modicum of disposable income.) 

I won’t rehash the history of the new regime’s dangerous decisions and confounding errors of judgement—and that’s putting it charitably. Or share my anxieties about the Beloved Platform turning into a red-pilled fuckfest of racist, sexist pile-ons. 

Even when a longtime web acquaintance persuaded the new owner to “democratize” the blue checkmark by charging for it (and we’ll skip that history, which is still in progress, as well), I kept using Twitter, kept paying my Twitter Blue dues, and kept hoping for the best.

Even as brilliant people with vital jobs got kicked out by the thousands. Even when respected friends and colleagues abandoned Twitter like it was a room that smelled of corpses. Even when each day’s freshly absurd Twitter news cycle conjured disbelief worthy of U.S. Election Night 2016.

“Maybe it won’t be so bad,” I whispered to myself.

“I’ll hang in there,” I said.

As if continuing to use Twitter was some bizarre loyalty test to the platform itself, and not to the ideas and human beings that drove it. Like loyalty to a friend who drives his car into trees while drunk. “I’m not going to abandon him now, he needs help.”

Here comes the punchline: one day Twitter emailed me to say that my Twitter Blue account was being discontinued, but I would soon have the opportunity to pay for an exciting *new* version of Twitter Blue.

Then Twitter emailed me inviting me to roll over my credit card so as to become a member of the new Twitter Blue. Which made me wonder: do I continue to go by the principle of paying for software I use, even when I disapprove of the direction in which a new owner is taking the platform? Or do I register my dislike of that direction by refusing to pay, even if it accelerates the death of the platform? (Whereas I was still hoping for the platform to survive and right itself, no pun intended.)

In the end, and I know I’ll lose many of you here, I decided to keep paying. And now the promised punchline: Twitter was unable to accept my credit card, and the subscription failed. 

I tried for maybe 30 minutes.

I’ve successfully used software for over 30 years, and I’ve written a few things about UX and web design and development, so I generally have some idea of what I’m doing when I interact with internet content, and I also know that shopping carts are supposed to work. They’re not supposed to make users think. They’re supposed to make it easy to pay, whether you actually need the product or not.

Yet somehow—I wonder if it had to do with (illegally) firing most of the staff?—Twitter was not able to take my money.

The attempt to subscribe failed. Over and over. Perhaps it was my higher power telling me something. Perhaps it was my unconscious telling me something. But most likely, it was simple engineering and UX incompetence, caused by the removal of almost everyone at Twitter who knew what they were doing.

And the second punchline? I still have my blue checkmark. Which I’ve had since, like, 2006, or whenever the original Twitter first bestowed it. I guess because I’m of some small note in my field.

Of course, for all of having 322K followers, almost nobody sees my tweets, as the stats (and lack of engagement) plainly show me.

So either most of my 322K followers have abandoned the platform, or the algorithm works to minimize my footprint. And, theoretically, that latter situation would change if I paid Twitter the monthly $8—or, I believe it has gone up to $11, now, with price increases over time part of this week’s strategy to frighten folks into subscribing while they can still afford do so.

But I tried to give Twitter my money, even when I had Enormous Doubts that it was the right thing to do. And they simply wouldn’t take it. La de da. And for now I’m content to wait, peck my posts into the maw of the blind white whale, and see what changes next. 

Twitter Blue, Twitter Blues, Twitter blew it.

Categories
Advocacy Archiving Browsers Community Design glamorous HTML industry javascript launches links Off My Lawn! people Publications Responsive Web Design Standards State of the Web Stories The Profession W3C Web Design Web Design History Web Standards Websites

He Built This City: The Return of Glenn Davis

You may not know his name, but he played a huge part in creating the web you take for granted today. 

As the first person to realize, way back in 1994, that the emerging web could be a playground, he created Cool Site of the Day as a single-focused blog dedicated to surfacing interesting sites, thereby demonstrating the web’s potential while creating its first viral content. (As an example, traffic from his followers, or, as we called them back then, readers, brought NASA’s web server to its knees.)

He co-founded The Web Standards Project, which succeeded in bringing standards to our browsers at a time when browser makers saw the web as a software market to be dominated, and not a precious commons to be nurtured.

He anticipated responsive web design by more than 20 years with his formulation of Liquid, Ice, and Jello as the three possible ways a designer could negotiate the need for meaningful layout vis-a-vis the unknowns of the user’s browsing environment.

He taught the web DHTML through his educational Project Cool Site. 

And then, like a handful of other vital contributors to the early web (e.g. Todd Fahrner and Dean Allen), he vanished from the scene he’d played so large a role in creating.

He’s ba-ack

Glenn Davis wasn’t always missed. Like many other creators of culture, he is autistic and can be abrasive and socially unclueful without realizing it. Before he was diagnosed, some people said Glenn was an a**hole—and some no doubt still will say that. I think of him as too big for any room that would have him. And I’m talking about him here because he is talking about himself (and the history of the early web) on his new website, Verevolf.

If you go there, start with the introduction, and, if it speaks to you, read his stories and consider sharing your own. That’s how we did it in the early days, and it’s still a fine way to do it—maybe even the best way.

I knew Glenn, I worked with him and a lot of other talented people on The Web Standards Project (you’re welcome!), and it’s my opinion that—if you’re interested in how the web got to be the web, or if you were around at the time and are curious about a fellow survivor—you might enjoy yourself.

Categories
Advertising client services Design glamorous industry

Fear of getting noticed

Back when I was in advertising, one of my team’s clients was a well-known Irish Airline. They could only afford an 1/8th-page ad in the travel section of the paper. But my partners and I didn’t think creativity was dependent on budget. We were determined to deliver great ads for them—ads that would make a viewer look, even though the ad was tiny and was surrounded by other ads.

So we created a standout campaign for them—the kind that would not simply be noticed, but would also make travel-focused consumers smile and encourage them to buy tickets.

We blew up our tiny layouts and mounted the enlargements on illustration board, for an impactful creative presentation when we met to show the client the work.

The great day came. The work was good, and we had rehearsed our presentation to perfection. We booked the conference room, had the client’s favorite snacks and beverages spread out when they arrived, and sold our little hearts out as we presented.

Silence.

The lead client blinked, cleared his throat, and finally said, in a thick Irish brogue:

“I’m afraid it’s far too clever for our needs. It calls too much attention to itself on the page,” he explained—as if getting a distracted newspaper reader to notice his company’s message was a bad thing.

The lead client asked us to set “Ireland $399” in bold type, stick a shamrock in one of the 9s, and call it a day.



Fear of getting noticed is a terrible thing. It’s also a self-fulfilling prophecy.

Clickbait headlines get a deservedly bad rap in digital marketing, but you know what else should get a bad rap? Blind, boring, infinitely ignorable links and titles, that’s what.

Crafting messages that get noticed and acted upon by their intended audience—the people for whom you create your company’s digital products in the first place—isn’t a crime. It’s your job.


Hat tip to Mark Mazut and Tim Irwin, my fellow passengers on the above disaster. Bit o’ nostalgia for those who remember The Ad Graveyard.

Categories
art art direction creativity Design Designers experience Illustration industry New York City NYC people Portfolios Startups Stories Web Design

Looking Back, Looking Ahead: artist Dan Licht

Illustration by Dan Licht: a scary cowboy smoking a stogie and sloshing his drink. His eyes are red and he looks like he's itching for a fight.
Illustration by Dan Licht
Illustration by Dan Licht.

In 1999, I had the good fortune to work alongside Dan Licht at an NYC digital startup called SenseNet, RIP. Back then, although still in his early 20s, Dan was already an accomplished art director and digital designer. Today he’s a fantastic comics illustrator, artist, and creative director. Check his recent art on Instagram and his client work at Daniel V. Licht dot com.

A heroic letter carrier is pictured sending letters on their way in this illustration by Dan Licht. The picture has a great deal of energy, and the action is all flying toward you, the viewer.
“Protect the U.S. Postal Service,” a 2020 illustration by Dan Licht.
Categories
Advocacy automattic Blogs and Blogging Brands Community Design industry Own your content software Standards Web Design Web Standards wordpress

Enabling Folks to Express Themselves on the Web: State of the Word 2021

Screenshot of slide highlighting the four phases of WordPress Gutenberg.

Not only are we enabling folks to express themselves uniquely on the web, unlike the cookie cutter looks that all the social sites try to put you into. We’re doing it in a way which is standards-based, interoperable, based on open source, and increases the amount of freedom on the web.

—Matt Mullenweg, State of the Word 

In a live address, Automattic’s Matt Mullenweg

  • Introduces Openverse (an opt-in content commons);
  • Announces that WordPress’s beginner-friendly Learn.Wordpress.org is now available in 21 languages;
  • Philosophizes about Web3 and the “decentralized web” —which, despite big company colonization attempts, is really what the web has always been;
  • Extols the virtues of Open Source;
  • And more. 

Watch the 2021 #StateoftheWord annual keynote address on YouTube. It’s two hours long, so bring popcorn.

Selected Additional Reactions & Commentary

Hat tips to Chenda Ngak, Reyes Martínez, and Josepha Haden.

Categories
An Event Apart Appearances art direction better-know-a-speaker books Career conferences Design Designers Education events Genius glamorous Illustration industry Interviews New York City NYC Off My Lawn! speaking Stories Surviving Teaching The Profession UX Web Design Web Design History work

My Night With Essl

Mike Essl and I discuss his portfolio.
Mike Essl and I discuss his portfolio on Night 2 of An Event Apart Online Together Fall Summit.

Herewith, a scene from last night’s interview with legendary web & book designer (and Dean of The Cooper Union School of Art) Mike Essl, who shared his portfolio, career highlights, early web design history, and more. Fun!

If you get a chance to meet, work with, or learn from Mike, take it. He’s brilliant, hilarious, warmly human, and one of the most creative people you’ll ever have the good fortune to know. 

Mike Essl

So ended Day 2 of An Event Apart Online Together Fall Summit 2021. Day 3 begins in less than two hours. You can still join us … or watch later On Demand.

Categories
Designers Ideas industry Interviews links people podcasts User Experience UX Web Design work

Amplifying voices

Some of the interviewees of the Technically Speaking podcast.

New episodes of Harrison Wheeler’s Technically Speaking podcast are coming, and Technically Speaking will run live interviews at San Francisco Design Week June 7–13. 

The podcast amplifies voices of underrepresented leaders who want to inspire the next generation of black and brown designers through authentic, thought-provoking, and immersive storytelling. 

Learn more on the podcast’s homepage, listen to past episodes, and sign up for the newsletter to be notified about upcoming content. 

Categories
Best practices Browsers Code Design development Future-Friendly HTML Ideas industry Internship IXD Layout links Multi-Device Responsive Web Design software Standards State of the Web User Experience UX Web Design Web Design History Web Standards Websites

Saving Your Web Workflows with Prototyping

Our static tools and linear workflows aren’t the right fit for the flexible, diverse reality of today’s Web. Making prototyping a central element of your workflows will radically change how you approach problem solution and save you a lot of headaches – and money. But most importantly, you will be creating the right products and features in a way that resonates with the true nature of the Web. A discourse on processes, flexibility, the Web as a material, and how we build things.

Saving Your Web Workflows with Prototyping – Matthias Ott
Categories
Advocacy art direction Design Designers Ideas industry interface IXD Jason Santa Maria links Off My Lawn! Redesigns Responsive Web Design State of the Web Tech The Profession User Experience UX Web Design Web Design History webfonts

The Web We Lost: Luke Dorny Redesign

Like 90s hip-hop, The Web We Lost™ retains a near-mystical hold on the hearts and minds of those who were lucky enough to be part of it. Luke Dorny’s recent, lovingly hand-carved redesign of his personal site encompasses several generations of that pioneering creative web. As such, it will repay your curiosity.

Details, details.

Check Luke’s article page for textural, typographic, and interactive hat tips to great old sites from the likes of k10k, Cameron Moll, Jason Santa Maria, and more. 

And don’t stop there; each section of the updated lukedorny.com offers its own little bonus delights. Like the floating titles (on first load) and touchable, complex thumbnail highlights on the “observer” (AKA home) page. 

And by home page, I don’t mean the home page that loads when you first hit the site: that’s a narrow, fixed-width design that’s both a tribute and a goof.

No, I mean the home page that replaces that narrow initial home page once the cookies kick in. Want to see the initial, fixed-width home page again? I’m not sure that you can. Weird detail. Cool detail. Who thinks of such things? Some of us used to.

And don’t miss the subtle thrills of the silken pull threads (complete with shadows) and winking logo pull tab in the site’s footer. I could play with that all day.

Multiply animated elements, paths, and shadows bring life to the footer of Luke Dorny’s newly redesigned website.

Now, no site exactly needs those loving details. But danged if they don’t encourage you to spend time on the site and actually peruse its content

There was a time when we thought about things like that. We knew people had a big choice in which websites they chose to visit. (Because people did have a big choice back in them days before social media consolidation.) And we worked to be worthy of their time and attention.

Days of future past

We can still strive to be worthy by sweating details and staying alive to the creative possibilities of the page. Not on every project, of course. But certainly on our personal sites. And we don’t have to limit our creative love and attention only to our personal sites. We pushed ourselves, back then; we can do it again.

In our products, we can remember to add delight as we subtract friction.

And just as an unexpected bouquet can brighten the day for someone we love, in the sites we design for partners, we can be on the lookout for opportunities to pleasantly surprise with unexpected, little, loving details.

Crafted with care doesn’t have to mean bespoke. But it’s remarkable what can happen when, in the early planning stage of a new project, we act as if we’re going to have to create each page from scratch.

In calling Luke Dorny’s site to your attention, I must disclaim a few things:

  • I haven’t run accessibility tests on lukedorny.com or even tried to navigate it with images off, or via the keyboard.
  • Using pixel fonts for body copy, headlines, labels, and so on—while entirely appropriate to the period Luke’s celebrating and conceptually necessary for the design to work as it should—isn’t the most readable choice and may cause difficulty for some readers.
  • I haven’t tested the site in every browser and on every known device. I haven’t checked its optimization. For all I know, the site may pass such tests with flying colors, but I tend to think all this beauty comes at a price in terms of assets and bandwidth. 

Nevertheless, I do commend this fine website to your loving attention. Maybe spend time on it instead of Twitter next time you take a break?

I’ll be back soon with more examples of sites trying harder.


Simulcast on Automattic Design

Categories
Blue Beanie Day glamorous industry State of the Web

Another Blue Beanie Day

Yesterday was the nth annual Blue Beanie Day. (I’ve lost track of what year the standardista holiday started.) I was awake at 1:00 AM on Friday night/Saturday morning, so I tweeted “Happy #BlueBeanieDay,” then slept. No blog post, no prelude—just a past-midnight tweet, over and out.

Saturday, once or twice, I checked Twitter and retweeted most of the Blue Beanie Day tweets I found.

Most, because I omitted a soft-porn one that seemed to be capitalizing on the hashtag to advertise its Instagram feed (which, to judge by the tweet, consists of reposts of old Suicide Girls pictorials). So maybe the hashtag trended briefly for that person. One measure of social media success on Twitter is when someone who doesn’t understand or care about your hashtag uses it to draw attention to a tweet that has nothing to do with your cause—which tells you a lot about Twitter, and social media, and where we are as a culture. But I digress.

That shrinking feeling

Generally, each year, Blue Beanie Day gets smaller, possibly in part because I’m too busy to promote it beforehand (or during, or after). And because it immediately follows U.S. Thanksgiving, so gets broadcast when many U.S. web folks are offline and in food comas.

Blue Beanie Day also gets smaller each year because web design as a practice and as a discipline keeps shrinking … even though frontend UX, or whatever we’re calling it this week, clearly continues to grow.

Mainly, though, Blue Beanie Day is receding from view because our industry as a whole thinks less and less about accessibility (not that we ever had an A game on the subject), and talks less and less about progressive enhancement, preferring to chase the ephemeral goal posts of over-engineered solutions to non-problems.

If web design were automotive design, we’d be past the invention of mass production and on to designing self-obsoleting tail fins. But I digress, and I regret the negative spin this mini-memoir is taking.

Because, really, I’m happy and grateful.

Blue Beanie Day matters

In spite of our industry’s (I hope temporary) focus on complexity for its own sake, there are still a lot of you who do this work in the service of people we used to call “end-users,” and who will care about web standards and inclusive, accessible design for as long as you’re here to practice it.

To you, the true believers, whether you knew about/celebrated Blue Beanie Day or not, I give thanks.

Thanks for showing up every day to try to make the web a little better. Thanks for your optimism, especially when it gets harder to stay positive. You make an inclusive web possible.

Thanks for keeping Blue Beanie Day alive, not just on your head, but in your heart.

Categories
A Book Apart Advocacy art direction Best practices Design Designers Happy Cog™ industry

Expressive Design Systems

Yesenia Perez-Cruz started her career as a designer at Happy Cog Philadelphia. From the first day, her design gifts were unmistakable. As her career progressed, she moved from one challenging role to another. At companies like Vox Media and Shopify, and at conferences around the world, she has been a design team leader, a popular speaker, an advocate for design systems, and a voice of our industry. Today that voice took book form.

Expressive Design Systems, the first book by Yesenia Perez-Cruz, is now available from A Book Apart.

Categories
business Career client management client services clients Design experience glamorous industry IXD Microblogging Own your content project management The Essentials The Profession twitter UX Web Design Wit and Wisdom work

Design Kickoff Meetings

Posted here for posterity:

Design kickoff meetings are like first dates that prepare you for an exciting relationship with a person who doesn’t exist.

Categories
A List Apart Advertising art direction Best practices Brands conferences Content First Content-First Deck, the Fonts Ideas industry Medium Platforms Publications Publishing reportage Standards State of the Web studio.zeldman The Essentials The Profession Themes and Templates Usability User Experience UX Web Design Zeldman

Authoritative, Readable, Branded: Report from Poynter Design Challenge, Part 2

Poynter style guide

THIS year’s Poynter Digital Newspaper Design Challenge was an attempt by several designers and pundits, working and thinking in parallel, to save real news via design. In Part 1 of my report from Poynter, I discussed the questions driving the challenge, and talked about the design work done in response to it by my colleagues Kat Downs Mulder, Mike Swartz, Lucie Lacava, and Jared Cocken. Here in Part 2, I’ll discuss my own work and the approach we took at my studio. But we begin with a quick look back at the past designs that brought us to this point:

Experiment 1: The Deck

During the past decade and a half, as both a publication designer and a publisher, I watched in horror as our publications became reader-hostile minefields of intrusive ads, overlays, and popups. The first thing I tried to do about this (besides removing the web equivalent of chart junk from my magazine) was to offer an alternative approach to advertising via The Deck, an ad network I cofounded with Jim Coudal of coudal.com and Jason Fried of Basecamp (formerly 37signals). The Deck permitted only one appropriately targeted ad per each page of content viewed. As primary instigator Jim Coudal put it:

A buy in The Deck reaches the creative community on the web in an uncluttered, controlled environment, far more valuable than a standard banner or a single text ad among dozens of others.

Jim, Jason, and I hoped that our cost-per-influence model would replace the CPM race to the bottom, and that our quasi-religious use of whitespace would be widely imitated by the smartest publications online.

But that didn’t happen. Advertising just got more intrusive. The Deck succeeded as a small business supporting a network of interesting small publications, but not at all as a primary influencer on the direction taken by advertising that supports web content.

Experiment 2: Readability

Then about seven years ago, my friend Rich Ziade and his engineers created Readability, an app that sat between you and the ugly site you were trying to read, the way screen readers sit between visual websites and blind web users. Readability grabbed an article page’s primary content, removed the junk, and replaced the cluttered and illegible layout with a clean, readable page inspired by the clarity of iBooks and Kindle, which were just taking off at the time.

Rich released Readability 1.0 as open source; Apple immediately absorbed it into the Safari browser, where it continues to provide Safari’s built-in “reader” mode. (Safari’s “reader” mode was Apple’s first step in decluttering the web and returning it to the people who use it; “content blocking” would be the second step.)

Moreover, Readability 2.0, released by Rich’s then-company Arc90 the following year, added automatic payment for content creators slash publishers, as I explained at the time to anyone who would listen. Had Readability been allowed to continue the experiment, content monetization might have been less of a problem than it is today, and publication brands (the notion that it matters who publishes what we read) would be in exactly the same pickle they’re in anyway—except that readers would get their news in Readability’s attractive and customizable format, instead of from Apple News, Facebook, and the like.

I used to go around the world on lecture tours, warning my fellow designers that if we didn’t figure out how to declutter and compellingly brand sites, apps like Readability would do it for us. I still go around on lecture tours, but I’ve moved on to other issues. As for Readability, it was killed by a digital lynch mob after one powerful blogger, misunderstanding the motivation behind it, issued the digerati equivalent of a fatw?. But that’s another story.

Experiment 3: Big Type Revolution

In 2012, inspired by Readability and frustrated by the industry’s determination to make ever less legible, ever more cluttered sites full of tracking and popups and everything except what readers need, I bet big on large type:

This redesign is a response to ebooks, to web type, to mobile, and to wonderful applications like Instapaper and Readability that address the problem of most websites’ pointlessly cluttered interfaces and content-hostile text layouts by actually removing the designer from the equation. (That’s not all these apps do, but it’s one benefit of using them, and it indicates how pathetic much of our web design is when our visitors increasingly turn to third party applications simply to read our sites’ content. It also suggests that those who don’t design for readers might soon not be designing for anyone.)

Writing in Forbes, Anthony Wing Kosner saw the future in my initially crude experiment:

If you want to know where the web is going, one clue is to look at the personal sites of top-tier web designers. And one trend that just bubbled to the surface is large body type—the kind you don’t have to command-plus to read.

Jeffrey Zeldman…made a particularly strong point about it in his “Web Design Manifesto 2012,” that he published yesterday.

Large Type: One Web Designer Puts Content First in a Big Way

Not to brag (okay, too late), but he wasn’t wrong. It was the future.

(Also, I’m fairly sure I wasn’t the only designer at the time who reacted against tiny type and cluttered anti-user layouts by stripping pages down to only their most necessary elements, and boosting the type size to enforce a more relaxed reading posture. The idea was in the air.)

The experiment becomes the norm

In any case, soon enough, readable (big type and plenty of whitespace) layouts starting popping up everywhere. At medium.com. In Mike Pick’s redesign of A List Apart. In article pages for The New York Times, Washington Post, Vox, Newsweek, The New Yorker, and, eventually, many other publications.

An uncluttered page focused on the reading experience (reminder: big type and plenty of whitespace) is now the default at several leading news publications. But many smaller publications, struggling just to survive, have not kept up. And so we have a perfect crisis:

Publications that do not encourage reading, loyalty, or repeat visits are struggling to survive at the very moment real news is under attack from an authoritarian president. What to do?

 

A two-up from the Poynter challenge

My response to the Poynter Design Challenge

There are many ways to respond to an existential crisis like the one facing most news publications. You can rethink the relationship between reader and publication. Rethink the job of the publication. Make news work more like a lifestyle app. Make it more immersive. My colleagues followed those paths out brilliantly (as described in Part 1).

But I went for the low-hanging fruit. The thing any publisher, no matter how cash-strapped, could do. The thing I had seen working since I started yelling about big type in 2012. I went for a clean, uncluttered, authoritative, branded page. Authoritative because this isn’t fake news. Branded because the source matters.

The easiest, fastest, most readily attainable path to clean, uncluttered, authoritative, branded design is through typography.

 

Sample reader layout from the Poynter challenge

Any publication can be readable

Any newspaper, however poor, can afford better typography. Any newspaper with a designer on staff can attain it, if the paper stops treating design as a lackey of marketing or editorial or advertising, and sets designers free to create great reading experiences.

In my work, which is still underway (and will continue for some time), I focused on creating what I call “reader” layouts (and probably other designers call them that too; but I just don’t know). Layouts that are branded, authoritative, clean, uncluttered, and easy to read.

I played with type hierarchies and created simple style guides. Most of my little pages began as Typecast templates that I customized. And then Noël Jackson from my studio cleaned up the HTML and CSS to make it more portable. We put the stuff up on GitHub for whoever wants to play with it.

These are only starting points. Any designer can create these kinds of layouts. There’s nothing special about what I did. You can do the same for your paper. (And if you can’t, you can hire us.)

The work I share here is the start of a project that will continue at our studio for a long time. #realnews for the win!

Additional reading

Categories
Acclaim Advocacy Appearances art direction Best practices Brands conferences Damned Fine Journalism democracy Design Designers ForHire Ideas industry interface Layout Press Publications Publishing Redesigns reportage State of the Web Usability User Experience Web Design

Digital newspaper design challenge: a report from Poynter, part 1

CAN design create a better user experience that engages readers and drives revenue? Can it fight fake news and help save real journalism at a time when news organizations large and small are underfinanced and under attack?

These questions drove the Poynter Design Challenge, “a project to create new visual models for digital news publications” sponsored by William R. Hearst III, hosted by the Poynter Institute, and directed by publication designer Roger Black.

The challenge began October 17–18 in New York, with five pundits and five designers, of whom I was honored to be one, workshopping a project brief during a two-day conference event at the Columbia Journalism School. (You can watch videos of all these sessions courtesy of Fora.tv.)

The next phase took place yesterday in St. Petersburg, Florida, as the four other designers and I presented our work to a live audience. In this short piece, I’ll talk about the designs my colleagues presented; in the next, I’ll discuss my own.

Reconnecting with the people: the challenge for digital news

Roger Black described the difficulties facing digital news publications:

The challenge is serious. Fake news crowds real news. Numbers no longer add up for publishers. Readers jump from site to site without knowing where they are, or staying for long. You can see the brief for this project here.

Can design help? Well, as a I designer, I think it can. I mean, the design of most news pages is not what you’d call attractive. But the solutions proposed at Poynter will be much more strategic than cosmetic. And they’re strategies that can be combined.
Five design answers that add up, Roger Black, January 20, 2017

“A news publication might think a bit more like Fitbit”

News prototype by Kat Downs Mulder, Graphics director at The Washington Post.

Between us, we designers had about a century of experience designing digital publications—internally, as consultants, or both. This means that, even though an open “design challenge” brief necessarily omits an unknown number of the specific requirements any actual publication design assignment would include, all of us were aware of, and to some degree addressed, typical news publication requirements not included in our brief.

Kat Downs Mulder, Graphics Director at The Washington Post, shared a prototype for a big-brand news site. Kat had just given birth to a healthy baby boy (congratulations!), so her work was presented by two of her colleagues from The Post. Kat did not design with the avid, committed news reader in mind (since those folks are not the problem for most publications). Instead, she pondered how to engage the typically fragmented attention of today’s distracted and passive news reader:

“A big-brand news site [should be] aware that people have a lot more to do in their lives than read the news,” Kat posited. Thus, “A news publication might think a bit more like Fitbit. That is, it should make you feel like it’s working for you. A reader should say, ‘I’m reading everything I need to know.’”

Keep that dopamine pumping

Kat presented a multi-paned prototype. The wider pane on the right contained news content; the narrower pane at left was navigation. As I’ve just described it, this isn’t much different from the current Post website, but Kat’s prototype was very different, because it prized reader control over editorial director control; kept track of what you read; encouraged extra reading the way Fitbit encourages extra steps, and rewarded it the same way Fitbit does, with an accumulation of points that give the reader dopamine hits and create the perception that the “news app” is working for her—as a rewarding part of her busy lifestyle.

An Operating System for your city

Mike Swartz, Partner at Upstatement, a design and engineering studio in Boston, took on the challenge to smaller publications (such as his original hometown paper, the Pittsburgh Post-Gazette) which lack the resources of a Washington Post or New York Times.

Mike’s presentation, “information OS for a city: redefining the opportunity for local media,” turned the journalistic prowess of a good local paper into a superpower, connecting readers to their city the way the “terrible towel” stunt concocted in desperation by radio announcer Myron Cope in 1975 reconnected Pittsburghers to their hometown football team, and helped the Steelers win Super Bowl X over the Dallas Cowboys.

There’s a potential for an operation like the [Post Gazette] to rebrand itself as more of an “informational operating system” for its city. With different types of products that are focused and useful and not necessarily bundled into a traditional news format, we can create more enjoyable experiences and more useful products readers will love.

Building reader interest and finding a way to pay for it all

Lucie Lacava designed an app targeted at millennials.

Where the rest of us avoided the elephant in the room, in her design Lucie Lacava, president of Lacava Design Inc., boldly confronted the challenges of advertising and monetization. Algorithm-driven advertising frustrates users, who, in desperation, block it. Choked for income as a result, publications and advertisers create more and more intrusive forms of unwanted advertising. Nobody wins.

And while subscription models have worked, at least partly, for some of the very top news publications, such models are not likely to help most news publications in the near term.

Digital publication as digital application

Lucie’s design addressed these challenges by recasting the news as a hyper-customized application targeted at younger users, who get to choose news streams and ads that are relevant to them. “The elusive millennial” was Lucie’s target. I cannot do her idea justice with a couple of paragraphs and a single screen shot.

Affordable, immersive VR is here

Jared Cocken, brand and product designer for hire and co-founder of STYLSH.co., approached the “attention war” by showing how any size publication could create “video or VR driven stories that enrich a user’s understanding of the world around them.”

Because VR video is immersive, it holds viewer attention. Because it is reality-based, it fights fake news. (It’s hard to call bullshit on a scene you can explore from any angle.) VR also, potentially, builds compassion. It’s one thing to read about conditions in a Syrian refugee camp, another to visually experience them in VR.

Until now VR and video have been cost-prohibitive, but, working (and co-presenting) with VR startup founder Anna Rose and Hollywood producer/actor Banks Boutté, Jared showed how even woefully under-financed newsrooms can use newly designed, super-affordable tools to create “video or VR-driven stories that enrich a user’s understanding of the world around them.”

(For more on VR and the web, see webvr.info and VR Gets Real with WebVR by studio.zeldman’s Roland Dubois.)

Parting thought for now

Blogging about a conference is like tweeting about a sexual experience. You had to be there. I wanted to record and share the outlines of what my fellow designers presented, but these few paragraphs should in no way be considered authentically representative of the deep thinking and work that went into every presentation.

You may see holes in some of the arguments presented here. In some cases, I might agree with you—some ideas, while dazzlingly creative, did not seem to me like the right way to save news. But in most cases, if an idea seems wrong, blame my telling. If you had been there and heard and seen everything, the value of the proposal would have far more apparent than it can be here.

I love that each of us took on a quite different aspect of the problem, and addressed it using very different tools. I’ll be back soon with a short write-up of the design approach I took. Meanwhile, I want to thank all the pundits, designers, and attendees in New York and St. Petersburg—and the Poynter Institute, Roger Black, and William R. Hearst III for making it all possible.

 

Also published in Track Changes.

%d bloggers like this: