SXSW 2011 – Breaking Taboos – Pros Get Real About Money

SXSW 2011 – Breaking Taboos: Pros Get Real About Money Matters

Session by: Whitney Hess and Marc Hemeon

On a personal note, what a pleasure to finally have a chance to meet Whitney Hess in person!  I’ve been a big fan of her writing (and Tweeting) for quite a while, and it was a real pleasure to have the opportunity to finally introduce myself in person, and get a chance to hear her dynamic presentation style.

Anyway, I’m interested in money, aren’t you? So when Whitney Hess comes to town to give the lowdown on money and what to do with it (or how to get it AND keep it) then I’m all ears.  We’ve got a small ballroom that’s packed with about 50 or so folks, standing room only.  The room setup is chairs spread around three sides of the room, all facing an open space in the center, ala theater in the round, so that’s different.  Makes for a fun venue!

And now, into money matters…

Whitney Hess and Marc HemeonTo a packed room in the Marriott across the street and past the Starbucks from the Austin Convention Center, Whitney Hess and Marc Hemeon will hold forth on matters of money.

They begin, asking the audience who is present what sort of work they do, by a show of hands.  The audience responds with lots of raised hands for designers, developers, and then a few other mixed types such as agency owners. There are introductions about who Whitney Hess and Marc Hemeon are, where they came from, what they’re doing.  Marc’s into designing things like logos and such, Whitney does usability testing (oops, that’s so old-school, I mean “UX testing”) and related behavioral research.

Whitney: What are some of your questions (asked of the audience)? Various responses including answer about too much or not enough hourly charge, retainer vs. time and material, endless changes (been there, done that). More suggestions from the audience about some clients not being profitable, and some that are very, and how to balance the two.  Questions about Spec work, to which when asked to give a gladiatorial “thumbs up or thumbs down” the entire audience gave thumbs down. More requests, is pitching a waste of time? What about intellectual property? When is it ok to take out a loan, when to start billing?

Mark and Whitney realize, with a bit of a “deer in the headlights look” I think, that this audience has LOTS of questions about money matters, probably way more than can fit into a day-long presentation, much less an hour.  And so, they begin.

Whitney: She’s been independent since 2008, when she went indie, she decided to not charge by the hour. She says, value of work should not be valued by number of hours. She feels it’s not appropriate for her to double charge her clients if it takes twice as long to get to a strategy. She says, I negotiate a rate in advance, I don’t tell my hourly rate, I just work from the client’s budget. What’s the amount of my brain they can occupy? Whitney says, if they ask, “how much do you cost?”  I answer with how much is your budget?  I keep pushing for a number, start with $100k and they start talking. Here’s my tip she says, whoever mentions a monetary amount first, is the loser in the negotiation.  She continues, I give a discount to any client willing to pay up front in full. Otherwise I get 50% up front and 50% at end of project. Whitney says her reason to not charge hours is she can’t always figure out how many hours it’ll actually take to do the project.

When asked, many people in the room said they ate money by going way over on hours when they quoted a flat-rate for a project (ouch, been there and done that too).

Marc: I do things different from Whitney, I bill for anything and everything I do on the client’s behalf.  I send invoices every 2 weeks. He says, if you call me, you get a bill. Marc said, a time and materials contract is how I bill. This is because sometimes I get there faster, sometimes it takes longer to get there. He added, Freshbooks.com is what I use, it’s great. It’s where I enter and track my time. Marc gives us a story about a guy who was a friend of his that did 50 hours of work for a prospective client, but his wasn’t used.  His friend didn’t send an invoice. Marc said to his friend, “send them an invoice! You did work for them, whether they used it or not, you need to be paid for your time!” His friend did, and they paid his friend. (I like stories with happy endings!)

Marc added, he publishes his rate on his website, he lets his prospective clients know what it costs to hire him to do their work.

Whitney: I let my clients know in advance what they are going to be charged. You must set expectations, and not be afraid to talk to clients about it. She adds, do you value your work, is your work good?

When asked by an audience member who was concerned about charging enough vs. other competitors, Whitney says, “Am I charging enough or not enough vs. other people? I don’t worry about other people. I project confidence because I know I’m good, even though I’ve not been doing this a long time vs. some of my peers.”

