Backhanded positivity

My MacBuntu

I’ve switched all my writing activities over to a MacBook running Ubuntu.

I can’t say why exactly – maybe it’s just a honeymoon thing? – but I feel much better using this machine.

I think it might be this: I prefer suffering from awful design done by well-meaning coders who can’t design worth a shit, over suffering from awful design done by world-class design talents who use dark patterns to wring desired behaviors and dollars out of me.


The pitfalls of rapid, piecemeal design

When you design really rapidly, piecemeal, driven by the need to keep developers busy, it is impossible to design systematically. This means big glaring oversights wherever the design team fails anticipate a specific user need in order to design for it. The faster designers are driven, and the more they must focus on the details without reference to the system that gives the details a logical place within a whole, the more these oversight holes will riddle an experience. If the designer didn’t imagine you doing what you’re trying to do, you’re out of luck.

When designers work systematically, it is not necessary to anticipate every particular user need. Users might even find new uses beyond those intended or even conceived by designers. The tool has its own logic that is adaptable to many situations.

I hate the idea that the radical user-centricity I’ve championed for decades might have helped contribute to the degradation of user experiences.

Service malpractice

Feature idea for Notability

I just submitted a feature request for Notability:

I have an idea for a service Ginger Labs could offer to Notability users. Imagine this scenario: a user is experiencing some kind of technical issue. With the concept I’m proposing, the user could contact Ginger Labs and receive help resolving that problem. My hypothesis is that this would serve user needs more effectively than the current service, which consists of the user submitting a help ticket and receiving a message assuring them that “nothing is more important to us than helping you”, followed by literally months and months of apologies for not yet addressing the issue.

Organizational incompetence

Bullshit and chickenshit

Much of what happens in organizations can be classified under two categories: bullshit and chickenshit.

Bullshit is that class of lofty, uplifting, meaningful-feeling words and gestures that seem to promise something of enormous importance — but that important something can never be fulfilled through any practical action.

Chickenshit is that class of practical activities that seem like they ought to contribute in some way to some important end — but, in fact contribute nothing of any value to anything that matters.

Bullshit is meaning without practice. Chickenshit is practice without meaning.

Bringing together meaning and practice, so meaning inspires action toward a realizable vision, and practical actions contribute to realizing this meaningful vision — this is one of design’s key functions.

Another key function of design is to ensure the design is good, both in vision and execution: that it does something useful for people, that people find it easy to learn, use, and master, and that people enjoy using it. A good design will be chosen, used and recommended.

Design leads the conception and actualization of good, practical, visions.

When design is allowed to do its work, it helps groups of people align on a genuinely good, meaningful and achievable vision and helps them see the big, intricate picture of how diverse disciplines can coordinate their efforts and contribute to achieving this vision. Design then helps keep this alignment intact through implementation and subsequent release cycles, so that the meaning envisioned is realized and maintained in practice.

When design is not allowed to do its work, which is almost all the time, blathermouth executives give inspiring talks and emails, get their comms people to hang inspiring posters everywhere, and generally slather their organizations in bullshit, before disappearing into conference rooms to do very prestigious chickenshit all day.

Their subordinates ignore the bullshit and do their less prestigious chickenshit, which is laboriously measured and tracked for no good reason, except to provide other people the chance to do some chickenshit.

Sometimes employees are herded into rooms for bullshit workshops, while chickenshit accumulates in high acrid heaps back at their desks.

If, by some miracle, a good, practical vision is designed in this workshop, that vision is unlikely to survive what happens after. In subsequent meetings the vision gets divided into initiatives, then subdivided into work streams and hauled to far-flung silos, where the work is chopped and diced into chicken turd-sized tasks and poured into a backlog. The backlog is emptied, task by task, by people who have no idea how this important-seeming work will contribute to anything that matters.

And when all the bits of work are complete, it’s all globbed back together in a form that barely resembles the vision. That’s ok, though. The executives re-emerge from their conference rooms to do an all-hands where they bullshit on and on about how this chickenshit frankenstein is the realization of a vision that could never have happened without the dedication and leadership of everyone, especially of whatshername and so-and-so, and they hand out recognitions, promotions, layoffs and such. They then file back into their conference rooms for more very prestigious chickenshit.

A bullshit press release is issued.

Then there’s a major software release. Or maybe there is some change to core services. Or a new generation of product hits the stores. And all the customers and users who have to deal with these “improvements” get to figure them out and adjust their lives to accommodate them. They’re all inconvenienced, confused and frustrated, but there’s nowhere else to go, because the competitors are just as chickenshitty and bullshitty. Business as usual. Bullshit and chickenshit.

Moral: Organizations — entire industries, in fact — export their dysfunction to the larger world in the form of bad design: bullshit-coated chickenshit.

Service malpractice

“Your call is very important to us”

