Tag Info

The easiest way to fix it is make them the same people. Hire people with both UX and development skills. Knowing code makes your UX better, because you know what is possible and what the impact of your UX decisions are. Knowing UX makes your code better, because you can prevent development decisions from compromising the experience. They're ultimately two ...

From what I have experienced, it is rather a problem of team management than a problem specific to UX VS. Developers. Each company will have the risk of two teams being in a competition, whether it is the cooks VS. the dishwashers in a restaurant, the drivers VS. the mechanics in a bus company, etc. Based on that, try to reduce group separation. Having ...

First off, it's not wrong of the client to refer to the admin side as back-end. It's actually fairly common terminology to call any aspects of a content management system that aren't publicly available the "back end." This confusion between the front and back end of a CMS and the front and back end of code may be a large part of the problem you're ...

Normally, I prefer to start with a example which may not be the project core but explains the client the philosophy behind. And once the client understand the concept he starts believing in you and then you should bring in the core topic. Let me explain you with an example. First try to explain you Front-end and Back-end idea with reference to something he ...

This is not the definite answer, but perhaps you can try to think of the difference between UI/UX and front-end development as the difference between design and implementation. The problem is that UX designers tend to come from either a graphic design or software development background, and so there are naturally overlaps between their role and that of a ...

Involve developers in the design process. This helps developers understand what how and why the design is the way it is, and it helps the designers understand any technical limitations there may be and look to create a design which enables it. It also helps create empathy amongst teams to understand what each other are working towards. There should be a ...

Personally, I love Balsamiq because it allows you to focus on the information and interaction, and not needless details. This is right level for functional design that has to be passed around and agreed upon. However, this has to be translated into detailed specific layout. This is best done by the actual developer, and possibly with an agile review cycle ...

A customer probably doesn't need to know or care what a back end or a front end is. To the user it is simply a website and all they are worried about is the website to working to do what they need. The complexity of the details like this are things that we concern ourselves with, not them, so trying to explain to the customer is defeating the purpose of ...

User Experience is something that many people claim to do but few do it well, the reason there is so much work out there for people who only do user experience (and are not visual designers and/or front end coders). Usually the larger the project the higher the need to have a dedicated user experience person / team. It's much like constructing a building. ...

Ideal solution is that UX and Front End Dev aren't separate departments run by different managers and housed in different org charts. How practical that solution is entirely dependent on your corporate structure. I find the bigger the corporate structure, the more segregation there is between each individual component of the process. What happens where ...

Though I like J. Jeffryes answer,my primary challenge with that is that not only are people who can code and design expensive,they dont really have time to focus on multiple tasks in parallel i.e. code and design at the same time.Also throw in the mix of having to attend UI reviews, usability testing sessions,code reviews and product management stuff and you ...