IT Governance & Processes
Unclear ownership, inconsistent decisions, and processes nobody quite trusts.
My approach
Map responsibilities, simplify the steps, and make the right way easier.
A LITTLE STRUCTURE. A LOT OF CURIOSITY.
Global IT / Processes / AI & Automation
And occasionally convince them to cooperate.
Working across IT, governance, automation and AI to turn complex problems into simpler systems.
01 /THE PERSON, NOT JUST THE JOB TITLE
I’m Megi. I work where technology, processes and people meet — which is usually where the interesting questions start. I’m curious about how systems work, pragmatic about what needs to change, and comfortable moving between the technical details and the bigger picture.
Infrastructure, governance, automation, AI: I don’t see these as separate conversations. I like understanding the connections, finding the friction, and making complicated things a little simpler. Technology should solve an actual problem. Preferably without creating three new ones.
Somewhere between a Teams call, an architecture diagram and an Excel file that became much more complicated than originally planned.
I like processes. Even more when they actually work.02 /CONNECTED DISCIPLINES
Technology should solve an actual problem.
Unclear ownership, inconsistent decisions, and processes nobody quite trusts.
Map responsibilities, simplify the steps, and make the right way easier.
Connected environments with disconnected visibility.
Bring infrastructure, Azure, and governance into the same conversation.
A lot of AI potential. Not always an obvious use case.
Start with a real task, experiment with agents and Copilot, and question the output.
Repetitive work and handoffs that consume attention.
Understand the process before connecting APIs or building a workflow.
Plenty of data, not enough context for a decision.
Connect the question to the data, then make the answer understandable.
Many systems, incomplete information, and important decisions to make.
Structure the questions around infrastructure, risks, dependencies, and integration.
New tools layered on top of old ways of working.
Connect technology choices to the people and processes they affect.
03 /THINGS I BUILD & QUESTIONS I EXPLORE
The context matters as much as the code.
Restaurant management for tables, reservations and orders.
Barber shop management with online appointment booking.
A mobile and web application for cooking and recipes.
A company showcase focused on design and services.
A visually impactful landing page for automotive services.
An elegant brand website with a focus on visual identity.
Bringing cloud infrastructure into focus.
Cloud environments need a coherent way to understand infrastructure and monitor what is happening.
Bring monitoring into a shared control-plane application rather than treating each view in isolation.
What if governance could be a little less manual?
Governance information can be scattered across documents, decisions, and conversations.
Explore an AI assistant that helps organize context and surface questions, while leaving decisions with people.
Less chasing updates. More moving work forward.
Manual handoffs can make a simple request surprisingly complicated.
Map the process, clarify ownership, then explore a workflow that connects the steps.
04 /HOW I THINK
Complexity is sometimes necessary. Confusion isn’t.
Automate boring things.
If a process requires a 40-page manual, maybe the process is the problem.
AI is useful when it actually helps someone do something better.
Ask “why?” at least one more time.
05 /MY TOOLBOX
No skill percentages. Just useful connections.
The foundations: understanding environments, connecting services, and keeping the architecture manageable.
06 / LAB
finding_interesting_problems()
explore_agentic_ai()
question_old_processes()
build_random_things()
meet_interesting_humans()
07 /THE PEOPLE I WORK WITH
I asked the people who actually have to work with me.
Worked with me? Leave a reference.
Nice ones preferred. Honesty tolerated.08 /BEYOND THE JOB TITLE
Understanding how something works is interesting. Understanding why it works that way is usually more interesting.
Learning, experimenting with AI, and changing my mind when a better idea comes along.
New places, new conversations, and the occasional unnecessarily complicated way of simplifying something.
37.7749° N / 122.4194° W
I came here to explore.
Now I’m considering what comes next.
09 /SAN FRANCISCO / OPEN TO OPPORTUNITIES
Dangerous place for someone this curious about tech.
I work at the intersection of IT governance, automation, cloud and AI.
I’m currently spending time in San Francisco, probably one of the worst possible places to keep someone like me away from new ideas.
INTERESTED IN MEETING PEOPLE BUILDING IN
OPEN TO
Good conversations tend to lead somewhere.10 /WHY MEGI?
I understand what happens when new technology meets real organizations, legacy infrastructure, organizational requirements and processes.
I’m especially interested in turning AI and AI agents into practical enterprise tools rather than demos.
I naturally work between technology, governance and business processes.
When I see a repetitive or complicated process, my first instinct is usually: “Can we automate this?”
I ask questions. A lot of them. Especially “why are we still doing it this way?”
Let’s talk.
11 /LET’S TALK
Let’s figure it out.
A project, a question, or a complicated system that could use a little clarity. I’m listening.