Hey, companies, please listen. When you put people on hold for long stretches of time, or when you take days and days to respond to a help ticket, how about dropping that bullshit about how important this call or this help request is to you? Because it is not important to you, and your blather does nothing but add another redundant drop of cynicism into the infinite bullshit ocean we’re all drowning in. 

The cliche is true, far truer than your marketing blather: Actions speak louder than words. The fact that we have all learned to expect long waits, says very loudly: “We know you’ll put up with this.”


OK, customers, now I’m talking to you.

These companies who claim to care so much about your very important call have calculated exactly how long they can make you wait without losing your business. They track it carefully. They know who drops off and they know the bottom-line consequences of drop-offs.

Shortening your wait time would require hiring more customer service personnel. That is expensive and most companies don’t want to spend money to make you any happier than they have to. They want to spend the least amount possible to keep your business and they want to pocket the rest.

Sadly, that customer service representative (CSR) who finally does speak to you after that long, infuriating wait might very well care how you feel. Many of them dearly want positive interactions with the people they speak with all day every day. But they are “the throat to choke”. Yelling at the CSR is yelling at the company. And so they are yelled at, harangued, bullied and threatened all day. Customers ask their names and address them by name frequently in an oh-so-savvy attempt to signal how they will be held accountable for how things go.

These CSRs are tracked closely and scored. They are supposed to keep your call as short as possible, so they can move on to the next pissed-off customer, and the next, and the next — as many as possible, to squeeze the most value out of them. The call centers are understaffed, so it is important to keep prodding them snd keeping them trotting as briskly as possible through their endless call queue every minute of the day.

CSRs are also scored on how much they can upsell and cross-sell to these customers, who are very much not in the mood to be upsold or cross-sold after sitting on hold listening to “we care” bullshit for the better part of an hour.

And then when it is all over, the customer evaluates them on how satisfied they are. Good luck, CSR.

And, understand: these CSRs are surrounded by posters and banners and huge screens that assure them that Our Employees Are Our #1 Asset. We Appreciate Our Employees. Teamwork Makes the Dream Work. And So On. They too are subjected to empty words belied by the most conclusive demonstrations of the emptiness of the empty words — but your bullshit sentence time lasted 20-40 minutes. Theirs is every minute of every day.  

Meanwhile, the folks creating all this misery are far, far away, hiding behind data dashboards, business intelligence applications and spreadsheets and totally out of earshot of your complaints. The only thing they hear from you is your complacent sticking around for more abuse, always almost, but not quite ever, willing to tell them to fuck off.

Moral: Most customer misery is produced backstage, far from view of customers, and the same misery affects everyone you’ll ever be allowed to talk to. So be nice to those poor front line people trying to help you. Instead, quit. If you can, discontinue your service online, so you don’t make that poor CSR’s day worse by putting a cancellation on their scorecard.


Apple atrocities

Pasting with formatting

Why is the default paste on nearly every application “paste with formatting”? Is that really what most users want most of the time?

Has anyone even looked into it? From all appearances nobody has. Every app has “paste with formatting” as the default, and has created its own unique, complicated and counterintuitive multi-key combo to get “paste without formatting”. Since it is different in every app we never learn it. We use the menu, or develop awkward workarounds to shed the formatting.

But somehow worse than this is Apple’s implementation in Mail on iOS. Get a load of this: there is no paste without formatting option at all. There is no “remove formatting” or “set to default” option, either. The normal formatting of the email must be manually applied, parameter by parameter.

So imagine a scenario where a very bitter user named Stephen sees a headline on a website set in 72 point Jackass Sans Bold Italic from one of those eye-destroying light-on-dark night formats ever design lemming in the world has decided on masse to make the norm. If this angry little Stephen person tries to copy this headline and paste it into an email to the last person on earth willing to listen to his bilious spew, he will have to first find and select the white text he just pasted, which is completely invisible against the white background of the email, then manually reformat it to match the typeface and size the rest of the email is set in, whatever that is.

Let’s just hope this Stephen guy has a blog dedicated to shit design where he can vent his fury. When bad design is your muse, your inspiration will heave forth endlessly.

Moral: Always, always, always offer “paste without formatting”, and maybe even consider making that the default. Just because every other designer is doing something, that doesn’t mean it is the smart thing to do. I swear, designers are some of the most conformist innovators you’ll ever meet.

Dumb ideas

Everyone is not a designer

A great many people, many of whom are not professional designers, have begun telling people that they are designers.

Consequently, a great many people who have never systematically practiced design have come to expect acknowledgment of the fact that they designers, and they especially come to expect this from professional designers.

A professional designer who won’t embrace everyone else as fellow designers is a snob or a jerk.

Well, I happen to be one of these snobbish jerks.

I have good reasons for this, in addition to actually being a snob and a jerk.

For one thing, part of my job is attempting to get other people to do design, and I’m here to tell you: a lot of people suck at it and can’t do it.

For another, I have to use things that non-designers have designed or product managed, and that has led to the miserable existence of this garbage blog.

