Menu

Posts tagged “culture”

The challenge with remote work is what happens next

Sticking with the theme of remote work, Steven Sinofsky wrote a great post called Why Remote Engineering Is So Difficult!? There’s a lot of food for thought, but here’s the main issue:

The core challenge with remote work is not how it is defined right here and now. In fact that is often very easy. It usually only takes a single in person meeting to define how things should be split up. Then the collaboration tools can help to nurture the work and project. It is often the case that this work is very successful for the initial run of the project. The challenge is not the short term, but what happens next. […]

If I had to sum up all of these in one challenge, it is that however you find you can divide the work across geography at a point in time, it simply isn’t sustainable. The very model you use to keep work geographically efficient are globally sub-optimal for the evolution of your code. It is a constraint that creates unnecessary tradeoffs.

Projects often start off ok, but then start to unravel as every small miscommunication and missed messages add up to a much bigger problem. I find this stuff fascinating not just because I work at Jive (where we don’t use email at all), but because we’re seeing such an explosion of remote work everywhere as our tools keep getting better and better.

Steph Yiu’s post Still figuring it out: communicating remotely with lots of people is another good one to read, since she walks through all the tools they use to get their work done. Our setup at Jive is very similar, except that we use our own tool where they use P2 (their Wordpress intranet theme).

Smart cities and dumb technologies

Adam Greenfield reminds us that the “smartness” of technologies comes from the people who use it, not the technology itself. From The smartest cities rely on citizen cunning and unglamorous technology:

It’s simply that in both these cases, the sustaining interactivity was for the most part founded on the use of mature technologies, long deglamorised and long settled into what the technology-consulting practice Gartner refers to as the “trough of disillusionment”.

The true enablers of participation turn out to be nothing more exciting than cheap commodity devices, reliable access to sufficiently high-bandwidth connectivity, and generic cloud services. These implications should be carefully mulled over by developers, those responsible for crafting municipal and national policy, and funding bodies in the philanthropic sector.

I like the term “deglamorised” very much. It’s a reminder that our goal as designers isn’t to make cool stuff—it’s to help people do great things with the stuff me make.

Technology and time fixing vs. time working

I really enjoyed Eddie Smith’s The ascent of failure, a post on the many ways our technology can fail us. He starts off with a parenting story that’s infinitely relatable, and goes on to make some good points about how fiddly we’ve become with our technology:

With Yosemite and iOS 8, we have even more interdependence through features like Handoff. Now, a MacBook, iPhone, and iPad are no longer three things but a system of things—an ecosystem with an even higher chance of failure by virtue of sitting atop an ever-rising house of cards.

I think it’s worth pondering the time we spend fixing our tools and toys versus the time we spend solving problems and actually getting to play.

I’m not convinced that having complex tools is a necessary condition for achieving remarkable results.

Maybe this non-complexity is another reason why vinyl is seeing such a revival. Or why paper notebooks are making a strong comeback, spurred on by brands like Field Notes, Moleskine, and the one I personally use (and love): Baron Fig.

When only some workers in a company are remote

There are lots of great points in Chris Hardie’s Distributed vs. In-Person Teams, an article on the challenges and opportunities of remote work. But this part, in particular, stood out because I’ve experienced it myself:

Having some remote workers is harder than being fully local or fully distributed. […] This dual approach is probably a recipe for disaster when it comes to building shared vision and common culture in an organization. If there are team members who have a daily experience of being in the same space together and sharing all of the quirks and benefits of that, remote workers will almost always feel excluded in some way, culturally, logistically or both. When only part of the team is forced to consider the implications of having a distributed group, an unfair burden falls to the remote worker to keep their needs in front of everyone else. At best it adds a weird kind of tension to team relationships, and without incredible discipline and initiative, it probably won’t work in the long run.

This gets even worse when the remote workers are in different time zones. The remote workers are almost always the ones who have to give up their evenings to do Skype calls.

The real reason for vinyl

Dave Pell in a short note about music streaming, radio, and high-res audio:

I’m at the tail-end of a pretty severe audio-related midlife crisis (related: Anyone want to buy some vinyl?) and I’m convinced that the return to Vinyl and the quest for audio excellence has less to do with sound quality and more to do with nostalgia for what listening to music used to be — an often communal activity that required focus and was more than just a soundtrack for whatever else you happened to be doing at the moment.

As someone who is at the beginning of his vinyl-related mid-life crisis, Dave’s words really resonated. Yes, I’m chasing upgrades and better sound, but I also know that one of the real reasons I’m doing it is because I get to sit on the floor with friends and nerd out about music:

Yes, it makes me write pretentious pieces on Medium about “the experience” of vinyl, and I feel a little bit embarrassed about that. But on the other hand, maybe it’s ok. I think it’s possible to be self-aware about the real reason why we do things, yet still embrace what we thought it represented and enjoy that. I have to believe it’s possible to hold those opposing things in my head without spontaneously self-combusting. And you know what, if my chase for audio excellence is actually about a chase for closer connection with other people, it’s probably ok anyway.

That’s my story and I’m sticking with it.

Expanding our technology worldviews

A couple of weeks ago Andrew Watts published A Teenager’s View on Social Media, and the post got a lot of attention. Most of the tech world linked to it. Today, danah boyd (whose work researching teen use of social media I highly admire) published a response called An Old Fogey’s Analysis of a Teenager’s View on Social Media. She makes some excellent points about how the story was reported, particularly the narrative that was built around one person’s experiences:

I don’t for a second fault Andrew for not having a perspective beyond his peer group. But I do fault both the tech elite and journalists for not thinking critically through what he posted and presuming that a single person’s experience can speak on behalf of an entire generation. There’s a reason why researchers and organizations like Pew Research are doing the work that they do — they do so to make sure that we don’t forget about the populations that aren’t already in our networks. The fact that professionals prefer anecdotes from people like us over concerted efforts to understand a demographic as a whole is shameful. More importantly, it’s downright dangerous. It shapes what the tech industry builds and invests in, what gets promoted by journalists, and what gets legitimized by institutions of power. This is precisely why and how the tech industry is complicit in the increasing structural inequality that is plaguing our society.

Our church is doing a series on social justice at the moment, leading up to MLK day. Yesterday the amazing Michelle Jones read a section of Maya Angelou’s eulogy to Coretta Scott King, and those words seem to fit well with danah’s piece and the conversations we’ve been having in the US recently:

Many times on those late evenings she would say to me, “Sister, it shouldn’t be an ‘either-or’, should it? Peace and justice should belong to all people, everywhere, all the time. Isn’t that right?” And I said then and I say now, “Coretta Scott King, you’re absolutely right. I do believe that peace and justice should belong to every person, everywhere, all the time.”

And those of us who gather here, principalities, presidents, senators, those of us who run great companies, who know something about being parents, who know something about being preachers and teachers — those of us, we owe something from this minute on; so that this gathering is not just another footnote on the pages of history. We owe something.

I pledge to you, my sister, I will never cease.

I mean to say I want to see a better world.

I mean to say I want to see some peace somewhere.

I mean to say I want to see some honesty, some fair play.

I want to see kindness and justice. This is what I want to see and I want to see it through my eyes and through your eyes, Coretta Scott King.

If we’re going to see justice, honesty, and fair play, we’re going to have to step out of what we know and what we’re comfortable with, and speak up (and do up) to do our parts to bring others along with us. And that means, at the very least, to change our perceptions of the tech world and the people who use the things we make. I’ve written before about the digital usability divide (what danah calls “increasing structural inequality”), and I only see it getting worse unless we — who make the web — get a better understanding of all demographics.

You're even righter than you think

Oh man, Some 2015 Predictions on The Awl is so good. It’s hard to pick a favorite, but if I have to:

No human, for the entirety of 2015, will be convinced of anything but his own rightness by any “explainer” site. They will become extremely popular, fully stocked with “Perfect Response” and “Reasons Why” posts that are first and foremost affirming to the reader, and secondarily intended to demonstrate the rightness and virtue of the sharer. One high-growth post-type in 2015: “You’re Right, But For Even Better Reasons Than You Think.”

