Posts Tagged ‘process’

Our Four-Day Work Week

Thursday, March 10th, 2011

(Update: Though I mentioned it on Twitter, I neglected to make reference here that I was inspired to write this post by a similar one written by Cameron Moll.)

Ever since Angela and I started Unit in 2007, we’ve made four-and-a-half day work weeks the norm. Our reasoning for this schedule is twofold. First, we find it simply doesn’t take five full days each week to accomplish our work, provided we work smartly. Secondly, and perhaps most importantly, it’s a quality-of-life choice.

One of the fundamental tenets of our practice is to cultivate a high quality of life for ourselves and our team. We’ve learned that our quality of life is improved significantly when the work week is shorter, allowing us to spend more time with our families, on individual pursuits, and away from the rigorously-professional processes of work life. While all of us here greatly enjoy our work, we value the idea of responsibly fitting work into our lives, and not the other way around.

We have rules for Fridays. No project launches, no discovery meetings, in fact no meetings of any kind. Friday is when the pressure valve is opened, not tightened. Working smartly, most of our project work is accomplished in just four days. There are exceptions, but Friday half-days here are often when folks use the structure of office time to work on personal projects, to write articles or blog posts, or to catch up on things left behind by the sometimes overly-structured activities of the work week.

It’s worth noting that we’re able to make this sort of schedule work because we run a tight ship here at Unit. Everyone on our team works in a highly-organized manner and runs his or her projects such that everyone involved—our our side and the client’s side—knows exactly what’s being accomplished, by whom, and when it is due. This along with clear and regular communication among those involved in projects ensures that there are no loose ends that invite unnecessary interruptions or crises on Friday afternoon. In short, if the phone rings on Friday, it’s a new inquiry and not a current client.

Our folks value how we structure the week and how it allows for no-pressure, half-day Fridays here, and that pays off in plenty of tangibles and intangibles for all of us. If you employ the requisite organization and professional practices, there’s no reason you can’t do the same and enjoy the many benefits that come from this sort of schedule. I wholeheartedly recommend it.

New Product from Unit: Curations

Thursday, October 7th, 2010

We are very excited to share with you the latest in UI goodness: the Curations Series.

A Curation is a polished distillation of the best thoughts and articles the people of Unit have to offer on any given subject, taken from this blog and our personal sites. Each Curation volume is laser-focused on keeping your design, development, and professional chops at their absolute best.

Here at Unit we are unabashedly proud of how we do business, and we want to share these processes with you. So, quite fittingly, we open the Curations Series with PROCESS, a collection of short essays on design project process. PROCESS contains examinations and advice on aspects of design project process, such as working with overseas clients and other agencies, team interactions, handling deadlines, conducting design presentations, maintaining professional integrity, and much more.

On sale now in PDF and ePub formats. Enjoy!

Working with Multiple Agencies

Wednesday, August 11th, 2010

Unit’s approach to working with other agencies to successfully bring a client’s project to fruition is simple, straight-forward, and has had a genuinely positive impact on the quality of our work. It allows us to maintain professional relationships. It ensures the client receives our best effort. It enables close collaboration with the other contractors which provides the best possible results in the final product.

Despite these obviously desirable outcomes, our approach seems to be the exception rather than the rule in the web design and development industry. What follows is an explanation of the way in which we prefer to work and why it is the best-case scenario for our clients.

The Allegory of the Stool

To understand the client/agency relationships we encourage as well as why we believe they are effective, it is useful to consider a stool. Building a simple stool is not a particularly daunting task, but doing so successfully does require attention to a few critical details. The stool is the configuration of pieces (people) chosen to bring a project off.

The first critical element of a stool is the seat. The seat is the reason for having a stool in the first place and without a seat one can never have a stool. The seat is the project.

Next, one must add some legs to the stool in order to elevate the seat. After all, a seat on the ground does not a stool make. But how many legs to add? Can we get away with just one?

The One-Legged Stool

As it turns out, yes! A stool with only a single leg can be made to balance if it is carefully constructed and never disturbed. Yet, it is far from an ideal construction. It can tip in any direction and will do so when presented with the slightest turbulence. A person may sit on this stool, but not without constantly working to stay upright. Successfully using a one-legged stool is a precarious balancing act.

One-Legged Stool

A project set up as a one-legged stool provides many points of failure and inherent instability.

In the design world, one-legged stools come about because of the all-too-common practice of subcontracting. More explicitly, they occur when Agency One are hired to deliver all aspects of a project and then Agency One, in turn, hire Agency Two (or more) to handle aspects of the project Agency One aren’t equipped to handle on their own.

