Corporate Conflicts A Cantakerous Cacophany of Confusion.

One topic that constantly is under debate in the corporate design world is: “Who makes the final decision.” Does the designer, business analyst, information architect, developer etc? Personally, this has been a major area of contention. When it comes to design and the user interface everyone wants to proclaim they are Caesar. Can you blame them? Everyone wants to have a say in what an application looks like?

Believe me I have seen some crazy ideas about what a “good application looks” and functions like. Next thing you know you and the rest of your team are throwing around generalizations about things such as:

  • one color is better than another
  • one navigation is better for the users than another
  • one feature is more important
  • one bug is higher priority
  • design is secondary to function
  • one technology is better to use than another

That’s just a short list. It’s easy to see how on a daily basis we encounter these conflicts that can disable, disrupt, and derail a development team. If your team is larger then 5 people this can drastically change your time line. How can you eliminate conflict? Well, the short answer is you can’t, but there is good news. You can begin to identify your sources of conflict and the impending arguments and cut them off at the pass.

Now every once in awhile there are members of a team that are not “team players.” They have such passion and zeal for their work that they cannot and will not back down. Even after reprimands, and threats, and warnings. Your final recourse may be to remove the broken wheel from your team. This happens in corporations as well as independent design teams. Sometimes there is just no recourse, and if you are in that situation and have exausted all your other conflict resolution chances, do you have the balls to make the decision to transfer, or remove the problem?

Stay tuned for more on this topic.

Related articles:

  1. Features In The Front Usability Get To The Back
  2. So what is this corporate thinkers site all about?
  3. Blog Respose: Bowman Leaves Google
  4. When is it the Right Time to Use Icons?
  5. Agile UI Design Series: UI Design in an Agile Project Cycle Part 1

Leave a Reply

comments-bottom

More UI Design Guide Articles

SXSW 2009 Interactive – Survival Guide & Tips This will be my 3rd year attending SXW and every year is different experience. There is  just so much information to gain you will be exhausted. If you aren’t exhausted.  You are doing something wrong. Here are some tips I put together to prepare you before heading out to the event. If you... Mar 5th, 2009 | one response
Agile UI Design: A Fundamental Miscalculation in UI Design Excellence? I’ve been banging my head against a wall trying to figure this question out for some time now.  Can existing in an agile development cycle truly create the best ui design? I’ve worked in Agile development environments. I’ve worked with structured project management. I’ve... Mar 25th, 2009 | 15 responses
UI Design Dissection: Google Reader What Makes an Application Great? There are some applications I never used or expected to use for more then a few days. And in any given week I try out about 10 – 15 new applications. I do this because I love analyzing and predicting new trends, design patterns, and visualizing work-flows. Usually, I end up with using 0 of... Apr 3rd, 2009 | no responses

Twitter is a great way to share new and exciting resources with all our viewers. Each day I provide links and commentary on all things UI. You can find UI resources, UI design examples, new techniques, and a lot more by Following @UIDESIGNGUIDE on Twitter.

The idea for this design blog first came about two years ago at SXSW Interactive.

Currently UI Design guide is in its fourth redesign. This site takes quite a bit of time to maintain as well as write the content. Just like UI Design this site is a passion that keeps evolving.

Inside, I cover articles on many topics icluding: lessons, prototyping methods, agile UX methods, design reviews, design challenges, application features, and of course design experiences, just to name a few.

With all the blogs out there you may be asking yourself who are you to give advice? That's a fair question. If you have a moment feel free to read about my design history.