Back in August I had the pleasure off hearing Jason Fried of 37Signals discuss 37Signal’s philosophies and methods. The presentation essentially followed the same script & theme which you can see here.

For those unfamiliar with 37Signals’ software and design principals here are a few examples to give you a flavor of their thinking:

• Less is more.
• Meetings are useless.
• Working remotely and collaborating is better then being in an office and interrupting each other.
• Chunk large projects into smaller bits which can be completed quickly.
• Focus on speed rather then perfection.
• Don’t do specification, wireframing or usability studies. They are a waste of time.
• Personas are bullshit.
• Invest in what doesn’t change like speed and customer service.
• Roadmaps and planning are useless.
• Morale feeds off progress.

Now, I’m a big fan of 37Signals and what they have done; however it’s a mistake for interactive agencies, web designers and developers to wholeheartedly adopt 37Signals’ ways of working without establishing a strong reputation first. It is key to point out that 37Signals is a product development company, not an agency focused on developing marketing sites or building custom client applications. 37Signals builds for 37Signals!

I asked Jason, “Why don’t you do consulting work or client work any longer?” His response was “it isn’t profitable compared to product development.” I’m sure he is 100% correct. The 12 person team at 37Signals is raking in millions of dollars in revenue each year. By contrast client work is time consuming, labor intensive and involves lots of education between both sides of the project. We are a company of 9 people and we haven’t even crossed the million dollar revenue mark yet.

Jason’s presentation did address several audience questions about client work. Which can be summed up as follows:

• Select your client’s carefully. Not every client is a good match.
• Train your clients on how you work, rather then how they expect you to work.
• RFPs and scope-of-work project estimations should be avoided at all cost because the written description can be interpreted differently depending on the reader.

37Signals originally started as a web design company and then they morphed into a product development company because the product work was far more profitable. Therefore I have to be critical of how their recommendations apply to us interactive agencies. Their advice doesn’t come from success in the client services area!

The ONLY way a client is going to be willing to accept those 3 points is if they know your agency’s record, and they RESPECT your abilities above all other agencies. Let’s use an example. If Widget Corp is looking for an agency to redesign their aging ecommerce site, and two other equal agencies are willing to bend to the desires of Widget Corp’s RFP, then good luck getting that project.

There is something to be said about standing your ground and holding true to your principles however at the end of the day if you don’t have revenue, then you don’t have a business. I’m not interested in being a martyr for the cause.

I’ve always admired the work of IDEO. They are a company which solves problems for their clients in a very fluid and evolving manner. They have put themselves in a position of respect, they do amazing work and I’m pretty sure they are VERY profitable. Any web company doing client related work would be well served to study the success of IDEO while blending in the philosophies of 37Signal’s product development methodologies.

At Imulus we plan on doing things differently. We’ll be proof that a interactive agency can develop great products while doing extraordinary client work. We don’t believe the two are mutually exclusive. Our position is the our brand of doing great client work and great product development will put us in a position of respect. This position will allow us to negotiate using the 3 points above.

This is our position and what makes Imulus unique in the realm of interactive agencies.

We don’t use Monster, Dice or CareerBuilder to find our next employee. Instead we are big fans of Craigslist and highly focused community sites. For instance, when we are looking for CSS Expert we’ll target CSS Beauty.

Any job posting usually nets 20 resumes a day for at least 1 week after the posting. Experience ranges widely across any of the resumes we receive. We’ve seen everything from individuals who think they are a God’s gift to us; to people who have amazing web skills but send resumes loaded with typos and broken links.

We don’t read every line in a resume. We don’t have time for that, instead we believe in the “Blink Test“. We are looking at each resume for “it”, whatever “it” is. This means that each resume is scanned and decided on in less then 20 seconds. If we find a resume which takes longer then 20 seconds to evaluate we move it to the “maybe” pile and it’s passed onto the office for evaluation. If the majority of the office is intrigued then we move the resume to the “strong” pile where we proceed to the interview process.

So what is “it”?
There is consistency to our approach. I believe there is a set of 4 characteristics that the “maybe” and “strong” piles have in common.

• Simplicity: We look at the candidate’s ability to communicate their skills in the most concise way possible. This extends into code and design, not just written communication.
• Honesty: Yes, everyone believes they are hardworking, dedicated and organized. However, let us call references to figure that out for ourselves.
• Show Us: We are not looking a monster list of applications used, but instead we are looking for examples of how the tools were used to solve problems.
• Writing Skills: It’s tough to hide the inability to write. If the resume is fraught with poor grammar, typos and sentence structure then it will lead to ineffective email communication or poor internal documentation. (This one personally is my biggest challenge.)

So, if you know anyone who has these characteristics and is looking for an job, send them our way.

Being a small business owner and a supporter of Barack Obama I really want clarification on Joe “the Plumber” Wurzelbacher’s two-hundred and fifty-thousand dollar question.

