March is Colon Cancer Awareness Month.

You will see the blue ribbon.You will see reminders to get screened at 45.You will see statistics shared across social media.

You should.

The numbers matter.

But this month is not abstract to me.

I had colon cancer.And I had it before 45.

The Numbers Are Not Small

Colorectal cancer is the third most commonly diagnosed cancer in the United States.

It is the second leading cause of cancer-related death when men and women are combined.

More than 150,000 Americans will be diagnosed this year.

Over 50,000 people will die from it.

Rates in adults under 50 have been rising for years. That shift is significant enough that screening guidelines were lowered from age 50 to 45 for average-risk adults.

That change happened because the data demanded it.

I was not 45.

The Part That Took Three Years

I had symptoms for over three years before a doctor recommended a colonoscopy.

Three years.

When you are under 45, colon cancer is not high on the list of assumptions. It gets categorized as something else. Stress. Diet. Hemorrhoids. Something minor.

And most of the time, it is something minor.

But sometimes it is not.

Colon cancer often develops from polyps that grow slowly and quietly. Early stages may not cause dramatic symptoms.

When symptoms do appear, they can look ordinary:

• Changes in bowel habits
• Blood in the stool
• Persistent abdominal discomfort
• Fatigue
• Unintended weight loss

All things that can be rationalized.

The phrase “you are too young” creates a delay.

Delay changes outcomes.

I was fortunate that mine was eventually caught.

Not everyone gets that timing.

This Is Not Rare. It Is Visible.

Colorectal cancer has affected many people we recognize.

• Chadwick Boseman died at 43 after a private battle with colon cancer.
• James Van Der Beek died at 48 from colorectal cancer.
• Kirstie Alley died from colorectal cancer at 71.
• Jamie Samuelsen, a longtime Detroit sports radio host, died at 48 after publicly encouraging listeners to get screened.

Different ages. Different careers. Different visibility.

Same disease.

Famous or not, local or national, the biology does not change.

Why Screening Matters

Colon cancer is one of the most preventable cancers.

Most colorectal cancers begin as polyps. During a colonoscopy, those polyps can be identified and removed before they become cancerous.

That is prevention in action.

When colon cancer is caught early and confined to the colon, the five-year survival rate is around 90 percent.

When it spreads to distant organs, survival rates drop dramatically.

Early detection does not just improve outcomes. It transforms them.

Screening is not about fear.

It is about probability.

What Statistics Do Not Show

Statistics measure incidence, mortality, and trends.

They do not measure the uncertainty of living with unexplained symptoms.

They do not measure the moment a routine appointment becomes something else.

They do not measure the conversations with your family.

They do not measure how long you replay prior years in your head.

Numbers are clean.

Cancer is not.

I am here because mine was detected and treated.

That fact does not show up in a graph.

But it is the difference between survival and something else.

Why I Am Saying This During March

Awareness months can fade into background noise.

A ribbon.A post.A reminder that gets scrolled past.

Colon Cancer Awareness Month exists because this disease is common, because it is serious, and because in many cases it is preventable or highly treatable when caught early.

If you are 45 or older and have not scheduled a screening, do it.

If you are younger and experiencing symptoms, advocate for yourself.

If something persists, ask harder questions.

Three years is a long time to normalize something that is not normal.

If you are going through this or are worried about something and do not know who to talk to, you are welcome to reach out.

I am not a doctor. I will not give medical advice.

But I understand what it feels like to sit with uncertainty, and I am willing to listen.

Before March Ends

Do one practical thing.

Schedule an appointment.Ask a question.Encourage someone close to you to stop postponing theirs.

Colon cancer is not rare.

It is increasing in younger adults.

And when caught early, it is often highly treatable and sometimes preventable.

This month is not just about awareness for me.

It is a reminder that the numbers are real.

I was one of them.

And I am still here.

Sources

• American Cancer Society – Cancer Facts and Figures 2024
• U.S. Preventive Services Task Force – Colorectal Cancer Screening Recommendation
• National Cancer Institute – SEER Cancer Statistics Review
• Centers for Disease Control and Prevention – Colorectal Cancer Statistics
• Associated Press reporting on colorectal cancer cases involving Chadwick Boseman and James Van Der Beek

