You promoted your best software engineer. Now execution is slowing - and it doesn't make sense.

Meetings are quieter. Decisions bottleneck. Strong engineers hesitate instead of leading.

This is one of the most expensive failure modes in engineering orgs - not because people are incapable, but because technical excellence doesn't train human systems.

The cost: Decision velocity drops. Retention risk rises. Your leadership pipeline stalls.

I've seen this pattern from every angle - as an engineer, a leader, and an exec scaling teams under pressure for 25 years.

What makes my approach different is my background in anthropology and psychology. I don't just see the technical systems. I see the human ones - and I know how to bridge them.

One recent example: I helped a board that was ready to fire their entire engineering team. Same people. Redesigned system. They went from annual releases to shipping every two weeks - and had zero turnover in the following year.

The team wasn't the problem. The system was.

I help CTOs, VPs of Engineering, and CEOs turn strong engineers into trusted leaders - before you lose momentum, morale, or talent.

What changes:

↳ Meetings become productive, not painful 
↳ Delegation actually happens 
↳ Decision velocity increases 
↳ Retention risk drops 
↳ Leadership pipeline stabilizes

This isn't generic leadership training. It's systems-level coaching for engineers - grounded in how teams actually work and how leadership signals shape outcomes.

If you're watching this pattern emerge, let's talk.

👉 coded2lead.com

Robert Harris

The board’s first question caught everyone off guard:
"How many developers do we need to fire?"

Deadlines were slipping by months.
Bugs were outpacing features.
Product and Engineering were barely speaking.

From their perspective, it looked obvious:
People problem.

After 25 years inside engineering orgs, I’ve learned to pause when the entire system looks stuck.

Because most of the time...

It’s not the talent.

It’s the environment they’re operating in.

Six months later, that same "underperforming" team was shipping every two weeks.

No one fired.
No one quit.

The people didn’t change.

The system did.

Robert N. Harris

I turn your promoted engineers into force‑multiplying leaders | Founder, coded2lead | Book intro: coded2lead.com

"Robert jumps on a lot of grenades for us."
A developer told me that years ago.
It wasn’t a compliment.

But it opened my eyes -
and I started seeing this pattern everywhere.

Many engineering leaders accidentally train three specific dysfunction patterns - not through neglect, but through good intentions.

I broke down all three in this week’s Human Systems for Engineering Leaders.

The 3 Paradoxes of Helping No engineering leader sets out to harm their team. But intention and impact don't always travel together. And in my experie

Open article: The 3 Paradoxes of Helping by Robert N. Harris • 4 min read

"I'm going for a mental health maintenance walk."

I've said that to my team countless times -
because leaders normalize whatever they model repeatedly.

Last Monday everything broke at once, and I needed to take my own medicine.

Claude stopped Clauding.  
My computer stopped computing.  
My icemaker stopped making ice.  

It reminded me that entropy isn't just a good idea - IT'S THE LAW.

The old version of me would have powered through.
But powering through is how you train heroics.
And heroics are how you accidentally build burnout culture.

So I went for a walk.

Because the system is always learning -
even if you think nobody is watching.

If I don't step away when I'm overloaded,  
I teach them not to.

Culture isn't what you say it is.  
It's what you model under pressure.

Your software engineering team looks strong on paper.
But execution is slipping.

The team is talented.  
The roadmap is clear.  
The tooling is modern.

And yet...

• decisions keep stalling  
• the same bugs keep resurfacing  
• meetings get strangely quiet when it matters most

That pattern is a clue.

Leaders often jump to:  
"We hired wrong."

But when I see this pattern across an entire team, 
I start looking somewhere else.

Persistent hesitation in smart teams is rarely random.

It’s usually a human system signal.

I help CTOs & VPs turn promoted engineers into trusted leaders before execution stalls | Founder, coded2lead | Book intro: coded2lead.com

Your engineering team knows you're responsive.
You're helpful. You care.
And somehow... that's the problem.

Because your software team keeps coming back to you.

Every decision. Every blocker. Every judgment call.

Here's what that pattern is actually telling you:

- They've learned decisions belong to you
- They've learned "check with me first" is the real rule
- They've learned their judgment isn't trusted - even if you've never said that

You didn't create this on purpose.