Marc: It’s important to remember who you’re dealing with, big companies probably have set budgets they can’t increase.  For example, when I was at Oakley, a budget of $10k was a budget of $10k, and that couldn’t be changed. Big companies are like that.

Whitney: If a prospect says they don’t know a budget, I don’t work with them because I need to work for a company that’s going to succeed, any company not willing to commit to a budget is probably not a good company in the long run, and thus not a good client.  Whitney adds, you need to succeed by having confidence and projecting that confidence. I was in a bad job, wasn’t very ambitious, realized I was not going anywhere, I decided I was going to be the product. I doubled my rate, which created the image of being worth something.

Marc: Turns to the audience and reminds them, “But your work better not suck if you’re charging $500 per hour!”

Whitney: I don’t bring up budget first.  Instead, I am asking the client about their background, I get a lot of referrals so I ask about that too.  I then later on, after understanding the goals and needs of the client, ask for budget as matter of fact.  I establish my credibility first.

An audience member asks; “How do I know I’m great?  How do I get there?”

Whitney: You must know you’re the s-h-i-(you know what).  Do you do good work?  Yes? Then you’re the s-h-i- .  You have to believe you’re good, after all, you’re here learning, right?  But she cautions, it’s the Prada vs. the Gap – some people value Prada, some are all about Gap, you clients are either Prada or Gap too.

An audience member asks about Startups; What’s the percentage of time/equity/pay?

Marc: First, I say partner with someone who does something, creates something, not just talks. Second, stick up for yourself and negotiate hard, you don’t know how long you’ll be working with them. Cash and equity, or all equity? No, I never have.  Marc adds, remember that equity is actually zero money going in, equity at the start anyway is worthless.

Whitney: Let’s switch to talking about contracts, because none of this matters without a contract in place.  You need a contract. You must design the scope before you start, to get a contract. For me, I know my schedule, activity, when I’m presenting findings, using a phase by phase schedule (it’s not day by day). I stick to the deadlines, I break it out as phases, but don’t break pricing by activity.  That all goes into the contract.

Marc: I don’t have a big contract, just 2 pages.  That’s because I need flexibility, because I charge time and materials.

Whitney: The more structure I have the better for me, because I need that structure to work, but Mark needs the ability to have creativity.

Marc: I did logos for $20k even though $1k was proposed, because people want to keep making changes and want control. I send an invoice every two weeks.  You get a bill from me that says $500, which doesn’t seem big, but get 30 of those invoices and wow!

Whitney: Contracts should always include termination clause. I had a lawyer help me craft this. I take start and end date, divide by 2, if you terminate me prior to this date I get 50%, if after the date, you owe me the 2nd 50%. You can’t just book me then let me go, that’s an opportunity lost for me where I could have booked another client. Flip side is if I leave first, contract says (for some clients) I will pro-rate, and pay them back or only be entitled to remainder. If only 3 weeks left, I pay them the 3 weeks (if they paid up front).

Marc: My contract is only 2 pages.  But if you want to see a much bigger contract, go to the AIGA.com contract. They have a big contract that is a good one to consider.

Whitney: Having a lawyer is crucial.  This is your business, the web is not going to give you the answer. The lawyer needs to feel your pain if something goes wrong with your contract. Whitney adds, What about an LLC?  Yes, you HAVE to do an LLC.  That’s because they can only sue your business, not you personally, if you are using an LLC for your business.

An audience member asks about scope creep, Whitney responds: With scope creep, you have to pull the contract out and remind people what the project is. Check yourself against what you’ve said in the contract you’re doing.

Marc shakes his head, probably due to the fact that with Time and Materials scope creep, although unpleasant, is not financially an issue as he simply keeps billing for the added time spent on the project.

And with that, our hour has quickly gone and it’s time for us to leave.  I’ve enjoyed having a chance to blog about this, and of course meet Marc and Whitney.  And more sessions here I come!

Posted in Usability Business | Tagged , | 2 Comments

You Don’t Know Use Cases

You Don’t Know Use Cases, Yet

Book Review: Writing Effective Use Cases by Alistair Cockburn

I’m willing to bet your Use Cases are written wrong (you do USE Use Cases, right?), or are not as effective as they could be, and I know this because mine were.  However, I had the pleasure of reading and using the book ‘Writing Effective Use Cases’ by Alistair Cockburn and now I have seen the light.

Turns out not only were my Use Cases wrong, so were all the people around me who were writing them for companies like WellPoint, Marsh & McLennan, Countrywide, Disney, and a host of smaller firms.  Well, maybe wrong is a bit strong, but certainly my Use Cases were far less effective and efficient than they could have been, I’m betting you have the same problem.

Why should you care about Use Cases?

To put it simply, you should care about Use Cases because an effective set of Use Cases will save you (and your team) major amounts of TIME, MONEY, and even potentially YOUR JOB.

Writing Effective Use Cases by Alistair Cockburn

Writing Effective Use Cases by Alistair Cockburn

Writing Effective Use Cases by Alistair Cockburn is a book that will teach you the correct way to write and utilize Use Cases, and by doing so save your projects (thus potentially saving YOU).  It is, without a doubt, one of the most important books you’ll read in the entire year.  Period.

Everyone, and I do mean EVERYONE needs to read and use this book.  This includes people who:

  • Work with websites, apps or anything else people interact with
  • Are part of a team that deals with websites, apps or anything else people interact with
  • Are in some way involved with people who work with websites, apps or anything else people interact with

To illustrate my point, I’ve slightly edited the script of the all-time best-ever classic movie, Casablanca, to highlight the importance of Use Cases:

INT. – GAMBLING HALL IN RICK’S BAR – NIGHT

Rick spins suddenly as the door in the gambling hall bursts open and is quickly slammed shut by Ugate.  Ugate braces his back to the door while several men on the other side pound on it attempting to break it down.

UGATE:

Rick! You’ve got to hide me! Rick!
They want to make changes to the requirements!

RICK:

Ugate, don’t be a fool, you can’t get away!
You’ve GOT to make those requirements changes!
You don’t have a set of solid and pre-approved Use Cases!

UGATE:

Rick!  Help me!
They told me the requirements were set,
they told me there wouldn’t BE any more changes!

In desperation, Ugate quickly moves away from the door, pulls out a pistol and fires several shots toward the door. Several bystanders in the hall scream.  The door smashes open and three Gendarme I.T. developer-type men enter, grabbing Ugate.

UGATE:

Rick!  Help me! Rick…!

The Gendarme I.T. developers wrestle the gun out of Ugate’s hands and quickly drag him out the door.

BYSTANDER PROJECT MANAGER:

I hope Rick when they come to get me
with requirements changes you’ll be more of a help!

Rick turns, speaking to the bystander PM and the room in general.

RICK:

I stick my neck out for no one!
Especially for anybody crazy enough to not have
a good set of Use Cases that everyone on the
project team approves prior to starting the project!

END

What’s a Use Case?

Here’s a quote from the book:

“A use case captures a contract between the stakeholders of a system about its behavior.  The use case describes the system’s behavior under various conditions as the system responds to a request from one of the stakeholders, called the primary actor.  The primary actor initiates an interaction with the system to accomplish some goal. The system responds, protecting the interests of all the stakeholders. Different sequences of behavior, or scenarios, can unfold, depending on the particular requests made and the conditions surrounding the requests.  The use case gathers those different scenarios together.”

The book continues,

“Use cases are fundamentally a text form, although they can be written using flow charts, sequence charts, Petri nets, or programming languages.  Under normal circumstances, they serve as a means of communication from one person to another, often among people with no special training.  Simple text is, therefore, usually the best choice.”

Here’s an example of what a Use Case looks like.

Example Use Case

Why are Use Cases so important?

Use Cases are important because they are the foundation and agreed-upon approach that a team will base a System Under Design on.  Use Cases if written properly will help everyone on the team.  Whether your team is composed of business owners, operations staff, executives, developers or project managers, a good Use Case will help all of them clearly understand exactly what the expected behavior is of a System Under Design is, and isn’t.  The Use Case helps the team understand each of the components, from the highest level behavior all the way down to sub-function behavior, everyone will know exactly how it’ll work.