Why Apple has a successful design culture

I’m not a big fan of these types of articles, but I did like Mark Kawano’s point about what makes Apple a successful design organization in 4 Myths About Apple Design, From An Ex-Apple Designer:

It’s actually the engineering culture, and the way the organization is structured to appreciate and support design. Everybody there is thinking about UX and design, not just the designers. And that’s what makes everything about the product so much better … much more than any individual designer or design team.

If everyone cares about design, the usual mantra that “UX is 50% design, 50% politics” turns into a much more manageable ratio.

The downsides of tracking everything about ourselves

As is often the case with these things, I just noticed two articles that make very similar points about the quantified self movement. In Quantify Thyself LM Sacasas makes the point that we don’t know what we don’t measure:

Not only do we tend to pay more attention to what we can measure, we begin to care more about what can measure. Perhaps that is because measurement affords us a degree of ostensible control over whatever it is that we are able to measure. It makes self-improvement tangible and manageable, but it does so, in part, by a reduction of the self to those dimensions that register on whatever tool or device we happen to be using to take our measure.

In a similar vein, Anne Helen Petersen has a great piece on Buzzfeed called Big Mother Is Watching You: The Track-Everything Revolution Is Here Whether You Want It Or Not. Here’s the kicker:

But there’s something to be said for the allure and beauty of the mysteries not only of our confusing, previously unknowable bodies, but the intricacies of life. For the daily banalities of tuning the thermostat, or of knowing you had a good night’s sleep because you feel good, not because an app indicated as much. For the pleasure of running without knowing how fast or how long or how many calories but simply because your body could and did move, and that even without a digital trace, a GPS footprint, or way to leverage evidence thereof against friends and co-workers — it nonetheless felt something like being alive.

What makes online collaboration successful

Smarther Than You Think

I just finished Clive Thompson’s Smarter Than You Think: How Technology Is Changing Our Minds for the Better and really enjoyed it. So much of what we read about technology these days is doom and gloom that I wanted to spend time on something a little more positive. And turns out, there’s much to be positive about.

There are many stand-out moments in the book. One is the exploration of ambient awareness — how social media often makes our in-person connections stronger because we know so much about each other’s minutia that we can skip the small talk and jump straight to the important stuff when we see each other. But the part I want to elaborate on a little bit here is what historical events tell us about the important criteria to meet for collective thinking to be successful.

Clive points out four important aspects of successful online collaboration:

  1. Collective thinking requires a focused problem to solve. One disastrous story Clive tells is when the LA Times create a wiki page on the Iraq War and encouraged people to edit it. No focused outcome = a rapid decline into the bottom half of the internet. But give people a common problem to solve — like “Which tent hospitals in Cairo need help, and what do they need?”, and people start to shine together.
  2. Collective problem solving requires a mix of contributors. Specifically, it needs to have really big central contributors, and then a lot of people making small contributions to push the solution forward. As Clive puts it, “these hard-core and lightweight contributors form a symbiotic whole,” coming up with the best solution in the fastest possible way.
  3. Collective thinking requires a culture of “good faith collaboration”. Contributors need to struggle constantly to remain polite to each other. And it is a struggle, but a necessary one. As Anil Dash once said, if your website’s full of assholes, it’s your fault.
  4. To be really smart an online group can’t have too much contact with each other. This sounds counterintuitive, but the evidence supporting the point is pretty overwhelming. Clive goes over a few examples that shows that “traditional brainstorming simply doesn’t work as well as thinking alone, then pooling results.” This also explains why Design Studio is such an effective way to solve design problems. So one of the secrets of online collaboration is that it “inherently fits the model of people working together intimately but remotely,” as Clive puts it.

There’s much more to say about the book, but I think I’ll stop here and just encourage you again to read it. You’ll agree with a lot of it, disagree with some of it, and think about all of it for days after finishing it. That’s all we could ever ask of a book.