Now, of course, the idea that everyone is a designer is not entirely wrong. After all, we do all design, sometimes multiple times a day.

But does this mean that everyone is a designer? Isn’t a designer someone who has put enough effort into developing design skills that they’re good at it? I mean, think about it. Everyone prepares food. Do we go around claiming that everyone is a chef? Don’t we reserve that term for someone who has deliberately cultivated their cooking skills?

It is strange to me that out of all the professions, it is design that is required to flatter everyone else that they’re also designers.

Now I’m all for the idea that everyone can and often should participate in design.  I’ll also say that most people could benefit if they improved their design skills. Some people have talent and can potentially improve their design skills a lot and become really great designers. And a great many people just don’t have the ability and temperament and won’t ever get that good at design. So what? Nobody’s good at everything.

So, everyone designs. Not everyone designs well. Not everyone cares if they design well or not. Some think they design well, because they aren’t even clear on what a designer is supposed to do, and don’t bother going about it the right way.

Those who do care if they design well, and work at figuring out the best methods for doing it well, and then practice these methods in order to get better and better at them — those are the people we should call designers.

Moral: Until we say that everyone who cooks is a chef, everyone who obeys the law is a lawyer, everyone who speculates on other people’s minds are psychologists, everyone who puts a bandaid on a cut is a doctor, everyone who has a theological opinion is a priest, everyone who believes in gravity is a physicist — let’s please fucking stop saying everyone is a designer.


1Password on iOS

Cloud computing sounds so ethereal, ubiquitous and all-enveloping, doesn’t it? All your data is up there and if you reach up, as if reaching for the stars, the data is just there for you.

Bullshit. It never is. The data gets all constipated and backed up in some corner of your device or detained in some very physical and faraway data center and is more often than not unavailable where and when you need it, creating an impression less of ubiquitous availability than of arbitrary belligerence.

You take you duckface selfie on your phone and it is supposed to also be on your computer, too, like magic. Except it isn’t. And these software wizards seem to think it will spoil the effect if they give you any visibility into the kludgy syncing process that’s stalling out, so you can, you know, know what the fuck is going on with your photo.

These cloud companies behave like bad magicians. They prance about and carry on as if everything is going just beautifully, and nobody is noticing that nothing is working right. But all the dramatic cape swooshes and wand waving only highlights how badly the trick has failed. Oops, no rabbit in the hat, but ta-da, anyway.

(By the way, when I am in charge, companies will have to prove they can pull off cloud-computing effects before using the word “Cloud”. Those who can’t will be required to use a more appropriate description: “Sky-Gravel Computing”.)

But 1Password in iOS is a whole new level of spastic. They can’t even sync between their app and their own plug-in. And this is not an occasional annoyance. This is every single time I make the mistake of setting up a new account on an iOS device. I’ll go to the 1Password app and enter a new login and password. Then I’ll try to pull up the 1Password plug-in, and it’s never heard of any of it.

It’s like how many nanometers to sync a handful of bytes across? You can’t even cloud compute a minute string of data across the space of a single device? I’m sure it is all super-damn technical and complicated. But again, if you can’t pull off an operation as expected, don’t say “ta-da.” Just put a message up explaining that Apple’s made it impossible for our developers to make the scattered chunks of 1Passwork functionality work in a graceful coordinated fashion, probably because they are hobbling our product so everyone will use their even worse Keychain password mismanagement. And to help it along, do these fourteen easy steps, or just wait around for x number of minutes. Whatever. Just let me the status of the sync. Handle it like Palm Pilot did back in 1997 and say what’s syncing from where to where until it finishes. It’s not magical, but it is something far better: it helps me know what is going on.

Moral: If you can’t pull off a magical effect, don’t attempt magic. Observe the limits of your technology and design within what the technology can do gracefully. You might be proud of pushing the technology beyond its limits, but frankly, what has been actually been pushed beyond its limits is your own competence.


And yes. This 1Password tantrum was ignited in the process of trying and failing to get this shitty blog up working with the WordPress iOS app. I had to write this whole diatribe on a browser based WordPress interface. That, of course sucked, because it defaulted to “block editing” which is pointless and distracting. For no fault of my own, half my paragraphs are inside a block and half are not. I’m leaving them looking all misspaced and stupid purely out of spite. I’m sure my fruitless attempts to disable this scope-bloating impediment will be the topic of the next post.


WordPress again

Honestly, I have no one to blame but myself for installing WordPress again, knowing its current toiletward trajectory.

Of course, I know it will suck right away. But, because I’ve been using WordPress since the long-past days when it was actually good, I know from painful experience that this suckiness will positively pale in comparison to the suckiness of the next ill-conceived update to WordPress, where they will break the remaining functioning remnants of this demented mess with some product manager’s vision of how other people ought to want to work. Because what is WordPress other than a vehicle for some ambitious jackass’s ego bloat and career advancement?