From Pepperdine to Intent: Why I’ve Always Believed in Strong Teams

From Pepperdine to Intent: Why I’ve Always Believed in Strong Teams

Introduction

This didn’t start with AI.

It didn’t start with architecture frameworks.

And it definitely didn’t start with a blog.

It started with a simple realization I had years ago:

I just loved being on strong teams.

Not perfect teams. Not corporate-polished teams.

Just teams where people thought for themselves, pushed each other, and moved toward something that mattered.

That idea has stayed with me ever since.

What Is Learn → Teach → Master?

At its core, Learn → Teach → Master is a way of thinking about growth:

• Learn: Understand something deeply enough to apply it

• Teach: Share it clearly enough that others can use it

• Master: Refine it through repetition, feedback, and real-world pressure

It’s not academic.

It’s not theoretical.

It’s how real teams get better—together.

Where It All Started

Back at Pepperdine University, I studied business—everything from statistics and economics to management theory and systems thinking.

We talked about:

• probability

• ergonomics

• adaptive systems

• early versions of lean thinking

• what would later become things like Kanban and just-in-time delivery

At the time, it felt like a lot of disconnected ideas.

But looking back now, there was a pattern:

All of it was trying to answer one question—

How do people work better together?

And even then, I wasn’t drawn to the theory as much as the experience.

I noticed something simple:

• Some teams struggled constantly

• Others just… worked

The difference wasn’t intelligence.

It wasn’t even experience.

It was alignment.

The Team Realization

Over the years, working across projects and organizations, that belief only got stronger.

The best teams I’ve ever been on had a few things in common:

• They didn’t wait to be told what to do

• They understood the goal—not just the task

• They challenged each other without ego

• They moved forward with clarity

It felt less like management…

and more like momentum.

Kind of like a championship team.

Not because they were perfect, but because:

Everyone knew what they were trying to do—and believed in it.

Enter Intent-Driven Thinking

Years later, when I started working more deeply in engineering environments, I saw a gap.

Talented people.

Hardworking teams.

But something was off.

There was effort… without alignment.

That’s when intent-driven thinking clicked for me.

Not as a buzzword—but as something I had been seeing my whole life.

What if teams didn’t just receive requirements…

What if they clearly defined what they intended to build—and why?

Because when a team shares intent:

• decisions get faster

• quality improves

• learning accelerates

And suddenly, the team starts behaving like…

a team.

Why It Matters

Most organizations focus on:

• tools

• processes

• delivery speed

But the real differentiator isn’t any of those.

It’s this:

Do your teams actually understand—and own—what they’re building?

Because when they do:

• onboarding becomes learning, not confusion

• collaboration becomes natural, not forced

• delivery becomes consistent, not chaotic

That’s where Learn → Teach → Master comes alive.

Not as a framework on paper…

but as a way teams operate every day.

The Personal Side

If I’m being honest, this has never just been about systems.

It’s been about something simpler.

I’ve always wanted to be part of teams that:

• think independently

• grow together

• and go after something with clarity and purpose

That hasn’t always been easy.

There were long nights.

Moments of frustration.

Times where I had to step in and help people get up to speed when they weren’t ready.

But those experiences didn’t break the idea.

They reinforced it.

They showed me that if strong teams don’t exist…

You build them.

Key Takeaways

• Great teams aren’t accidental—they’re aligned

• Learning, teaching, and mastering are team activities, not individual ones

• Intent is the missing link between effort and outcome

• Strong teams behave more like championship teams than managed groups

• If the system doesn’t produce strong teams… build a better system

Final Thought

At the end of the day, this isn’t about methodology.

It’s about belief.

If a group of people clearly understands what they’re trying to do…

and commits to getting better together…

They can build almost anything.

And that’s something I’ve believed since Pepperdine.

Now, we just have better ways to make it real.