Actio is Milapasa's digital event-management system: custom registration forms, an event calendar, participant categorisation, meeting-link distribution, live support during events, and post-event reporting. It is still sold today at actioevents.com, and it still sits front and centre on milapasa.com.

This is early-career work — 2022, my Software Developer year at Milapasa — and this page is deliberately smaller than the others. It is here because it is where I first worked on a product that had to survive contact with a live audience, and because the habits it taught show up in everything above it. Milapasa's wider work — including its strategic partnership with WeGlobal, the EU-projects consultancy whose programmes I supported with portal and IT work — is on the about page and the resume.

At a glance

  • Product — digital event management: registration, participant categorisation, reporting, and QR-code entry at the door.
  • My part — designed the product's landing page, represented Actio in the field — moderating its live events and setting venues up in advance with the team — and ran QR-code check-in at the door. I did not build the application itself.
  • Company — Milapasa; the product is theirs, and it was a team effort.
  • Status — in production; sold publicly at actioevents.com.

What I owned, and what I did not

The landing page design was mine, and the field was mine too: I represented Actio at its live events, moderated them, travelled ahead with the team to set the venues up, and ran QR-code check-in at the door. The product application itself was built by Milapasa's development team — I make no claim to its code or architecture. The company owns the product and its roadmap.

What the door teaches

The part of Actio I value most in hindsight was not written in an editor. At live events, I stood at the entrance with the team, scanning QR codes and letting people in. When a registration record is wrong, the person it belongs to is standing in front of you, and the queue behind them is growing. That is a feedback loop no dashboard provides, and it permanently changed what I consider a "small" data bug.

The path from that door to the systems above it is fairly direct: the same instinct — that software's real test happens at the point of contact, not in the build log — is why Cendra shipped with production verification as a habit, and why LILA evaluates whether its assistant was right in front of the user, not just plausible in a test set.

One more thing belongs on this page, because the page is about where habits come from. Milapasa, founded by Deniz Egemen Aladağ, and WEglobal — the strategic umbrella it worked under, with Levent Erkan and Levent Ergen — gave me the warmest working life I have known: hosting international project managers, moderating live events, changing cities to fix a problem at its source. I learned customer experience there before I had the vocabulary for it, and I am grateful for it.

milapasa.com today — Actio still front and centre, next to Me-Learning, the learning platform I also worked on during my IT Analyst year.