I Don’t Have a Content Strategy. I Have a Habit of Noticing Things.

Apparently, my biggest content challenge is not finding things to say.

It’s trying to keep up with all the ideas that show up along the way.

I’ve never had a giant content machine.

No perfectly planned calendar.

No elaborate content-batching system.

No Sunday night routine where I sit down and create ten posts for the week.

Honestly, that sounds exhausting.

My approach is much simpler.

I live.

I talk to people.

I pay attention.

And then something happens.

A founder says something that makes me stop.

A conversation sticks with me.

I notice a pattern.

Or I experience something myself and think:

Wait... other people probably feel this too.

And there it is.

An idea.

Sometimes it becomes a LinkedIn post.

Sometimes it becomes a conversation with a client.

Sometimes it sits in the back of my mind for three days before I finally figure out why it bothered me.

And sometimes I wake up thinking about something that happened the previous week and realize I apparently wasn't finished thinking about it yet.

That happens a lot.

I think noticing and reflecting is a skill.

We spend a lot of time talking about listening.

Good leaders listen.

Good advisors listen.

Good managers listen.

And obviously, I agree.

But I think there is another layer to it.

You have to notice.

Not just what someone is saying.

What they're not saying.

The hesitation before an answer.

The thing they keep coming back to.

The issue they mention casually three times in one conversation.

The disconnect between what someone says is happening and what seems to actually be happening.

The energy in the room when a particular topic comes up.

The thing that seems small but keeps showing up.

Those details matter.

And you don't always notice them when you're rushing to solve the problem.

Sometimes you notice them because you have enough space to actually pay attention.

This is also how I work with clients

This is where I realized my approach to content is actually very similar to my approach to my work.

I don't want to walk into a business with a predetermined answer.

I want to understand the business first.

I want to talk to the founder.

I want to understand what the leadership team is experiencing.

I want to hear from employees.

I want to understand how work actually happens.

And then I want to look for the patterns.

Because what is documented in an organization and what is actually happening are often two very different things.

You can have a beautiful policy sitting in a handbook while everyone has developed an entirely different way of doing things.

You can have an organizational chart that looks perfectly logical while everyone knows the real decision-maker is someone completely different.

You can have a founder who says they want their team to take more ownership while still being the person everyone has to go to for every decision.

None of those things necessarily show up in a spreadsheet.

You notice them through conversations.

Through observation.

Through asking another question when the obvious answer doesn't quite make sense.

The temptation to systematize everything

There is a lot of pressure to systematize everything.

And I understand why.

Systems create consistency.

They make things repeatable.

They allow businesses to grow.

But I think there is a difference between creating useful systems and trying to systematize the human parts of our work.

You can absolutely create a system for what happens after you notice something.

You can capture ideas.

Document patterns.

Create processes.

Build accountability.

But I don't think you can manufacture the noticing itself.

And I don't think you should try.

Because the specificity is often where the value lives.

The founder who says something almost in passing.

The employee who finally tells you what has actually been bothering them.

The small interaction that makes you realize there is a much bigger issue underneath it.

Those moments aren't always predictable.

You have to be present enough to catch them.

Maybe that's the real work

I think a lot of my work comes down to curiosity.

Not assuming I already know.

Not rushing to the solution.

Being willing to sit in the conversation a little longer.

Asking:

What's really going on here?

What am I missing?

Why does this keep coming up?

What is happening beneath the surface?

And sometimes the most useful thing I can do for a founder isn't give them an answer.

It's help them see something they couldn't see when they were standing in the middle of it.

That's why I don't worry too much about having a content machine.

The ideas will come.

There are always conversations.

Always patterns.

Always things worth thinking about.

My job is to notice them.

And maybe that's a pretty good approach to business, too.

Pay attention.

Stay curious.

Notice what keeps showing up.

Because sometimes the thing you're looking for isn't something you need to go find.

It's something that's already happening right in front of you.