No. While it seems to be annoying, I see four problems with not having to enter the login information again:
I will remember my new password better if I have to type it once more. (I keep forgetting my new e-banking password because I don't have to re-enter it, and I of course don't store it in the browser.)
If I want to store the password, the browser PW ...
In my opinion: YES.
The authentication has been done when the password is reset, so the user could be logged in. And it annoys the hell out of me when after password reset I'm not logged in.
I can't think of any case I wouldn't want to be logged in after resetting password, why would I even ask for password reset if I don't want to log in?
There's a million things that you could to do to grow your skills and make yourself a better UX designer. Here are some ideas off the top of my head:
Talk to your manager about how you can grow your skills to help the team out.
Conduct a baseline usability study on the most recent version of the product that you designed and determine whether users are ...
You should have the buttons at the bottom right because:
The standard for modals is to have the buttons at the bottom, so it is likely where people will look for action buttons
It is a more natural visual flow reading in a Z pattern, and one that has become entrenched.
A button on the right is typical for a submit button as it has the feeling of moving ...
There isn't really a standard or convention that define these terms, but there's some sense in how these often differ.
First, the term flow denotes a non-linear path, i.e. one that branches.
Then, flow in UX denotes through the system. Meaning that the analysis makes use of the system templates (either existing or those of the design).
The Previous button should not act like the Back button. The Previous button means "go to the next-lowest numbered step"; the Back button means "go to the screen you were on before this one". In any given context they may have the same effect or different effects.
So here are two paths the user could take.
Step 1 Next→ Step 2 Next→ Step 3 Previous→ Step 2 ...
In your experiences, what has worked well, and what would you make
sure you never done again?
Be a designer who develops AND a developer who designs.
White board concepts and solutions with developers as you either
flesh out features or solve technical solutions. Be willing to bend and
compromise and stand up for your ideas. Expect the ...
As msparer suggested, Stating the main action first and then offering context/side effects is a very good step to take.
The other thing I'd definitely do is to label your buttons descriptively.
It could look something like this:
Are you sure you want to close all transactions on terminal x?
Closing will also print the transactions of 11/20/2014.
If the war room is for making a tight deadline, then I'd say the comment from @Roger-Attrill is perfect. Especially the coffee. Don't forget the coffee.
However, if it's used for brainstorm sessions, there might be some other components you can use for an effective and most of all creative brainstorm session. Make sure people inside the room don't get ...
This answer applies to most presentations, not just UX ones.
A good presentation is like a story, where you take your audience on the journey that you want them to experience. If you send the presentation to them ahead of time, you lose the ability to take them on that journey.
There are other potential negatives as well in that your audience may start ...
Try shopping anything on amazon without logging in first.
Browse -> pickout the item -> add to card -> proceed to check-out -> log-in -> continue with address selection and payment.
Amazon can easily be the top player who needs to worry about user flow and logging in :) So, YES, login should just be a step outside the flow and back in i.e.
Some names could be...
Progress Bar (although it can be confusing in certain contexts, in my opinion)
Step Progress Bar
Segmented Progress Bar
Step by Step Progress Bar
Navigation vs. Indication
If the steps are clickable links I ...
Custom HTTP error pages improve web sites' experience, security
Every web server can display HTTP error pages, but default error pages don't provide useful information to your visitors. Some error pages may even leak sensitive information about your site, such as URL or file paths, database details, and even code. But you can replace ...
Is it even neccessary to show how many children are left to be approved at all?
How many administrators will be doing the approvals? If it is more than one then the task will probably be split up anyway (please correct me if I'm wrong) so instead of showing the progress bar you could do one of the following:
on approval of one listing ask the admin if they ...
I agree with Igor-G that one conversion type (getting a new signup) is more valuable than the other (an existing user logging back in), but I think the primary reason is slightly more complex, and would still make sense even if the two we're of equal value to the company.
It's a function of how much each user-type's conversion likelihood can be influenced ...
When deciding between a modal and inline entry, consider what is communicated to the user by your choice:
Inline Blank Entry
"You're going to be doing this a lot, so we don't want it to be a big deal."
"Don't worry too much, this is easy to fix if you make a mistake."
"We expect you to enter multiple items."
"Please focus. This is too ...
You can group all tasks that have to run simultaneously. Something like this:
When "Add task" under "When complete..." is clicked a new task is created in a new
group and the button changes to "Add simultaneous task" like the group above.
Cancel buttons can be extremely useful. For example, in the screenshot below it gives me peace of mind in knowing I can successfully exit the process at any time.
Especially useful with forms requiring multiple steps. Closing the window on a page/step 2 can cause confusion as to what will happen with the data you have already supplied. This is where I would ...
The Right Information
Firstly, make sure your displays show the information the user needs to make good decisions and input. The use of a color-coded matrix assumes that your user is trying to achieve a certain pattern of assignments, such as a certain number of people in each duty type per day (e.g., have adequate coverage when some are on vacation), or ...
I follow a similar process but with an extra step - flow design.
I prefer, as I'm the UX person, to know what it is the user needs to achieve. I like to either use pre-written (or I write them myself) use cases based on what the stystem needs to help the user achieve.
To use a website example:
As a customer I want to be able to add an item to my basket, ...
Some points for good labeling are:
Short – 'submitted' vs 'uploaded_for_processing'
Distinguishable from each other – bad: 'uploading' and
'uploaded', good: 'uploading' and 'submitted'
Same styling rules – try not to mix verbs and nouns and use same case
Understandable – user should know business process to match labels in UI to business phases
For taking ...
Rather than trying to display this audit trail in a single, very large and complicated diagram, consider presenting it as a log with a simple diagram for each change.
In my wireframe below, I am showing the history of a single task. For each record, I am showing a brief description of who did what and then illustrating the flow between steps with a basic ...
A problem I see there is that the initial action has an implied consequence that might confuse your users. According to your mockup, the transaction day gets closed as soon as the data gets printed.
It seems like "Printing" is the main action and closing the transaction day is the side-effect. It really should be the other way round.
Name the CTA "Close ...
Allow 2 views: Sequential view for displaying orders by sequential steps, and a production floor view to show bottlenecks and throughput.
Since you can't have a strict order across all steps, have two ways to view the world: at the order level, and the production floor. They serve two different purposes.
In either view, you can indicate on the left how ...
I would push back on the recommendation in this case unless the person can give you a business case or user story that specifically requires a cancel button.
If the primary method of navigation to this form is via bookmark or in a list of internal tools/links that people bookmark, and the form is not clearly part of a hierarchy or other discernible ...
This is my second answer; posted after the OP updated the question with more info.
The left suggestion gives you the option to "download files" by pressing a button for each list item. Once the files has been downloaded, an icon indicates that. The text on the button is enough to make the following states understandable, no matter your exact choice of icon.
At SmartyStreets, we just revamped our checkout experience and went through the same questions you are asking. Quick intro: To use our service, an account is required, so users must either login or create an account on-the-fly as they go through checkout.
The top part of the checkout form (see an example), users are asked to login if they already have an ...
Being able to do things using different ways is a good thing. People discover parts of the application differently and follow different paths towards a goal, so if you provide them more ways to get to the same result, it makes life easier for your users.
One example of an application that does this well is Word 2010.
To align my text, I can either use ...
Why is it wrong?
OpenID has several drawbacks:
You're actually going to a totally different website in order to register or authenticate. This is not how things work ordinary. For years, registration and authentication for a website was done on the same website: the user was moved to a different website either because he wanted to, or because he was ...
Workflow is a set of steps to reach the goal. It's a general term (Workflow).
In UX field you can see both terms Task flow and User flow are used mostly interchangeable.
For me Task Flow is a good name for the results of Task Analysis technique. At the same time the results of the User Analysis techniques (in narrow sense) are User Models, Persons, but not ...