Valuebounds User Experience Design Principles-7470d

.puters-and-Technology The key to success of any project is the right approach. We should never be limited in what we can ac.plish; to enlarge the perimeter of our success we must have the right understanding of the world around us. The key to Valuebounds success on project after project starts with the right mindset as personified by a core set of design principles; a core set of values that we use to approach each and every project. Understanding the goals The foundation of a successful project begins before you even start to plan things. The chief thing that you are trying to ac.plish with the project may get lost in the hundreds of details that youre trying to capture in these documents. So, the first thing we want to understand are the real motivators behind the project and how to translate these into business and user goals. Many times, through the process of discovery, we uncover goals that the client wasnt even aware of. At other times, we even identify conflicting goals. We realize conflicts within departments or even conflicts in what the client is trying to ac.plish and what is being asked for. This leads us to our second principle: Question assumptions. Questioning assumptions We try our best not to take anything for granted. If the client specified something in the RFP, we want to know why its in there and how important it is to the projects success. We want to know what functionality can be exchanged for other functionality or ideas that might help you better achieve your goals. Nothing is off-limits here. This process has actually proven to deliver results. Its something like, if you ask for an apple, then Ill give you an apple. But what if it was an orange that you really wanted? Then its my fault for not really probing into your mind to understand what you really wanted, for not questioning your assumptions about what youre looking for. Its the same with functionality. Often clients have very specific requirements around some functionality that they want. However, its always better to question why each bit of functionality has been requested for and concentrate the feature-set on our real goal. Thus, by understanding and questioning the underlying, we can handle the real problems that the project is trying to solve. Understanding the users needs You have your goals, and ask for functionality that you want. Now, depending on them maybe weve even created some .pelling designs around your powerful goals, but how do we know that what you want to build will actually achieve your goals? We are missing some key information here that we can only obtain by talking to your users. Talking to your users or potential users is the best and only way to actually understand how they want to interact with your website or web application, and this is its a crucial way of how we work. Having said that, dont assume that we call up random users and ask them: How do you want to interact with this website? We dont do that, because it does not work that way. Its not your user’s job to know this; its really your job. We can use a range of techniques from contextual interviews to iterative usability testing to understand the users real needs (versus how they describe the need), and often we .bine these two techniques together to achieve great results. Iterate A perfect website cannot be created at one go. What weve learned over the years of our experience is that websites are not fixed; they change and evolve with the user’s changing needs over the time. Just because the project has been .pleted does not mean that the product is finished. As we ac.plish meeting your user’s need, it does not mean that their needs wont change over time or that new needs wont arise. Thus, what we create is the basic building block, the right start. This building block has all the right ingredients and potential that can ultimately be.e something great. With Drupal as your backend, you will have the technology to grow and adapt your web presence as your audience needs change and grow. With this .es our last principle, that is what we want to deliver is a product that is as simple as possible. This is because we dont want you spend time and money building something immense only to find, after launch, that you only needed half of what you built. Starting simple Giving in to a .mon human trait, we all tend to want to launch a web product in the most perfect, and .plete state possible. If we think of a gallery, we visualize Flickr. If we think of a blog platform, we imagine Blogger or WordPress. We never stop to think that these services started out very different than what they have be.e today and maybe have different goals or are meeting a different need than what youre trying to achieve with your web product. The conclusion in fewer words is – start as simple as possible. The first version of the gallery on your website might not be an exact replica of Flickr. And thats perfectly fine, because you dont want to be just another version of Flickr, otherwise why would the users use your site and not Flickr? You want to gain your own territory as an individual business, that is unique and thus, having its own set of users. This is why, by starting with fewer features and concentrating on out.es, we give you more space to learn from your users, to understand what they really want. We also help you to understand and explore how you want to interact with your customers, and how you can build a truly unique user and brand experience for your users. When you truly understand your users needs and ac.plish to provide what they want, your website automatically grows to take the shape of what it actually should be and continue to evolve. This is how we deliver the project and help in its process of growth. Valuebound is a leading Drupal Development .pany providing Enterprise Drupal web solutions. For more information on Drupal Development, contact us at [email protected] 相关的主题文章: