Lead the business.
Stay close to the work.

I’ve done the work. I understand the stakes.

I’m first-generation white collar, with blue-collar roots. I built my career in computer labs, on client sites, and through delivery. Service desk, QA, business analysis, development, architecture, program management, and business operations have each changed the way I see a problem.

An ambiguous requirement becomes a developer’s uncertainty, then a project manager’s scope problem, then a director’s budget conversation. I’ve been each of those people. That is why I want the outcome, the constraints, and the definition of done clear before a team starts building.

Leadership means giving other people room to deliver.

I stay technically close to the work so the direction is credible. Then I make the handoff explicit: what matters, what is constrained, who owns the decision, and what the team should bring back for review. Being the architect does not mean becoming the bottleneck.

Staffing is more than finding an available person. It is matching capability to the work, being honest about gaps, and putting the right support around the team. A delivery plan that depends on everyone being a hero is a weak plan.

Read the demand before it becomes a staffing problem.

A staffing dashboard should help make a decision before a delivery team feels the constraint. I look across committed work, draft scope, and opportunities mature enough to create a credible demand signal. Those are different kinds of evidence; they should not be flattened into one optimistic forecast.

I compare likely timing, duration, and skill needs with available capacity. A sustained gap may justify hiring ahead of the need. A short peak may call for redeployment or specialist support. An early opportunity may call for preparation and another review, not additional payroll. The judgment is in knowing which situation you are in and changing the plan when the signals change.

Give people a menu they can understand.

A team can understand its work deeply and still need help seeing where AI fits. Asking it to specify an agent before explaining the possibilities is like asking someone to order without a menu. I start by listening: show me the work, the exceptions, the decisions, and what happens next.

That is stakeholder elicitation, capability translation, and opportunity discovery. I make the choices concrete, check data and access requirements with the technical team, and help stakeholders compare value, effort, risk, and readiness. Sometimes the right starting point is assistance; sometimes it is automation; sometimes a conventional rule is enough.

My advisory work includes facilitating those conversations and turning the findings into a concise leadership roadmap with a deeper technical companion. The aim is a shared direction, explicit prerequisites, and a proposed pilot the team can evaluate. A roadmap is a decision artifact; implementation and measured results come afterward.

Start with the work people hate doing twice.

My first question is usually, “What do you hate doing twice?” I’m looking for the repeatable work, the missing decision, or the handoff that keeps creating friction. Sometimes the answer is an agent. Sometimes it is a clearer process, a conventional integration, or a rule that should have been documented years ago.

I use Crawl, Walk, Run to make that distinction concrete: establish a repeatable process, prove value within a bounded scope, then expand. Agree on acceptance criteria. Show the work early. Train the people who will operate it. An organization should become more capable because of the engagement.

Governance belongs inside the work.

At OPTiMO, I led the implementation behind CMMI Development Level 3: operational strategy, supporting tools, training, and the audit lifecycle. The point was to create a process the organization could actually use.

I bring that same expectation to AI. Define the authority, preserve the evidence, understand the cost, and know who owns the result. Let an agent complete permitted work. Ask for another pass when the evidence is incomplete. Escalate when the task needs judgment or authority the system does not have.

Building keeps the strategy honest.

My independent products are where I test the engineering choices I bring into consulting. Power Platform X-Ray turns architecture knowledge into repeatable delivery material. HeadHunterAgent.AI explores orchestration, retrieval, model economics, and operational resilience. The Wrap Sheet tests how creative generation can stay connected to deterministic facts.

I choose models and platforms for the problem: capability, reliability, cost, and the operating environment. Technical currency is earned by building, measuring, and changing your mind when the evidence warrants it. A new model announcement does not substitute for an evaluation.

The team is part of the outcome.

I care about teams that can tell the truth early, challenge a weak assumption, and carry the work forward after the original architect leaves the room. Retrospectives, practical training, and a shared definition of done are operating habits.

The combination I bring is executive accountability and technical judgment: lead the practice, set the architecture, support the specialists, and stay responsible for what happens next.