Loupe was being developed off the back of key insights from the client and his company and partners after over a decade in the industry, I asked the client to share his insights and pain points, and to ask the same of his co-workers in specific relevant roles.
I used these insights to form a set of basic user personas to cover the broad number different user types. All these user types would be using the workflow tool we were developing, so collating their pain points helped to inform the ideation process.
I looked at several industry standard photography production management software, which showed a high level of bloat overall. The client assisted in creating a list of major pain points expressed from various users in the industry.
We started by documenting and prioritising a list of user stories the solution should contain, based on insights from research and workshops performed around existing workflows, and also started a backlog for potential future iterations.
I went straight into mocking up solutions at a higher fidelity than usual at this stage of the process so key workflows and ideas could be expressed as we already had a design system setup. These included methods of contextualising data, displaying data and functional scope.
At this stage in the project, we already had a fairly comprehensive design system, which I extended with new components required for this feature set.
We performed a number of stakeholder interviews and user tests, and iterated our solutions on the fly in response to stakeholders either misunderstanding workflows or coming with suggestions of their own.
The tests were performed over three rounds, with iterations on solutions in between each round. We made a number of mistakes with the first round, which we refined for the second round, eventually arriving at a satisfactory and workable, but not yet perfect solution.
I was involved in the front-end implementation of design for this feature set, working alongside more experienced developers in a React Typescript / Electron environment.
Our sprints for the implementation involved a lot of back and forth with stakeholders and potential users they could provide to us, resulting in tweaks in behaviour, state and interactivity. We worked any viable feedback into following sprints, working iteratively.
The feature set is now core to the functionality of the platform, supporting many other key features. The product is still in active development with closed testing ongoing.
Let's Chat
.png)