In the video Joe tells Obama that he is “getting ready to buy a company which makes between $250 to $280 thousand dollars a year.” OK… stop right there, is this gross or net?

As a small business owner you are taxed on your NET profits, not your GROSS. Let’s just make some guesstimates here, say Joe has 2 other employees. If Joe’s business is pulling in $250k a year and you minus expenses, say $45k per plumber, plus the cost of the trucks, gas, health insurance and various other expenses, then Joe might be left with under $100k in taxable salary.

Under Obama’s plan Joe will pay less taxes. This isn’t rocket science and I’m not sure why the difference hasn’t been asked. I blame Obama for not asking the right follow-up questions to Joe.

If Joe is REALLY pulling in NET profits of $260k then I’m going to start learning how to lay pipe!

Right on the heels of my Quantcast posting; I’ve decided to give Quantcast some respect for helping me figure out which of the microblogging services are on the rise. My gut told me Twitter and it looks like my gut was correct.

Initially I thought this chart was showing me the rise in interest in Twitter and the adoption of it by so many new users. However, ff we make this chart relative it even suggests that Pownce and Jaiku are loosing steam / users.

Is there anything wrong with Pownce and Jaiku? Jaiku yes, Pownce not at all. Jaiku was solid before Google acquired them but it has taken forever for Google to re-open Jaiku for the general public. Pownce on the other hand is a solid service and sometimes seems easier to use and more reliable then Twitter. Kevin Rose and gang are no strangers to high-use sites and I believe Pownce will compete better with Twitter over time.

Tonight Jason Fried from 37signals spoke at the Oriental Theater in east Denver. He discussed everything from client deliverables to the 37signals four-day workweek. In essence, Jason’s talk boiled down to three key points:

1. Don’t work on hard problems. Break them down and keep things simple.
2. Avoid distractions (open office environments, meetings, e-mail, etc.) get a site or product out of your head and into production ASAP.
3. Deliverables are bullshit, clients don’t care, the end product is what matters.

First off, I want to say I have great respect for 37signals and their impact on the industry. Having the chance to talk with Jason about issues such as: stopping IE6 support, disregarding Photoshop in the design process, and scaling with growth, was an absolute treat. Clearly the team at 37signals is one of the most innovative and talented in the industry.

However, I think 37signals dominance in the web products field has distorted their ability to critique the client-based approach. And while I don’t have knowledge to speculate specifically on day to day client interaction, I do have a few things to offer from a developer perspective.

Team chemistry is important.

First, people working from home all the time can be harmful to the group chemistry. Jason and team do a huge amount of work via telecommuting. Relying on campfire, screen sharing, and video chat interactions for the bulk of their communication. They feel this helps minimize distractions and keep people productive.

I’m not sold this is the way to go. I think it’s hard to truly feel connected and dedicated to your team if you don’t spend real time with them. When’s the last time you became really good friends with someone without spending some serious face-to-face time with them? For me it’s never happened, not once. And as great as chatting online is, it’s not the same as being in the same room and hashing things out. You miss the subtle face gestures, the inside jokes, the bantering, and the all around comradery that happens in the workplace. Part of the reason Imulus does great work is because we have dedication to one another. Even on days when I’m completely out of wack mentally I still find myself focused on helping the team. Why? Because I’m relied on to help create the great stuff we build. And I trust those I work with to do the same. As ridiculous as our office gets sometimes in the end we get shit done and we do it for each other and ourselves.

Deliverables have a purpose, it just needs to be refined sometimes.

Second, I don’t buy that all deliverables are bullshit. Just as some companies like to skip Photoshop (37signals) and go straight to coding, and others (Apple) like to make mockups pixel perfect it’s impossible to say that one solution is better than the other. Yet, we can agree that certain processes work better for certain people as well as certain projects.

Let’s talk about the way we work. Imulus’ basic approach is to offer the client a timeline, design brief, wire frame, and mockup of the final interface. Now, it’s important to realize that we haven’t always done it this way. In fact, for some time before I came to Imulus the wireframe process was basically nixed. What was the result? Instead of 5 hours spent reworking things in the wire frame process, 25 hours was spent reworking things in the development process. Look, we aren’t naïve, we recognize that clients change their mind and get new ideas all the time. However, we’ve found that most of this re-thinking takes place in the wire frame stage. And therefore we save hours of coding changes by altering the approach up front. In essence, if you’re building a car and the frame is faulty, why wait until the upholstery’s getting put on the seats to fix it?

Still, we know it’s a strong possibility that some of our deliverables are blown out of proportion. And as most firms do we will continue to collaborate and narrow down our inefficiencies. However, we have found that some deliverables are an extremely important step, and just because some projects or companies don’t require them doesn’t mean they aren’t important.

In conclusion

Clearly 37signals has clout and track record to support the way they work. And regardless of how that alters the Imulus process we love hearing about it. It’s phenomenal that they have so much passion behind what they do. I hope over time we can refine our own process to the point they have. Until then it’s great hearing a second opinion about things.