Leadership isn’t heavy because of authority.
It’s heavy because of responsibility.

This episode explores the quieter side of leadership that rarely gets talked about, the invisible pressure, constant context switching, and unclear systems that slowly wear leaders down over time.

This isn’t leadership theory.
It’s about what actually breaks teams when intentions are good, but systems aren’t.

🎧 Listen to the full episode.

In this episode, I talk about:

• Why leadership pressure feels overwhelming, not like failure
• The hidden cost of constant context switching
• How unclear systems quietly drain leverage from tech leads
• The difference between control and real leadership impact
• Why good intentions aren’t enough to sustain healthy teams

Who This Episode Is For

This episode is for:

• Tech leads who feel constantly pulled into everything
• Engineering managers who carry more responsibility than authority
• Developers transitioning into leadership without real guidance
• Anyone who feels busy all day but is still behind

If you’re looking for quick hacks or motivational slogans, this probably isn’t for you.

Mentioned in This Episode

Tech Lead Operating System

The Tech Lead Operating System referenced in this episode is a practical framework for reducing friction, reclaiming focus, and building real leverage in your role.

It’s designed to help tech leads move from reactive work to intentional leadership, without burning out or micromanaging.

👉 Tech Lead Operating System

Closing Section

Most leadership stress isn’t caused by effort or capability.
It comes from systems that were never designed to support the role.

This episode is about noticing that weight and understanding where it actually comes from.

Everyone is making New Year’s resolutions.

Communicate better.
Move faster.
Care more.

None of that fixes a system designed to reward burnout and call it commitment.

Your company does not need a fresh start.
It needs a refusal to keep pretending broken is normal.

This is not a resolution.

It is a reckoning.

Stop Optimizing Broken Systems

If your process requires heroics to succeed, the process is the problem.

Yet every year leaders announce “improvements” that do nothing but rearrange the same broken steps. New templates. New ceremonies. New acronyms that promise clarity and deliver fatigue.

Optimization is only useful when the foundation is sound.

If your teams need constant escalation, late nights, and emotional gymnastics to ship, you are not leading improvement. You are managing damage.

Before you improve anything, ask one uncomfortable question.

Would this system still work if everyone only worked normal hours?

If the answer is no, the system is lying to you.

Fire Your Worst Process

You already know which one it is.

The approval chain that exists only to protect egos.
The status report nobody reads but everyone is afraid to stop sending.
The spreadsheet that gets copied, not trusted.

Kill it.

Do not replace it yet.
Let the absence expose what was never adding value in the first place.

Progress often begins with deletion.

Culture Is What Happens When Things Go Wrong

Pizza is not culture.
Slack emojis are not trust.

Culture is how leadership behaves when production breaks, when a deadline slips, when a developer makes a mistake in front of a room full of executives.

If fear drives behavior, you do not have a culture problem.
You have a leadership problem.

No resolution fixes that. Only courage does.

Burn the Word “Urgent” to the Ground

Urgency is the laziest form of management.

It replaces prioritization.
It hides poor planning.
It turns smart people into reactive messes.

When everything is urgent, nobody learns. Nobody improves. Everyone just survives.

Reckoning means deciding what truly matters and letting everything else wait.

The Reckoning Is Quiet

There will be no launch party.
No slogans.
No transformation roadmap.

It will look like canceled meetings, deleted processes, and leaders saying no more than yes.

That is not rebellion.

That is responsibility.

New year.
New rules.
Burn the rest.

Let’s get this out of the way.

If you believe respect is earned, you are already starting from the wrong place.

And if you’re a leader who demands respect, you’re not leading.
You’re posturing.

The Lie Bad Leaders Love

“Respect is earned” sounds tough.
It sounds disciplined.
It sounds like something strong leaders say.

It’s also a convenient excuse to treat people like garbage.

Because what that phrase usually means is:

• I don’t trust you
• I don’t owe you basic decency
• My title puts me above you

That’s not leadership.

That’s insecurity with authority.

Everyone Starts With Respect

