HOW I WORK
Start with people. Find the real problem. Build something that lasts.
My work rarely starts with a perfectly defined problem or an obvious answer. I’m often brought into situations where the objective is clear but the path is not, where different groups see different pieces of the problem, or where a solution that makes sense on paper still has to work in the real world.
My approach is structured, but not rigid:
These stages are not intended to suggest every project follows a perfectly linear sequence. They represent the questions and disciplines I return to when moving complicated work from ambiguity toward practical execution.
01 / LISTEN
Get close to the work before trying to change it.
Understand how the work is actually experienced by customers, employees, leaders, subject-matter experts, and operational teams before prescribing a solution.
HOW I APPROACH IT
I ask questions, listen for different perspectives, learn how the existing process works, and pay attention to the gap between how work is supposed to happen and how it actually happens.
The people closest to the work often see friction, dependencies, risks, and unintended consequences that are difficult to see from farther away.
PRINCIPLES
Curiosity before prescription
Respect subject-matter expertise
Understand different stakeholder realities
Frontline feedback is operational intelligence, not simply sentiment
Listening does not mean every opinion becomes the decision
IN PRACTICE
At ISACA, customer feedback and operational evidence helped identify improvement opportunities within customer-support operations.
I later built a frontline advisory mechanism that gave employees earlier visibility into proposed changes and a way to provide practical operational feedback before implementation.
During an operational conflict over a shared support mailbox, I first heard the requesting team’s rationale before explaining why the work did not fit my team’s scope and capacity.
Listen long enough to understand the system, not just the request.
02 / DIAGNOSE
Separate the symptom from the problem underneath it.
Determine what is actually causing friction and where intervention will create meaningful value.
HOW I APPROACH IT
I combine qualitative insight with quantitative evidence. Depending on the problem, that may mean customer feedback, employee feedback, operational data, performance measures, process review, impact assessment, resource or capacity analysis, or external research.
I look for patterns and test assumptions rather than treating the first explanation as the root cause.
PRINCIPLES
Pair human insight with evidence
Look for patterns rather than isolated complaints
Question legacy assumptions
Distinguish activity from value
Understand the operating system around the problem
IN PRACTICE
At ISACA, customer feedback, operational data, and performance reviews were used to identify and prioritize customer and operational improvement opportunities.
During the peak-period support redesign, demand data and employee feedback showed that an established support model consumed significant resources despite low use.
During COVID, I researched external approaches and assessed internal systems, policies, procedures, operational controls, and risk considerations before recommending alternatives.
In the Engagement Forum story, I recognized that the recurring problem was not one inefficient meeting. It was the stakeholder-engagement mechanism itself.
Fix the mechanism underneath the repeated problem.
03 / CREATE CLARITY
Turn ambiguity into something people can decide and execute.
Give leaders and teams enough structure to understand what matters, what choices exist, what risks and trade-offs accompany them, and what must happen next.
HOW I APPROACH IT
I clarify the business outcome, constraints, affected groups, options, risks, dependencies, ownership, decision needs, measures of success, and path forward.
When priorities compete, I make the trade-offs visible instead of pretending everything can be equally important.
PRINCIPLES
Define the problem before building the solution
Make decision ownership explicit
Surface risks and dependencies early
Translate complexity rather than transferring it
Strategy becomes valuable when it becomes executable
IN PRACTICE
At ISACA, my peer, my leader, and I assessed roughly 25 improvement opportunities, narrowed them to approximately 5–7 priorities, and developed a 3–5-year roadmap and budget. Funding was approved and the prioritized initiatives were implemented.
For COVID curbside service, I developed executive options with risk, effort, and cost trade-offs; executives selected the path, and I led operationalization.
For sales compensation, I translated the business direction into an impact assessment and coordinated implementation requirements across functions.
During acquisition-related planning, I used frameworks, dependencies, milestones, readiness needs, and governance to make complicated transition work executable.
Create enough structure for a good decision, then enough clarity for others to execute it.
04 / DESIGN TOGETHER
Design with the people who understand and experience the work.
Build solutions that incorporate the expertise and practical realities required for successful execution.
HOW I APPROACH IT
I bring together the people who understand different parts of the system: operators, frontline employees, subject-matter experts, functional partners, control functions, leaders, and people who will ultimately use or support the solution.
My role is not to pretend I am the expert in every discipline. It is to ask useful questions, make connections across expertise, clarify decisions, and help the group arrive at something workable.
PRINCIPLES
Solutions should not be designed in isolation
Engage affected people early enough to shape the solution
Respect expertise without surrendering accountability
Shared input does not mean unclear decision rights
Design for the real operating environment
IN PRACTICE
The frontline advisory network gave employees and leaders earlier visibility into proposed initiatives so practical operational feedback could enter solution design.
Curbside operationalization required coordination across operational partners and control functions after leadership selected the path.
The ISACA certification automation demonstrates the value of frontline ideas: the original automation initiative came from frontline talent, and broader organizational support helped scale the improvement.
Cross-functional work has repeatedly spanned Sales, Operations, Finance, HR, Marketing, Technology, Engineering, training, communications, and frontline teams, as reflected throughout my career materials.
The people closest to the work should have a voice before the solution reaches them.
05 / TEST & LEARN
Treat assumptions as things that can be tested.
Reduce unnecessary risk, learn from evidence, and make it acceptable for the original plan to change when reality says it should.
HOW I APPROACH IT
Depending on the work, I use scenarios, pilots, readiness checks, feedback loops, performance measures, or structured reviews.
I am comfortable recommending a staged approach when organizational readiness or uncertainty makes an all-at-once decision unnecessarily risky.
PRINCIPLES
A pilot is a way to learn, not simply validate a preferred answer
Measurement should inform the next decision
Changing the route is not abandoning the objective
Speed and risk management are not opposites
Implementation is not the same as success
IN PRACTICE
For the redesigned peak-period support model, I used a reduced-staffing pilot and continued measurement rather than forcing immediate elimination of the existing model.
For live chat, I developed demand and capacity scenarios and pilot measures rather than building the operating model around one staffing assumption.
When introducing After-Action Reviews, I first modeled the practice on projects I led, applied those lessons to later work, and used the resulting evidence to build the organizational case.
My broader change framework has consistently emphasized feedback loops, adoption, behavior, business outcomes, and continuous adjustment.
Use evidence to improve the decision, not defend the original plan.
06 / MAKE IT SUSTAINABLE
Build something that can keep working without you.
Move a solution from project activity into an operating capability with clear ownership, usable tools, governance, knowledge, measurement, and reinforcement.
HOW I APPROACH IT
I think about sustainment before launch: who owns the work, what routines support it, how issues surface, what people need to know, how performance will be measured, and what documentation or mechanisms need to remain.
When the work is successful, it should eventually stop depending on the person who created it.
PRINCIPLES
Build capability, not dependency
Define operational ownership
Document what needs to be repeatable
Embed learning into future execution
Make useful mechanisms easy for others to adopt and improve
Sustainability matters more than preserving personal ownership
IN PRACTICE
The recurring Engagement Forum remained in use through the sale of the company.
The standardized project impact-assessment approach I originally created was later expanded by others and became established departmental practice.
After-Action Reviews became integrated into the department’s project-execution structure after I modeled the practice, built the organizational case, and supported adoption.
My career materials consistently describe the value I bring as building repeatable mechanisms and organizational capabilities that continue delivering value beyond implementation.
The best evidence of good work is that the organization can continue receiving value after the person who built it moves on.
THE CLOSING PRINCIPLE
Structure without unnecessary bureaucracy.
My approach is deliberately structured, but I do not believe more process automatically means better execution.
The appropriate solution depends on the problem, the people, the risks, and the organization’s readiness.
Sometimes the answer is a detailed operating model. Sometimes it is a pilot. Sometimes it is a decision framework, a forum, a spreadsheet, a playbook, or simply getting the right people into the same conversation.
The method should serve the outcome, not the other way around.
Strategic Problem Solving • Operational Excellence • Human-Centered Design • Data-Informed Decision Making • Cross-Functional Leadership • Change Leadership • Operating Model Design • Organizational Capability Building