I Don't Know What My Brand Is. But I Know What I Care About.

And from a marketing perspective, I understand why defining a category matters.

People need to understand what you offer before they can decide whether they need it.

Clarity creates opportunities.

Ambiguity creates friction.

I don't disagree with any of that.

But I've spent much of my life fascinated by something that categories tend to overlook.

Human beings are rarely as simple as the labels we assign to them.

We are collections of experiences, interests, abilities, contradictions, aspirations, and values.

The person someone sees in a professional setting is only one expression of a much more complicated individual.

Yet we often feel compelled to reduce ourselves to something that fits neatly beneath our name on a LinkedIn profile.

A title.

A specialty.

A marketable identity.

And the more I've thought about that conversation, the more I've realized why I struggled to define mine.

It's not that I don't know what I'm capable of.

It's that the things I find most meaningful don't necessarily belong to one profession.

They're not confined to a title.

And they certainly aren't exclusive to a particular industry.

They're simply the things I care about.

I Love Building Things That People Actually Use

I've always enjoyed building things.

Not necessarily in the traditional sense of physically constructing something, although I've always appreciated that too.

I'm talking about taking an idea, a problem, or an opportunity and helping transform it into something tangible.

Something meaningful.

Something that makes another person's life a little easier, more productive, or more fulfilling.

Sometimes that's a product.

Sometimes it's a process.

Sometimes it's a team.

Sometimes it's an environment where people can finally do the kind of work they've always been capable of doing.

I've spent time learning about software development, and I find the complexity of building modern applications fascinating.

The architecture.

The design.

The countless decisions required to transform a concept into something functional.

But what interests me most isn't necessarily the technology itself.

It's the person on the other side of it.

The person who's going to use what we've created.

The problem we're trying to solve for them.

The value that exists when someone can finally do something they couldn't do before.

I think that's why I've always found myself drawn toward systems thinking, leadership, and organizational development.

Because a system isn't valuable simply because it's sophisticated.

A product isn't successful simply because it's technically impressive.

And a team isn't high-performing simply because it contains talented people.

The value comes from what those things make possible for someone else.

I love being part of that.

I love watching an idea become a reality.

I love watching people work through something difficult and eventually discover a better way forward.

And I especially love the moment when something we've invested so much energy into begins creating value beyond the people who built it.

But is that product development?

Innovation?

Leadership?

Organizational transformation?

I suppose it could be any of those things.

And perhaps that's part of my problem.

I've never been particularly interested in which category the work belongs to.

I've been interested in whether the work matters.

I Don't Just Build Teams. I Become Part of Them.

There's something about working closely with a group of people that I've always had difficulty explaining.

When I'm responsible for a team, I don't experience that relationship as simply a collection of people who report to me.

Of course, there's an organizational structure.

There are expectations, accountabilities, performance conversations, and professional boundaries.

I understand the responsibility that comes with having a management title.

But the relationship has never felt purely transactional to me.

The people I work with become part of my life.

And in some small way, I become part of theirs.

We spend an extraordinary amount of time together.

We navigate challenges.

We celebrate successes.

We experience frustrations.

We disagree.

We learn about one another.

Over time, we begin recognizing the things that make each person unique.

You learn who thrives when given an ambiguous problem.

Who needs additional context before feeling comfortable making a decision.

Who has an incredible ability to bring calm to a difficult situation.

Who can make an entire room laugh when everyone desperately needs a moment of levity.

But you also begin understanding that the people sitting beside you are carrying entire lives that exist beyond the work.

They have families.

Responsibilities.

Ambitions.

Struggles.

Things they're excited about.

Things they're worried about.

Things they may not feel comfortable sharing.

And I think that awareness changes how you lead.

Because once you begin seeing people as complete human beings rather than simply the roles they occupy, it's difficult to go back.

I don't believe those relationships should require people to share personal details they would prefer to keep private.

Caring about someone means respecting their boundaries too.

But when people choose to let you into portions of their lives, even in small ways, I believe there's a responsibility to treat that trust with genuine appreciation.

