here are my comments:
- are the tab section following a step by step process (eg you ha to fill in “management” and after you can go to “maintenance”)?
The tabs are not meant to follow any sort of sequential process.
Maybe you can reach a compromise between business wishes and design approach. AS a quick win I would try to display all the TABS in one line (UL, LI) according to the PRIO defined by the business logic of the app. I know that the screen real estate is not enough, you could design a scrollable feature or put the rest of the tabs in a context action button. As an improvement, I would try to define a process to let the user decide which tabs are visible at the first glance
- are the tab sections entry points for different screens it doesn’t matter where u will start (eg I open the app and I select “documents”)
Yes, the tab sections are entry points for different screens, it makes no difference where you start
Maybe here you could define the visibility of each TAB per user type, I’m not 100% sure that all the TABS are needed for all the user types
- What about the validation of each tab (server/client side)?
I’m not certain if you’re asking about some sort of overall validation, but each tab has different validation rules from both client and server sides, as they’re content varies significantly
I’m asking because what will happen if you have asynchronous validations (server side and client side) how do u communicate errors and notifications for each screen?
- Regarding the buttons, what about the hierarchy of these actions?
There is really no hierarchy for the buttons, they were just arbitrarily placed where they’re at in the wire-frame
I suggest challenging your stakeholders with a quick and dirty usability test. Ask 10 users wich buttons they will use most. The ones that are at the bottom of the ranking can be grouped by the context action button
- Do they have the same weight in terms of task accomplishment?
Each button is important, but the Edit Vehicle Options and Change Customer Assignment buttons are most important here since they will ONLY appear on this screen, whereas the others appear elsewhere
I suggest defining a style (CSS class) for the primary call to action (CTA) and a style for the secondary CTA
- Do u really need a dropdown for the “minority vendor” (if the value list is a simple yes/no)?
Great point. We really don’t need a dropdown for a Boolean value like this. Do you think a toggle button or radio button would work best?
YES! I believe that dropdowns are the user interface last resort
- What about the device targets?
I assume you’re referring to whether or not the application will have a mobile version. If so, currently that is out of scope for the project. This is only meant to be used on desktops and laptops
This is already a good starting point for a UX strategy. I suggest keeping in mind that often users shrink browser windows because they work with more than one app at the time
- Did u challenge your stakeholders with UX KPIs (eg time to accomplish the task)?
I’m not a designer, so can you please elaborate as to how best to go about doing this
In my experience, as a designer, I always tried to build trust between business people, engineers and designers. Defining key performance indicators (KPIs) related to the UX/UI helped me a lot in agreeing on to do lists and in taking shared decisions for the future of the product.
Did u ask your stakeholders what are the main goals of the re-design (if is a re-design) project?
Did they mention what they want to measure and to compare vis-à-vis the old version?
Let us know how the thing are going!