Posts Tagged ‘professionalism’

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.

Professional Happiness

Monday, February 21st, 2011

In keeping with the feedback and insights I’ve gleaned from my almost daily conversations with designers and design professionals over the past 6 years, Elaine Wherry noted recently on her blog that “UX professionals are some of the most professionally unhappy folks I’ve ever encountered.” She goes on to make a distinction between emotionally unhappy and professionally unhappy, but in practice no such distinction exists. If a designer is unhappy, the work suffers; as does the agency and its clients.

Angela and I started our agency in direct response to the various incarnations of idiocy that cause designers professional dissatisfaction and unhappiness and, as a result, agency and client dissatisfaction and unhappiness. In our previous agency experience we long observed the sorts of poor planning, bad decisions, mechanical disconnects, and perceptional voids that eventuated in corrupted and inferior project processes and results. Therefore, we work to preempt and obviate these things in our own agency so that our team doesn’t have to deal with them in internal and client projects. The result, we’ve maintained, is that we and our team members are far happier and more satisfied than our brethren in other agencies.

I say, “we’ve maintained,” because I wondered today if our folks still feel the professional and personal happiness and satisfaction that we’ve worked hard to facilitate. So I conducted a private poll among our team members. The results: strong as ever. Seems that we’ve still got it.

To be clear, our folks seldom if ever have to deal with idiocy like invisible stakeholders, feet-dragging clients, and approval mazes…and NEVER have to deal with committees, abusive clients, the clients’ processes. In every case it is Angela and I who pick the clients we’ll work with and we who define the project processes. In other words, it is we who maintain our own professionalism and work to maintain that of our staff. As owners, it’s our job.

Equally important to client-centric issues are internal issues. Our designers never have to deal with the confusion and idiocy of shared responsibility. Our internal processes ensure that it is the assigned designer who defines the design process and each knows that it is s/he that has ultimate responsibility for project success. While some or all of our team regularly collaborate on projects, the assigned designer has full responsibility for how to involve his/her peers and for making the final decisions. This, along with investments of trust from both the client and the agency owners, ensures that our folks get to bring their best, uncorrupted ideas, execution, and results to every project.

I make a point of saying so today because, as I observed at the start of this post, so many of our peers do not get to experience this sort of institutionally-maintained professional satisfaction and happiness. I see this as a consequential failing of too many of my agency owner/principal peers. It is a simple fact: if your people are not satisfied and happy, you have failed your mandate and your clients are sharing in the consequences.

Oh snap. Yes, I’m throwing it down. Okay, Angela and I passed this exam this time, but we don’t want to become complacent. It takes work and I just wanted to make sure that we were still successful in that work. Professionalism means doing what is necessary to work happily and uncompromisingly. And uncompromising means uncompromising. You are or you’re not.

Mediocrity and the Innovator

Tuesday, December 7th, 2010

“If there is any one way to confess one’s own mediocrity, it is the willingness to place one’s work in the absolute power of a group, particularly a group of one’s professional colleagues. Of any forms of tyranny, this is the worst; it is directed against a single human attribute: the mind—and against a single enemy: the innovator. The innovator, by definition, is the man who challenges the established practices of his profession. To grant a professional monopoly to any group is to sacrifice human ability and abolish progress; to advocate such a monopoly is to confess that one has nothing to sacrifice.”

— Ayn Rand on “guild socialism”

from Capitalism: The Unknown Ideal

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!

White Labeling Unify

Tuesday, August 17th, 2010

The current model for most web applications gives us a trade-off: free with explicit product branding, or paid with the ability to have your way with the branding. This leads us to believe that there is some actual monetary cost to allowing a change of brand. There isn’t. So what do you get for your money? At best, you get permission to at best confuse or at worst, permission to rip-off your client. This is not creating value. This is snake oil, and at Unit we refuse to take part in this charade.

Justification, Disassembled

There is one very simple reason to not allow white labeling for Unify: any branding change would alter the code, and we cannot properly support our product once the source code has been changed. Beyond this, I would like to put a finer point on our position. The following are some of the common reasons that people use to justify white labeling, each rebutted by our philosophical perspectives behind Unify.

Doomsday Scenario: “My clients will get confused! They need their brand at the top of an app.”

This morning I hit snooze on my Seiko alarm, ate some Kashi cereal,  drove to work in my Jeep, woke up my lazy iMac and posted this to the blog using WordPress. At no moment did I get confused… at least not about the brands I was using. (Thanks to David Airey for his similar progression in Logo Design Love).

