465- From Department of No to Department of Risk w/Jeff Posluns

Phil Howard & Jeff Posluns

465- From Department of No to Department of Risk w/Jeff Posluns

THE IT LEADERSHIP PODCAST
EPISODE 465

465- From Department of No to Department of Risk w/Jeff Posluns

20
1 X
20
00:00 | 00:00

Short Clips

Episode Highlights

Jeff Posluns

GUEST BIO

Jeff Posluns runs the tech part of Traffic Tech, a third- and fourth-party logistics company with about 40 offices around the world and about 1,200 people. In his view, a project without a business owner should not start, because the business owner defines the outcomes. He applies the same thinking to funding: most organizations fund projects, the team disbands after go-live, and technical debt stays invisible until something fails, so he advises persistent funding of business capabilities, with lifecycle and run costs approved at the same time as the build.

Technology risk is business risk, and the business should own it. When ownership is unclear, risks get accepted by default because nobody made a decision, so he puts technology risk on the enterprise risk register with named business owners. A new initiative starts with the named business executive, the number and the date, and he decides up front how progress will be measured and at what point in the spending to ask whether the project should be stopped and shelved. He also argues that a CIO still needs real technical depth, or ends up approving decisions they can't evaluate.

When a request is unreasonable, he answers as the Department of Risk: a risk assessment from the GRC team, and the list of what the business has to accept. Spend a day changing the color of a baby puke green button, and you might lose two loads of melted Hershey Kisses and have to make an insurance claim. His priorities come from a meeting every two weeks, with five high-priority projects that have delivery dates and five medium ones with target dates, and his one-line advice for technologists is to learn to hate the right things.

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, and the tech part of Traffic Tech

[03:59] No business owner, no project

[07:23] How technology gets funded, and technical debt

[09:16] The three-month ERP, and technology as a business decision

[14:29] Technology risk is business risk

[20:20] The business as internal customer, and three SOCs

[26:00] The named executive, the number and the date

[32:04] Technical depth, and saying no with credibility

[36:35] Five high priorities, five medium, everything else

[40:59] The Department of Risk and the baby puke green button

[47:44] Diagram fatigue and Clean Language

[53:04] Learn to hate the right things

KEY TAKEAWAYS

Don't start a project until a business owner has defined the outcomes they're looking for.
Approve lifecycle and run costs at the same time as the build, so technical debt is visible and the total cost of ownership gets discussed before anyone signs off.
Put technology risk on the enterprise risk register with named business owners, so every deferred decision becomes an explicit risk acceptance.
Start an initiative with the named business executive, the number and the date, and decide how you'll measure progress and at what point you'd stop and shelve it.
Keep five high priorities with delivery dates and five medium ones with target dates; anything that pulls a person off a high priority goes through a formal change register and the prioritization committee.
Answer an unreasonable request with a risk assessment and what the business will have to accept, and keep your technology team out of the meetings about button colors.
465- From Department of No to Department of Risk w/Jeff Posluns
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.