An operations leader who builds software around the way work actually happens.

I am an operations leader first. For nearly three decades, I have worked across restaurants, retail, warehouse operations, logistics, and service businesses. That experience taught me to look closely at how work gets done, how people are supported, and where a process creates unnecessary difficulty.

Leadership means balancing support with accountability. People need clear expectations, useful coaching, and the chance to grow. They also need leaders who follow through and address problems directly.

I enjoy helping employees develop their skills and confidence. I also enjoy improving the systems around them so good performance is easier to repeat.

The goal is not simply more activity. I want measurable improvements in performance, consistency, decision making, and the daily experience of the people doing the work.

Software is another way I solve operational problems. I build when I see a recurring issue that can be handled more clearly, consistently, or efficiently.

Forecast Flow began with a need for better information when planning demand and labor. Labor Flow grew from the need to apply staffing guidelines quickly without hiding the reasoning behind the recommendation.

Experience and judgment still matter. The purpose of the software is to give managers a stronger starting point, reduce avoidable guesswork, and make the next decision easier to understand.

I use Forecast Flow and Labor Flow in my operational role at the Apple Valley Mister Car Wash location. They are tools I developed and use at the site level. They are not company wide systems or officially endorsed applications.

The rest of the portfolio follows the same operations first approach. Goals Flow organizes weekly plans and daily direction. Hire Flow supports better preparation for candidate conversations. Feedback Flow helps managers work through customer concerns with greater consistency.

These applications support managers rather than replace them.

Better information leads to better decisions, but the manager still provides context, judgment, coaching, and accountability.

A useful tool should help an experienced manager move faster and help a newer manager build confidence. In both cases, the person remains responsible for the decision.

I start with the recurring problem, not the technology. I look for the cause, the information people are missing, and the point where the workflow breaks down.

Treating the same symptom every day wastes time. A better system should make the problem less likely to return or make the response faster and more consistent when it does.

Technology should simplify work. If a feature adds steps without improving the result, it does not belong.

I measure a tool by what changes after people use it. The result should be clearer decisions, less repetitive work, stronger consistency, or a better experience for the team and customer.

JY Foundry gives me a place to show how I think, what I notice, and how I turn an operational problem into a working solution.

The case studies make that process visible. They document the original need, the decisions behind the product, the current result, and the work that still remains.

They also give me a disciplined way to keep learning. Building a tool forces me to define the problem clearly, test my assumptions, and decide whether the result genuinely improves the work.

The applications are the evidence. The larger story is curiosity backed by follow through.