John D. Cook writes some scary true words in Productivity and negative space:

People who fracture their time putting out fires seem more productive, or at least more responsive, than the people who block out time to think. It’s harder to notice someone not being frantic. Thinkers don’t fare well in environments that reward activity more than accomplishment.

This is such a huge problem in big corporations today. People who are running from meeting to meeting are perceived to be more productive than those who sit at their desks working all day[1]. And the problem is worse for programmers - very few managers understand what they do, so it’s hard for them to stomach days and days of solid coding without seeing something “tangible” (in their view).

It all comes back the difference between Makers and Managers, and how the Makers should be evaluated on completely different criteria than the Managers. Criteria that reward the quality of what they make, not the number of status updates they give.

(link via Graham Poulter)

---

1. I’m not saying that people who have a lot of meetings are necessarily less productive, just that those who are not in meetings are “out of sight, out of mind”, and therefore not seen as particularly productive.  â†©

I love pretty much everything Frank Chimero writes, and his essay on the meaning of design from a few weeks back still rings in my ears:

We should care more about our craft because w’re granted an opportunity to contribute to the world. We should care more about what we say because each time we speak, ther’s someone there to listen. We should care more about our audiences because they are the ones who give our work value. We might think that design work is about you or about me or anyone else who makes it, or maybe about the things that we make and the artifacts we produce, but don’t let this way of thinking fool you. The things we make are all just excuses to speak with one another and to help one another. We are all linked, and the things that we make for each other strengthen the invisible threads that tie us all together.

Many people won’t agree with this sentiment. Many will think it’s silly to think about something as trivial as web design in this grandiose way. They’ll remind us that we’re just making web sites, not saving the world. And that’s fine - not everyone is going to care as much about design, or even understand why some of us do.

But I do care. I care because I think we have the opportunity to shape a technology that is at once exhilarating and dangerous. A technology that has the massive opportunity to bring people closer together, if we can just keep it together long enough not to destroy each other in YouTube comments and flaming blog posts.

So, yes, I care a lot about this, probably more than I should. But I’m with Frank on this: everything we do is just an excuse “to speak with one another and to help one another.”

I’m still slowly making my way through Sherry Turkle’s Alone Together, and this quote really jumped out at me this morning:

We have to love our technology enough to describe it accurately. And we have to love ourselves enough to confront technology’s true effects on us. These amended narratives are a kind of realtechnik. The realtechnik of connectivity culture is about possibilities and fulfillment, but it also about the problems and dislocations of the tethered self. Technology helps us manage life stresses but generates anxieties of its own. The two are often closely linked.

It seems like everyone was looking for developers at this year’s Tech4Africa conference. We heard some fantastic startup ideas, and each pitch was usually punctuated with something like, “And if you know any good developers, please let me know.” Cennydd Bowles made the following observation after the first day of the conference:

I understand and support the rush to find good developers because I love all the local ideas entering the market (much of my own talk at Tech4Africa was dedicated to improving developer environments). But I’m concerned about tech startups[1] going on the hunt for developers without also looking for quality User Experience Design skills at the same time[2]. In Tart Up Your Startup! Erika Hall explains the dangers of ignoring UX in startups:

You are making UX design decisions as soon as you specify anything you expect another human to interact with, as soon as you specify anything that has implications for how a human might interact with it. Of course, you are are also making system design decisions, but we assume you are comfortable with that sort of thing.

So don’t pretend like you aren’t making design decisions already. And don’t make them by omission. You cannot NOT design something. The floor of Silicon Valley is littered with the crumbling husks of great ideas””useful products and services that died in the shell before they hatched out of their impenetrable engineering-specified interfaces.

So if this is so important, why are most South African tech startups (and large companies, for that matter) not looking for UX designers? In this article I’d like to explore what I believe the three main, interconnected explanations are, and how this is actually an opportunity for the design community to prove the value we can add to product development. I’d love to hear your thoughts and observations on this topic as well. If you think I’m missing the boat, please let me know.

1. Hiring is expensive

A very legitimate concern most startups have is that hiring people costs a lot of money, and making the wrong decisions on who to get involved can be extremely costly. So naturally the first requirement is a developer who can actually build the product. It’s logical, and the prudent thing to do. The danger is that you could end up wasting a lot of money by going down the wrong path if you don’t have design skills on board from the beginning.

