Skip to main content
Team Lead, Project Manager2014
#Python#Django#PostgreSQL#JavaScript#jQuery#Bootstrap

EEF (SCO) — Youth Economic Forum Management System

Government contract to run a large international event: 12 curators, 72 local coordinators, 5000+ participants. Technically flawless, psychologically exhausting. A lesson that gov contracts require both technology and people work.

In Short

We built a CRM for a forum at the “keep 5000 people organized for a week” level. Registration, accommodation, transfers, sessions, catering, reporting — all in real time.

Technically we delivered 100%. Psychologically — it was hell of sudden changes and “need it by lunch.” Since then, I flinch at “can we have it today?”

What Worked Well

  • Single participant database with live arrival and accommodation statuses.
  • Dashboards for curators and coordinators: who’s where, what’s on fire, where’s the bus.
  • One‑click printing of badges/vouchers (and the tenth click when everything changed again).
  • Excel exports “the way they like it” (plus six other formats — because yes).
5000+
participants
72
coordinators
12
curators

Pain Points

  • Requirements changed daily and contradicted each other.
  • Approvals took five signatures; changes were “right now.”
  • “Two‑hour urgent” requests turned into office sleepovers.

Lessons

  • In gov contracts, product is also communication. Without it, any code becomes pain.
  • Printed documents are part of UX. If they’re hard to print, everything falls apart.
  • Don’t promise “by lunch.” Honest timelines save everyone’s nerves.