I need some simple corrections to this silverlight wireframe: [url removed, login to view]
The corrections are presented here as questions/suggestions provided by a reviewer. I will rephrase them into more concrete, less ambiguous actions to be taken.
The quote given should cover implementing these corrections.
a. Inter page linkages and a startup page can help, like dummy entry to the application( a simple login form leading to a dummy dashboard page can help).
Also like when i go to the detailed guest view there is no way to come out of there…
an exit button can tell us a lot during usability tests, particularly indicating that the user got confused and left without doing the task or after doing the task.
b. Since we will devise scenarios based on each of the modules of the software ( For e.g. Event component or the Guests list component),
We may need to explicitly indicate these components on the pages. By titles on the top.
c. The links on the left hand side of the sketchflow prototype can be distracting to the user. The idea is that in a prototype we should try and show the software as close to the real environment or scenario.
So just like we are using web page and hence the web environment can be identified, we can also remove/hide the navigation panel on the left, make the top links active and make it feel ( if not look) like a real application.
d. Can we avoid the hand writing font in the prototype to make it more readable, since the testing of the labels can become more easy if we do so.
e. Mocking up some dummy functionality can also help, like when u add a new event, nothing happens currently, can we have some dummy form displayed for the user to fill?
Also deleting or removing an event or a guest, does not show any visual change currently. Some change can help in communicating the user the task is done.
Note: There are loads of places in which the functionality is missing, however adding those which we plan to test will be useful. We don't want to frustrate the volunteer for testing.
f. Although i see that sketch flow has a good tool to let the users give feedback, but i would recommend that you take print outs of the screen to the users, at the end of the tests the users can mark on it what they think should improve.
However drawing on screen is not easy for all the users, and pen/ pencil is the most basic interaction people are accustomed to express.
Now for some detailed input on each component:
- The two lists Upcoming events and Past events, have only one set of Edit/ Delete / Create button.
Obviously the user can get confused with the mapping.
Suggestion: We can use tabs for "upcoming events" and " past events". This can help in using more screen space for the complete list of events.
- The calendar on the right needs to be tested. We can make better use of the calendar by having a todays date at the top, along with displaying events on the calendar etc.
We can also further make calendar based view for the interface( something on the lines of google calendar). Need to see some possibilities for the same.
- In the spec the following interaction is specified.:
When clicking the title of an event, edit event for that event is opened.
Alternatively, the user can select an event and click "edit selected".
It is only possible to edit one event at a time.
If multiple events are selected, there should be a popup warning saying "Please select only one event".
Such interactions can be irritating to the users, if the user cannot edit more than one event at a time, then the possibility of selecting more than one event at a time should be avoided.
I understand that the problem arrives when the user has to delete more than one event.
This can be solved using the following pattern.
a. Keep an event title in the list as a hyper link, along with the same checkbox structure. So in that case one can click on the event to view/edit it, as well as have multiple select while deleting.
This avoids display of the error "please select only one event".
A similar pattern is implemented in gmail inbox if you observed in detail. The mails are the events and a delete button exists, but no view button exists.
We need to answer the question, what is the goal of the user in events panel, and what are the scenarios in which it may be used?
- I have some questions here.
Is the Guestlist page and Event details page the same? If so then we should change the title, since it can confuse the user further on.
- Import from Excel or previous events interaction needs to be detailed out in the prototype. Since the interaction of the user adding csv contacts will be very different to that of adding from previous events.
- The add/edit guests interaction is a bit different from the edit guests interaction from the list above. There needs to be some consistency in the interaction for better usability.
We can keep the add guestlist entry as a hidden div type button. Which on click expands in length on the same page.
So the user can use that section only when he needs it, and rest of the times the page remains clean.
How does the admin choose a particular event to enter spend.
Can he see previous expenditure spent across events.
Can we have graphs here to display spend by various users in the past…
Basically instead of just keeping this section as "Enter Spend" how about making it " Spend Details" hence including input as well as view of all the spend in an event or by a specific guest across events.
7 freelancer bu iş için ortalamada 772$ teklif veriyor
Hello :) I have lots of experience programming in Silverlight and WPF/RIA webservices. I can make your requested modifications in 10 days. Regards, Alexey