Yes. Everyone.

Day one.
Before the first commit.
Before the first mistake.
Before they “prove themselves.”

People walk in assuming you’ll be fair, reasonable, and not an asshole.

That respect is loaned to you.

And many leaders light it on fire.

How You Burn Respect Fast

You don’t lose respect in one big moment.
You lose it in dozens of tiny ones.

• Talking over people
• Dismissing questions
• Making decisions in private and announcing them as facts
• Flexing your title instead of your judgment

Every one of those moments tells your team the same thing:

“I don’t actually respect you.”

And once people hear that message enough times, they stop giving you anything extra.

They give you compliance.
They give you silence.
They give you the bare minimum.

Fear Is Not Respect

It’s just quieter.

Let’s be brutally honest.

When people stop pushing back, stop disagreeing, and stop offering ideas…

That’s not alignment.

That’s fear.

Fear lasts until someone finds another job.
Respect lasts even when they don’t have to stay.

If your team is quiet, don’t congratulate yourself.
Ask why.

Here’s the Part Leaders Hate

If you need to announce that you deserve respect, you don’t have it.

If you lead through fear, people aren’t following you.

They’re waiting you out.

And the second they can leave, they will.

What Real Respect Actually Looks Like

(And Why It’s Not Sexy)

Real respect is boring.

It’s consistency.
It’s fairness.
It’s doing what you said you’d do.

It’s admitting you’re wrong without spinning it.
It’s listening without preparing your rebuttal.
It’s treating junior people like adults, not obstacles.

Not because they earned it.

Because that’s the baseline.

Stop Saying “Respect Is Earned”

Say this instead:

Respect is given.

And leaders are responsible for not wasting it.

Every interaction is a withdrawal or a deposit.

Most leaders are overdrawn and don’t even know it.

Final Word

Your title didn’t earn you respect.

Your experience doesn’t protect it.

And your authority won’t save it.

Respect is not earned.

It’s maintained.

And once you burn it,
no amount of leadership training will bring it back.

🎧 Podcast Episode

This post pairs with the podcast episode “Respect Is Not Earned.”

Listen Now

Nobody warns you that the weird part of getting promoted is not the work. It is the silence. The same people who used to talk freely around you now pause, filter, and choose their words like you are recording everything for evidence.

You did not suddenly become untrustworthy. You just crossed an invisible line and everyone is pretending it is not there.

I have even led someone who used to be my boss. That experience wipes out any fantasy that leadership is about power. You cannot posture your way through that situation. You either learn how to lead with clarity or you quietly lose credibility one awkward interaction at a time.

Most new leaders try to solve the discomfort by working harder in public. More meetings. Longer Slack threads. Excessive transparency that is really just insecurity wearing a name badge. It feels responsible, but what it really does is teach your team that you do not trust yourself yet.

Here is the part nobody wants to admit.

If you avoid acknowledging the shift, your team will invent their own explanation. And it will be worse than anything you could have said out loud.

Some will assume you are playing favorites. Others will think you are afraid to lead. A few will decide you are no different than the managers they already learned not to trust. None of that happens because of what you do. It happens because of what you leave unsaid.

So say it.

You are in a new role. The relationship will change. Expectations will be clearer. Feedback will be more direct. You are still the same person, but you are not pretending the job is the same.

That is not ego. That is respect.

This transition is not about proving you deserve the title. It is about building boundaries that allow the team to function without guessing what you are thinking. Some friendships will cool. Some conversations will get harder. That is the cost of leadership, not a sign you are doing it wrong.

You were never supposed to figure this out alone. You were just dropped into a system that treats leadership like a personality trait instead of a skill. And then it wonders why people struggle the moment the rules change without warning.

Let’s get uncomfortable.

If your leadership strategy is counting hours, you are not managing productivity.
You are managing fear with a spreadsheet.

Time tracking isn’t leadership.
It’s insecurity wearing a dashboard.

Why Leaders Obsess Over Hours

Leaders track hours because:

• They don’t trust their people
• They don’t know how to measure impact
• They confuse control with clarity

So they reach for the easiest metric they can weaponize.

Time.

