I facilitated interviews with people in varied personas in about 10 of our largest companies. We asked them the structure of their company, if they had any existing ERP systems they utilized, what their expectations and use cases would be for limiting their asset population, etc.

We recorded all of these interviews and documented them into empathy maps.

From these meetings and the documentation, the PO and I were able to extract several features we thought were useful.

I put together design briefs for all of these features and scoured the internet for any examples I could find of hierarchy structures.

I drew inspiration from workday, google drive, apple, and any other kind of hierarchy, regardless of if it was people or files.

Please see this link for a full research brief.

I took each feature one by one and mapped out the workflows/user journeys. I then validated these concepts with internal stakeholders and engineering before proceeding with a design.

I then came up with some basic low-fi designs to present to the stakeholders. I wanted them to focus on the use cases and not the design here, so I included no design system elements. I illustrated both the company structures we were aiming to capture and the simple workflows of the features.

Then, utilizing our design system I created full workflows for each feature. I then validated these again internally and created empathy maps. After another round of iteration, I fixed up the workflows and screens, presented them to engineering for approval, and created presentations and prototypes to give to the users for validation and testing.