Overlay gap
Tags: overlays, mobile, design, ui
Published: 2020-04-27 11:18:39

---
title: Overlay gap
published: true
date: 2020-04-20 15:39:33 UTC
tags: overlays,mobile,design,ui
canonical_url: https://adactio.com/journal/16786
---

I think a lot about [Danielle’s talk at Patterns Day last year](https://vimeo.com/showcase/4673650/video/345903813).

<iframe src="https://player.vimeo.com/video/345903813" width="426" height="240" frameborder="0" allow="autoplay; fullscreen" allowfullscreen></iframe>

[Around about the six minute mark](https://vimeo.com/showcase/4673650/video/345903813#t=374s) she starts talking about [gaps and overlaps](https://clearleft.com/posts/workplace-topology).

> **Gaps** are where hidden complexity live. If we don’t have a category to cover it, in effect it becomes invisible. But that doesn’t mean it’s not there. Unidentified gaps cause inconsistency and confusion.
> 
> **Overlaps** occur when two separate categories encompass some of the same areas of responsibility. They cause conflict, duplication of effort, and unnecessary friction.

This is the bit I keep thinking about. It’s such an insightful lens to view things through. On just about any project, tensions are almost due to either gaps (“I thought someone else was doing that”) or overlaps (“Oh, you’re doing that? I thought we were doing that”).

When I was [talking to Gerry on his new podcast](https://www.thisishcd.com/episodes/world-wide-waste-with-gerry-mcgovern/jeremy-keith-weve-ruined-the-web-heres-how-we-fix-it/) recently, we were trying to figure out why web performance is in such a woeful state. I mused that there may be a gap. Perhaps designers think it’s a technical problem and developers think it’s a design problem. I guess you could try to bridge this gap by having someone whose job is to focus entirely on performance. But I suspect the better—but harder—solution is to create a _shared_ culture of performance, of the kind [Lara wrote about in her book](http://designingforperformance.com/changing-culture/):

> Performance is truly everyone’s responsibility. Anyone who affects the user experience of a site has a relationship to how it performs. While it’s possible for you to single-handedly build and maintain an incredibly fast experience, you’d be constantly fighting an uphill battle when other contributors touch the site and make changes, or as the Web continues to evolve.

I suspect there’s a similar ownership gap at play when it comes to [the ubiquitous obtrusive overlays that are plastered on so many websites these days.](https://twitter.com/lukew/status/1169826669735006209)

Kirill Grouchnikov recently published a gallery of screenshots showcasing [the beauty of modern mobile websites](https://www.pushing-pixels.org/2020/02/26/the-beauty-of-modern-mobile-websites.html):

> There are two things common between the websites in these screenshots that I took yesterday.
> 
> 1. They are beautifully designed, with great typography, clear branding, all optimized for readability.
> 2. I had to install Firefox, Adblock Plus and uBlock Origin, as well as manually select and remove additional elements such as subscription overlays.
> 
> The web can be beautiful. Except it’s not right now.

How is this dissonance possible? How can designers and developers who clearly care about the user experience be responsible for unleashing such user-hostile interfaces?

> [PM/Legal/Marketing made me do it](https://twitter.com/lukew/status/1166069177276256256)

I get that. But surely the solution can’t be to shrug our shoulders, pass the buck, and say “not my job.” Somebody designed each one of those obtrusive overlays. Somebody coded up each one and pushed them into production.

It’s clear that this is a problem of communication and understanding, rather than a technical problem. As always. We like to talk about how hard and complex our technical work is, but frankly, it’s a lot easier to get a computer to do what you want than to convince a human. Not least because you also need to understand what that other human wants. [As Danielle says](https://clearleft.com/posts/workplace-topology):

> Recognising the gaps and overlaps is only half the battle. If we apply tools to a people problem, we will only end up moving the problem somewhere else.
> 
> Some issues _can_ be solved with better tools or better processes. In most of our workplaces, we tend to reach for tools and processes by default, because they feel easier to implement. But as often as not, it’s not a technology problem. It’s a people problem. And the solution actually involves communication skills, or effective dialogue.

So let’s say it is someone in the marketing department who is pushing to have an obtrusive newsletter sign-up form get shoved in the user’s face. Talk to them. Figure out what their goals are—what _outcome_ are they hoping to get to. If they don’t seem to understand the user-experience implications, talk to them about that. But it needs to be a two-way conversation. You need to understand what they need before you start telling them what you want.

I realise that makes it sound patronisingly simple, and I know that in actuality it’s a sisyphean task. It may be that genuine understanding between people is the wickedest of design problems. But even if this problem seems insurmoutable, at least you’d be tackling the _right_ problem.

Because the web can’t survive [like this](https://twitter.com/HugdiSpencer/status/1171487383008579584).