People don't stop being human when they walk into an office or log into a meeting.

And I've never wanted to be the kind of leader who forgets that.

High Performance Is Something I Believe I Understand

If someone asked me what I feel particularly confident doing, building high-performing teams would be near the top of the list.

Not because I possess some secret formula.

Not because every team I've ever worked with has been perfect.

And certainly not because I've never made mistakes.

I've made plenty.

But I've spent years observing how people interact, how systems influence behavior, and how the conditions surrounding a team can either unlock or suppress its potential.

I've learned that you can assemble a group of extraordinarily talented people and still struggle to produce meaningful outcomes.

I've also learned that people who might be overlooked individually can accomplish remarkable things when they're part of the right environment.

And I don't think that's a coincidence.

I believe high performance is largely a product of the conditions we create.

Trust.

Clarity.

Accountability.

Autonomy.

Psychological safety.

Shared purpose.

Opportunities to learn.

The freedom to challenge assumptions.

The confidence to ask for help.

None of these things guarantees success.

But when they're present and reinforced consistently, people have a much better opportunity to do extraordinary work together.

I feel confident in my ability to help create those conditions.

I know how to connect with people.

I know how to recognize strengths that aren't always immediately obvious.

I know how to bring people together around a problem worth solving.

And I know that when people believe their contributions matter, their relationship with the work begins to change.

They stop simply completing assignments.

They begin taking ownership.

They stop waiting for someone to tell them what to think.

They begin challenging the way things have always been done.

And eventually, something remarkable happens.

They begin elevating one another.

That's when I believe a team starts becoming something truly special.

But I want to be careful about one thing.

I don't believe leaders create high-performing teams by making people dependent on them.

I believe they create the conditions that allow people to develop the trust, capability, and confidence to perform together.

The team deserves ownership of its accomplishments.

The leader's responsibility is to help create an environment where those accomplishments become possible.

So, am I a team builder?

A servant leader?

A coach?

A systems thinker?

Again, I don't know that any single description captures it.

Because all of those things are connected.

And separating them feels like trying to explain an entire painting by describing only one of its colors.

Maybe the Simplest Answer Is That I Care

I've spent years thinking about how to describe the value I bring to other people.

And after all that reflection, I keep returning to an answer that almost feels too simple.

I care.

That's it.

I care about the people I work with.

I care about whether they're happy.

I care about what they're learning.

I care about whether they feel valued.

I care about the problems they're facing.

I care about the challenges they don't always know how to communicate.

I care about their aspirations, even when those aspirations might eventually take them somewhere beyond my team or organization.

I care about their families.

About the things that excite them.

About the hobbies and interests that make them who they are.

About the frustrations they carry.

About the things they enjoy and the things they'd rather never have to deal with again.

And I care about whether the time they spend working contributes something positive to the lives they're trying to build.

I recognize how this might sound.

Caring isn't a particularly unique value proposition.

Most leaders would probably tell you they care about their people.

Most organizations include some variation of caring, respect, or putting people first among their stated values.

And that's precisely why I think the distinction matters.

Caring isn't particularly meaningful as a statement. It becomes meaningful through behavior.

It's easy to say you care about someone's development.

It's more difficult to have the uncomfortable conversation that helps them recognize what's holding them back.

It's easy to say you care about work-life balance.

It's more difficult to challenge an unrealistic commitment when doing so might disappoint someone above you.

It's easy to celebrate an employee's contributions.

It's more difficult to advocate for that employee when they aren't in the room.

It's easy to encourage someone to pursue their aspirations.

It's more difficult to support them when achieving those aspirations means they'll eventually leave your team.

Those are the moments when caring becomes something more than a sentiment.

It becomes a choice.

And those choices, repeated consistently over time, are what I believe define a leader.

I won't pretend I always get them right.

Sometimes I misread a situation.

Sometimes I don't recognize that someone needs support quickly enough.

Sometimes I have to revisit a conversation and acknowledge that I could have handled it differently.

But the underlying intention remains the same.

I want what's best for the people I have the privilege of serving.

Not what's most convenient for me.

