👋 I am Erdem, a product designer working on the parts of software that carry the most operational weight. Internal tooling, configuration systems, and dashboards where a wrong default costs money.

The screens that decide whether a platform works are usually the last ones to get design attention. Configuration flows, investigation tooling, tables holding thousands of rows.

That gap is expensive. An unclear status becomes a support ticket. An ambiguous default becomes a payout error. It is also where renewal risk sits, because customers judge a platform on the tools their own team opens every morning.

So I work where attention is underpriced. Most of my week goes on the parts that never appear in a portfolio: reading the data model, arguing about field order, deciding which settings a person should never have to see. The visual work is the last ten percent.

I did not plan this. I started in consumer work, launching car rental inside a super app and leading a mobile suite, then took on an internal tool nobody wanted. The constraints turned out to be more interesting than the freedom I thought I was after. When a payout is wrong, someone loses money and somebody has to explain it. That makes teams honest.

Consumer work taught me to measure. Platform work taught me that the measurement usually points at a structural problem rather than a visual one. I use both.