Insights from my projects
Insights
What worked on my projects, in what order I did it, and what I needed from the company.
- 01An AI app prototype: how it works in practiceI start a working AI app prototype from one decision the company has to make and from the real questions of its future users. That’s how I built the prototype of MAIA, an assistant for Adamed’s medical consultants.Read more · Adamed MAIA
- 02A sales dashboard for a Shopify store: what to measure and how to connect itA good sales dashboard first answers a simple question: how are sales doing against the plan. For that to work, the numbers from Shopify, Google, Meta and Klaviyo have to be comparable. That’s how I built the dashboard for the team of Berries, a jewellery brand.Read more · Berries
- 03Designing a product in code instead of Figma: when it’s worth itDesigning in code pays off when the product already works and new features have to be tested in the real interface. Since April 2025 that’s how I’ve designed the team version of Spark at Readdle. Figma stays, but for specifications.Read more · Spark
- 04How to build a design team in a company: from the first hire to a shared systemA design team starts to work when the company has a shared design system, a clear path from design to developers, and one place for change requests. That’s how I built from scratch, and led for seven years, a team of twenty at Capgemini. I later brought the same principles to Done Deliveries.Read more · Capgemini
- 05How to prepare a company for AI: from the goal and the data to a first versionI start an AI implementation from a goal that can be measured and from the data the company already has. Only then do I pick the tool. That’s how I worked on the MAIA assistant for Adamed and on the Berries team’s dashboard.Read more · Adamed MAIA