There are myriad issues with subcontracting and in his article Lies, Deception, and Subcontracting, Andy has written about them at length, but the short version is that at some level the agency is dealing dishonestly with its client.

At worst, the agency is deceiving the client into believing that the agency is capable of work it cannot do and must hire others to accomplish. In this situation the client is kept in the dark about who is actually doing the work and a facade of responsibility is maintained by the agency. Participating in such a scheme is not only bad news for the project, it is also patently unethical.

Not all subcontracting is based on deception however. An agency could be perfectly forthright with its client about what its true capabilities are and who will be doing which parts of the project. Unfortunately, even a transparent subcontracting situation is a dishonest one. The agency is still assuming responsibility for work it isn’t doing and people it doesn’t manage. They are still building a one-legged stool.

Project collaborations set up this way are so unstable because a failure at any point can topple the whole process:

  1. If the subcontractor fails, the agency can’t pick up the slack for work it couldn’t do in the first place.
  2. If the agency fails (or bails), the client loses all of its hired talent.
  3. If the client pulls out, the agency is left holding the bill for its subcontractors.
  4. Depending on the situation, any of the preceding can result in litigation.

At Unit, we flat refuse to be part of the house of cards that is a one-legged stool project. Most of us have had the experience at some point in our careers and were left understanding just how demeaning and unprofessional subcontracting really is.

The Two-Legged Stool

Two heads are better than one and so is a stool with two legs better than the contraption with just one. While inherently unstable, a two-legged stool is easier to balance on because it can only tip over in two directions. Its instabilities can be predicted and planned for by an alert sitter. Still, the stool is not constructed for success and sitter is solely responsible for keeping the seat upright.

Two-Legged Stool

Two-legged stools are usable but take a lot of work to keep upright.

Clients, especially those that are unpracticed at managing such projects, have a tendency to segment the workflow. Perhaps they prefer to first produce all of the design comps and then later worry about building the site out. Or maybe they desire a working product before considering the design. If the project is not segmented chronologically it may still be segmented by function with the client providing all of the communication between different agencies.

In whatever arrangements the pieces end up, a two-legged stool is created when the client works directly with the involved agencies (good) but the agencies work independently of each other (not as good). Everyone is in an honest business relationship and there are fewer points of failure, but the project is susceptible to two major flaws.

Chronological Segmentation: Every project has tweaks. Adjustments must be made as the various pieces are integrated. If the project is set up so that one agency must fully complete its work before the other begins, then these adjustments become a major hassle instead of a natural part of the project end game. The worst outcome of this is the loss of trust from the client’s perception of a job imperfectly done.

Function Segmentation: It is proper that different people should handle the aspects of a project that fit with their expertise. But if a client keeps these people ignorant of each other it is setting itself up to be the communications hub for people who need to speak a completely different language.

Clients are experts in their business (or should be if you are going to work with them). They are not experts in your field and trying to communicate with other experts through your client is an exercise in futility. Not only will the messages not be conveyed clearly, but since neither agency has a commitment to work with the other, both will be mainly concerned with protecting their reputation (and work) from the influence of the “other guys”. This is far from ideal and puts the quality of the finished product in jeopardy.

Two-legged stool projects are not the end of the world and they can produce great results, but they do so in spite of their flaws. We see our fair share of these projects at Unit but it certainly isn’t our preferred way to work nor is it what we suggest to our clients.

The Three-Legged Stool

A stool with three legs is fully stable. It stands on its own. It supports a weight without the active involvement of the sitter. It requires a strong jolt to upset the balance of a stool standing on three legs.

Three-Legged Stool

Three-legged stools are the most stable and best set up for success.

When the client is working directly with all agencies involved in a project, and those agencies are collaborating with each other, a three-legged stool has been achieved.

It is the best-case scenario for all involved parties. The agencies are only contracted to do the work they are best suited for. They all have a direct line to the client and each other so no intermediary translation is needed. They can collaborate to integrate and adjust the project without affecting project quality or disturbing the client’s trust. The ramifications of any one party’s failure is mitigated as much as possible. Best of all the work, and not the politics, is in the best position to receive everyone’s focus.

This is how Unit loves to work. Three-legged stool projects have demonstrated superior results time after time and so we recommend it to all clients seeking our services.

In Case of Design — Inject Critical Thinking

Tuesday, June 8th, 2010

