Building Systems That Make Organizations Work Better

As MCA grew, enterprise HR processes needed to function consistently across locations and departments. Fragmented workflows and manual workarounds created avoidable administrative burden.

As companies grow, it's easy for processes to become fragmented. Different departments develop different approaches, information lives in multiple systems, and employees spend valuable time working around processes that were never designed to support an organization at scale.

I've spent a significant part of my career identifying those challenges and helping build better solutions.

Replacing workarounds with reliable processes

At MCA, I led enterprise HR technology initiatives and improvements involving ADP, employee information management, reporting, and administrative workflows.

My responsibilities included evaluating business needs, determining system requirements, approving workflows and configurations, coordinating vendors, and working across HR, payroll, finance, IT, and operations to implement changes.

I was particularly focused on developing processes that could be used consistently across locations while remaining practical for the employees and managers responsible for using them.

That meant looking beyond what a system could technically do and asking whether it would actually make the organization more effective.

Making Technology Work for People

I've never believed that implementing new technology automatically means improving a process.

For me, the test was whether employees, managers, and business leaders could use the information and workflows more reliably, not whether a new feature had been activated.

I worked to reduce unnecessary manual work, consolidate information, improve reporting, and introduce automation and self-service capabilities where they made sense.

I also oversaw training and change management to help employees and managers understand new processes and adopt them successfully.

Those efforts required listening to the people doing the work, understanding where existing processes created frustration, and balancing operational needs with the practical realities of implementation.

Building for the Long Term

The improvements we made helped reduce recurring errors, eliminate duplicated work, improve information accuracy, and give leadership more consistent data for decision-making.

Just as importantly, I focused on developing systems and processes that would continue functioning without requiring constant intervention from the person who created them.

That has always been an important measure of success for me.

A well-designed process shouldn't depend on one person knowing how to make it work. It should be understandable, repeatable, and capable of supporting the organization as it grows.

Whether I'm working with technology, policies, reporting, or organizational structure, my objective is the same: make the business easier to manage, give people better tools, and create a stronger foundation for whatever comes next.