Designing the best process for UX in a startup
After several experiences in medium-sized to large companies during 6 years, I finally chose to join a startup last year. A great opportunity to set up an optimal workflow. Here is my feedback on the process we have built for UX.
In my previous jobs, processes have been in place for a long time. It was difficult to deeply change them, regardless of the strengh of my motivation.
I improved some parts, but ended up still quite frustrated struggling to do my work the most efficiently I could: either I was too beforehand without a clear visibility on developments, or I was expected to only do user testing which was too late to make big changes. For both situations, a lot of time could have been saved by having a better process, to integrate a great UX to the product.
I don’t blame anyone, UX Design is quite a new profession. Its role and integration in companies aren’t well established yet. A brand new company was the opportunity for me to start over.
When I joined Opuscope, the company was 6 months old and I was the third employee. We develop a XR (VR, AR & MR) app based on its ease of use for a public without technical skills: Minsight.
The two founders knew the importance of having a dedicated UX designer in their core team (which is not so common, especially for startups founders), and that the way to work with her/him in the company was decisive for the product success (since its VP, Value Proposition, mainly relies on the UX).
They gave me the freedom to think about the best conditions for me to work. A way to design my own work experience which is quite a mise en abyme for a UX Designer.
The process progressively emerged in our team. It now consists in 3 main steps for UX Design.
1. Roadmap: Define the functionalities to develop
Since our VP is the ease of use, the UX needs to be part of the development prioritization.
A product can’t be user-friendly if:
- functionalities the user really needs aren’t available: your product will be off the target, won’t be used and then there won’t be a product market fit.
- it doesn’t match the user’s expectations: if you propose an advanced functionality, the user will expect the basic one to be in your product. If it’s missing, the user won’t understand why and might get lost or not use it properly. The experience won’t be satisfying.
Therefore we prioritize future developments together in the roadmap, taking into account the app goals, user’s needs and development complexity.
2. Design: Build relevant and complete specifications
First, I work on a design proposition on my own. I do a lot of researches and technology watch to get inspirations, and see best and bad practices. Then I make a first design according to our practical problematic and our product.
Then I confront it to developers and graphic designers for them to give me their feedback, ideas and feasibility. If needed we work together to reach a compromise.
By the way, this step is really important for a UX designer: the better we understand the other jobs’ constraints, the better we can anticipate them in our future designs.
Finally, I document the chosen design with specifications, visuals, behaviors descriptions, references, etc., so that developers and graphic designers can do their part in the best conditions.
It is also a gain of time for the future, we always have a comprehensible history of our different designs to refer to if needed.
I mainly use G Suite with Slides for wireframes, Drawings for user flows and Docs for the complete feature specification; then I share them on Drive in the proper folder.
3. Review: Test the feature
Once the development is done, the feature can be tested. During this step we make sure that:
- what has been designed on paper works well in reality: we can’t be sure a design is the good one without testing it; first by ourselves and at best and if possible, with user testing.
- the design has been respected: let’s be honest, sometimes some things are forgotten or misunderstood. It is our responsibility to follow developments and validate the UX.
At Opuscope, we decided to put the UX review at the same level as the code review. The developer creates a merge request, and they can merge on master only if it has been approved by both the code reviewer and the UX reviewer. This is a guarantee for a stable code and, above all, a great experience, because in the end, all that matters for the customers is our VP.
Technically speaking, we use Gitlab to do this. If I see a design problem in the merge request, I start a discussion in it to report it. I often use screen recordings to show the problem from the user’s point of view. We can all comment the discussion and we close it when the problem is resolved. A discussion is created for each problem to be able to easily follow the development.
I also use Gitlab to create issues relative to UX improvements for existing features. We work on it with the assignee just as for a merge request discussion. When the issue is ready, the assignee puts the “UX-review-ready” tag.
I described the process we always do for each feature, note that for some we have additional steps like prototyping or collecting customers feedback.
I understand we are a startup with a small team, however I think this process can be applied to larger companies when I consider my previous ones. For those, the only obstacles were old habits and the difficulty to make a change for several people at once. If you use this process from the beginning I’m fully confident it will work. Indeed, I’m excited to see how the process will evolve over time as Opuscope grows. For larger companies, now that you know our process, you can try to make it yours too more easily.
That’s all for the best process we found, it may seem quite obvious but believe me, it is not.
Thank you for reading my first article, I hope you liked it!
Feel free to share it and to give us some feedback, we are looking forward to reading your thoughts! Indeed, we are always interested in improving our ideas.
If you want to become a UX Designer or to know more about this position in emerging technologies, you can read my other articles:
This job is quite trendy, but one doesn’t become a UX expert just like that. Several backgrounds exist, and psychology…medium.com
A feedback on what it is like to be a UX Designer in emerging technologies based on my experiences in humanoid robotics…medium.com