Frida Jeppsson has just released her curated collection on critical discourse, In Case of Design—Inject Critical Thinking, featuring essay contributions by Max Bruinsma, Gareth Williams, Donna Loveday, Rory Dodd, Steven Heller, Rick Poynor, Michael Rock, Anna Gerber and Teal Triggs, Kate Andrews, and myself.

In Case of Design--Inject Critical Thinking

I just received my advance copy yesterday (took a while to go from Sweden to Texas), but the book is now available from Frida’s website.

The essays in the book examine critical discourse from several vantage points and in different contexts. As the editor, design critic and curator Frida Jeppsson puts it, “The book is as much an experiment as an excursion aiming to investigate what scenarios, results, and opportunities a new language and an illuminated and extended critical discourse can produce.” Having just received my copy, I have yet to consume the entire contents, but the parts I’ve read have been wonderful and, given the other contributors, the rest promises to be excellent.

Hats off to Frida for collecting thoughts on this important topic and presenting them so nicely. And thanks so much for including me among the contributors.

Scoping a Project

Tuesday, June 8th, 2010

Wireframes

Here’s a set of project wireframes up for evaluation as part of the scope-defining process for a project bid. So instead of 56 separate templates to design we defined 31 modular components (for design/CSS) and some variations on form layouts. What seemed a large-ish design project became far more manageable after an inventory.

Not all project scope processes are this involved, but the occasional wallpapering exercise for evaluation can help. Good times.

Makin’ Days

Tuesday, February 9th, 2010

We didn’t have to create Just Made My Day. There was no imperative dictating the (at this moment) mostly unprofitable format, and definitely no room in the market for another site that lets users share updates about their lives. We did feel, though, that it was worth it to craft a little beacon of positivity on the oft-negative internet. It has been so good to us, after all.

The following is the casually recollected time line of concept-to-creation for Just Made My Day: Unit’s latest way to brighten people’s day:

Concept

Nov. 4th, 2009 — An idea comes to Andy while showering. Not specifically focused on anything, he thinks about how nice it would be to create a place online where “folks could just celebrate the cool things that happened to them, especially the cool people who did something nice for them”.

Nov. 5th, 2009 — Andy takes R.A. and me out for coffee. The trip is a Trojan horse laden with a new undertaking for Unit. It’s solid idea from the start: “Just Made My Day” (JMMD if you’re savvy) will be a site to allow users to easily share the little things that make them happy. We discuss the various implications, difficulties, and merits of launching such a site. Quick sketches and wire-frames are scribbled on scrap paper. R.A. uses phrases like “implicit moderation” and “social-media authorization APIs”. We emerge highly caffeinated, with a foundation for moving forward.

Design

Nov. 5th, 2009 — While watching a documentary on Monty Python—Almost the Truth: (The Lawyers Cut)—I think it would be nice to rip-off Terry Gilliam’s collage style for something. It occurs to me that JMMD would be ripe for experimentation.

Nov. 6th, 2009 — Although there’s no plan for me to design JMMD, I decide to get a jump on a look and feel rattling in my head. I spend a quite Friday morning making a collage of landscape elements. I want to create an impression that is inherently positive, and will behoove users to behave. While playing with more organic layouts of nature, I realize that a fully symmetrical approach allows the landscape to both be more pleasant, and act more as a background to the form elements, not a focal point. The resulting masthead gets me excited; I decide to finish a full design comp.

Nov. 10th, 2009 — I finish out a full comp of the site design. Somehow, the thrill is gone. I wind up with what I feel is a muddy attempt at redesigning Rotten Tomatoes. The design needs more simplicity, and serious amount of editing. It occurs to me that I’m riding a little too hard on the landscape concept; it needs to be a website, not an art project.

Nov. 13th, 2009 — I show Andy my design. We decide this is the right direction, but it needs some work. Angela later tells me about some great little games on the Xbox arcade.

Nov. 17th, 2009 — On Angela’s recommendation, I download Braid late one evening and am blown away by its ingenuity and pure artistry. Shortly before bed—still humming a haunting tune from Braid—I have a few design-related epiphanies. When I say them out loud, my sleepy wife does her best to act like I am smart, God bless her.

Nov. 18th, 2009 — I complete the design that will become JMMD. I make some tweaks to the form to give it affordance, and help it feel more balanced. Now, we’re ready to build this thing.

Development

Nov. 19th, 2009 — The entire Unit crew sees JMMD as an opportunity to push our knowledge. We have already begun delving in to HTML5, and this looks like another great opportunity to work with it. I think that a parallax technique will really make this design sing, and begin learning how to pull off such a thing.