It also has to be said that in some cases, startups take the considered approach to, as Erika Hall puts it in her article, “Get your nerds to swot up on usability principles and muddle through, yo.” It’s definitely an option, but if it doesn’t work it can turn out to be an expensive detour.

2. Limited visibility into the value of User Experience Design

As we were discussing this topic over breakfast at the conference, @ndorfin brought up the point that for most people, Design still means Graphic Design, or more specifically, Graphic Design for print. So it’s no surprise that tech startups don’t think about the need for a designer - they don’t see the value that something like billboard design could bring to their interactive product.

UX is, of course, a much larger concept used to describe the process of understanding a market and finding solutions that work for that market. User Experience Designers solve problems by uncovering user needs and helping to create products that meet those needs. Until an understanding and appreciation of the benefits of UX become pervasive in the South African tech space, it will not be highly sought after.

I want to be very clear about this. It’s not the tech community’s fault that the benefits of UX are generally not well understood. It’s our fault. As designers it is our responsibility to show others the value of what we do in a convincing way (i.e., irrefutable evidence of revenue/conversion increases). We can’t expect people to come ask us what we do like w’re at a high school dance waiting for someone to notice us. We have to make ourselves known, and do it loudly.

3. The current maturity level of User Experience Design in South Africa

UX is still in its infancy in South Africa. In @cennydd and @boxman’s session at Tech4Africa called March of the UX Designers they shared their views on the maturity cycle of a particular skill set in an organization. They talked about six distinct stages:

• Unrecognized
• Interested
• Invested
• Committed
• Engaged
• Embedded

Most organizations in the US and UK have reached at least the stage where everyone is committed to making UX a priority. Some are engaging people from multiple disciplines in the process, and others go so far as to have deeply embedded cultures of Design. In most South African organizations it feels like User Experience Design is still mostly unrecognized, or at best something ther’s mild interest in (with a few notable exceptions).

Again, I want to be clear that I’m not passing judgement here. I’m simply pointing out that we are at the beginning of a natural cycle that the UK and US have gone through as well. It’s a cycle we should be aware of, but it shouldn’t paralyze us. It’s actually an exciting place to be - we have an opportunity to make a real difference to how organizations do business.

What we can do about it

Ther’s one thing I know is not an option for us as a UX community in South Africa. We can’t play the victim and go sit in a corner, drawing sketches on napkins while we complain about how no one understands us. We know that when users struggle with an interface it’s our fault, not theirs. How is this situation any different? If w’re a misunderstood or unrecognized industry, how is that not our fault, and our problem to solve?

The only way to get UX to the next level of maturity in South Africa is to do what the US and UK did: we need to become childishly loud about what we do and how we can contribute to better products that make more money. Whether you do research, write content, or spend most of your time in OmniGraffle or Photoshop, it’s time to explain to our companies, our clients, the Internet, and the public space in South Africa what UX is and what value a user-centered design process can bring. We need to make it impossible to ignore UX during product development.

If we do that effectively, maybe next year w’ll see demand for an additional skill set at Tech4Africa”¦

---

1. I’m refering specifically to startups that sell physical/virtual products/services, not the agency model of selling time. â†©
2. I’m making an and argument here, not an either/or argument - both types of skills are needed. â†©

I was privileged to speak at Tech4Africa 2011 about a topic that I care about a great deal: how our environments and the way we work impact the quality of the software we produce. The talk came out of a question I keep asking myself over and over: why, despite our best efforts, do we still too often produce low quality software? Here’s the talk summary:

Why do we see so many web applications with inferior user experiences? Why do UX designers often get stuck being asked to “make the design pop a little more,” with no room or incentive to innovate? Why do some web developers feel demotivated and unable to break out of doing things the way they’ve always been done?

In this talk I explore some of the main causes of ineffective software development, and discuss practical recommendations on how to improve team structures and development processes to build high quality software that users care about, want to use, and that therefore makes more money for the business.

I discuss how designers and developers can work better together, how to ensure everyone gets input into the roadmap without it becoming chaos, and how to make sure that the business benefits are clearly articulated and communicated.