Not necessarily what's easiest for the organization.

What's genuinely going to help them become the people they're capable of becoming.

And I understand that caring alone isn't enough.

People also need competence, honest feedback, clear expectations, and accountability.

Good intentions don't automatically produce good outcomes.

But I believe genuine care changes how you approach all of those responsibilities.

It gives them a purpose beyond simply fulfilling a management obligation.

The People Stay With You

One of the things I've come to appreciate most about leadership is how the relationships continue to shape you long after the circumstances that created them have changed.

Teams evolve.

People move on.

Organizations restructure.

Responsibilities change.

The group of people you work with today may look completely different a few years from now.

That's simply part of professional life.

But I've never viewed those relationships as something that loses its meaning when the reporting structure changes.

The people I've worked with have helped shape who I am.

Their experiences have challenged my assumptions.

Their perspectives have broadened my thinking.

Their questions have pushed me to learn things I might otherwise never have explored.

Their successes have reminded me why I love leadership.

And their challenges have taught me lessons that no book or professional certification could have provided.

I've learned from people with decades of experience.

I've learned from people just beginning their careers.

I've learned from people who agreed with me and people who challenged almost everything I believed.

And I genuinely believe I'm better because of those relationships.

I hope, in some small way, they've gained something meaningful from knowing me too.

Not necessarily because I taught them something profound.

Maybe I simply helped them see a possibility they hadn't considered.

Maybe I created enough space for them to demonstrate what they were capable of.

Maybe I helped them navigate a difficult moment.

Or perhaps I was just someone who listened when they needed to be heard.

I don't need every relationship to result in some extraordinary professional accomplishment.

Sometimes the meaningful part is simply having been there for someone.

And I think that's something our obsession with measuring outcomes can occasionally cause us to overlook.

Not every meaningful contribution can be captured on a performance review, a résumé, or a quarterly business report.

Some of the most important things we do for other people may never appear on any of those documents.

But that doesn't make them any less valuable.

Maybe I Was Trying to Answer the Wrong Question

When I think back to that LinkedIn conversation, I can appreciate what the person was trying to accomplish.

They were attempting to help me communicate my value in a way that other people could understand.

That's important.

Particularly when you're trying to build a business, attract opportunities, or establish yourself in a crowded professional landscape.

People need some understanding of what you offer.

And I don't believe there's anything inherently wrong with creating a personal brand.

In fact, I recognize that not being able to articulate your value can make it difficult for the people who might benefit from your work to find you.

That's a legitimate challenge.

But I think the conversation stayed with me because it forced me to confront a distinction I hadn't fully considered.

There's a difference between what I do and why I do it.

What I do has changed throughout my career.

I've worked in different industries.

Held different titles.

Taken on different responsibilities.

Developed different capabilities.

And I expect that evolution to continue.

But why I do those things has remained remarkably consistent.

I enjoy helping people.

I love building things that create value.

I want to solve meaningful problems.

I find fulfillment in watching people grow.

And I genuinely care about the individuals whose lives intersect with mine.

Those things don't necessarily form a narrowly defined professional category.

But they explain almost every meaningful career decision I've made.

Maybe that's why I've struggled so much with the question of branding.

I've been trying to describe something that I experience less as a product and more as a purpose.

A product needs to be defined.

A service needs to be understood.

But a purpose can express itself through an extraordinary number of different activities.

I can fulfill that purpose while managing engineers.

While coaching someone through a difficult decision.

While helping an organization rethink how its teams work.

While writing an article.

While speaking to a group of people.

Or while sitting across from someone who's having a difficult day and simply needs someone to listen.

The activity changes.

The intention doesn't.

And perhaps that's the common thread I've been searching for all along.

I Don't Want to Be Everything to Everyone

There's a potential criticism of this perspective that I think is worth addressing.

If you refuse to define what you offer, how can anyone understand when they should seek you out?

That's a fair question.

And I don't think the answer is to claim that I can help everyone with everything.

I can't.

I have strengths and limitations, just like anyone else.

There are problems I'm well equipped to help solve, and others that require expertise I don't possess.

