• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Prioritising almost anything – UXcamp London

Prioritising almost anything – UXcamp London



Presentation I gave at UXcamp London in August 2009. ...

Presentation I gave at UXcamp London in August 2009.
A little technique to help prioritise almost anything, alone or with a group.

Download this presentation and the templates here:



Total Views
Views on SlideShare
Embed Views



13 Embeds 2,456

http://evalottalamm.wordpress.com 2032
http://www.projekt-log.de 348
http://www.slideshare.net 23
http://www.linkedin.com 16
http://lanyrd.com 14
https://www.linkedin.com 6
http://vizthinker.com 6
http://wearethreesixty.com 4
url_unknown 3
http://1x9.tumblr.com 1
http://www.mefeedia.com 1
http://www.lmodules.com 1
http://translate.googleusercontent.com 1



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.


12 of 2 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Prioritise what? <br /> Anything really <br /> Todo lists <br /> Things you want to see on your trip to Paris <br /> Business opportunities <br /> Feature lists
  • Why prioritise? <br /> <br /> Bringing things in order <br /> deciding what is important, what is less important <br /> knowing what to do first, where to start
  • And how? <br /> A simple technique to the rescue: <br /> As all things have more than one side to them,choose two parameters to rate the items by. <br /> <br /> For example: <br /> Urgency of item vs. hassle of getting it done (for the todo lists) <br /> Possible enjoyment vs. how much you can impress your friends with photos <br /> Business importance vs. Market viability <br /> Potential revenue vs. Development cost <br /> Business benefit vs. User needs
  • Possible enjoyment vs. how much you can impress your friends with photos(for your trip to Paris)
  • Business importance vs. Market viability(for business opportunities)
  • Potential revenue vs. Development cost(for for feature lists)
  • Business benefit vs. User needs(for for feature lists) <br /> <br /> I used these two axis for some of my projects and found them to work quite well for getting a first prioritisation of feature lists to define scope.
  • We need a scale to rate the things on. <br /> Keep it simple: 1 to 5 points.
  • But as we have limited resources (in time, in money, in attention, ...) we somehow need need to limit the amount of points we can give out. <br /> <br /> A simple formula:(Max. points) = (Middle value of your point scale) * (# of items) <br /> <br /> Example: <br /> If we have 5 items to rate on a scale from 1 to 5, we have 15 points maximum to dish out.
  • So when we rate, we need to stay within this limit.
  • Use it with a group <br /> and that&#x2019;s where it becomes really handy! <br /> <br /> When to use it with a group? <br /> In a project with several stakeholders <br /> when defining skope <br /> when you need to build consensus
  • 1. Identify all stakeholders <br /> that need to be involved in the prioritisation. <br /> Get experts from different areas who have insights that will help to priorotise (business/financial, UX, user research, customer support)
  • 2. Gather all items that should be prioritised <br /> Write a short description for each item <br /> Fill them in the participant template
  • 3. Preparation session with all stakeholders involved <br /> Get everybody in one room. <br /> Explain the technique, how it works and and its benefits <br /> Go through all items on the list together. Make sure that everybody has the same understanding of what they mean. <br /> Gather any items that are missing from the list
  • 4. Send out the rating template to all participants <br /> Give the participants 2-3 days to send back the sheet (don&#x2019;t leave them too much time, the whole process should be wrapped up within a week) <br /> Include invite to the evaluation session together with the spreadsheet. <br /> Schedule the evaluation session shortly after the deadline for sending the ratings in. Give yourself some time to merge the results.
  • 5. Collate the ratings in one spreadsheet <br /> Tip: when copying and pasting the numbers into the synthesis part of the template, paste them into a non-formated text file first to keep formatting of target cells <br /> Sort the spreadsheet descending by overall rating to get a ranked list (note that this ranking is not necessarily the order of importance as you might see on the diagram that you&#x2019;ll create) <br /> <br /> Create a diagram of the first ranking <br /> export data on &#x201C;csv export&#x201D; tab as csv file <br /> use the ruby script to create svg file from your csv file <br /> open svg file in illustrator and format to your liking <br /> you can see the clustered areas which things to focus on, which ones to consider and which ones to neglect
  • Evaluation session <br /> Present the diagram with the first rough rating <br /> Go through each item on the spreadsheet from the highest ranked to the lowest. Discuss if the ranking makes sense. <br /> In the collated view it is easy to spot items that were ranked controversially. Discuss why people ranked it high or low. <br /> You can correct the ranking by modifying the points in the &#x201C;corrected values&#x201D; columns on the right to reflect the group consensus <br /> Capture comments and reasons for re-ranking in the spreadsheet <br /> <br /> <br /> Things to keep in mind <br /> The outcome of the rating is NOT gospel. <br /> First and foremost this rating tool is great to get a first stab at prioritisation (so that you don&#x2019;t start from a blank slate) and to trigger a discussion and facilitate consensus amongst a group of stakeholders <br /> <br /> Wrapping up <br /> Create a new diagram based on the corrected ranking values and take it from there.
  • Who should you involve? <br /> the stakeholders on the project <br /> it&#x2019;s possible to have different stakeholders rating only one aspect (their area of concern / expertise) though it might also be interesting to force all stakeholders to put themselves in the shoes of the others and rate on the other axis as well (make them think about user needs) <br /> <br /> Why does it work? <br /> people feel involved <br /> their opinion is heard <br /> easy to spot controversial items and start a discussion around these <br /> Extra Bonus: you impress the business guys with your excel skills and make them marvel at the functional AND beautiful excel file. And they&#x2019;ll want to use it as well :) (yes, you talk their language and you talk it with style :) <br /> <br /> Questions?
  • http://evalottalamm.wordpress.com/2009/08/25/prioritising-almost-anything/
  • mail: evalotta@evalotta.net <br /> twitter: @evalottchen <br /> url: www.evalotta.net <br /> download this presentation and the templates here: <br /> http://evalotta.net/_stuff/prioritisation_kit.zip

Prioritising almost anything – UXcamp London Prioritising almost anything – UXcamp London Presentation Transcript