...
Key Issue Addressed | Iteration #1 | Iteration #2 | ||
|---|---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="29e93cb0bb3cad41-21d11094-42324e7a-8d028beb-6495627206537fd3b7f6c907"><ac:plain-text-body><![CDATA[ | 1. Users felt bombarded with information when they first looked at the website. | [insert picture] |
| ]]></ac:plain-text-body></ac:structured-macro> |
2. Users did not understand the connection between the middle and right panels. |
|
| ||
3. Users had difficulties finding how to mark a task as important. |
|
| ||
4. Users wanted to use the tabs on the left. |
|
|
...
It seemed like prioritization of tasks was one of your main need that you ofund in GR1
- We decided to scrap notion of relative priority and implement this notion two tiered ordering – important or unimportant.
...
How did you identify important/unimportant
- This was done through the notion of starring.
- There was a lot of trouble figuring out how to "mark important" this is why change to starrted.
- Lots of users
I wish the task actually hadn't been called "starred". If you're making the change to the task you're not actually testing ithe important feature.
- Good point.
Were you looking for gmail metaphor or is this how things are playing out?
- Good design characteristics are found in gmail and/or asana.
- People are finding that the external consistency makes features easier to learn.
- Some poeple, however, are looking for certain aspects that we have not implemented, such as notifications appearing in the tab bar as (#) where # is the number of new incoming jobs.
It sounds like the second prototyping went well, maybe a third round can be done .sbefore you start implementing your product.
- Noted.