New answers tagged

3

I think modal could be an overkill, as it will take the focus away from the page - and moreover its not justified for something like an edit function in the context of the application. Take a look at the below suggested flow: 1) Initially, the user is visually shown which are the editable vs non editable categories. As seen, Reqs are shown to be editable, ...


1

This is a more common problem than the number of questions that have been asked about it, so I think it is a good place to summarize a couple of key points that may help you to determine what the best combination of strategies might be: Labelling of the call-to-action: the wording that you use can play a small part to address this issue. I know that people ...


1

"The earlier system just had all fields editable at all time, which avoided this problem - is that still the best way to go?" Yes. What is the difference between the fields of a requirement to the fields of its evaluation? - None. The evaluation fields are also "saved" locally and you do not have 'Save' and 'Discard' buttons for them, and that's because ...


1

The solution I would use here is fairly simple- pull out the nested edit unto a modal window. I've also made some modifications to try and address some of the slight UX issues in the original mockups. download bmml source – Wireframes created with Balsamiq Mockups (Pretend that the above mockup is presented beneath the grey overlay) ...


1

What is the ultimate goal for the user? Evaluate the Law? Edit the Requirement? Edit and Evaluate? I suspect the ultimate goal is to just Evaluate, and if so this should be the primary Call to Action trigger. I also suspect that Editing the Requirement is an occasional supplementary activity so it's trigger needs to be very different to the primary ...


3

I think you can get close with just a couple of changes from where you are now. Have a different and informative CTA for the requirements Currently you have 'Save' (local) and 'Save all changes' (global). This seems potentially confusing. If you changed the CTA to something like the following, the user would be made aware that this change is local, not ...


1

I'm a big believer in the Keep It Simple Stupid (KISS) principle. Assuming you have to keep the basic design (i.e. the table with accordion expander), one of the main things you have to consider is the workflow of your users. If the majority of the time users would only be expanding the selection to view it, then I would leave it as is. On the other hand, ...



Top 50 recent answers are included