Hours Don’t Build Products

You can be logged in for ten hours and accomplish nothing that matters.

The Damage You’re Creating

When you obsess over time:

• Developers learn to game the system
• Innovation becomes dangerous
• Creativity becomes suspicious
• Trust dies quietly

You don’t get honesty.
You get compliance.

And compliance never built anything great.

What Real Leaders Measure

Real leaders measure things that actually move companies forward.

• Time to unblock
• Speed of learning
• Friction per release
• Recovery after failure

Not because these are easy.
But because they matter.

The Line in the Sand

You either lead people,
or you audit them.

You don’t get to pretend it’s the same thing.

Closing

If you track hours instead of outcomes, you don’t have a productivity problem.

You have a courage problem.

Lead.
Don’t Ctrl.

You’re already here questioning bad leadership.
Might as well wear it too.

Don’t forget to check out the merch.
👉 Get it here

Most tech leads think their job is to put out fires.

They jump into broken builds.
They fix production issues at midnight.
They unblock tickets like human-Jira automation.

That feels productive.
It’s also the fastest way to burn yourself out and cap your team’s growth.

In this episode, we talk about the real job of a tech lead, and why your value isn’t in how many fires you fight, but how many fires never happen because of you.

What we cover in this episode

• Why “hero mode” is seductive and destructive
• The difference between being busy and being effective
• How tech leads accidentally become bottlenecks
• What it actually means to be a force multiplier
• Where tech leads should spend their time instead

This isn’t anti-hands-on.
It’s anti-wasted-effort.

Listen to the episode

👉 Spotify: Listen now
👉 Apple Podcasts: Listen here

The mindset shift most tech leads miss

Firefighters react.

Force multipliers design systems, expectations, and teams that don’t need constant rescue.

If your team can’t move without you:

• You’re not leading
• You’re just really good at fixing emergencies

And emergencies are a symptom, not a strategy.

Who this episode is for

• New tech leads who are wondering why they’re exhausted
• Senior engineers who are being “soft-promoted” into chaos
• Managers who think leadership means availability
• Anyone stuck being the smartest person in every room

If that made you uncomfortable, good.
That’s where growth lives.

If this episode hit home

• Share it with a tech lead stuck in firefighter mode
• Follow the podcast wherever you’re listening
• Check out the rest of LeadDontCtrl for more no-BS leadership content

More episodes coming.
Same honesty.
No corporate theater.

I’ve spent years watching good engineers get promoted into leadership roles with almost no preparation for what the job actually is.

They’re smart. They care. They want to do right by their teams.

And then they’re handed vague advice, overloaded with responsibility, and quietly expected to “figure it out.”

That gap, between what leadership sounds like and what it actually requires, is why I started a new podcast called Lead Don’t Ctrl.

Episode 0 is live now. It’s intentionally called Episode 0, because arrays start at index zero... and because leadership should start with context.

In that episode, I explain:

What “Lead Don’t Ctrl” actually means

Who this podcast is for (and who it’s not)

Why so much leadership in tech defaults to control instead of clarity

Episode 1 is coming next, and it goes deeper into the real job of a tech lead, the part nobody trains you for.

If you’ve ever stepped into leadership and thought, “Why does this feel harder than it should?”, this podcast is for you.

🎧 Listen to Episode 0 on Spotify: Why This Podcast Exists (And Who It’s For)

🎧 Listen to Episode 0 on Apple Podcasts: Why This Podcast Exists (And Who It’s For)

Lead well. Don’t control.

Let’s kill a myth.

Hard work does not get you promoted in tech.

It gets you more work.

If you’re the person who always says yes, closes the most tickets, and quietly fixes messes, congratulations. You’ve made yourself indispensable.

And invisible.

The Promotion Lie

Here’s what nobody wants to say out loud:

Companies don’t promote the hardest workers.
They promote the people they trust when things go sideways.

That’s a completely different skill set.

Grinding proves reliability.
Leadership roles require judgment.

And if all you demonstrate is obedience and output, you’ll stay right where you are, productive, exhausted, and confused.

The Trap High Performers Fall Into

High performers are especially vulnerable to this.

