A persona describes one category of the target users of your system as a fictitious but realistic person with goals and needs. It is useful because it summarises the user, their role, their skills and aptitudes, their preferences, and their goals. Personas give rise to user stories, and keep the user stories focused on the goals of real users. The persona needs to include a name and a picture, so that developers, business analysts, and testers can relate to it as if it was a real person. It should include the following details: their demographic characteristics (e.g. age, disability) that might affect their interaction with the product, and their requirements in using it their role in using the software (e.g. admin, editor, contributor, supervisor) what their job title is activities they do in their spare time which might affect their performance (either beneficially or adversely) their goals in using the software common tasks they will want to carry out using the software W...
Sometimes prototyping can seem like a big investment of time, but I find it is always worth it. In this article on User Experience Prototyping , Paul Boag, who has been in the field of user experience for over a decade, writes about the benefits of prototyping. When most people think of prototyping they are thinking about mocking up a user interface. There is no doubt that prototyping can help in this area. Organisations use prototyping to define and test experiences using all kinds of interfaces. Interfaces from mobile apps to enterprise systems. He identifies three key benefits of prototypes: they are inspiring , and allow people to understand what is being proposed, because they show stakeholders what it will look like; they ensure a common vision - it is much easier to agree to something and come away with a shared understanding of it if you have actually seen what it will look like; they are testable - you can actually do usability testing with them and fix any usability issues b...
An easy-to-read prose style is the first thing you need to get people to read your posts. Here are a few pointers: Say what you mean Use an appropriate tone Call a spade a spade – don’t say ‘utilise’ when you mean ‘use’ Vary your sentence length – too many short sentences is ‘choppy’; too many long sentences is boring. Avoid passive voice, e.g. ‘the business was lost by the inability of the sales team to convince the buyer of the uniqueness of their product’ (replace with ‘the sales team lost the business because they couldn’t convince the buyer that their product was unique’) Avoid clichés and stock phrases, e.g. France bit off more than it could chew in Vietnam , and America’s intervention was too little, too late . Avoid too many qualifiers, e.g. Most people usually think that many puppies are generally pretty cute. Avoid too many prepositional phrases, e.g. “the organisational culture of [your organisation]” could be replaced with “the way [your organisation] is organised”. Avoid t...
Comments
Post a Comment