• Seth Godin Teaches a Good Lesson About Design

    [A guest post by Karam Debly]

    Through a friend, I learned that Seth Godin put out a call on his blog for developers to apply to build a mobile app.

    I wrote the following in my application.

    “I’m writing to tell you that I don’t think your blog, which i love, warrants an app.

    We believe strongly in responsive design and your site should be designed to look good on any platform.

    I have a hunch that if people are asking you for an app they are either responding to trends or telling you your site doesn’t look good on mobile devices and/or tablets.

    A solid designer should be trying to solve a problem, not building you shit you don’t need.”

    I wrote that quickly. Besides grammar, I would change the last sentence. Solid is vague, I mean responsible.

    I have since looked at his site and blog (I should’ve looked before I hit send, I can be impulsive). Both sites don’t work on common mobile and tablet screen resolutions.

    There’s a great lesson here.

    What do you tell a potential client who is asking for a proposal for something that you think is missing the problem in the first place? Even if that potential client is Seth Godin.

    I would ask the client to back up and describe the problem in more detail.

    Is the problem really that Seth Godin doesn’t have a mobile app? Or is that a symptom of the problem?

    The problem, in my humble opinion, is that his site doesn’t work on smaller screens. It’s very difficult to read. Mobile users aren’t tolerating pinch to zoom anymore. And they shouldn’t. Designers have built a better way to interact with a site on smaller screens.

    I think Mobile apps can be useful. It’s just that none of the other details he wrote warrant an app either. He’s not interested in monetization (Let’s be honest, that’s a big reason for mobile app development). The main feature for the app is that it displays articles from his RSS feed and links to sell his books. Oh, and share buttons for social media. These are all features that could be easily incorporated in a responsive site. There’s one vague requirement that I’m just going to interpret as “anything else you think would be cool” and leave it out of this.

    Seth doesn’t need a mobile app. He needs a new site. And a responsible design company would tell him that. I’m surprised he missed something this obvious. I’m also surprised that no one around him pointed out his mistake. However, I won’t be surprised that mobile app developers won’t mention that. They are responding to his call after all.

    Seth messed up, it happens. Don’t let your clients make the same mistake. They might end up blaming you. They should. You’re supposed to be the expert.

    P.S. I put TBD in the Budget field of my application.


  • Winnipeg is a Freelance Town

    After being laid-off from my job as an interaction designer at Think Shift earlier this year, I exchanged some emo IMs with a good friend and former-Winnipegger. I told him that I was looking at getting into freelance full-time, to which he replied “Winnipeg is a freelance town.”

    He was right.

    I’ve spent the majority of my 10+ year career working as a remote freelancer. I’ve spent less time at “real jobs” in “real offices” than I have spent working in my “home office.” I took the interaction design job at Think Shift partially to see what I had been missing and partially because I believed the myth of job security.

    I’m sure some people would be unhappy working from home without co-workers or face-to-face interaction; and others would be inherently unhappy working for a boss in an office. I’m not one of those people. I don’t know whether I prefer one to the other. There are pros and cons to each. But most of these factors could be lumped into a “soft” category: offices have face-to-face interaction, group collaboration. Home offices have more time with families, optional clothing, shorter commutes, better coffee. With the exception of health benefits and different tax rules, none of major differences have much of an affect my bottom line. They don’t affect my ability to pay the bills, which after-all is the whole point of a job.

    When it comes to salary, “real jobs” in Winnipeg cannot compete with freelance. Based on my limited experience most Winnipeg employers live in a stereotypical Winnipeg bubble. They seem to worry endlessly about dealing with stereotypically “cheap” Winnipeg clients. They’re more likely to try to compete on price than quality and seek out clients who are more interested in price than quality (or vice versa, maybe it’s chicken and egg). Even the larger web shops seem hesitant (with typical Winnipeg insecurity) to compete for work nationally, let alone internationally. For all these reasons, Winnipeg web shops are completely unable to compete for salaries nationally.

    (And for the most part that’s seems to be OK with Winnipeggers.)

    The hourly rates I’m able to charge are completely unreasonable for any full-time salaried position in town – I know because I’ve had job placement agents (that’s the PC name for “headhunters” right?) tell me as much. At the same time, my rates are entirely acceptable to clients in larger markets. Local businesses are also willing to pay my rates because they are still significantly lower than the hourly rates a full on web shops needs to charge to pay the bills.

    Some of the most talented designers and developers I know run successful freelance businesses or work remotely for companies like Automattic,  Shopify (I believe Shopify has a local office now) and Black Pixel.


  • The One Where I Read The Mule Blog

    I stumbled across the Mule Design blog yesterday. It’s good. I had a minor epiphany (is there a word for that?) when I read this:

    When a client says, “I don’t like green”, most designers translate the sentence into “You must change the green.” But no one asked you to, did they? They merely made a statement about their subjective dislike of a particular color. Your job, as a designer, is first and foremost to listen. And then to gather data. Don’t jump the gun. How, if at all, does the client’s subjective taste enter into the success of the project?

    ~ I Hate Green