Hi, I'm Anna. 👋
Systems Analysis &
Process Automation
Engineering approach to IT delivery. 9+ years turning complex workflows into working, automated systems.
What is your priority right now?
I am typically engaged to handle these challenges
New Product Launch
Turning a business idea into clear requirements, system design, and structured delivery — from first stakeholder interview to working product.
- → Business intent clarified: stakeholder interviews, User Stories, PRD
- → System requirements ready for development
- → Cross-functional delivery coordinated: business, users, dev
- → Acceptance criteria defined, documentation delivered
Operational Excellence
Finding the constraint that limits your operations and engineering it out — with automation, clear ownership, and measurable results.
- → Process mapped, constraint identified (TOC)
- → Workflows automated: CRM, SharePoint, portals
- → Teams aligned: responsibilities, escalation, conflict resolution
- → New process documented and maintained automatically
My Approach: Tech, Process, Adoption
Engineering DNA
Rooted in my MATI degree and C/C++ background. I approach business processes as engineering systems — stable, measurable, and technically feasible. If I write requirements, they are ready to code.
Theory of Constraints
I don't optimize "everything". I identify the single bottleneck limiting your system and focus resources there. This ensures the highest ROI with minimal disruption to the business.
Adoption & Communication
A solution that isn't understood won't be adopted. I structure deliverables — reports, specs, interfaces — around how people actually process information: clear hierarchy, cognitive limits, minimal friction. The goal is not just a working system, but one that stakeholders accept and teams can maintain.
Analysis in Practice
Lastik — Data De-identification Tool
Live open-source product · Zero data transmission · GDPR pseudonymisation
Lastik — Data De-identification Tool
Live open-source product · Zero data transmission · GDPR pseudonymisation
Data Model Quality Framework
Approval cycle reduced from ~1 week to 1–2 days · Error shift from Review to Entry · Adopted as team standard
Data Model Quality Framework
Approval cycle reduced from ~1 week to 1–2 days · Error shift from Review to Entry · Adopted as team standard
Ticket Bliss: Smooth Rides Ahead
3 critical path failures identified · Two-tier solutions proposed · Process governance recommendations
Ticket Bliss: Smooth Rides Ahead
3 critical path failures identified · Two-tier solutions proposed · Process governance recommendations
If you're solving a similar challenge — I'm happy to talk.