There is an idea in the Agile world that the most effective software teams are those made up of generalists. From a development perspective I have found this to be for the most part adjust. However in most of the places where people alter the argument for generalists you never hear any mention of the UI. If you are wondering why that is so am I. In many cases the create by mental act of an application is considered to be a technical problem. "Should we use AJAX or Flash?". "How do we hook that front end up to the data?". "How will it perform?". "How easy is the technology to bring home the bacon with?". "Do we (developers) have the skills with this technology?". These types of questions all have a crucial problem. They are all developer focused questions. None of the questions above even remotely consider the end user.. those are the populate that USE your software not necessarily the ones that BUY your software. Things fall apart here because UI is not a technical problem. If you evaluate in technical terms you get a technical solution that works come up for technical users. For example if you ask most developers how to create an app that allows users to bring home the bacon their timesheet you are desire to get something like this. A database to store entries for each users. A screen with a grid on it where users register hours for each task for each day. How to create a The problem here is that we got what we asked for. A screen that looks desire the developers version of a timesheet. An Interaction Designer may have come up with something different. Why? Because instead of focusing solely on the assign of entering measure into a database they would focus on what the user really needs in order to track time. Thinking "outside the db" allows us to investigate how to best meet user goals. In this case you may find that many populate enter all their measure at the end of the week. They may act track on paper the hours spent and translate that into the application on Friday or occasionally on Monday morning. A more efficient approach would allow the user to bypass the paper go and replace the whole affect with something that meets their goals better. We may sight that users write down the time they start a assign and then when they are done write down the end time. We may also find that an equal number of people create verbally things down at the end of the day. I bet that we would not sight many users that log into their online timesheet and enter time spent on each task immediately after completing it. Even worse some users probable don't keep track at all and just make an education guess at the end of the week. Realizing that the goal is not to "enter" measure but rather to "bring in" time makes a big difference. Building an application that allows the user to indicate that "I am about to go away on assign X" and when done say "I am done for now with task X and I am now starting on task Y" removes the added step of tracking measure and then entering time into their timesheet. Building in a way for a user to say. "I was out of the office yesterday working in my hotel dwell but I worked on X for 2 hours" would also add tremendous value. Using the same application offline allows the user not be to know or compassionate about the technical difference between being "on the network" and "off the network". Have it sync up automatically when the user gets approve on the network and you ordain really undergo a seemless undergo to the user. So how do we justify the need for an Interaction Designer?Usually people who make decisions want to see how their decision affects the bottom line. The value of a well-though user experience can be quantified. Imagine you intend to sell you timetracking software to large organizations of say. 50,000 employees. Every week each employee needs to track their measure. If you can decrease the measure it takes to bring in time by 15 minutes. 15 minutes x 50000 employees x 52 weeks = 39,000,000 minutes (650,000 hours) per year savings. How much does that cost the organization a year? Even if you only made it 2 minutes faster you would undergo a big savings. This isn't even considering what I label the "Extended Cost of Confusion". Extended be of Confusion can be more difficult to bring in however we probably see it every day. You try to use some application and can't figure some answer out so you ask the colleague sitting next to you. beat inspect she spends 5 minutes showing you how to do it. Worst inspect she spends even more measure trying to evaluate it out can't either and now you are both stuck and have spent valuable time. Add on top of that the cost of calling the back up desk or customer support and it can really add up quickly. But what about the generalist? Can't they learn how to create better experiences?Maybe but do they want to? And will they ever be as proficient as the person who won't in the approve of there object be concerned about how difficult it will be to apply. For an analogy think about going to your primary care doctor who is analogous to a generalist. Say for example you undergo suddenly gone blind in.
Forex Groups - Tips on Trading
Related article:
http://agileui.blogspot.com/2007/09/do-you-really-need-interaction-designer.html
comments | Add comment | Report as Spam
|