Dominika Michalska

AI you can trust, with value you can measure.

I’m Dominika. I help teams ship AI that people actually use, with the risks known before launch, not after. I decide when it’s good enough and how people and AI share the work.

Product manager for five years. Building AI products since 2024.

Drawn portrait of Dominika Michalska Drawn portrait of Dominika Michalska
Dominika Michalska

Selected outcomes

How I can help

Putting AI products into production

From the first tests to a stable release: finding the real user problem, prototyping, testing variants, and bringing engineers, designers and domain experts into one plan.

See the AI translation product

Designing how people and AI work together

How people and AI share the work: what the system decides, what goes back to a person, and how to measure whether it creates value.

See the grant verifier case

Tell me what you are working on

Selected work

Grant verification: from scores to evidence

At work · AI startup · 2024⁠–⁠25

Reviewers checking 200-page grant applications needed findings they could defend. The verifier compares the programme rules, the application and its annexes, and flags potential inconsistencies with links to the relevant sources.

Final verification went from 5 hours to 2⁠–⁠3, with a person still reviewing.

Read the case

FlagNeeds a decision

The project length does not match the rules or the schedule

Why it was flagged. The programme allows up to 24 months. Section 2 describes a 30-month project. The schedule in Annex 3 ends after 28 months.

Sources. Programme rules, §4 · Section 2, p. 6 · Annex 3

Reconstruction with invented data.

AI translation for customer service: tests to production

At work · client work · AI

One wrong digit can mean the wrong order. We tested whether product names and catalogue numbers survived a translated call, and the findings shaped the glossary and the rules for alphanumeric strings.

Customers call in their own language; the agent switches on real-time translation for both sides.

Read the case

  1. The caller wantsTo order a model by name and catalogue number, e.g. Nova 90, NV-90-4120-B.
  2. The test foundNames and alphanumeric strings did not come through reliably.
  3. The changeA glossary of proper names and rules for digits and letters.
Reconstruction of a real test scenario. Model and number invented.

Adtech platform: from pilot to production

At work · software house, client work

In the pilot, most users chose the traditional route over the tool. I fixed the main campaign-creation flow first and shipped only what supported adoption, instead of working through a large backlog.

Quarter on quarter, in production: conversion of new users +36%, adoption +20%, monthly retention 62%.

Read the case

  1. Conversion+36%New users who reached their first campaign
  2. Adoption+20%Users with access who have created at least one campaign
  3. Retention62%Users who created a campaign and created one again the following month, in the second quarter
The three measures and how each one was defined. Growth is relative, quarter on quarter: two consecutive quarters in production. An active user is one who created a campaign.
Own experiment

The Last Mile, a browser game about shipping AI products. An AI tester won every run by taking shortcuts, so I rebuilt the scoring: a win now needs both launch performance and responsible decisions.

All work · The Not-Built List

Working together

“She actively involved engineers in the product discovery process, valued technical input, and was always open to re-evaluating priorities when new information emerged.”
Engineer on my team. More recommendations

A tool to use today

TRACE autonomy checklist

Define what an AI system can decide, who is responsible and what still needs work. Five questions, a worked example and a summary to share with your team. About 15 minutes.

Open the checklist

Contact

Putting AI into production, or changing how your team works with it?

Write to me here · or on LinkedIn

Trust-Critical AI

Notes on building AI products, testing decisions and learning from what goes wrong. Sent when I have something worth sharing.

Read and subscribe to the newsletter ↗