And the type of System Under Design that Use Cases are created for do not matter, it could be anything from; creating an application to buy stocks over the internet, developing a new process for handling customer service calls or even texting someone using a smartphone.

The importance comes from several aspects of well written Use Cases including:

  • They clearly define what is in scope, and thus by definition what is out of scope
  • They provide sufficient detail so all team members clearly understand the purpose and function of each of the components of the System Under Design
  • Well-written Use Cases only provide the actual information necessary for understanding the behavior of the System Under Design, there is no extra, technically advanced, distracting or conflicting information
  • Because they are non-technical in writing style, everyone can read, understand, use and refer back to the Use Case
  • The Use Case acts as a contract and project guide, ensuring agreement and alignment of all parties involved in developing the System Under Design
  • A well-written Use Case acts as the foundation upon which all project management, requirements documentation, development and testing will stem from

Well-written Use Cases identify the points of success as well as failure for a System Under Design, ensuring there are no hidden ‘gotchas’ when a system or process is being developed.  This alone can often save a project.  This means a far better user experience that ensures the solution will benefit the end users and the company and/or team developing it.

A good set of Use Cases, starting at the top most summary level (typically referred to as Cloud or White) and going down to the more detailed sub-function level (typically labeled Fish or Indigo) provides a complete blueprint for how the System Under Design will behave across all situations and actors.  As such, they are a living set of documents that can be incorporated into the Requirements Document and thus referred to over and over again as questions or issues arise during development.  For this reason alone Use Cases are worth their weight in gold.

The other major benefit of a good set of Use Cases is helping to ensure the best possible user experience is provided because all functional and process issues have been considered and ironed-out way before development ever commences.

Many companies write and use Use Cases in their development efforts, however I’ve seldom (if ever) seen consistent and well constructed Use Cases.  There’s just as much variation to the format and quality of Use Cases as there are projects, or so it would seem.

Learn the correct way to write a Use Case

Believe it or not, there is a correct (and thus incorrect) way to write a Use Case, and you owe it to yourself to learn it.  The book, Writing Effective Use Cases by Alistair Cockburn is the tool you need to help you learn the correct way to write and use Use Cases.

The book itself is very easy to read and use, and is structured to allow anyone to:

  • Understand what use cases are, including the format, context and contents
  • Develop their own Use Cases, simple at first, but adding complexity over time
  • Take quizzes at the end of each chapter (with some answers included) to ensure the concepts are clearly understood
  • Act as a reference and handy ‘how-to’ tool when you start writing (or reading other) Use Cases

Conclusion: You don’t know Use Cases, yet

So my guess is just like me, you probably don’t know an efficient vs. non-efficient Use Case.  Like mine, I’m betting your Use Cases (assuming you use Use Cases, which you most definitely should) are probably not written as effectively as they could be.  Some of you may actually be calling your documents ‘Use Cases’ when in fact they aren’t Use Cases at all.  My former Use Cases were a very poor rendition of what a proper Use Case is.  But after reading and using the book ‘Writing Effective Use Cases’ by Alistair Cockburn I’m on the path to victory.

Now you can be too.

Reading and using this book to create effective Use Cases absolutely will benefit you, your team and your company the next time you have to participate in the design or creation of a System or Process.  And who knows? By being so much more effective and efficient, the next job you save, or promotion received, just might end up being your own!

As Rick said to Captain Renault:

RICK:

Louis, I think this is the beginning
of a beautiful friendship (with Use Cases).

Posted in Books, User Centered Design | Tagged , , , , , | 2 Comments

2010 Top 10 Useful Usability Articles

The Top 10 Useful Usability Articles for 2010

Technically the year is not over yet, but I think it’s pretty safe to provide you with the list of the top 10 most popular Useful Usability articles.  Who determined the top 10 list?  You and your fellow readers did! My methodology was simple, I evaluated Google Analytics to determine the most popular content for 2010 as measured by unique page views.  Turns out there were a few interesting surprises in the list!

2010 Top 10 Articles from Useful Usability

So here then, ranked in order are the top 10 most popular articles as ranked by you…

1. 24 Usability Testing Tools