So here are the slides from my talk - I hope you find it useful. If you’d like to read more about this topic, you can check out a two-part series of articles that I wrote for Smashing Magazine.

W. Brian Arthur wrote a very interesting article for McKinsey Quarterly called The second economy (h/t to @justinspratt for the link). Registration is required to view the article but it’s worth it.

Much has been written about digitization and technology’s impact on society, but Arthur takes a fresh approach by looking at the digital economy as an unseen layer underneath the physical economy. He starts by defining communication for this (second) economy:

[Processes] are “speaking to” other processes in the digital economy, in a constant conversation among multiple servers and multiple semi-intelligent nodes that are updating things, querying things, checking things off, readjusting things, and eventually connecting back with processes and humans in the physical economy.

You know, like Siri does. In fact, notice how perfectly Siri fits into Arthur’s central thesis about the second economy:

If I were to look for adjectives to describe this second economy, I’d say it is vast, silent, connected, unseen, and autonomous (meaning that human beings may design it but are not directly involved in running it). It is remotely executing and global, always on, and endlessly configurable. It is concurrent””a great computer expression””which means that everything happens in parallel. It is self-configuring, meaning it constantly reconfigures itself on the fly, and increasingly it is also self-organizing, self-architecting, and self-healing.

These last descriptors sound biological””and they are. In fact, I’m beginning to think of this second economy, which is under the surface of the physical economy, as a huge interconnected root system, very much like the root system for aspen trees. For every acre of aspen trees above the ground, ther’s about ten miles of roots underneath, all interconnected with one another, “communicating” with each other.

Arthur makes it clear that he’s not interested in the realm of Sci-Fi and AI. He’s not sharing a completely improbable vision of the future (well, with the exception of driverless cars, depending on how much of a Google believer you are). And even though nothing he describes is brand new, this idea of a silent, interconnected layer underneath the physical one gives us a new lens through which to view the digitization of our lives.

I don’t want to get all “The End Is Near!” on you, but I’m currently reading Sherry Turkle’s Alone Together - Why We Expect More from Technology and Less from Each Other, and Arthur’s article reminded me of her words of caution:

Now demarcations blur as technology accompanies us everywhere, all the time. We are too quick to celebrate the continual presence of a technology that knows no respect for traditional and helpful lines in the sand.

[A] stream of messages makes it impossible to find moments of solitude, time when other people are showing us neither dependency nor affection. In solitude we don’t reject the world but have the space to think our own thoughts. But if your phone is always with you, seeking solitude can look suspiciously like hiding.

Hopefully there will still be places to hide once the second economy has fully established itself.

I love the Automattic Creed that all their employees have to sign before they join the company:

I will never stop learning. I won’t just work on things that are assigned to me. I know ther’s no such thing as a status quo. I will build our business sustainably through passionate and loyal customers. I will never pass up an opportunity to help out a colleague, and I’ll remember the days before I knew everything.

I am more motivated by impact than money, and I know that Open Source is one of the most powerful ideas of our generation. I will communicate as much as possible, because it’s the oxygen of a distributed company.

I am in a marathon, not a sprint, and no matter how far away the goal is, the only way to get there is by putting one foot in front of another every day. Given time, there is no problem that’s insurmountable.

(h/t to @SwimGeek for the link)

This is going to sound like such a lame “management guru” thing to say, but it’s true: the cultural fit of the people you hire is more important than their past experience or absolute skill level. I’ve seen this time and time again. If I have a choice between hiring someone who is highly skilled in their work but doesn’t display humility and a genuine drive to learn more, and someone who knows enough to know that there is much to learn and they’re hungry to get there, I’ll choose the latter every time.

We recently went through an exercise to define our team values, and in many ways it’s similar to Automattic’s creed. I won’t bore you with the whole thing, but here are the main points. This is how we want other people to describe our team:

• We are zealots about quality
• We have autonomy to do what’s best for the product, its users, and our business
• We have a high fix:complain ratio
• We have a healthy work/life perspective
• We are empathetic to the core

The relationship between a healthy culture and doing great work is causal, not simply correlation. Good culture is the prerequisite for great work to happen, and actually causes it. Alan Cooper recently address this issue in a great article called The pipeline to your corporate soul:

If you want to improve the quality of your website, app, or software, you need to also improve the quality of your organization. You need to ferret out the people who play politics but don’t get things done. You need to squash bureaucracy that stops innovation with doubt and red tape. You need to eliminate the energy drains, systemic distortions, and toxic people that force others to act like corporate drones instead of like entrepreneurs with a vested interest in success.

If you put a bunch of talented, energetic, ambitious people together and make it easy for them to collaborate and do great things, they will. I haven’t seen a single example of great work preceding a clearly defined and healthy culture - even if it’s just an unspoken understanding between two startup founders. Spending time on getting your culture right is worth the effort.

Dhanji Prasanna wrote a great article about his experiences on the Google Wave team, and the difficulties of working in large development teams. He brings a particularly interesting perspective to UI engineering:

To say we should have been better prepared or organized is to miss the point - large teams starting on a new project are inherently dysfunctional. One common consequence of all this chaos is that experienced engineers seclude themselves to their area of expertise. At a company like Google, this generally means infrastructure or backend architecture. A major externality of this is that fresh grads, and junior engineers are shunted to the UI layer. I have seen this happen time and again in a number of organizations, and it is a critical, unrecognized problem.

UI is hard.

You need the same mix of experienced talent working in the UI as you do with traditional “serious” stuff. This is where Apple is simply ahead of everyone else - taking design seriously is not about having a dictator fuss over seams and pixels. It’s about giving it the same consideration that you give any other critical part of the system.

I’ve experienced this first-hand, and I’ve also seen what happens when backend developers are forced to do UI work (which can happen for a variety of reasons). I’ve heard developers say that they don’t like to do UI work because “it’s not real programming”. They prefer to focus on the real stuff, not this fluffy CSS/JavaScript thing.

Whether or not their perception is accurate is only one part of the discussion. What I want to point out is this: If you make backend developers do front-end work that they’re not passionate about (or worse, work they find embarrassing to do), they’re not going to be motivated to expand their knowledge and do a good job. That’s unfair to everyone and disastrous for the product.

It’s essential to have dedicated UI engineers in an organization so that everyone can focus on the technologies that they’re obsessed with.

I remember exactly when I decided to stop reading Mashable. I saw the headline Facebook Users Beware: Facebook’s New Feature Could Embarrass You on Twitter, clicked through, hunted for the words of the article among the sea of ads and social sharing icons, and then closed the tab after realizing it’s just another rehash of Facebook frictionless sharing (albeit in a tantalizing way). I went back to my Twitter feed and unfollowed them.

I’m sure the article was great for traffic, though. It is the perfect linkbait title backed up by a perfect SEO-ified URL (/new-facebook-feature). Here’s a screen shot of what’s visible above the fold:

You can’t see a single word from the actual article without scrolling. It reminded me of a comment that Merlin Mann recently made in his typically funny and obnoxious style:

I think I’ve finally hit the limit of my tolerance for web content that’s designed to make advertisers happy. I have no problem with working hard to build an audience - I have a blog, after all. But we seem to be in this bizarre race to the intellectual bottom to write the most generic article in the world so that everyone with an Internet connection will click through. And the only purpose seems to be to keep the advertising monster fed, fat, and happy.

I’m worried that all the noise makes it increasingly difficult for quality content[1] to be seen. Worse, I’m worried that it’s discouraging the creation of quality content because what’s successful (i.e. what gets the most clicks) is mostly lowest-common-denominator blog post titles that either start with a number or end with a question mark. James Bridle sums up this problem so well in The New Value of Text:

Like over-stuffed attendees at a dull banquet, the mind wanders. We are terrified that people are dumbing down, and so we provide them with ever dumber entertainment. We sell them ever greater distractions, hoping to dazzle them further.

Or as Marco Arment put it: “Anti-intellectualism is one of my biggest fears for our society.”

Yet despite all the evidence to the contrary there is still a common refrain on the Internet that quality content will always find its way out of the depths of obscurity. Kristina Halvorson recently complained about the fact that computer-generated articles are gaining traction. Joshua Porter responded: “Re: quality content…there is always room at the top.” My response to that was cynical, but borne out of the type of regurgitation you see everywhere:

I used to believe that if you write with passion and clarity about a topic you know well (or want to know more about), you will find and build an audience. I believed that maybe, if you’re smart about it, you could find a way for some part of that audience to pay you money to sustain whatever obsession drove you to self-publishing (and to do it without selling your soul in the process). There are certainly examples of that out there (Daring Fireball, Shawn Blanc, Ben Brooks, etc.), but I’m not convinced any more that such an option exists for anyone who works hard and gives it a solid go.

The problem is not that people don’t have enough time, it’s that people don’t have enough attention. Like an oil well there’s only so much there, and once the well runs dry you don’t have a lot of options:

So one effect of Peak Attention is that every human mind has been mined to capacity using attention-oil drilling technologies. To get to Clay Shirky’s hypothetical notion of cognitive surplus, we need Alternative Attention sources.

The wells of attention are being drilled to depletion by linkbait headlines, ad-infested pages, “jumps” and random pagination, and content that is engineered to be “consumed” in 1 minute or less of quick scanning - just enough time to capture those almighty eyeballs[2]. And the reality is that “Alternative Attention sources” simply don’t exist.

I don’t know where we go from here. I just know that I’ve stopped reading sites that cater more for advertisers than for me as a reader. It won’t make much of a difference, but it will hopefully help me sleep better.

---

1. Of course, we’re never going to agree on what “quality content” means. It’s one of those “you know it when you see it” things, and everyone’s definition will be different. Still, my personal view is that quality content presents two or more of the following components: (1) new information, (2) interpretation of information, and/or (3) a well considered personal opinion about what the information means.  â†©
2. Wait, who am I to decide what people should and shouldn’t read? You’re absolutely right, I can’t do that so I should get off my high horse and let people read whatever they want to read. This is an opinion piece.  â†©

It’s amazing to see the outpouring of condolences and memories and stories about Steve Jobs and the effect that he’s had on our lives. What’s most telling to me is the countless people - myself included - who feel like we have a connection with him because of the products he brought into this world. That’s extraordinary.

This morning I counted the number of Apple products we have in our house (12), and I realized that Steve Jobs and those products helped me figure out what I want to do with my life. He showed us the power of beautiful design, and he built products that want you to succeed in whatever it is that you choose to make.

I think Seth Godin said it best:

Steve devoted his professional life to giving us (you, me and a billion other people) the most powerful device ever available to an ordinary person. Everything in our world is different because of the device you’re reading this on.

What are we going to do with it?

I made this on a Mac. And this Mac will continue to inspire me to make better things.

Thank you, Steve.

Update: Of course Frank Chimero would come along and say what I was trying to say, only much better:

That sadness [you feel] is for the loss of a man who unabashedly devoted his life to making things that helped others live well.

We all have that same opportunity. Take a moment to consider your job. Boil it down to its essence: you make things for other people. The most important concept to learn from Jobs is embedded in how we feel after using one of his products. That very same thing is happening now in his wake. Look closely and you will see it: wonderful experiences have an afterglow to them. The delight we find in what we do is in some way lost in the moment, but captured in our memories.

Update 2: There are so many amazing tributes coming through that it’s hard to keep up. I want to preserve the ones that spoke to me in some way, so it might as well be in this post. Here is Michael Lopp:

My first thought as I stared long and hard at Appl’s home page yesterday wasn’t a specific Steve story or one of his many insightful quotes. The thought was”¦

You are underestimating the future. You are fretting about the now; worrying about little things that don’t matter. You are wasting precious energy obsessing over irrelevant details. You don’t believe that a better future is out there and can be built, that it can exceed peopl’s expectations, because you’re spending so much time considering the truth of the present and the seemingly important lessons of the past.

You are underestimating the future because you believe you cannot see it, but you can - you’ve seen it done before.

Update 3: Ok, just one more (I think). Here is Shawn Blanc in 3rd-Party Family:

You and I are on the same team. We all are. We may link to the same articles, review the same products, develop apps for the same market, and design with the same intense perfectionism, but we are a community. Let’s continue to fight for each other, encourage each other, and work together to make amazing things.

We are the 3rd-party family of Apple nerds. Let’s make a dent.

I’ll drink to that.