They think:

“If I just keep delivering, someone will notice.”

What actually happens:

• You get shielded from bigger decisions
• You get looped in after choices are made
• You become execution, not influence

That’s not a promotion path.
That’s a holding pattern.

What Senior Actually Looks Like

Senior engineers don’t just build what’s asked.

They:

• challenge unclear work
• surface risk early
• think beyond their own tickets
• protect the team from bad decisions

They don’t wait for permission to think.

I Broke This Down in a Video (Because Text Only Goes So Far)

Watch: Stop Trying Be a Senior Developer - Do This Instead

If this post made you uncomfortable, good.
I explain why this happens, and what actually works, in this video.

👉 Watch it here:
https://youtu.be/if9nUIZvNBs

Lead, Don’t Grind

If your entire career strategy is “outwork everyone,” you’re not building leverage.

You’re burning fuel.

Stop trying to be impressive.
Start trying to be effective.

That’s how people actually level up.

Lead. Don't Ctrl.

Alright rebels, it’s official:
LeadDontCtrl is on YouTube.

Right now, the channel is stocked with leadership shorts, fast hits of rebellious, truth-first, no-BS tech leadership wisdom. Think of them as microdoses of “stop doing that, here’s a better way.”

But don’t get too comfortable.
Bigger, louder things are coming.

What’s Live Right Now

I’ve posted a series of shorts covering:

• What tech leads actually do (hint: it’s not micromanaging)
• Why indecisive leaders stall teams
• The subtle art of not running your standup like a TED Talk
• Real leadership moves that don’t require a corporate playbook

They’re quick, sharp, and designed to jolt you out of bad leadership habits.

What’s Coming Next

More Shorts

Because apparently the internet loves leadership truth bombs served in under 60 seconds.

First Long-Form Video: "Career Advice I Give Every Developer I Mentor (But Never See Online)"

This is the one I’m most excited about.
It’s all the career guidance I wish someone would have told me, the stuff I share privately with developers I mentor, but never see anyone talking about publicly.

It’s honest. It’s practical. And it’s probably going to annoy a few “leadership influencers,” which makes it even better.

Why This Matters

The internet is packed with leadership advice written by people who haven’t led anything except their LinkedIn profile.
This channel is the antidote, modern leadership, real engineering experience, and zero corporate frosting.

Join the Rebellion Early

⚡ Subscribe here: https://www.youtube.com/@leaddontctrl
New shorts are already rolling out, and long-form episodes are on deck.

Get in now before middle management discovers it and tries to schedule a meeting about it.

Somewhere along the way, “leadership” in tech got reduced to dashboards and burndown charts.

How many tickets closed this sprint?
How many story points completed?
How fast did that team crank through the backlog?

Look, metrics have their place. But if your leadership boils down to counting tickets, you’re not leading, you’re babysitting output.

Here’s the real truth:
Teams don’t stick around for Jira reports. They stick around because they trust each other. They ship faster because they trust their leaders. They innovate because they trust that failure won’t be punished.

Trust is the multiplier. Without it, no amount of ticket-closing will save you.

A team that trusts you will work through fire for you. A team that doesn’t will sandbag, disengage, and quietly polish their LinkedIn profile.

So stop obsessing over the shallow metrics. Start asking yourself the harder questions:

• Do my people feel safe to tell me when something’s broken?
• Do they believe I have their back when they take a risk?
• Do they trust me to make decisions that aren’t just about my ego or my metrics dashboard?

Because here’s the kicker:
If you build trust, the tickets take care of themselves.
If you don’t, no amount of metrics will make you a leader worth following.

Hey, since you made it this far, you might actually care about becoming a better leader. Good news: I wrote an ebook that’ll help you skip years of trial and error.

📘 Get Tech Leadership Made Simple.

We all know that guy, the one who treats daily standup like open mic night.
He’s got 2 minutes to say what he worked on yesterday, and somehow turns it into a TED Talk about Docker, the roadmap, his weekend hike, and three side quests no one asked for.