Brands are not built to confuse. In fact, they clarify. A brand is a promise between the producer and the customer. Over time it is reinforced by good experiences and destroyed by bad ones. It is an honest face: recognizable and persistent. White labeling masks that face, and what do you consider the intentions of man behind a mask?

With Unify, we are building a brand through consistency and upkeep, and removing the brand would nullify any responsibility we take for our product. Marketing efforts, customer support, twitter chatter, blog posts on updates and improvements; all would be nullified by this obfuscation. This cost is too high to negate all of these efforts in the hopes of not confusing people who are smart enough – and familiar enough with brands – not to get lost.

The Appeal to Revenue: “You can charge tons more for a white label license! I will pay it!”

The only person who “pays” when costs go up is the end-client. The problem is, as explained above, THEY see no benefit. The only person who benefits from white-labeling is the middleman. The go-between gets to represent someone else’s work as their own, and the client pays a premium. How is this fair?

We have crafted a price and a model for Unify that correctly reflects its value. Inflating this price is not in our best interest. This larger price would communicate to those fitting the bill that there are more features, larger resources dedicated to customer service and bloated expansion towards bells and whistles. This is not our perspective on Unify. Unify is a simple tool, like a hammer; it does not bludgeon better with a different name on the side.

Also, there is an idea that comes up intermittently in our white-label discussions: that our “real” customers [designer/developers] want to be able to put their name on our product to make them look good. They are willing to pay five times the price – or more – so that they can tell their client that Unify is a custom-built CMS tailored to their needs. This, of course, is lying and is the worst possible justification for white labeling.

Truth be told, we want to look good, too. Not the “we” of Unit Interactive, but the “we” that makes Unify. We take pride in our product, and again, we want to build a brand behind that product that adds value and trust. We are not in the business of artificially inflating other people’s prowess. We only want Unify to be the best product for the people who have to use it every day.

High Anxiety: “My client will not understand why I charge my fee for a CMS when they can find that your product costs under $25.”

How a professional justifies their rates is not our business, but there is an easy answer to this: Time. Unify takes time to plan, install and to test (not much, though). One’s time is still worth money, so charge accordingly. If a person cannot rectify their rate with our price and their time, that person needs to sincerely reevaluate their pricing.

A Contrast in Black & White

“…black labeling is the practice of offering a ghosted service; where authorship, responsibility, or accomplishment (or all 3) are misrepresented in order to hide the truth of one’s inadequate skill, responsibility, or accomplishment. In plain English, by word this is known as lying; by deed this is known as deliberate deception.”

Here, Andy has drawn a decisive line between the honest uses of white labeling, and what he calls black labeling. By his definition only commodities can be appropriately white labeled. By our definition of what our actual product is – consistency of innovation, customer support, and a determination to keep things simple – Unify is a service. The code changes, but our commitment to serving to our customers stays the same.

Any attempt to white label Unify would really be black labeling, and would destroy Unify. This is not merely my opinion: it is the result of much internal debate and input from users – mostly to the contrary – that has led me to firmly stand against the ability to re-brand Unify. In most implementations, black labeling destroys brands and experiences. Where some argue that it adds consistency, it instead severely muddies the water for the people who are our main concern: the user. White labeling should be relegated to the few opportunities where it makes sense, and it is disheartening to see that it has become so ubiquitous in the life of a web designer.

SXSW Panel on Client Interactions

Thursday, August 12th, 2010

I’m pleased to say that talented designer, developer, and pro advice maven Lea Alcantara is pitching a 2011 SXSW panel on client interactions and has asked me to take part. Along with Rogie King and likely one or two others we’ll be discussing how we maintain professional and successful client relationships.

The SXSW Panel Picker lists the panel thusly:
Getting tired of all the client hate? There are a ton of articles, videos and parodies out there that bemoan the client-vendor relationship. But does it really have to be that bad? A panel of esteemed professionals of all types (freelancers to studio honchos) explain how they get and keep their BEST clients, and how we can turn client meltdowns into client success (which means a happy you).

  1. What’s the craziest request you’ve fulfilled for a client?
  2. What are some ground rules you set with clients at the start?
  3. Give me an example where you turned around a sour situation into an excellent one.
  4. How much of your client work is based on referrals?
  5. How important is it to maintain relationships with current clients? How do you maintain them?

If you’re going to SXSW and would like to attend this panel, of just think it’s a worthwhile exercise, vote us up and get us on the schedule!

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.

The Most Important Element of a Professional Designer

Tuesday, June 8th, 2010

Eyes Ears or Mouth?

Recommended
Most Popular
Underappreciated