1

What is the official/unofficial name of the technique I have seen designer use by placing lots of Post it notes along a wall and categorizing them into normally three groups.

Normally someone writes all the collective ideas the group has and then they all start placing them on the wall where they think they belong.

  • Keep side, these are essential features for the UI
  • Maybe middle, features which are undecided are placed in the middle
  • Drop side, unecessary features that can be removed from the design scope

Any information or demonstration videos would be appreciated, as I would like to start using it within my design stage.

Also any other cool/alternative team activities you could suggest would be welcome!

Thanks

1

What you are asking about is not a single process / task, but is rather made up of many different processes / tasks depending on your goals.

A good place to start would be the Slideshare from Becoming a Stickynote Ninja - UX Week 2008.

| improve this answer | |
2

I think you are alluding to Scrum/Agile methodology. Everyone has their own unique 'bastardized' version but it is a much more fluid approach (rather than the traditional Waterfall process)

http://en.wikipedia.org/wiki/Agile_software_development

and this site mimics the sticky notes:

http://scrumy.com/

| improve this answer | |
2

Common things done with post-its in the UX process:

  • card sorting: useful for sorting all the 'parts' (be it content, goals, objectives, etc.) of a site into meaningful categories.

  • flow diagrams: mapping out the content structure of a site

  • paper prototyping: simple wireframing on paper.

In this particular case, it sounds like one is prioritizing features into a matrix. I don't know of a particular term for this other than 'prioritizing features'.

| improve this answer | |
0

We use it for organizing requirements we collect - irrespective of the source: user testing, stakeholder interviews, PRDs, backlogs, UX evals etc... the method we use is called "Affinity Diagraming" - clustering needs, features, requirements, issues, limitations, opportunities into "like-categories/groups" - and naming, prioritizing, scoping and planning from there.

But if you follow Lean UX, there's another method of (Users/Needs, Uses/Features) - and mapping out tests: - "We believe [customer type] has a need to/for [need/action/behavior]" - "The smallest thing we can to to prove it is [experiment]" - "We will know we have succeeded when [quantitative/measurable outcome] or [qualitative/observable outcome] is achieved.)

You may call it "Lean UX Workshop" or "Ideation" from the school of Design Thinking. Hope this helped.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.