Nov. 24th, 2009 — I finish the parallax effect, add some birds and the main title in Chunk Five, using some @font-face goodness via Font Squirrel. I put up a teaser site, and begin developing the rest of the site.

Nov. 25th, 2009 — I really want to make sure I am using HTML5 to its fullest, so I read up on everything. I start working heavily with CSS3 techniques as well. We discuss the ramifications of leaving Internet Explorer in the dust. We are okay with this.

Dec. 7th, 2009 — I finish front-end development. We decide WordPress will work best as an engine for posts. I begin integrating a theme and R.A. helps me build a set of plug-ins to allow users to post. Basically, we turn WordPress inside-out. Next, we begin learning authorization APIs for Twitter, Facebook, and Open ID.

Dec. 18th, 2009 — Early on, we decided that in order to lower the barrier for entry as much as possible, we would need to allow users to log in using social media accounts. We were sure they wouldn’t want to create and remember a whole new account for our little site. Twitter authorization (oauth) was the easiest (IMO). We test and then soft-launch JMMD without Facebook or Open ID integration. Over the holidays, we leak the site to a few friends and family, and allow some initial posts to build up.

Jan. 13th 2009 — I finish up Facebook authorization using Facebook Connect. We use RPX to allow Open ID. Next we fire up the Twitter clients and start telling the loyal web denizens of our latest project.

Epilogue

So far, response has been overwhelmingly positive. Even if it were a failure, though, this scrappy Unit staff was able to take a great idea from concept to launch in just over 2 months. We learned a lot and we are proud of the fruits of that labor.

Thank you to everyone who is making days, or sharing about days made!

Hey Unitards! Are Graphic Mock Ups Even Applicable?

Thursday, August 7th, 2008

Andy Says: I think the most conspicuous examples of those who don’t use graphic mock ups in their website/app projects are companies who don’t have clients. They build applications for themselves to then market as products. This context is significantly different from that of designing for clients. Clients generally need to see something concrete and tangible in order to invest full confidence in your work, especially when there are important branding concerns associated with it. For my work with clients of Unit Interactive, I always craft graphic comps. I’ve often skipped this phase when working for personal projects, but that’s an entirely different context.

Angela Says: I have always produced comps for the designs I’ve created for my clients. Creating comps first allows you to really think through the information design and defines the structure the site will take on. In essence, you are creating a blueprint that dictates the end result and allows for quicker development time, as the design decisions have already been decided. Would a good contractor start building a house without architectural plans? Would you want to live in that house after it was built?

Also, I advocate the HTML being semantic and some of the design decisions made in the comp stage can help determine the correct context for the markup. And one more thing, any graphics that are used in the site have to be created anyway, so why not pull those graphics from the whole picture that you’ve already poured over in great detail, rather than making them piece by piece as you go?

Nathan Says: Photoshop [Macromedia savvies read “Fireworks”] cannot correctly emulate the browser environment. It’s true. The fonts are handled differently, colors skew, and pixel-perfect negative space sometimes requires lots of finagling. This fact makes me think I should go all 37signals on Adobe a give it the cold shoulder. But then I remember a mantra from my design education: Always start in pencils. Pencils allow for the exploration of more ideas in a shorter amount of time than full Photoshoped comps. This helps me to not lock in on any one idea too soon, and stay focused on concepts, eschewing execution until necessary.

Graphic mock ups set a foundation for a completed, functional site in much the same way that pencils lay the groundwork for the aesthetics: by allowing me to focus on only what is necessary for that step in the process. Also, in my experience, clients have a hesitancy to skip steps where they should be able to provide input and/or approval, and by giving them that stake in the visual approach, you build a trust that allows further decisions to go more smoothly.

Beyond Comp Review: Two designs enter. One leaves.

Thursday, July 31st, 2008

In my previous experience, I had always heard “Marketing execs/business owners are Type A Personalities, so they like to see as many options as possible…” This modus operandi kept me overworking conceptual failures, over-thinking muddled compositions, and mired in revisions. I could see that this system was broken, though I wasn’t sure of how it could be done better.

Once I became an official Unitard, Andy and Angela introduced me to their two comp approach. As Andy puts it: “We try to give two intelligent design directions, because after that we’re just finding new ways to decorate the information”. This was compelling, but it wasn’t until I adopted this practice myself, that I fully understood the benefits. (more…)

Recommended
Most Popular
Underappreciated