Product: L&D software
Materials: Web application, interactive protoypes, and custom iconography
Admin Frameworks: SCRUM, Sprints, Waterfall, and PLG
UX artifacts: Personas, experience map, journey maps, user flow, metrics, sitemap, UX wireframes, interactive prototyping, A/B test, and user interviews
Work highlights: Implementing Design Sprints, rapid deliveries with a design system, adding accessibilty to the product, and generating interactive prototypes for Sales
Software: Sketch, Figma, Zeplin, Illustrator, Photoshop, ProtoPie, Notion, Confluence, Jira, Trello.
Materials: Web application, interactive protoypes, and custom iconography
Admin Frameworks: SCRUM, Sprints, Waterfall, and PLG
UX artifacts: Personas, experience map, journey maps, user flow, metrics, sitemap, UX wireframes, interactive prototyping, A/B test, and user interviews
Work highlights: Implementing Design Sprints, rapid deliveries with a design system, adding accessibilty to the product, and generating interactive prototypes for Sales
Software: Sketch, Figma, Zeplin, Illustrator, Photoshop, ProtoPie, Notion, Confluence, Jira, Trello.
Introduction
As a Product Designer, I've been collaborating in defining user goals, Personas, mapping out the user experience, documenting work processes, leading design sessions, framing problems, generating a Design System for delivering rapid designs, and creating interactive prototypes. I was involved in the process of analyzing and generating graphic solutions of data for Insight's section.
Design Sessions
As a team, we conducted several design sessions to understand the problem or feature to develop. For instance, we modified the Design Sprint framework to fit our needs and work faster to elaborate a solution.
Design sessions have two approaches depending on the feature's complexity. The short one or 'Quick wins' could last from one to three days. We don't have to spend a lot of time analyzing requirements since it's an improvement or update for an existent component —We already know the output.
The longer one lasts one sprint (two weeks), if we find that the feature is complex enough to be finished in one sprint, we can split it in increments, so we can plan and organize in a better way our work through two or more sprints.
Discover
The big picture as a Product Designer for a small company, you have to take the role sometimes of a researcher for understanding user's behaviors or finding pain points/frictions in a given task. In some other cases, you have to be in 'bulk mode' creating visuals for quick wins or preparing components for the Design System.
In the end, it doesn't matter which role you're involved in, the process is pretty much the same —it starts with understanding the problem or the needs (Problem Framing), taking the time to research, and generating a lot of questions for a better understanding (Discovering), creating the necessary assets to accomplish the task (flows, maps, sketches, or low-quality mockups), iterate until it fits with the needs, and documenting everything to hand it off to the Development or business team.
UX Process
Our most recent process implemented was linking Epics, User Stories, and Acceptance Criteria, a new way to connect everyone in the company from business, Client Success, Delivery, UX to the QA team. The goal was to align everyone in one single chain of activities or duties, so we can move forward avoiding friction in the handoff.
The big picture as a Product Designer for a small company, you have to take the role sometimes of a researcher for understanding user's behaviors or finding pain points/frictions in a given task. In some other cases, you have to be in 'bulk mode' creating visuals for quick wins or preparing components for the Design System.
In the end, it doesn't matter which role you're involved in, the process is pretty much the same —it starts with understanding the problem or the needs (Problem Framing), taking the time to research, and generating a lot of questions for a better understanding (Discovering), creating the necessary assets to accomplish the task (flows, maps, sketches, or low-quality mockups), iterate until it fits with the needs, and documenting everything to hand it off to the Development or business team.
Digesting data
As a part of the Discovery team, we needed to review, discuss, and digest all the data from our research. Creating a presentation to be explained to the core team was essential to align the criteria and bounds of discussion.
Collaborating in defining roadmaps based on OKR's was a periodical activity to align efforts for the following three months.
Documenting
I think that documenting should be a must-have process in every company or team —It doesn't matter how small or big they are. As a Product Designer, I need to keep clear and constant communication with the team, in particular with Product Owners and Developers.
I took the initiative to start using a system called 'logbooks' to document and hand over every deliverable that includes requirements, user stories, flows, mockups, accessibility, and any other resource.
Atomic Design
We believe in modularity and rapid deliveries using a Design System. Yes, it could take some time to finish it —however, the gain is way much better than pain. We love working using the Atomic Design structure, it allows us to build complex components from simple ones.
Components
Mockups
Workboard section
Planning board (fullscreen)
Use case of first time informative modal
Smart search component
Gallery