You created it by being the most capable person in the room - consistently, visibly.

And now you're the constraining resource.

Because of that, your reach never exceeds your grasp.

Your team’s ceiling becomes your capacity.

And no amount of hiring fixes it - because every new engineer just gets absorbed into the same pattern.

The fix isn't delegation.

It's a different kind of trust.

One that looks less like "let me know if you need help"... and more like "you decide - I'll back you either way."

The most expensive question I ever asked my engineering team was:
"Any blockers?"


"Nope."  
"Good here."  
"All good."

Twelve seconds.  
Clean standup.  
Everyone aligned.

Or so I thought.

What I eventually realized was that I had built a perfectly calibrated silence machine.

The team wasn't agreeing with me.

They were doing the math.

Raising a blocker meant owning the problem in front of everyone.  
Admitting uncertainty meant looking like you didn’t have the answer.  
Questioning the plan meant becoming the person who slows things down.

So the calculation quietly ran in the background:

Is this worth it?

And most of the time the answer was no.

Silence in engineering meetings often isn’t alignment.

It’s risk management.

Once I started hearing silence that way, it changed the question I asked in the room.

Instead of  
"Does everyone agree?"

I started asking:

"What might we be missing here?"

You’d be amazed how often that changed the signal.

Have you ever discovered that a quiet meeting wasn't actually agreement?

If your software engineering org suddenly feels harder to move...
this pattern shows up a lot.

Leaders keep applying technical fixes...
to what are fundamentally human system problems.

And the system responds exactly as designed.

So they add process.  
They add tooling.  
They add more visibility layers.

And still:

• decisions bottleneck  
• teams hesitate  
• the same delivery patterns repeat

Underneath every tech stack is a human operating system.

And that layer quietly shapes everything that runs on top.

When a strong engineering team suddenly starts playing it safe,  
most leaders misread the signal.

When the whole team shifts behavior at once,  
assume adaptation before incompetence.

Human systems respond quickly to their environment.

Watch what the system is actually reinforcing.

If the system quietly rewards:

• keeping your head down  
• shipping fast over shipping right  
• protecting yourself over owning outcomes

the culture will converge in that direction.

The behaviors that frustrate leaders most often aren’t personality flaws.

They’re survival strategies that made sense in context.

I found burnout culture asleep on my office couch one Monday morning.

Our lead engineer had been there all weekend.

Finishing a feature I needed shipped.

I thought I knew what burnout culture looked like.
I thought I'd recognize it if I was creating one.
But there it was - impossible to ignore. 
And snoring. 

I didn't ask him to sleep at the office.
But I had built a system where it felt necessary.

That's what hit me standing in the doorway.
It wasn't his dedication that put him there.
It was mine.

My pace. 
My urgency. 
My silence about what was actually sustainable.

I had never said "work weekends."
But the system I built said it clearly.
And he heard it.

I wasn't a bad leader. 
I cared deeply about that team.

But caring isn't a culture.
It's just an intention.

Culture is what happens when no one is watching.
And when no one was watching - my team was sleeping in my office.

That was the hidden curriculum I'd been teaching.

Not the values on the team wiki. 
Not what I said in one-on-ones.

What the system had learned from watching me.

That's what nobody tells you when you hand someone a team.

The culture you build isn't the one you intend.

It's the one your behavior teaches.

Your best engineer is stuck again.
And they're waiting for you.


You have the answer in your head.

So you give it to them.

Problem solved. Back to work.

Except... you just taught them something you didn't mean to teach.

Not the solution - the lesson underneath it:

When you're stuck, wait for your leader.

That's the hidden curriculum you've been teaching your software team.

Not what you said. 
What the system learned from watching you say it.

You didn't build a team in that moment. 
You built a helper.

And every time you do it - with the best intentions - the system gets better at producing people who wait.

The question worth sitting with:

When someone on your team comes to you stuck... 
do you give them the answer?

Or do you give them the context to find it themselves?

🔁 Career Transition

For the past several years, I’ve been running my own gardening business managing operations, optimising routes, tracking costs, and making day-to-day decisions that directly affected profitability. What started as simple tracking in spreadsheets slowly turned into a genuine interest in understanding patterns, performance, and how better data leads to better decisions.

That curiosity is what pushed me into data analytics.