Meanwhile, the quiet engineer?
They crushed a blocker, refactored half the backend, and solved a bug that’s haunted the repo since 2019, then said “Yesterday: fixed some auth logic. Today: unit tests.”
And that’s it.

The Loudest One in the Room Is Rarely the Smartest

It’s a dangerous myth: that the most vocal person is the most productive, the most influential, or the most valuable.

Spoiler alert:
Volume ≠ Value.

Loud != Leader.
Verbose != Visionary.

Sometimes, the ones saying the least are the ones making the biggest impact, while the talkers are just… talking.

Real Work Happens in the Silence

Your best engineers might not be “evangelizing their impact” in every meeting.
They might not be grandstanding in retros.
They might not have a Notion doc titled “How I Saved the Sprint.”

What they do have?

• Code that ships
• Systems that scale
• Colleagues who trust them
• A Git history that tells the real story

They don’t need a parade. They need a leader who sees them.

So… Are You Paying Attention?

As a leader, it’s your job to look past the noise.
Spot the quiet brilliance.
Reward the consistent ones, not just the charismatic ones.

That doesn’t mean ignoring your extroverts; it means not equating visibility with value.

It means saying, “I see you,” even if they didn’t shout to be seen.

TL;DR

• The loudest voice in standup ≠ the most valuable contributor
• Quiet engineers often carry your team—recognize them
• Value impact over airtime
• Be the leader who notices what others overlook

Hey, since you made it this far, you might actually care about becoming a better leader. Good news: I wrote an ebook that’ll help you skip years of trial and error.

📘 Get Tech Leadership Made Simple.

We’ve all been there: you open your calendar and it’s wall-to-wall with "decision-making" meetings that could’ve been a Slack message, an email, or better yet, a leader actually making a decision.

Here’s the uncomfortable truth:
If you’re calling a meeting for every single call, big or small, you’re not leading.
You’re crowd-sourcing authority like it’s trivia night and you forgot the answer to “Who’s responsible?”

Meetings Are Not a Substitute for Spine

A meeting should never be your first resort when you’re faced with a tough call.
Yes, input matters.
Yes, collaboration is beautiful.
But if you're bringing the whole team together just so nobody can point fingers at you later, you’re not empowering, you’re hiding.

Leadership requires judgment.
It requires ownership.
It requires the ability to make a call even if it's uncomfortable, unpopular, or risks being wrong.

And guess what? You will be wrong sometimes. That’s part of the job. Own it. Learn. Move on.

Meetings Should Be Multipliers, Not Muzzles

Great meetings energize, align, and unlock momentum. They’re strategic checkpoints, not tactical crutches.

Bad meetings?
They drain your team’s time and trust.
They make people think you don’t trust them, or yourself.
They turn your calendar into a slow, painful death spiral of indecision.

Here’s a simple litmus test:

• Do you already know the right call, but you're scared to make it? That’s a fear issue, not a collaboration need.
• Do you need input on a specific detail to move forward? Cool, a 15-minute sync might work.
• Do you need everyone to help you decide what snack to buy for the launch party? You’re running Game Night, not a dev team.

Leadership = Direction, Not Consensus

Stop trying to run your team like it’s a co-op board game.
Not every decision requires consensus. Hell, most of them don’t.
You weren’t given a leadership title to be the official Zoom meeting scheduler. You were given it because someone thought you could steer the ship.

So steer it.

And if you crash it? That’s part of the gig too. The best leaders learn faster from failure than others do from safety.

TL;DR for the Calendar-Happy Crowd:

• Stop defaulting to meetings.
• Make decisions. Own outcomes.
• Collaborate when needed, but lead always.
• Game night is for Settlers of Catan, not product roadmap pivots.

Hey, since you made it this far, you might actually care about becoming a better leader. Good news: I wrote an ebook that’ll help you skip years of trial and error.

📘 Get Tech Leadership Made Simple.

Look, I’m glad you’re proud of your role. That’s great. You probably worked hard to get here.
But if you start believing your team is “lucky to have you,” let me stop you right there.

You’ve got it backwards.

They show up every day. They put up with broken processes, half-baked roadmaps, Slack chaos, and, let’s be honest, you.
You are not their savior. You are not their career’s highlight reel.
They are not lucky.

