Category: Work

5 Thoughts About Unlimited Vacation

Processed with VSCOcam with t1 preset

A post on Paper Planes got me to thinking about vacation, and the nature of paid time off, and the way that great ideas can collide with the real world in unexpected ways. I also took a second look at Jacob’s great post about open vacation policies when writing this post.

  1. Open (or unlimited) vacation policies have counterintuitive results: again and again it turns out that when folks are simply given no upper boundary on their time off, they tend to take about average offered elsewhere, or somewhat less than average.
  2. We’re social animals: even with an open vacation policy removing the limits that an employer places on an employee, there exist other limits. Specifically, how much time off does my boss take? What about other folks on my work team? What are the consequences of taking frequent or lengthy vacations? These limitations aren’t placed on the employee by the employer, but rather exist in the mind of the employee – and prevent them (us!) from taking as much time as we perhaps need – or deserve!
  3. “What is measured can be managed” has a reverse: to offer an unlimited vacation policy, and then proceed to track the days taken off, resonates in an uncomfortable way – if after all, the policy is unlimited, why track? If the goal is to avoid managing the days off taken by employees, then measurement seems dissonant with that goal. I acknowledge this may be the result of legal requirements placed on HR by outside bodies – which is a difference that makes a difference.
  4. Track or not to track? Jacob says you must track vacation days for a few reasons, but mostly to ensure that there isn’t any implicit (or explicit!) biases at work. Mathias reports that they did not track days at first, but ended up tracking days off in order to require them. Automattic does track time taken off, likely for the same reasons that Jacob espouses it.
  5. Minimums and Paid-Paid Time Off: Companies have started to take the above four points and push the open vacation idea to the next level – minimum vacations, as described by Mathias, where employees have 25 mandatory vacation days. Or Evernote, who pays employees $1,000 when they take a week off, to ensure, one imagines, that they relax to the max.

Some part of this discussion reminds me of the discussion in Freakonomics, where Dubner and Levitt discuss a day care center that had a small number of parents who would consistently arrive late for child pickup – in order to fight against this, they imposed a $3 fine, and the unexpected result was that even more parents arrived late, the day care center replacing a moral penalty with a tiny financial penalty.

When we remove the upper limit of paid vacation, and also remove the motivating factors of the use-it-or-lose-it system, folks are left only with their own interpretations and psychological barriers – which lead to fewer trips to Aruba. And no one wants that.

(Yes, Daryl, I read Mathias’ company as “Tavis” as well. )

Ethnographic Fieldguide

From http://picography.co/

I’ve gushed before over Just Enough Research before, Erika Hall’s outstanding primer on UX research and thinking about research in a broader commercial sense, but this morning I came across a hidden gem.

In re-reading Chapter 5, I came across a link that I had missed before, to the Helsinki Design Lab – specifically their Ethnographic Fieldguide, a concise, delightfully Finnish document that outlines a manner of thinking and approaching research from an ethnographic perspective. What does that mean?

Ethnography aims to get under the skin of human behavior, to better understand the world and the specifics of the cultures we live in. The focus of the research can be anything from current cultural tendencies, to changing values, attitudes and norms, or concrete human behavior and its motivations within different situations and contexts.

You can find the Ethnographic Fieldguide, and learn more about the HDL, here.

More Speaking Resources!

tumblr_ndeqnctugu1sfie3io1_1280

In my ongoing quest to find and share resources to make myself and others better speakers, I sometimes find things that are useful, helpful, or just interesting. Here are two things I’ve recently come upon that have moved the needle on my presentation game: specifically how I build slide decks and what I put in them.

10 Tips on How to Make Slides from the folks at TED – if anyone knows anything about great slides, it’s TED.

In pursuit of their sixth tip, Use photos that enhance meaning, I’d like to introduce you to a resource I borrowed from Dave – a collection of collections, a meta-collection if you will: Stock Photos That Don’t Suck.

The featured image on this Post is from that list, specifically from New Old Stock.

Five Things I Learned About Live Chat

Computer_keyboard

This last weekend I made the move from our Akismet support team over to Team Hermes, a group of Happiness Engineers who cover live chat (that is, text-based chat support) for our regular paid users (That is, neither VIP nor Business), as well as covering in-app mobile support.