This article provides a list of 24 usability testing tools that I either use, or found particularly interesting.  The important thing to note about these tools is the vast majority are relative cheap and easy to use.  Trying out even a few of the tools from this list would be a great idea for any firm interested in expanding the amount and quality of its user research.

2. 15 Valuable Usability PDFs You Never Heard Of

A multi-year winner for top 10, this popular article lists 15 valuable usability documents in PDF form that many people may not be aware of.  It’s interesting to note that even though some of the research or findings are relatively speaking older, they still provide meaningful and relevant information on user experience best practices.  It’s definitely a list worth bookmarking.

3. Usability Is In The Details

This little article received a surprising amount of interest and comments, as it seems many people continue to be focused on improving minor, yet annoying, usability details as part of their optimization of interaction design.  The summary of this article in effect is a reminder to pay attention to the details, because even seemingly minor usability issues can cause vastly decreased performance and thus poor results.

4. How To Conduct A Usability Review

Students and practitioners alike seem to be interested in conducting usability reviews.  In my opinion this interest has increased over the years, which I attribute to the good job of educating and informing the masses on what usability is and why it benefits people and companies.  Hopefully this trend will continue to grow, as there are still plenty of examples of websites and applications that could use some improved usability mojo.

5. 5 Radical Ideas From Usability Presentations

I’m glad to see this article ranking so high, as it is one of my favorites and a good reminder that radical, meaning potentially useful, usability ideas are all around us, including in the 5 presentations mentioned.  I’m hoping that the growing interest in optimizing the user experience of websites and applications will extend well into 2011 and beyond and that we will be adding to this list with additional ideas.

6. 8 Free Tools For Good Information Architecture And Usability

This article lists 8 free useful tools for information architecture primarily, with extensions into usability.  There’s a growth of interesting free or cheap information architecture tools on the market and I urge you to try testing out a few new ones in the new year to see how they work for you.  You might just find a new favorite!

7. Usability Testing Makes Killer Online Marketing Campaigns

This article, an examination of how to use usability testing to make killer online marketing campaigns, is another favorite of mine, and I’m glad to see one of yours too.  This article is written for online marketing teams and is a reminder that one of the best ways to improve conversion is to conduct some usability testing prior to going live with a campaign.  Incremental improvements in conversion of 5 to 15% or more could easily turn a bust campaign into a goldmine.  I hope more online marketing teams will try usability testing of campaigns in the New Year, I think they’ll be thanking me (PS – If you feel like thanking me, I am easy to shop for, I like anything with a Dallas Cowboys logo on it).

8. 10 Must See Usability Videos

It’s reassuring to know that people are actually watching some of these 10 must see usability videos, because according to my Google Analytics report the average on-page time for this page is well over 11 minutes.  I hope that more interesting talks and seminars will eventually make it up onto YouTube and related sites, video is a great way to present interesting and compelling user experience information.  If a picture paints a thousand words, then these 10 usability videos are rich libraries of billions and billions of useful words.

9. 7 Reasons Why You Can’t Sell Usability

Another of my favorites, 7 Reasons Why You Can’t Sell Usability is directly aimed at the freelancers, small companies and even mega firms that are trying to assist their customers and clients with improved conversion and better sales.  And between you and me another reason this is one of my favorites is because of the cool graphics I created to help visually express the story.  But hey, that’s just the inner artist in me talking, there’s lots of good content including a valuable list of further resources at the bottom.  If you’ve not read this yet I urge you to do so, you won’t be sorry.

10. Main Navigation Types and Usability Part 2, Vertical Navigation

This one completely surprises me for two reasons; first, I wrote this in 2009 and at that time I felt it didn’t receive a lot of comments or apparent interest, and second, I assumed it would be somewhat old news to interaction designers and usability practitioners.  I’m gratified to know I was wrong on both assumptions.  I never did finish the series off (the third installment was to be on footer navigation), I may have to correct that error and write the final article.

Conclusion: Top 10 Useful Usability Articles for 2010

So that’s the list for the 2010 top 10 most popular useful usability articles as indicated by unique page views.  If I’ve left out your favorite be sure to mention it in the comments!  And happy new year to you!

Posted in Resources | Tagged , , , | Leave a comment