Less of a "solution", more of a foundation
From past experience I've learned presentations are often assumed as
final solutions, especially to those unfamiliar with the design
process. So directing the conversation around the concept of the design was just as
important as showing the interface "solution" screens.
I spoke to how components were essentially parts of features that should be introduced incrementally (hover over each screen below to see the priority of the components).
Signed on to lead the design road map
Through these screens, I was able to show the team why designing incrementally was the the best approach and that having a "read to build" solution would not be efficient. As a result of this presentation and my emphasis on following a human-centric design process, I was hired to lead the design for the entire project.
Screen 1: Viewing all shipments in the system
This screen below may appear simple but an engineer would tell you otherwise. All of these screens needed to be accessible at 3 different levels of permission to address the needs of 3 different user groups.
Screen 2: Shipping information for a specific order
Each screen is dedicated to showing components required for the application to function as a minimum viable product.
For instance, this screen shows the most complicated items of a shipment (e.g. items that need to be at a certain temperature while being transported) that need to be addressed in order to function as an MVP.
Screen 3: Editing parcel information within a
shipment of multiple parcels
By discussing components in detail, I was able to show the team just how much work was involved to produce each screen and why designing incrementally was the the best approach.
Despite my confidence in knowing what I was presenting, there were aspects of the design that I didn't anticipate being a challenge.
For example, this particular screen would become a UI challenge because I wasn't able to assess the complexity of the features accurately beforehand (more on this later).