Cincinnati Design Week and IxDA Cincinnati are partnering to bring you an awesome workshop on Collaborative Brainstorming for Better UX. It's on Tuesday, Oct. 1 at the Contemporary Arts Center starting at 7:00 om. It will be a 2 hour hands-on exploration into techniques and methods lead by Jessica Ivins (see the full description below) .
Hello! We would like to hear your ideas and opinions on having a mobile application for UX Specialists.
Help us brainstorm by answering the questions below. We look forward to receiving your thoughts and insights.
Do you know of tools/applications/activities that are useful for User Experience Specialists?
Do you think having a mobile application for User Experience Specialists will be useful?
If so, what features/tools should the application have?
I have a workflow in which users can choose to move their data through
processes, A, B, and C. Internally the states are actually a
sequence. So if the person selects C we first move the data through A
and then B.
I could present this as a radiobutton list, e.g.:
If the person selects Spindle, we secretly fold the data first, etc.
The sequence is hidden. But
sometimes the processes fail, so a user who selected Mutilate will
find that his data Folded properly but couldn't be Spindled.
I am debating whether or not I should disabled the OK button on a dialog box until the fields that need to be filled are "error free". Let's assume I have two fields on a dialog box: Name and Position. On dialog open, the name is empty and the position is defaulted to a predetermined value (which is editable). Let's assume I clearly identified both fields as mandatory. Do I leave the OK disabled until a name is entered or do I enable it and provide an error message if it is selected with no name entered?
I am working on a project that requires the ability to assign a user in the
system to a role. There are three roles to choose from and each role
provides rights to certain screens and tools.
If you choose the third role, you also need to select from a list of rights
that user will have. Note: this is something that will not happen often.
Something like this....
( ) role one
( ) role two
(.) role three
 right 1
 right 2
 right 3
 right 4
 right 5
As you can see, I need ideas as to how to better present this to the user.
I was selected to be one of the organizer of my company's engineering
off-site this year and one of the themes is "Innovation" - a whole day
is dedicated to it. I am currently the only UEx designer with the
company. The discussions of innovation will revolve around many
topics: technology, process, business and hopefully interaction