OnCoor

Requirement Gathering and Conceptualization

I began with in-depth discussions with the CEO, a seasoned expert in the data space. As he shared his vision for addressing a significant gap in enterprise data management, I found myself translating his abstract concepts into tangible design solutions. These conversations were crucial in shaping my understanding of the complex challenges we were tackling.

Design and Iteration

With a clear vision, I dove into the design process. I started by creating sketches, rough wireframes, and then eventually high-fidelity wireframes in Figma, carefully considering how to make complex data management tasks accessible through an intuitive interface. As I progressed, I developed interactive prototypes that brought the CEO's vision to life.

Recognizing the need for consistency across the platform, I took on the challenge of developing a comprehensive design system. This involved creating a library of icons, deciding typography, standardizing UI elements, and establishing design guidelines. This system became the backbone of our rapid iteration process, allowing us to quickly adapt and refine our designs as we received feedback.

Throughout this phase, the CEO would turn to me for input on layouts and user flows, and I drew upon industry standards and best practices to guide our decisions. These collaborative sessions were key to shaping the final product.

Redacted Example of Enterprise Objects Page UI

• The Enterprise Objects feature simplifies and automates data migration, allowing business users to transition datasets effortlessly. Traditionally, moving data between systems required manual ETL (Extract, Transform, Load) development, which was time-consuming and prone to errors. This feature eliminates that bottleneck by using an automated ETL generation engine to create and execute the necessary processes based on predefined data mappings.

  
  

• By handling multiple tables at once, it significantly accelerates the data transformation process while ensuring accuracy. Users also gain a clear, visual view of data movement, making it easier to track transitions. Importantly, this feature empowers business users to execute data processing jobs independently, giving them self-service control without relying on technical teams.

Development Support

As we moved into development, I translated our designs into user stories within Azure. This process required me to think deeply about each feature from the user's perspective, ensuring that our development team had a clear understanding of the desired functionality.

I frequently explained complex workflows to our developers, and as development progressed, I kept a close eye on the process, providing ongoing design guidance to ensure that the final product aligned with our initial vision.