Hey Modern Authors,

One of the most common questions I hear from aspiring authors is:

“How do I come up with a book idea?”

On the surface, it sounds like the right question.

After all, books start with ideas.

Right?

But recently, I was listening to Hamzah Shanbari talk about his journey to writing a book.

And honestly?

It reminded me of a pattern I see over and over again.

Someone spends years solving a problem.

They explain it hundreds of times.

They develop instincts around it.

They build frameworks without even realizing it.

And then one day they decide:

“Maybe I should write a book.”

But by that point?

The book is usually one of the last things that happened.

Not the first.

Hamzah's book followed that path.

His book didn't begin with an idea.

It began years earlier.

Long before there was a manuscript.

Long before there was a framework.

Long before there was even a plan to write a book.

It started with a problem.

Actually...

the same problem.

Over and over again.

As Hamzah built his career in construction and project management, he found himself encountering similar challenges repeatedly.

The projects were different.

The people were different.

The situations were different.

But certain patterns kept showing up.

And eventually, something interesting happened.

The book appeared.

Not as the beginning.

As the result.

Think about that for a second.

Most people spend years looking for a book idea.

Hamzah spent years living inside the very thing that would eventually become one.

Years of Solving the Same Problem Created Something Unexpected

When most people imagine a nonfiction book, they imagine a breakthrough idea.

A moment of inspiration.

A concept that suddenly arrives fully formed.

But that's rarely how expertise works.

And it wasn't how Hamzah's book emerged either.

Years of experience created observations.

Observations revealed patterns.

Patterns began connecting.

Over time, something became visible.

The same structures kept appearing again and again.

The same mistakes.

The same challenges.

The same solutions proving useful repeatedly.

That's when the progression starts becoming visible:

Problem
→ Experience
→ Observation
→ Pattern

The book wasn't driving the process.

The work was.

The Pattern Was More Valuable Than the Solution

This is where many aspiring authors get stuck.

They're looking for ideas.

But the strongest nonfiction books are often built on something much more durable.

Patterns.

Most people think books start like this:

Idea
→ Book

One insight.

One breakthrough.

One moment of inspiration.

But Hamzah's journey looked more like this:

Problem
→ Experience
→ Observation
→ Pattern
→ Framework
→ Book

That's a VERY different path.

Hamzah wasn't collecting interesting stories.

He was recognizing recurring structures.

The same communication breakdowns.

The same project risks.

The same leadership challenges.

The same lessons emerging from different situations.

Eventually, the pattern became more valuable than any individual solution.

Because solutions solve a single problem.

Patterns explain many problems.

That's an important distinction.

Ideas attract attention.

Patterns create frameworks.

And frameworks are often what people remember long after they've forgotten the original story.

​

The Moment Experience Became Intellectual Capital

At some point, experience stops being experience.

It becomes intellectual capital.

That's the transition many authors miss.

Because expertise alone is not intellectual capital.

Lots of people accumulate expertise.

Far fewer organize it.

What emerged from Hamzah's experience was more than a collection of solutions.

The same ideas kept appearing.

The same lessons kept resurfacing.

The same explanations kept proving useful.

Over time, those observations began taking on structure.

The knowledge stopped being personal.

It became transferable.

That's the moment something changes.

Experts encounter patterns.

Thought leaders recognize patterns.

Authors organize patterns into systems.

And once that happens, experience becomes something others can use.

Why Frameworks Matter

One of the reasons frameworks are so powerful is because they allow other people to benefit from experience they never personally lived through.

Think about what happened here.

Years of trial and error.

Years of observation.

Years of accumulated experience.

Condensed into something another person can understand much faster.

That's leverage.

A framework makes knowledge:

• Transferable
• Teachable
• Repeatable
• Memorable
• Scalable

Without a framework, expertise stays trapped inside experience.

With a framework, expertise begins traveling beyond the person who originally developed it.

That's what gives intellectual capital its value.

Or said another way:

Experience helps you solve a problem once.

A framework helps other people solve it repeatedly.

That's a very different outcome.

The Framework Was Already There

One of my favorite parts of Hamzah's story is that the framework wasn't invented.

It was recognized.

That's a very different process.

Most aspiring authors assume they need to invent a framework.

Create something new.

Come up with a breakthrough idea.

But that's usually not what happens.

Many of the strongest frameworks emerge from patterns that already exist.

The work happened first.

The observation happened second.

The naming happened later.

And once the pattern became visible, the framework almost felt obvious.

Think about that for a second.

The framework wasn't hiding in a brainstorming session.

It was hiding in years of experience.

Many authors already possess frameworks.

They simply haven't stepped back far enough to recognize them yet.

What if that's true for you too?

Most Experts Miss the Pattern They're Living

One reason many experts struggle to identify book ideas is because they are too close to their own experience.

The pattern feels obvious.

The explanation feels routine.

The lesson feels familiar.

After all, they've lived it hundreds of times.

That's exactly why it becomes difficult to see.

What feels ordinary to the expert often feels valuable to everyone else.

Hamzah didn't wake up one day and decide to invent a framework.

He spent years living inside it.

The framework was hidden inside:

Repeated problems.

Repeated observations.

Repeated explanations.

Eventually...

repeated patterns.

Eventually, the pattern became visible.

Not because it was new.

Because it had been there all along.

And that's often how intellectual capital develops.

Not through invention.

Through recognition.

Think about that for a second.

Many experts spend years searching for a book idea...

while standing directly on top of one.

That might be the most common pattern I see among aspiring authors.

The pattern feels too familiar to notice.

The language feels too obvious to document.

The insight feels too normal to matter.

But that's often the signal.

Because frameworks rarely arrive as breakthroughs.

They usually emerge as accumulated experience that finally becomes visible.

And once you see the pattern, you can't unsee it.

The Modern Author Question

This is where I think many aspiring authors ask the wrong question.

Instead of asking:

“What book should I write?”

Try asking:

“What pattern am I already living inside?”

That's a VERY different question.

Then go a little deeper:

What problem have I solved repeatedly?

What challenge keeps appearing in my work?

What mistake have I seen over and over again?

What do I explain so often that it has become second nature?

What pattern keeps showing up?

Because those questions tend to reveal something much more valuable than a book idea.

They reveal intellectual capital.

And in many cases, the book is already hiding inside the pattern.

The Real Asset Was Never the Book

Most people assume the book is the asset.

I'm not sure that's true.

The framework is the asset.

The intellectual capital is the asset.

The book is simply the vehicle.

It allows accumulated experience to travel farther than the author ever could alone.

The book was never the beginning.

It was the container.

The visible part of something that had been developing for years.

And if you look back at Hamzah's journey, the progression becomes remarkably clear:

Problem
→ Experience
→ Observation
→ Pattern
→ Framework
→ Intellectual Capital
→ Book

The book was the final expression.

Not the beginning.

The real work happened years earlier.

Inside repeated problems.

Repeated observations.

Repeated lessons.

That's why the strongest nonfiction books rarely begin with isolated ideas.

They emerge when repeated problem-solving reveals patterns.

Patterns become frameworks.

Frameworks become intellectual capital.

And eventually, that intellectual capital becomes a book worth sharing.

Happy Writing My Friends,

Eric

​
​
​