For years we have always done milestone approvals either by verbal approval or simple email confirmations. When I used to work at Refinery (now G2) we tried doing the legal / contract version of project approvals. I found that method to be cumbersome and difficult to quickly deploy. We’ve decided to try something new and I think it’s worth sharing. We’ve decided to use Wufoo. Using this service we can share pre-developed approval forms which log client acceptance along the development process.

I’ve blogged about Wufoo in the past. I think these guys are one of the most underated Web 2.0 companies out there. Their interfaces a rocking and their shit just works real well. We’ve setup about 14 pre-defined forms, which can be shared with our clients for approvals which take less then 30 seconds to read and submit.

Here is an example.

Here is what we are hoping to achieve with this shift in our process:

Deliberate Action. It’s too easy for a client to just give verbal approval, or reply to an email. Filling out a short form is a deliberate step which requires the user to read before taking action. It falls outside the normal workflow enough to be memorable.

What am I Signing? A short explanation helps the client understand the impact of what they are signing without all the legal mumbo-jumbo of a contract. It’s enough to explain the point and nothing more.

What’s Next? Once signed, what does that actually mean to the client. This is a friendly reminder of the next steps which will be taken on the project along with a statement about what it means to give approval to this task.

Get to Know Us. A quick “Thank you” followed by a “Did you know?” We see this as another opportunity to interact with our clients in a way which helps us better know each other.

I sincerely hope you try using Wufoo to replace the old sign & fax forms of the 80’s. I’d like to hear the results if you do make the switch.

I haven’t posted a critique on motion graphics in a while, and I know how much you have all waited and pined for another so here it is. What is the deal with all these commercials stealing their ideas from viral videos? (she says in her best Seinfeld voice). I get that it’s kind of cute and funny in an inside joke sort of way. One of the funniest music videos is Weezer’s Pork and Beans. This is mainly because they’re intentionally taking the viral videos that we all know and love and using that as a media.

What bothers me are the commercials that steal concepts from viral videos and it is unclear if they’re trying to be cute and pay homage to the original or if their just blatantly ripping it off. The video “Drive Through Rap” was remade into a commercial for Taco Bell. Personally I don’t think this is an homage, this is just a rip off.

Recently I saw a stop motion commercial that looked suspiciously like the animations from BLU. In this case I’m not so sure this was a rip off, because BLU themselves may have been responsible for the commercial. I unfortunately don’t know enough about the company (or who the commercial is for) to say for sure.

If any of you know any more please let me know. I am constantly amazed by the impact that YouTube has on our culture. (Please note, I intentionally left out the sand art commercial because I wasn’t sure if that was a viral video before or after the commercials — or if it counts as a viral video.)

Tonight I watched a phenomenal TED Talk given by John Francis. A man who is a leader and role model in in the field of environmental activism. For seventeen years he did not speak, but rather spent time listening, thinking, and writing. His story is fantastic and a great reminder to all of us that sometimes the most important thing you can do is listen and try to understand other people.

I think that truly listening and paying attention to people’s ideas is something we all could do better.

We run across a lot of discussion whether the stage of wireframing a website is important or not. Should you avoid the process of wireframing and just dive into design? What is the purpose of wireframes and why many designers and developers implement this stage as part of their planning tool?

Wireframes are an essential tool of communication that provide a rough guide to website structure. Their purpose is to give guidence to general layout, navigational elements, and content structure to designers, developers and clients. The stage of wireframing is achieved after the process of sitemaps has been approved. At this time, you should have in your hands a site structure in a hierarchical style. Here at Imulus, we take time at a wireframe stage in order to run the design and developing stage smoothly. Only an educated client will understand this process if explained. Sure, all clients would like to see their website redesigned in 24 hours…that would require a lot of java. We take time to explain to our clients why this stage is important to us and to them as well. They will understand.

Our designers will work through the wireframe stage to completion and then will sit down with our developers to discuss the many possibilities. This opens different perspectives which are always handy to get everything on track. For example, when it comes to talking about some special functionality feature for the site, it is a good thing that developers know this ahead of time and see what’s expected. They can see what problems they can run into and how to solve them ahead of time. It is too late if this got avoided when the design is already in development. As for the designers, it is easier to have a wireframe in hand. You get the idea where things are supposed to be, and start to visualize the design. Try to have some fun with wireframes. OK, sure, they can get boring sometimes especially when it comes to some revisions but that’s all because you’re anxious to start the designing and developing. Also, you don’t have to adhere strictly to what the wireframe is showing. We have run across many times where the wireframe was showing one thing, but in the design stage we have changed it. It’s all right to change the wireframe in the design stage as long as the purpose and direction is not lost. My advice is to spend whatever time necessary to complete the wireframing stage; it will make your job easier in the design stage, and will save headaches to developers, as well as to clients.

A book recommendation to follow on a wireframing stage: Web Redesign 2.0 | Workflow That Works by Kelly Goto & Emily Cotler

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.