I think part of becoming more effective is being honest about that distinction.

I'm not trying to suggest that professional specialization is unnecessary or that clear communication doesn't matter.

It absolutely does.

But I also don't want to confuse the need for clarity with the need to reduce my entire identity to one marketable phrase.

I can describe the work I'm capable of doing.

I can explain where my experience is most relevant.

I can articulate the kinds of problems I enjoy solving.

And I can acknowledge when someone else is better suited to help.

What I struggle with is the idea that any one of those descriptions should become the boundary of who I am.

Because I've spent much of my life growing beyond the expectations associated with whatever title I happened to hold at the time.

Why would I want to begin defining myself by those limitations now?

Maybe the answer isn't to abandon the idea of a brand.

Maybe it's simply to stop treating the brand as though it needs to represent the entirety of the person behind it.

What I Hope People Remember

I've thought about what I want people to say about me when I'm no longer part of their team.

And interestingly, very little of it has to do with my title or technical abilities.

I don't particularly care if someone remembers the organizational structure we worked within.

I don't need them to remember every initiative we delivered.

And I certainly don't expect them to remember the language from my LinkedIn headline.

I hope they remember that I listened.

That I took their concerns seriously.

That I challenged them because I believed in what they could become.

That I advocated for them.

That I celebrated their accomplishments.

That I respected the lives they had outside of work.

And that when things became difficult, I didn't suddenly forget they were human beings.

I hope they remember that they mattered to me.

Because they did.

They still do.

And that doesn't disappear simply because we're no longer working together.

Of course, I want to be remembered as someone who helped build successful teams and deliver meaningful outcomes.

I take pride in that work.

I believe deeply in the value of creating environments where people can accomplish extraordinary things together.

But if I had to choose between being remembered as an effective manager and being remembered as someone who genuinely cared, I'd hope the people I worked with never felt they had to separate the two.

Because in my mind, they should reinforce one another.

Caring about people isn't something separate from effective leadership. It's one of the reasons I believe effective leadership becomes possible.

So, What's My Brand?

Years later, I still can't give you a perfectly polished answer.

I'm a servant leader.

I'm someone who loves building things that people use.

I'm someone who believes that high-performing teams emerge when people are given the right conditions to succeed.

I'm a coach.

A learner.

A problem-solver.

A person who becomes genuinely invested in the lives and aspirations of the people around me.

And above all else, I'm someone who cares.

Maybe that's too broad.

Maybe it isn't specific enough to fit into a carefully defined market segment.

Maybe someone with a stronger understanding of personal branding could turn all of that into a compelling statement that immediately tells the world exactly what I offer.

I don't know.

And I'm okay with that.

Because I've come to realize that my objective has never been to become a brand.

It's been to become a person who leaves things better than he found them.

Better teams.

Better systems.

Better opportunities.

And, whenever possible, people who feel more confident, capable, and supported because our paths happened to cross.

I don't expect to accomplish that perfectly.

I'm still learning.

Still growing.

Still discovering things about myself.

And hopefully, I'll continue doing those things for the rest of my life.

But there's something comforting about recognizing that I don't necessarily need to know exactly what category I belong to in order to know what matters to me.

Maybe I don't have a brand because I've spent too much time trying to be useful rather than trying to be recognizable.

Or maybe I do have one, and it's simply harder to describe than a job title.

Either way, I keep coming back to the same thought.

At the end of my career, I don't want the greatest thing anyone can say about me to be that I was an exceptional manager, a talented speaker, or a successful consultant.

I want them to say something much simpler.

He cared.

Not because he said it.

Not because it was written in his biography.

But because they experienced it.

Because they felt it in the way they were treated.

Because they saw it in the opportunities they were given.

Because they knew that their growth, their well-being, and their lives genuinely mattered to someone.

And because, perhaps in some small way, that experience influenced how they went on to treat the people around them.

If that's what people remember, I think I'll be satisfied.

I still don't know exactly what box I fit into.

But I know the kind of impact I want to leave outside of it.

And for now, that's enough.