I’m now transitioning into a Data Analyst role, building hands-on experience in SQL and PostgreSQL to explore datasets, uncover trends, and turn raw numbers into clear, actionable insights. I recently completed the DataCamp Associate Data Analyst certification and continue developing practical projects using real-world data.

At the moment, I’m analysing LinkedIn engagement data to understand which content performs best, how posting behaviour impacts follower growth, and how reach translates into meaningful interaction.

What I bring to data:

- A business-owner mindset focused on outcomes, not just dashboards

- Real-world decision-making experience under pressure

- Clear communication of insights in a way people actually understand

I’m especially interested in roles where I can combine analytical thinking with commercial awareness, keep learning from experienced analysts and probably drink far too much tea while debugging SQL.

Alex Hedges

3,722 people applied.

This is the current state of the job market 

That number explains why job searching feels brutal right now.

This role went live about a week ago.
Hundreds of applications every day.

Most of those people aren’t underqualified.
They’re capable and serious about getting hired.

So when you don’t hear back,
it’s not always because you missed something.

It’s because you’re applying into volume.

People are still landing roles.
But they’re doing it in a market where patience matters more than speed.

Tech stack alone is not enough anymore. 

You have to avoid generic CVs 
You have to build and share in public 
You have to reach out to hiring managers 
You have to apply on company websites 

Don’t just hit ‘Easy Apply’ and hope for the best 

If you’re applying right now,
don’t mistake silence for failure.

This is what a crowded market looks like.

Your moment will come 
I’m fighting this job market right along side you

Just keep showing up! 

#DataAnalytics #JobSearch #CareerChange #LearningInPublic #TechCareers

Data Analyst | SQL • Data Analysis | Career Transition

“Why are you analysing data if you’re not a data analyst yet?”

Something I’ve been asked a few times.

And I get the question.

Because from the outside, it looks backwards.
No title.
No role.
Just datasets and SQL queries.

But that is the point.

You don’t wake up as a data analyst
and then start analysing data.

You analyse data long before it feels legitimate.

Every time I write a query and it breaks, I learn something.
Every time a join doesn’t behave how I expected, I slow down and understand why.
Every messy dataset forces better questions.

That confusion at 10pm?
That’s not failure.
That’s the job.

You don’t need a title to practice the work.

You need repetition.
Curiosity.
And the willingness to feel uncomfortable for longer than most people.

So if you’re analysing datasets, practising SQL, questioning your results keep going.

You’re not pretending.

You’re already doing the work.

#DataAnalytics #LearningInPublic #SelfTaught #SQL #CareerChange

No alternative text description for this image

From Garden Beds → Data Sets (Week 20) 🌱➡️📊

This week felt a bit smoother.

I’ve had more success with SQL on DataLemur, getting through a few queries without running into issues straight away which, a few weeks ago, definitely wasn’t the case.

One pattern I’m starting to notice is how often I overcomplicate queries that don’t need it.

I’ll jump ahead mentally, add logic too early, and create problems that weren’t there to begin with.

What’s helped is slowing everything down and breaking the query into steps…

- understand the question properly
- get the raw aggregation working
- sanity-check the output
- only then worry about formatting or optimisation

It sounds obvious, but doing this consistently has made a real difference.

Alongside SQL, I’ve been chipping away at my Power BI course.
I’ve just finished a short section on DAX interesting, slightly overwhelming, and definitely something I’ll need to revisit with real use cases.

The focus has now moved away from formulas and toward something just as important.. who the report is actually for.

How different audiences interpret the same chart.

How too much information creates friction instead of insight.

How clarity often matters more than complexity.

None of this feels flashy, but it feels foundational.

Current application numbers:
- 12 applications submitted
- 6 on LinkedIn
- 6 outside LinkedIn
- 6 rejections so far

We keep showing up and building foundations. 

#LearningInPublic #DataAnalytics #SQL #PowerBI #CareerChange

taplio

The Battle

Robert Harris

Alex Hedges

Followers

Posts

Engagements

Likes

Performance ScoreRobert Harris's LinkedIn Performance

Performance ScoreAlex Hedges's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Robert Harris

Alex Hedges

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Robert Harris's LinkedIn Performance

Performance ScoreAlex Hedges's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreRobert Harris's LinkedIn Performance