The person behind the platforms

I am an IT consultant, systems architect, and project manager. Organizations bring me in to build new technology systems, improve the ones they have, and keep everything running.

I started in software development and grew into business analysis, infrastructure, and project delivery. Because of that path, I am comfortable in the room with engineers and in the room with executives, and a lot of my job is translating between the two.

I have worked across financial services, mining, e-commerce, consulting, education, retail, and non-profits. Working in that many sectors teaches you something no single industry can: how a technology decision actually lands on operations, revenue, and the people who use the system every day.

Whatever I am building, a mobile app or an IT policy framework, my approach stays the same. Understand the problem properly, design the right solution, and deliver something the organization can measure.

I especially enjoy the unglamorous part: taking a manual, fragmented process and turning it into something organized that people can rely on.

Technology should serve the business, not the other way around.

Every system I recommend or build has to be connected to a real organizational need. So before anything gets built, I ask:

  1. What problem are we solving?
  2. Who will use this system?
  3. What process are we improving?
  4. What data matters?
  5. What does success look like?
  6. How will this system be managed after launch?
  7. How will it support growth?

I do not build systems for appearance. If the answers to those questions are vague, the project is not ready, and I would rather say so early than deliver something impressive that nobody uses.

What I hold myself to

  • Clarity

    Every project should be clearly understood before work begins.

  • Excellence

    If my name is on it, it should be built well and finished properly.

  • Practicality

    Technology must make sense for the organization’s size, budget, and capacity.

  • Reliability

    Systems should work, and when they break, someone should pick up the phone.

  • Growth

    I try to build something better on every project than I did on the last one.

  • Leadership

    Leading a team means taking responsibility and helping people do their best work.

See the work Work with me