Let's say you have a
foo. Any given
foo can be bought in multiple ways - loans over different terms, leases, etc. The
foo has certain properties which effect the payment scenarios, such as the MSRP, the selling price, the shipping cost, etc.
I have a screen that shows all the possible scenarios for a set of given
foos in which a customer might be interested in purchasing. Let's call this
Each payment scenario has its own screen that you click into with additional details and further options you can edit (such as the term, configuring different taxing parameters, etc.). Let's call this
If the selling price, shipping, etc. of a
foo needs to be edited, the obvious place to do it is on the top level,
Screen 1, when listing the
foos and the given payment scenario overviews. However, a concern has been raised that if a user is already in a payment scenario -
Screen 2, they have to click back to the
foo overview in order to edit this information. This is non-ideal, as it takes extra time and clicks for the user, interrupting their workflow.
On the other hand, we make this information visible on the child screens -
Screen 2. We can make it editable from these screens, instead of just viewable. However, I'm concerned that doing so will be confusing. For example:
- When editing the Selling Price of the
Screen 2, will the user know they are editing it for all other payment scenarios that pertain to that
- Will they think they are just editing those details for that specific scenario?
- If so, is there a (non-obtrusive) way to make it clear that this will effect the other payments?
- Is this even desirable? Is there a reason not to do this that overrides the additional ease-of-use?
- If we do implement it, is it better to remove the editing at the top level, to keep a single click-path to edit a given piece of information (a consistent complaint on our current design is that there are too many ways to complete a given action)?