Lightspeed Case Study: Salesperson Attribution
Project Details
At Lightspeed Commerce, I worked with the team focusing on the user-facing sales area of the software. Retail staff use this every day to make sales. We regularly held interviews with retailers to discuss workflows, identify pain points, requirements and to map current user journeys.
Through our user research, we identified the following problem statement to be solved: How might we help merchants know what staff member(s) contributed to a sale, so that they can accurately track staff performance?
Design Process
I started by creating the desired user journey in words, before touching any UI or drawing. This user journey is backed up with evidence and quotes from retailer interviews and is reviewed by peers (designers, product managers, engineers) to identify any knowledge gaps, pros and cons.
Once I can clearly describe in words how the ideal user journey will work, I then start on rough wireframes. I create these in Figma and/or Miro as it can then be shared and iterated over quickly and easily.
Wire framing is the part of my design process that takes the longest time - it’s a time to explore different ideas and solutions, experiment with flows and UI elements, share, workshop and review with others.
See some examples of my workflow and wireframes below.
Design Process
The next phase is the high-fidelity mock-up. I created these in Figma, utilising Lightspeed’s design system and library.
I create hi-fi prototypes as realistic as possible, as it gives a good feel for how it would function in the live application. It is great for sharing with a broader audience such as stakeholders, support and sales teams, as well customers to get feedback.
The Solution
Below is a video summarising the solution, made to share with my team as an asynchronous way for them to review and feedback. It also covers MoSCoW prioritisation for building the solution.