Archive for April 2011

Cooper: How To Create Effective Design Teams

Great Read. Too often, we work alone. Great design is a collaboration, not a solo event.

In the design world, the idea of working in a “team” often provokes dread. Teams introduce overhead; they require communication; members often battle to see their ideas implemented. The end result of teamwork is often seen as compromise, i.e. as a “taco pizza,” i.e. a situation in which everyone (including the customer) loses.

On the other hand, there are  many examples of highly functioning creative teams, and my own experience tells me that a team approach can be vastly more efficient and effective than working solo. Who doesn’t want a well-matched partner to ensure that the ideas flow, the problem is considered from all angles, and dead-ends are avoided? And lets face it – some of the most interesting and important problems are too big to solve alone.

Still, how do you ensure that people with similar skills and interests will work well together?

You make sure that each team member knows and understands their responsibilities, that they enjoy giving up a little personal ownership for the benefit of others’ perspectives and skills, and that they deeply trust the other team members to play their parts. Without those fundamental qualities, the team is likely to go the way of Tolstoy’s unhappy families – division, mistrust, high drama. Good material for a novel, but bad for designing compelling products and growing a business.

Read on…

 Comments | Comment

Five Tips For Recruiters: What To Know Before You Pitch Me

This is a cross-post of a blog entry over at Jobvite, a social recruiting platform. Enjoy.

Let's just say these are busy times in Silcon Valley, especially for developers and user experience types. Many of my friends in software development are getting multiple calls a day from recruiters, pitching the next startup or some great contract work.

It's nice to be wanted, but it's also a frustrating process having to say no thank you to recruiters especially when they have completely misread my resume. I've gotten a lot of calls for front-end developers, database architects, and even iPhone development – and none of those are things are on my resume.

I've worked before as a recruiter and have built a team from scratch, so I understand recruiters' needs. I also understand that, at their core, recruiters are sales people, except they have to sell two parties to close a deal.

Recruiting is like real estate, except you're brokering talent instead of houses. Both recruiters and real estate agents that are best at what they do have common traits. They both may make money on commission and depend on selling the candidate on the company and vice versa (the buyer and seller of a house). Both also have the same goal – to close the deal.

I'm in the unique position of doing user research by interviewing the same group of people that call me: recruiters. I strike up wonderful conversations with them, and it's a win-win situation. They tell me what they need (sometimes I can give it to them), and I get great feedback about their needs for applicant tracking and social recruiting.

Here are a few tips on how to get great candidates:

Reputation Is Everything

The phone call you make is the first time any candidate has been contacted by your company. Make it worthwhile. Like any interview, first impressions are everything. The candidate is interviewing you as much as you are interviewing them, and they'll be grading you on everything from your knowledge of the company to whether they understand what you do as a profession.

They'll be asking a list of questions, if they're any good. You're on the clock for presenting the company as a great place at which to work. Forty hours a week (or more, if you're at a startup) is a lot of time to spend anywhere. In other words, it's a decision no one should take lightly. In down economy, people will suck it up. On the way up, it's more of a sales pitch.

For some professional communities, word spreads fast. I used to live in Southern California, and we used to say, "Big city, small town." This applies to the Bay Area even more so. We trade stories about places to work and recruiters, especially in a superheated social media culture, so each impression speaks volumes.

Understand the Position

Hiring for software developers is much easier, because managers will give you a list of acronyms to use when finding candidates. Typing in Java, Swing, and Hibernate will get you a fair number of enterprise developers, for example. User Experience types are harder. We're in a field that's fairly amorphous and that works in conjunction with a lot of fields, like sales and marketing.

If you have questions, do research. Find out what a wireframe is. Learn about user research. Present a few initial candidates to the hiring managers, and ask questions like, "Does this person have enough experience?" before calling the candidates. Even better, join Quora, and do some searching there. There are a ton of questions about each of the fields, and the best and brightest that have written well-researched and thoughtful answers.

The best recruiters I know bracket candidates to get a good idea of the sweet spot for the position. They'll present people with too little or too much experience to get to that "just right" spot. The recruiters that I've worked with that understand what I do have captured more of my respect. I don't necessarily expect them to design a website, but I do want them to understand what I do.

Recognize the Candidate's Needs

When I was a graphic designer, my co-workers and I had a common joke about some of the jobs that we're offered – midnight shift, must make coffee, must answer phones – that had requirements totally outside of what we could or would want to do. The same goes for hiring people today. The best recruiters will do a good job of understanding who the candidate is and whether or not he or she would be willing to do the work required.

The best way to understand the candidate is to read their resume. Look at their experience level, where they have worked, and with what the brands. Even look at on what kind of applications they have worked. For example, the last time I designed a microsite that was very interactive was in the 20th century. I probably wouldn't want to do it again.

Have Realistic Expectations

There's nothing worse than getting a phone call, and they want to present you for a position that's at least $30 an hour under market rate, or the person has to move to Missoula, Montana when they obviously are never going to leave San Francisco.

As the economy comes back, there's going to be a lot of job shifting, and compensation is going to return to pre-recession levels. That requires a deeper understanding of what the market rate is, and how far off the client is in what they want. All companies want the best bang for the buck, but the true understanding of salary is that you are mitigating risk, not paying for experience.

Work with the client or your company to learn what their expectations are, and what they are willing to pay. Go to a few candidates and ask them ballpark figures of what they are expecting.

Build Relationships

The best recruiters I've worked with talk to me even if I'm not a commission. We talk about the market, companies, and what's going on. They've helped me standardize recruiter terminology for Jobvite, and we've gone out for drinks. We trade stories about the best places to work, and I help them understand some the motivations of other professionals we may know.

