From Operations to Power Platform Development

My Approach to Building Solutions

My Story

For 20 years, I worked in educational services, but my real expertise wasn't just in the education sector. It was in understanding how data moves through organizations, how decisions get made, and how the right systems can transform chaos into clarity.

The turning point came in 2016 when I built an enrollment tracking dashboard that became essential to our CFO's daily routine. For 8 years, that system ran flawlessly, updating every night, providing reliable data for critical business decisions. I watched executives use something I built to make planning decisions. That's when I realized: I wasn't just working in education, I was building business solutions.

But when organizational expansion required tracking additional training centers not in our centralized database, we tried to patch together a solution using email-based Excel submissions and Power BI. It was fragile. It broke constantly. I spent hours each month manually fixing format errors and cleaning data. I knew there was a better way.

That experience crystallized what I want to do next: help organizations get it right the first time. Not build patches. Not create workarounds. But design proper solutions that scale handle edge cases gracefully, and actually solve the business problem.

So I made a decision. I earned my Power Platform certifications, including PL-300 and the AI Business Professional credential, and I built the solutions I wish we'd had. Not as theoretical exercises, but as comprehensive portfolio projects: most recently Arcova Engage, a multi-surface engagement management system with an embedded AI agent, demonstrating exactly what I'd deliver, from requirements and data modeling through application development, automation, and AI integration.

Now I'm ready to bring those 20 years of operational wisdom and validated Power Platform and AI development skills to organizations that value both understanding the business problem AND knowing how to build the right solution.

My Approach to Solution Architecture

I believe great solution architecture starts with understanding the business problem and not jumping to technology.

Here's how I work:

1. Listen First, Design Second
Before I sketch a data model or open Power Apps, I want to understand: What's actually broken? What manual work are people doing that they hate? What decisions aren't getting made because the data isn't available? The technology comes after understanding the pain.

2. Design for the Real World
Systems fail in production because they don't account for edge cases. Someone will misspell a country name. Someone will submit the same data twice. Someone will need to correct an error after submission. I design for these realities upfront: validation rules, audit trails, soft deletes, comprehensive error handling.

3. Document Decisions
Every architectural choice involves tradeoffs. I document not just what I built, but why and what alternatives I considered, what I optimized for, what future implications the decision has. This isn't extra work; it's essential for maintainability and knowledge transfer.

4. Prioritize User Experience
The best-architected system fails if users won't use it. I think about workflows, minimize clicks, provide immediate feedback, and design for the least technical user in the room. My Power Apps have auto-save, clear validation messages, and confirmation receipts because that's what users need to trust the system.

5. Build for Scale and Change
Will this work with 10x the data? What happens when requirements change? I use normalized data models, delegation-friendly queries, and indexed columns because "it works now" isn't good enough. I'm designing for what the system will become, not just what it is today.

6. Learn and Improve
My portfolio projects document lessons learned and what I would do differently next time.  I don't see that as a weakness. That's a growth mindset. Every project teaches lessons. I document them, learn from them, and apply them next time.

Let's Talk About Your Next Project

I'd love to discuss how my combination of operational experience and technical capability could benefit your team. Whether you're hiring for a specific project or building out your team, let's connect.