You are.

The Myth of the “Hero Leader”

Corporate culture loves to romanticize leadership like you’re leading a band of hobbits into Mordor. You're not. You're just guiding a bunch of very smart, very tired professionals through another sprint planning.

You are not a hero for being in meetings all day.
You are not a visionary because you used “synergy” in a slide deck.
You are not irreplaceable. Neither am I. No one is.

So drop the ego and pick up some humility.

What Real Leadership Looks Like

It’s not about being the smartest in the room.
It’s about creating space for others to shine.

It’s about:

• Deflecting praise and redirecting it to the team that earned it
• Owning the failures so your people aren’t thrown under the bus
• Listening when they say they’re burnt out, frustrated, or confused
• Saying thank you more than once a quarter

The best leaders don’t see themselves as above the team, they see themselves as because of the team.

Signs You’re Leading With Ego

• You take credit for team wins
• You act like coaching is a chore, not a responsibility
• You downplay burnout or wave off PTO requests
• You think “they should be lucky to have a job”

If that’s you, I’m not saying you’re the villain. But you might be the reason someone’s updating their LinkedIn profile this week.

Gratitude > Arrogance

Real leaders know gratitude isn’t weakness.
It’s strength.
It keeps people around.
It makes work bearable, even meaningful.

Because at the end of the day, your team doesn’t owe you loyalty. They owe you their work. If you want more than that, respect, commitment, innovation, than you’d better earn it. Every damn day.

Your team isn’t lucky to have you.
You’re lucky they still believe in the work enough to stay.
Lead accordingly.

Lead. Don't Ctrl.

Hey, since you made it this far, you might actually care about becoming a better leader. Good news: I wrote an ebook that’ll help you skip years of trial and error.

📘 Get Tech Leadership Made Simple.

Let’s get one thing straight: delegation is not just yeeting tasks off your plate like you’re cleaning up for a surprise performance review.

If your idea of delegation is dropping an assignment on someone’s lap with zero context, no support, and a shrug that says “you got this,” congratulations, you’re not leading. You’re ditching.

And your team knows it.

The Dirty Truth About “Delegation”

Real talk? Most people in leadership positions aren’t delegating; they’re dodging. They pass off chaos, hope someone else sorts it out, and then act surprised when it doesn’t magically turn into a beautiful deck or a bug-free feature.

Delegation isn’t about doing less work.
It’s about doing different work.
More strategic. More supportive. More human.

If you’re not actively helping your people succeed, you’re just redistributing stress like it’s Halloween candy.

Signs You’re Ditching, Not Delegating:

• You assign work without explaining why it matters
• You throw a ticket over the fence and vanish like Batman
• You’re surprised when the outcome doesn’t match your imaginary expectations
• You give zero feedback until something’s on fire
• You’ve never said, “How can I help?” or “What do you need from me?”

If this hits a little too close to home... good. Awareness is the first step toward being less of a jackass.

What Real Delegation Looks Like

1. Clarity of Purpose
   Don't just assign a task. Explain the impact. Connect it to the bigger picture.
2. Clear Expectations
   Define success. Deadlines, deliverables, and quality standards, don’t assume they’re mind readers.
3. Ongoing Support
   Delegating doesn’t mean disappearing. Stay available. Check in. Offer help without micromanaging.
4. Ownership, Not Abdication
   They own the task, but you still own the outcome. If they fail, it’s not “their fault”, it’s yours too.
5. Debrief and Feedback
   After it’s done, talk about what went well and what could improve. That’s how people grow. That’s how you grow.

You’re not a leader because you hand out tasks. You’re a leader because you build people up in the process.

Delegating right means trust without abandonment, clarity without control, and support without smothering.

Get it wrong, and you’re just ditching responsibilities and hoping no one notices.

Get it right, and you create a team that thrives, even when you’re not in the room.

Which one do you want to be?

Lead. Don't Ctrl.

Hey, since you made it this far, you might actually care about becoming a better leader. Good news: I wrote an ebook that’ll help you skip years of trial and error.

📘 Get Tech Leadership Made Simple.