The Signal Archive

First Message

What actually decides if a technology gets used

Hi,

Most people evaluate technology the same way.

They look at what it does.

How fast it is.
How efficient.
How much better it seems than what came before.

And from there, they assume:

If it’s better, it will be adopted.

But if you’ve worked inside a specific industry,
you’ve already seen the flaw in that.

Technologies that clearly “work”
don’t always get used.

Or they get adopted slowly.
Or unevenly.
Or by players no one expected.

That’s because technology doesn’t enter a vacuum.

It enters a niche—

an environment that already has:

• power structures
• decision-makers
• constraints
• and people protecting their position

And inside that environment,
“better” is not the deciding factor.

Fit is.

I saw this early on working as an estimator.

New machinery was coming into the woodworking space.

More precise.
More capable.
Clearly an improvement.

But that wasn’t the real question.

The real question was:

Which shops could actually use it—and what would that do to competition?

Some shops would gain a major edge.

Others wouldn’t be able to integrate it at all.

Same machine.

Different outcomes.

That pattern repeats everywhere.

A technology only takes hold
if it aligns with the structure of the niche it enters—

or if it’s strong enough to reorganize that structure.

Most analysis misses this
because it focuses on the tool.

But the real story is:

what the tool does to the environment it enters.

In the next email, I’ll show you something you’ve likely experienced—

but probably haven’t had a clean way to explain:

why good ideas—sometimes obviously good ones—
get rejected inside otherwise capable organizations.

Todd

Second Message

Why obvious improvements get rejected

Hi, 

You’ve probably seen this happen.

A good idea shows up inside an organization.

Not speculative.
Not half-formed.

Something that clearly improves how things could be done.

It gets discussed.

People acknowledge it makes sense.

There’s even a moment where it feels like:

“This is going to move forward.”

And then it doesn’t.

It slows down.

It gets redirected.

Concerns start to appear—

not about whether it works,
but about timing… integration… risk… alignment…

Eventually, it fades out.

Or gets quietly shelved.

What’s frustrating about this isn’t just that the idea was good.

It’s that the organization wasn’t incompetent.

The people involved were capable.

In many cases, they agreed with the idea.

So what actually happened?

Most people explain this as:

• bureaucracy
• risk aversion
• internal politics

And those are real.

But they’re not the root cause.

The deeper reason is structural.

Every organization operates inside a niche—
an environment with an existing:

• power structure
• workflow logic
• set of incentives
• and internal balance

A new idea doesn’t just introduce improvement.

It introduces change to that structure.

And that’s where the resistance actually comes from.

Because even a good idea can:

• weaken someone’s role
• shift decision authority
• disrupt a stable process
• or advantage one group over another

And most of that is not openly stated.

It shows up as:

• “we need to evaluate this further”
• “this might not fit our current process”
• “the timing isn’t right”

But underneath those statements is a simpler dynamic:

The idea does not fit the current structure of the niche.

Or it fits—but not for the people currently in control.

This is why good ideas don’t fail randomly.

They fail predictably—

based on how they interact with the environment they enter.

Once you see this, something shifts.

You stop asking:

“Is this a good idea?”

And start asking:

• Who inside this organization does this help?
• Who does it create pressure on?
• What existing structure does it interfere with?
• Does it align with how decisions are actually made here?

That changes how you evaluate everything.

And it also explains something else you’ve probably seen:

Why the same idea can fail in one organization—
and succeed in another.

Same idea.

Different structure.

Different outcome.

In the next email, I’ll show you how to use this directly—

not just to understand what’s happening,
but to make better decisions about where to place your time, attention, and risk.

Todd

Third Message 

Use this before you trust any new technology

Hi, 

If you take one thing from the last two emails, it’s this:

A new idea or technology doesn’t succeed because it’s better.

It succeeds because it fits—or reshapes—the environment it enters.

That’s useful conceptually.

But it becomes powerful when you use it directly.

Here’s a simple way to do that.

The next time you see a new technology, don’t start with what it does.

Start with this:

1. Who inside the niche does this strengthen?

Not in theory—in practice.

• Does it make a specific role more valuable?
• Does it give someone leverage they didn’t have before?

If no one clearly benefits, adoption will stall.

2. Who does it create pressure on?

Every meaningful change has a cost.

• Does it reduce someone’s importance?
• Does it challenge an existing workflow or authority?

That pressure doesn’t disappear.

It slows things down—often quietly.

3. Who cannot realistically use it?

This is where most people get it wrong.

They assume:

“If it works, everyone will adopt it.”

But in reality:

• some firms lack the infrastructure
• some teams lack the skill
• some environments can’t absorb the change

