This design stacks the "original" version and the "pending proposal" vertically, keeping everything in the sidebar so the right side can display the corresponding map context of where this node is located and where the approved changes would take place.

Problems: 
This design is missing the ability to see who created the proposal, when they created it, and the notes they wrote about it. The vertical space is also very limited, so if the content in the nodes is longer, the user might have to scroll a lot to compare any changes which could be frustrating.

University of Michigan - Ann Arbor

We re-thought the flow and look of the pending proposal review and approval process. There were a number of issues with the original process including multiple clicks, lack of clarity on how to approve the proposal, lack of saliency on discovering the proposals, lack of signaling the user for the need to approve them, and it was often unclear what the proposed changes were.

Pending Proposal Review designs: Iteration 1

This design makes it clear which version is the newly proposed one, and exactly what changes are being proposed by highlighting them. We also limited the icons showing on the node to only what we thought was needed. The left sidebar panel gives a summary and notes of the proposal, and allows the user to either approve or disapprove the proposal.

Learn Before

Related