3 years at Trint in a nutshell

My scope of work at Trint include a wide range of disciplines. Initially overseeing Product and Marketing designs with the help of an other designer when the company counted about 30 people, I evolved towards product design as we grew up to almost 100 people.

From problem definition to actual implementation, I’ve had the opportunity to approach many of these disciplines:

  • Qualitative research with the help of UX researchers, taking part or driving user interviews
  • Quantitative research, exploring data informed designs based on insights from Mixpanel
  • Ideation sessions with paper sketching involving engineering teams early stage
  • Producing user flows and build quick click through prototypes to test ideas
  • User testing & prototypes iterations
  • UI components creation
  • Pattern library and Design System definition
  • Backlog prioritisation (mostly before we hired our first PM)
  • Facilitating implementation with constant communication
  • Product health (tracking bugs and prioritise fixes)

People love the product

Here is some feedback we’ve got about the product. Trint is an instant life saver for many people in the media industry and in the content creation landscape in general.

The project often starts with a discovery phase involving different teams internally with some ‘knows’ and ‘unknowns’ categorisation task about the area of work we want to approach.

Then we communicate with stakeholders about what priorities we’re picking up that will help to narrow down the scope and focus on what we want to build. It takes in account business needs, users needs, engineering capacities.

To gather users insights, some qualitative research is usually necessary and involve UX researchers and designers.

This research phase is followed by a ‘divergent phase’ involving some ideation sessions. Quick sketches, crazy ideas, where no one is right or wrong, only the quantity and the creative mind matters.

Once preferred ideas have been voted, we start building user flows, low-fidelity prototypes and we test and learn from them.

A few iterations of the prototype later, we start the implementation, keeping track of the progress through a Kanban board.

During the process we also have regular design critiques to challenge our ideas with other designers.