What Becoming a Father Taught Me About Consulting

Early in my career, I thought being a good technology consultant meant having the right technical answers.

If I understood the platform deeply enough and designed a solid solution, success would follow. Technical depth mattered, and it still does, but over time, I learned that correctness alone rarely determines outcomes.

That lesson became much clearer after becoming a father.

I have two daughters, Sienna, who is three, and Ruby, who is eight months old. Parenthood has a way of clarifying what responsibility really means. Many of the lessons it reinforces every day mirror the ones I learned later than I should have in consulting.

The Problem You Are Given Is Not Always the Real One

In consulting, clients often come with a clearly stated request. Automate this process. Implement this capability. Improve reporting.

Early on, I treated those requests as the problem to solve.

As a parent, you quickly learn that when a toddler is upset, the issue is rarely the thing they are pointing at. Hunger, exhaustion, or frustration are usually the real drivers. Addressing the surface issue without understanding the cause rarely works.

Consulting is no different. The real value comes from slowing down, asking better questions, and understanding context. That includes the business problem, the people involved, and the tradeoffs behind every decision. Without that context, even the best technical solution can miss the mark.

Clarity Matters More Than Complexity

There is a temptation in consulting to demonstrate value through complexity. More configuration, more features, more sophistication.

Parenthood challenges that instinct quickly. If you cannot explain something clearly to a child, it probably is not clear. The same applies when working with executives, stakeholders, and delivery teams.

Over time, I have learned that great consultants do not just solve problems. They create clarity. They help define what success actually looks like, surface tradeoffs early, and simplify decisions so teams can move forward with confidence. Clarity builds trust. Complexity without clarity erodes it.

Ownership Does Not End at Delivery

Before I had kids, I thought ownership in consulting ended when the work was delivered.

Parenthood removes that illusion fast. Responsibility does not stop once something is working. You observe, adapt, and adjust as reality unfolds.

In consulting, the most meaningful work happens after implementation, when solutions meet real-world constraints, edge cases appear, and assumptions are tested. Taking ownership means caring about outcomes, not just outputs.

How This Shapes My Approach Today

Today, technical depth is still table stakes, but it is no longer the goal.

My approach to consulting is shaped by the same lessons parenting reinforces:

• Listen before reacting
• Understand the system before changing it
• Be clear about goals and tradeoffs
• Optimize for long-term outcomes

Becoming a father did not make me a technology consultant, but it made me a better one.

Your value is not just in what you build. It is in how well you understand the people, context, and responsibility that come with it.