476- You Have to Market Yourself w/Ron Ijack

Phil Howard & Ron Ijack

476- You Have to Market Yourself w/Ron Ijack

THE IT LEADERSHIP PODCAST
EPISODE 476

476- You Have to Market Yourself w/Ron Ijack

20
1 X
20
00:00 | 00:00

Short Clips

Episode Highlights

Ron Ijack

GUEST BIO

Ron Ijack is a developer at heart who started writing code in the mid-90s and "almost fell into leadership roles along the way." He has sat on both sides of the table, and he knows how the welcome changes. In the interview, "you're the external guy who's coming to save us." Once you're inside, "you become the director that broke this." His answer is to keep fighting that battle: lead with data, lead with wins, and provide that value for the business. "It's marketing in a way. You have to market yourself." He calls himself the worst offender, because IT teams are so busy putting out fires that there's no time to keep track of everything they fixed.

Phil reads out a playbook for IT leaders that he builds live with Claude, and Ron tests each point against his own practice. Tech debt is something he absorbs silently: when a project carries a bunch of it, he bumps up the time frame and fixes it, and he brings the executive team the money saved or the revenue added. He gives projects names people remember (his middleware integration layer was called Middle Earth), likes the idea of a funny video at every town hall, and makes the case for meeting users where they are, with a ticket raised from Slack or a Claude skill instead of a seven-page form. He is all for documentation, yet he pushes back on the risk register as a shield: if you need one to cover yourself, "there's something wrong with your culture."

He closes with the advice he'd give his younger self: "Being right doesn't always matter." When the perception that you were wrong is strong enough, fighting it won't help, so "you have to change the perception," and your personal brand is "probably your biggest asset." He also explains how he learned to think like a business leader after moving from leading engineering at a software company into senior leadership at a brand: by learning what hits with the CEO and the board, and speaking to what's important to them.

Network Assessment

Your monthly IT spend should be boring.If it's not, something is wrong.

Network Friction Score
BoringChaotic
Do you have provider/support numbers handy, or is it 1-800-GO-POUND-SAND?

We review circuit consolidation, contracts, security, outage visibility, billing, and future flexibility to reduce chaos without forcing change.

▸Circuit consolidation
▸Contracts & pricing
▸Firewall management
▸Outage alerts
▸Edge security
▸Billing & licensing
Boring results. Reputable savings.
Consolidation that makes sense.
Show Notes

Episode Show Notes

Navigate through key moments in this episode with timestamped highlights, from initial introductions to deep dives into real-world use cases and implementation strategies.

[00:00] Cold open

[00:40] Why executives trust the outside voice

[09:10] You have to market yourself

[15:16] Keeping your voice after you join: the external guy

[16:12] A Claude skill for IT wins, and why domain knowledge still matters

[19:21] Business numbers and the tech debt he absorbs silently

[22:27] Name your wins and make the town hall memorable

[27:00] Warn early, own the losses, decide with what you know

[37:41] Choosing vendors, and two-way doors

[42:32] Meet users where they are, then make the ask and stop

[48:34] Outside credibility, teaching, documentation and staying visible

[59:21] Being right doesn't always matter, and learning to read people

KEY TAKEAWAYS

Keep track of the before and after on every project, and get the metrics while the work is fresh, so you have something to show at the board meeting or the year-end review.
Lead with data and wins, in the business's own numbers: the money you saved or the revenue you added.
Fold tech debt fixes into the project's time frame, and report wins that carry a concrete number, like the dollars saved by removing vendors.
Meet users where they are: let them raise a ticket from Slack or a Claude skill, and keep the seven-page form out of their way.
On a two-way-door decision, decide and move on. Take your time on the one-way doors, like your architecture stack or your data warehouse.
When people see you as the one who got it wrong, fighting it won't help. Work on changing the perception.
476- You Have to Market Yourself w/Ron Ijack
logo

You’ve Been Heard

You’ve Been Heard is where IT leaders stop being sidelined and start being amplified. We’re the triple-threat platform: podcast, community and vendor-neutral advisory that elevates your voice, your value, and your influence because when IT leaders rise, so does everything else.

© 2026 You've Been Heard. All rights reserved.