The best recruiters turn it into a professional friendship that goes beyond the initial sale, in the same way real estate agents reach out to people that live in the neighborhood. It's the virtual apple pie on Fourth of July. My favorite recruiters ask me for referrals, which I'll give without thinking twice. I'll tell them about companies that are looking for candidates, and match them up with other great people that are a better fit for the position.

I've referred over 30 people to positions over the last two years and will keep doing so. I almost always pass (or don't care) about the fee, because I enjoy the relationship. I would rather gain the trust and respect of a recruiter; and the social capital is in invaluable. I also understand the nature of Weak Ties, which is invaluable when building your career.

When someone is ready to explore new opportunities, all it takes is one great referral to seal the deal. That means if you get a shot, you can look like a hero to your client or company.

 Comments | Comment

Customers That Click: Seven Key Questions To Consider When Building A Best Class Website

Yup. I’ve hit writer block. Need some other people to help out.

Kim Proctor has been a featured podcaster on Usability Counts, and runs Customers That Click, a customer experience consultancy out of Los Angeles. This post is a concise list that should be considered when building a website. Enjoy.

You want visitors to come to your website and click around, return, and tell their friends – right? It takes a better than average site to do that.

What are your favorite websites – the ones that really impress you and make your life easier. It's the sites with great usability and great presentation that stay updated. Yes, of course, Facebook you might be saying, but also great ecommerce sites (think  Zappos.com,  amazon.com,  llbean.com,  overstock.com, etc).

However, many business websites end up either being too serious, too boring or too static. Sorry to say.  But that means you can really stand out from your competitors.

Here are the top 7 questions you need to consider when building or revamping your website.

1. How easy is it for your customers to find what they want? (Good correlated question: How many clicks does it take them to find key information?)

2. How easy is to scan the content on your pages to find what they want?

3. How clear is your content / message? (Consider style, tone, length, format.)

4. How often is your content updated?

5. How much do you offer for free (before a user has to register or pay)?

6. What kind of interaction is possible on your site (forums, commenting, rating, etc)?

7. How does your site compare to Web usability of your competitors and best in class websites?

The danger here is that you're so in love with your own voice or how you already built your website that you aren't willing to change and be what your customers want (and what will help your SEO too).

Be ready to slice and dice your website to pull customers in with helpful headlines, clear calls to action and labels. Don't ramble on – put the pay off up top and don't be afraid of graphics and buttons.

 Comments | Comment

Jeff Bullas: 10 Reasons Why Ducks Just Don’t Get Social Media

Sometimes, you just can’t make this stuff up:

So…Why don't ducks get social media?

  1. It's nearly impossible to type with webbed feet
  2. Computers just don't like water
  3. Broadband access isn't available in ponds…yet!
  4. Frankly, it all seems to be so much hard work maintaining all those updates
  5. Quacking comes naturally, tweeting is for other birds
  6. Blogging each night is just too much with ducklings to feed
  7. Stumbleupon is more to do with a slippery pond
  8. Delicious sounds like   a   a good worm treat
  9. Blogging is just too confusing
  10. Social media mobile apps for ducks just aren't popular, so no one is developing them

 Comments | Comment

Salon.com: What Would Don Draper Do?

From Salon.com:

The Web, email, podcasts and streamable/rippable online video combines a new search-and-aggregation culture with sheer infiniteness. Couple that with the now-ubiquitous use of DVR, and content has not only been disaggregated from its branded source, but also has had its old bonds to advertising severely weakened. Keep throwing circumventable ads at the audience, and they’ll just keep fast forwarding or clicking past them. Make ads technologically unavoidable, and the audience will likely go somewhere else because content consumers surfing the infinite Internet are no longer physically captive to a confined set of old-media conduits — they can and will find compelling content that has fewer ads.

Considering all that, unless media outlets are fusing unavoidable ads to truly unique products, those outlets will likely suffer if they stick to the old advertising-content formulas.

[Another] model is subscription, which substitutes user fees for ad revenue. That’s the Wall Street Journal/New York Times pay wall, XM/Sirius, independent podcasts, Netflix and iTunes. The former three are having trouble, in part, because much of their content remains similar to what other free outlets are offering. The latter three, on the other hand, are proving viable because much of their programming is, indeed, unique and not replicable.

For content to survive, there has to be innovation on how to marry content with advertising.

Something new. Something different. Something Google and Facebook aren’t pushing, because everything isn’t about pay per click.

The NYTimes.com paywall isn’t going to work (or is priced too high, because I’d pay for a lower price point — like one that was cheaper than receiving the physical paper version). Other experiments are failing. Only in extreme cases where the content has a high enough value (Wall Street Journal, for example) can there be existence of a pure subscription play.

I don’t know the answers. I don’t know if anyone does.

The question really is: What would  William Randolph Hearst do?

 Comments | Comment

UI Engineering: Fast Path To Great UX – Increased Exposure Hours

Great post:

For more than 20 years, we’ve known that teams spending time watching users, can see improvements. Yet we still see many teams with regular user research programs that produce complicated, unusable products. We couldn’t understand why, until now.

Each team member has to be exposed directly to the users themselves. Teams that have dedicated user research professionals, who watch the users, then in turn, report the results through documents or videos, don’t deliver the same benefits. It’s from the direct exposure to the users that we see the improvements in the design.

The more you watch them, the more you learn. Not exactly rocket science.

And…

The teams with the best results were those that kept up the research on an ongoing basis. It seems that six weeks was the bare minimum for a two-hour exposure dose. The teams with members who spent the minimum of two hours every six weeks saw far greater improvements to their design’s user experience than teams who didn’t meet the minimum. And teams with more frequent exposure, say two-hours every three weeks, saw even better results.

Nice. Why don’t more groups do usability testing?

 Comments | Comment