Those gaps shape adoption more than the technology itself.

4. Does it align with how decisions are actually made?

Not how they’re supposed to be made.

How they are made.

• centralized vs distributed
• fast vs cautious
• politically sensitive vs purely operational

If the technology doesn’t align with that, it won’t move—regardless of merit.

Put those four together, and something happens:

You stop reacting to the story around a technology—

and start seeing the structure of its adoption path.

This is why two people can look at the same development
and come to completely different conclusions.

One sees capability.

The other sees:

• where it will take hold
• where it will stall
• and where advantage is quietly forming

That difference compounds.

Because over time, you’re not just evaluating technology.

You’re positioning yourself relative to it.

And that’s where most of the real advantage sits.

In the next email, I’ll show you something that’s starting to happen right now—

not obvious yet, but already forming underneath the surface—

and how this same lens reveals it earlier than most people will see it.

Todd

Fourth Message

Most people won’t see this early

Hi,

Something is starting to happen across multiple industries.

It doesn’t look dramatic yet.

In most cases, it shows up as:

• small pilot programs
• uneven adoption
• tools that seem useful, but not essential

Easy to dismiss.

Or to overestimate.

But if you look at it through the lens we’ve been building,
a clearer pattern starts to form.

Take what’s happening with AI inside organizations.

At the surface level, the conversation is still about capability:

• how good the models are
• what they can automate
• how fast they’re improving

That’s where most people stop.

But underneath that, something more specific is happening.

AI is not being adopted evenly.

It’s being absorbed selectively—

by roles, teams, and individuals who can actually integrate it into their existing workflow.

If you run it through the four questions:

Who does this strengthen?

People who already:

• control workflows
• manage outputs
• or sit close to decision-making

They can use AI to extend what they already do.

Who does it create pressure on?

Roles built around:

• repetitive processing
• intermediate coordination
• or information handoffs

Not eliminated immediately—

but quietly compressed.

Who cannot realistically use it?

Not because it’s unavailable—

but because:

• their environment isn’t structured for it
• their workflow doesn’t support it
• or their incentives don’t reward its use

Does it align with how decisions are made?

In some organizations, yes.

In others, no.

Which is why adoption looks fast in one place—
and stalled in another.

Same technology.

Different outcomes.

That pattern is still early.

Which is why it doesn’t look like a clear shift yet.

But it’s already reorganizing:

• where leverage is building
• how work is distributed
• and who is gaining quiet advantage

Most people will recognize this later—

when it becomes visible in results.

But by then, the structure will already be set.

This is the difference this lens creates.

You’re not just seeing what a technology can do.

You’re seeing:

where it will actually take hold—and what that will change.

That doesn’t make you certain.

But it puts you earlier.

And over time, earlier compounds.

That’s what I’m building here.

A way to track these shifts as they form—

before they fully surface.

I’ll keep sending these.

Todd

The Signal Archive

The system remembers—even when reality changes

Hi, 

There’s a pattern I want to show you.

Once you see it, you’ll start noticing it everywhere.

Walk into a modern AI data center and something subtle shows up.

The machines doing the work run on direct current.

But the system feeding them doesn’t.

Power comes in as alternating current. It gets converted, stepped down, converted again—moving through multiple stages before it finally reaches the chips.

That setup made sense when it was built.

But at today’s scale, those extra steps start to matter.

More conversions → more heat
More heat → more cooling
More cooling → more cost

So naturally, people start asking:

Why not simplify it?

And yet—nothing changes quickly.

Here’s why.

Every system carries a kind of internal memory.

Not written down in one place—but embedded in how things get done.

How decisions are made.
How risks are evaluated.
How timelines are assumed.

I call this social memory.

It’s what allows large systems to function reliably over time.

But it comes with a tradeoff:

It’s built on the past.

When conditions change quickly, the system doesn’t reset.

It continues forward using what it already knows.

Step by step.

Incrementally.

Even if a cleaner solution exists.

That’s why you start to see things like this:

• Strong demand, but slow delivery
• Clear need, but long timelines
• Workarounds appearing before core systems adjust

Here’s the practical takeaway:

When something doesn’t line up—don’t just look for a technical explanation.

Ask:

Is the system still operating on assumptions that no longer fully apply?

That question alone can change how you interpret what you’re seeing.

It helps you separate:

• real physical limits
  from
• delays caused by how the system is organized

Most people focus on the technology.

But often, the real friction is in how the system understands itself.

If you start looking for that, you’ll see patterns earlier—and more clearly.

If you want the full breakdown of how this plays out in AI, energy, and infrastructure:

CLICK HERE

— Todd