My career began behind the camera, working across product, lifestyle, environmental portraiture, and customer-story photography.

​

Product photography taught me precision. Lighting, materials, composition, product fidelity, and hundreds of small decisions could change how something was perceived. Photographing people taught me something different. Good images often depended on trust, communication, observation, timing, and knowing when to provide direction and when to let a real moment happen.

​

Together, those experiences shaped how I think about commercial creative work. The craft matters, but so does understanding the audience, the purpose of the assignment, and what the image needs to accomplish for the business.

While working at Dell, I became increasingly curious about CGI as the industrial design team's renders became more sophisticated. I started paying attention to what they might become useful for beyond design review. I began asking questions, learning how the technology worked, and bringing the right people together to explore whether CGI could solve real commercial production needs.

​

I helped start the CGI conversation at Dell and helped move an early pilot from discussion into testing. The goal was not simply to prove that CGI could make an image. It was to learn it, test it, find where it broke, and understand where it offered an advantage over photography, where it did not, and what would be required to make it dependable in production.

​

That experience established a pattern that has stayed with me: new technology is most useful when you start with the problem, understand the existing process, and determine where the tool actually creates value.

Moving into visual direction changed the question from "Is this image good?" to "How do we make good work more repeatable?"

​

I brought a photographer's eye into CGI production and worked with artists on lighting, materials, composition, product correctness, and review. I created reference shoots called GoBys: physical photographs made as visual targets for CGI artists to match. Alongside those, I built lighting guidance, material references, SOPs, and a stronger internal review process.

​

I also trained 20 artists across two studios on photographic lighting. The goal was to take judgment that often lived in one person's eye and make it easier for a larger team to understand, apply, and review consistently.

​

This was where my focus began to widen from the image itself to how expectations, feedback, and standards moved through a team. The question was becoming less about making every decision myself and more about helping other people make good decisions consistently.

As the operation grew, the challenge expanded beyond individual images and reviews. People, workload, specialization, timing, and capacity became part of the creative problem.

​

A 9-person group was splitting its time between stills and animation largely based on who was available. I grew the organization to 16 and organized it by specialization, with 6 artists focused on still imagery and a 10-person animation group covering lighting, comp, VFX, technical leadership, motion, and editorial.

​

Each group could then develop the process its own work actually needed.

​

I also rebuilt the still-image pipeline and quality controls so the team could absorb roughly 30 to 40% more Dell volume while maintaining the visual standard. From there, I helped develop the animation operation into an efficient and profitable practice.

​

Production leadership taught me to look beyond whether an individual project was going well and pay attention to where the operation itself was under strain: whether the right people were doing the right work, where capacity was constrained, whether expectations were clear before review, and whether the process still fit the volume it needed to support.

Co-founding and running a production company widened the view again. Production decisions now had to account for client expectations, schedules, staffing, resources, delivery, and the business supporting all of it.

​

I standardized parts of intake, documentation, review, file organization, and handoff so a small team could manage complex production without losing track of what needed to happen next.

​

It reinforced something I had been learning throughout my career: most production problems do not live in only one place. A missed expectation can become a review problem. A staffing decision can become a capacity problem. A process that works at one volume may stop working at another.

​

Good operations means understanding those connections early enough to do something useful about them, while keeping the parts that already work intact.

​

That perspective now sits alongside the visual craft I started with. I still care about the image, but I also care about the people, decisions, processes, and business conditions that allow a team to deliver it well.