

Render of Bowl Studio running with strater kit
Bowl Studio
Converge the needs of developers and design teams in a common software solution
Lead UX and UI for the conception of the new software
Context
Epicnpoc is a software and services company that creates software tools for managing technology in complex environments, such as concept cars, smart homes, and retail. Our goal is to support our clients from the Epic (concept) to the POC (Proof of Concept). The Services division helps clients define their project objectives so that they can be specified to developers for integration into the final prototypes. Epicnpoc's vision has always been clear: to move from a services business to a product business by providing a unique management software tool that enables all actors to work together.
Missions
My first mission at Epicnpoc was to rethink the company's software. It began with understanding and familiarizing myself with the current version of the software. The second part consisted of imagining and defining the features and agreeing on a timeline for their implementation. Next came the exploration and formalization of the functionality and customer journey we wanted to implement. Without forgetting the customer projects we were running in parallel, which we used as a basis for our development.
Realisations
1_Understand developper's creation process
The first step is to understand from the developers the way they developed it and how they used it
2_Define features and timeline
The next step is to define the futur process of the software and how features can be implemented





Describe your experience
Develop your technical configuration
Export your project to digital or physical Setups
Demonstrate, test and get feedbacks
Iterate until you reach the best experience
3_Formalise features for MVP
Define the main features to create your project and begin to play with it
*Click on the features to change the preview.
4_Demonstrate ecosystem and get feedbacks
Create content to support the intentions and gather feedback with our client
Promote the ecosystem and its full potential at CES
Refine MVP to gather feedbacks from our customers

Made with:
Valentin
Hassenforder
5_Develop final interface and it's environement
Define final interface and final ecosystem

Final product

Challenges
The V1 of the software developed by the developers is 100% technical, making it difficult to change its use without starting from scratch.
Difficulty in changing the developers' vision of the software's objectives and functionality.
Difficulty gathering feedback outside of our customers.
The common vision from the beginning gradually disappeared, leading to a separation between the software team and the project team.
What I learned
Working as closely with user requirements as with developer constraints.
Product development process.
Developing our tools in line with the company's evolving vision.
Tools
Workshop
To build the new version of our software, we have to understand how V1 of the software is built and used by our developers.
Miro
Road map, benchmarking, research, interviews, and feature definition. Most of my research and reporting work was done using Miro.
Figma
From initial wireframes to final software versions, Figma remains the best tool for building the interface of our solution.
Illustrator






