At Graphext , I've been collaborating with the Development and Business departments, actively involved in enhancing the Exploratory Data Analysis and Predictive Modeling tool. Who are the users? Business analysts mostly as its a low-code product, and some Data Analysts & Scientists who've found the tool helpful for their analyses.
Here, I put into practice my expertise in Product Design to enhance workflows, suggested new features to optimize user experience, and conducted research and redesigns to facilitate users better understand their analyses.
My work spans across various aspects of the product, for which I developed skills across all phases – from initial research to design delivery. This involves making decisions aligned with the roadmap, projecting designs into the product’s future, reviewing deployments, studying feature usage through metrics and testing, and implementing improvements. My dedication motivates me to continually refine and optimize functionalities, for which my team and I ensure that our product not only meets but exceeds user expectations.
I work across various areas of the product, including a chart builder, the architecture of organizations and collaboration, CRUD of predictive models, creation and maintenance of the Design System, the light mode, and the refinement of advanced filtering, among others.
As the team is small, I have the chance of working across different areas. A colleague and I were in charge of creating the Design System and up to today, I've been the one maintaining it. To build Graphext, the developers use a library called blueprint, for which many of our components adapt to it and along with the front-end team (Isa, Luna & Raúl) , we've managed to work out a solution that fits both teams well.
In a data exploration and visualization tool, colors really matter. When we're building graphs and charts, we've got to think about the palettes we use. They've got to help users understand, see the big picture, and dive into the nitty-gritty details. Plus, we've got to consider everyone, including those with daltonism and low visibility, making sure our colors work for everyone. So, we're all about picking the right colors to make sure our charts not only look good but also make sense to everyone who uses them.
In Product Design as we now, we face various paths & methodologies when tackling a task. Sometimes tasks are driven by user demands, while other times our expertise guides our decisions. Each path has its own journey, but one thing remains constant: defining the problem statement and scope is crucial to stay aligned with what's needed.
My approach varies depending on the case and the time available to develop or enhance a feature, but most of the time, I follow this process (sounds crazy to simplify everything in bullet points, but let's try it):
A. Define problem statement & scope along with the Product Manager
B. If applies, analyze the current scenario: Identify key pains & review metrics
C. Begin diagramming, build basic flows in wireframe, use cases & screens
D. Review advancements with colleagues
E. If applies, build a prototype for testing (either with users or internally). Gather feedback and improve designs*
Note this is sometimes an iterative process
F. Prepare Handoff (divide tasks in mvps if applies, final designs, flows, specs, videos, notes, etc).
And yes, I'm constantly in contact with the developer team to review their work and clarify doubts if needed.