So, I spent my full work day yesterday deep in the live chat mines. Over a work day, I did 45 chats – not terrible for a first day! With only a single day of experience under my belt, here are a few early-stage insights on live chat as a medium of hospitality:

    1. Live Chat is very good at what it is very good at. Live Chat is, so far, good at two things: behaving like a human-powered search bar, answering questions with documentation or blog post recommendations, and debugging complicated problems with multi-step questioning. The trouble is when an operator has multiple chats that cover both flavors.

 

    1. Live Chat requires a different sort of focus than email or forum replies. Replying to an email allows a Happiness Engineer some space to explore and investigate and ensure that the reply is 100% correct as-is, a neatly-tied package that is ready to go. In Chat, there is a lot of uncertainty, and the need to balance multiple chat customers at once means you must be able to not only laser-focus on a single customer, you have to be able to switch between cases quickly with little time for recall.

 

    1. Live Chat requires a different mindset than email replies. Given the short time span between responses, there is no wall of authority in place: if an HE doesn’t know an answer, they have to admit it and then move forward with collaboration, a back-and-forth between the HE and the customer. In an email response, the HE would have time to research and be certain of their authority before replying. I like this ejection of ego from the equation; Live Chat feels much more “Let’s figure this out!” to email’s “Here is a solution.”

 

    1. Live Chat is not ideal for every problem: there were a few cases where I had to ask folks to seek support through other channels. These cases were big browser problems, where we needed full traceroutes to determine the underlying issue, and broad CSS customization, which, while something I _can_ do, would not be to the benefit of the rest of the folks waiting in the Live Chat line. Plus, our CSS Support Forum folks are so darn helpful!

 

    1. Live Chat would be a great tool for proactive, rather than reactive, support. I know that some companies use Chat on their sites as a sales lead generation tool – I think that in the pursuit of hospitality, offering Live Chat in an educational format would be a really outstanding application. Identify members of your team who are especially patient and tend to excel with new customers, and then create a Chat property specifically for the educational area of your site. Having a live human to work with might really change the onboarding process, and would at the very least help to illustrate where folks are getting caught up. In that way, educational Live Chat would serve both our user-facing hospitality needs as well as our hospitality-driven UX improvements by acting as chat-based user testing.

 

Today’s my second day – we’ll see how long the above remains true!

Automattic Lexicon: +t +d

Automattic is a fully distributed company; we all work from where ever we are, any flat surface with access to the internet. This comes with many benefits, as well as some curious downsides, but one of the most interesting things is the way that a fully global, exclusively-online working community interacts socially.

Like any group who spends time on the internet (ie in 2014, most groups) we are exposed to different memes and cultural references, and like any group, we create our own sort of tropes and references and inside jokes. One of these is “+t +d.”

20141102_144227

“+t +d” on the most superficial level is an abbreviation of an abbreviation – you begin with “Totally, Definitely,” which is reduced to save time and increase it’s cool factor, to “Totes Def,” which of course is naturally shortened even further to “+t +d.”

Yes, there are those who see this as an affront against the English language, a further breakdown of the same sort as emoji and text message shorthand. There’s something to that – I can see it both ways. However, I think that looking at this piece of the Automattic Lexicon and seeing it only as a shorthand is missing a bigger piece of the message here.

“+t +d” represents to me not just a quick affirmation, but rather an aspirational view of the way that Automatticians (and I would suggest all remote workers) have to approach The Work. “+t +d” is our version of “Yes, and…” the cornerstone to all great improvisational comedy. It represents a necessary positivity that absolutely needs to be injected into all of our work, and all of our interactions.

Working with people almost exclusively through text means that you have to be generous; you have to read only what’s on the page, and make assumptions only when they are justified and work toward a goal. It’s very easy to slip into negativity and read a message into a sentence that simply isn’t there – but if you maintain a sense of positivity, an ingrained automatic response of “Totally, definitely,” things work. Things flow. Great stuff is created.

Working with distributed teams on cohesive products means that you have to make space for error, and for oversight, and for outright missteps. Your response to these things cannot be defensive or accusatory, but rather “+t +d, what can I do to help?” – “+t +d, how can we fix this?” – pushing for the positive, for the tide that lifts us all rather than the torpedo that sinks.

Rick Steves, reknowned travel author and someone I consider a role model, talks about the need for militant optimism in travel – this resonates with me when I think about The Work. I think that “+t +d” is our militant optimism. It’s not always easy, and I’ve certainly fallen victim to defensiveness and pointing of fingers – but I try to stay positive. We all do. And from that trying, we’re able to work together, from all around the world, to make things that simply did not exist before.

+t +d everybody.