Libi-Tech
Senior delivery leadership for programs that can't afford to slip again.
Libi-Tech is my independent practice for program rescue and fractional program and operations leadership across supply chain, robotics, SaaS, CCTV, LPR, and HLS systems: 20+ years running complex, cross-functional delivery across the U.S., Europe, and Israel.
Tell me where it stands See how I helpWhat I Do
TRACK 01: RESCUE
Program Rescue
For programs already off the rails: schedule slippage, vendor conflict, unclear ownership. I step in as the senior delivery lead, diagnose the root cause, and rebuild a plan the team can actually execute against.
TRACK 02: LEAD
Program & Operations Consulting
Broader engagements: PMO setup, cross-functional program leadership, and operations oversight for organizations that need senior delivery experience without committing to a full-time hire.
Supply Chain
Robotics
SaaS Platforms
CCTV & LPR
HLS Systems
Need to explain your system to customers or investors? See Libi-Tech Studio, my animated story-video service.
About Me
I'm Oded Ben-Dori. For over two decades I've been the person organizations turn to when delivery gets hard: the one who steps into a complex, multi-stakeholder program and gets it moving again.
I've led cross-functional teams through the full lifecycle of large, technical programs: enterprise systems, supply chain and robotic fulfillment, and technology deployments, often serving as the bridge between engineering ambition and business reality. I also know what it's like to build and run something from scratch, having founded and led an AI-powered startup end to end: strategy, resourcing, and every hard call in between.
Libi-Tech is where I bring that same delivery discipline to organizations that need someone to step in, diagnose what's broken, and get a program back on track.
Track Record
Two decades split between running delivery from the inside and leading programs as an outside partner.
Caja Robotics
BriefCam
HTS
20+ years in project delivery and operations · portfolios across the U.S., Europe, and Israel
How Engagements Work
The same three states, every time.
STATUS: AT RISK
Diagnose
Week one. I assess where the program actually stands: scope, ownership, vendors, and schedule, and tell you the truth about it.
STATUS: STABILIZING
Rebuild the Plan
Weeks two through four. A delivery plan the team can execute, with clear ownership, a Gantt-driven schedule, and a structured status and issue-tracking cadence.
STATUS: ON TRACK
Deliver
Formal acceptance sign-off and clean handover documentation, with ongoing senior oversight until the program is stable enough to run without me, or through to completion.
Field Notes
Notes from the field on why programs actually derail, and what moves them back on track.
RESCUE DIAGNOSTICS
Quiet isn't stable: why a silent program is more at risk, not less
Most failing programs don't announce it. They go quiet. Here's the diagnostic pattern, and the data behind why it matters.
Read the full breakdown →TURNAROUND MECHANICS
Own the decision: turnarounds start with accountability, not a new plan
Unclear ownership is the root cause behind most of the waste PMI and McKinsey document. Here's how to fix it in week one.
Read the full breakdown →DECISION SPEED
Slow isn't careful: why decision paralysis sinks programs
Waiting for one more data point isn't diligence, it's cost. Here's the decision-paralysis pattern behind stalled programs, and how to check for it.
Read the full breakdown →INTEGRATION GAP
The robots work fine: why robotic rollouts stall on integration, not hardware
Every robotic fulfillment program I've been called into had working robots. The failure was always in the handoff nobody owned.
Read the full breakdown →FOUNDER NOTES
I didn't leave because the program failed
The program that pushed me out on my own was the one that closed green on paper. Here's what that gap actually costs, and why it took an outsider to close it.
Read the full breakdown →SCOPE DRIFT
The plan didn't change. The work did.
Scope creep rarely shows up as one big change. It shows up as a hundred small yeses that never went through change control. Here's how to spot it early.
Read the full breakdown →FALSE GREEN
The status report lied
Programs don't fail the week they turn red. They fail while everyone, including the person writing the report, still believes it's green. Here's why status reports lag reality.
Read the full breakdown →REWORK ECONOMICS
Built once. Billed twice.
Rework doesn't get logged as failure, it gets logged as a new ticket. Why vague acceptance criteria quietly double the cost of a build, and what to check before you sign off on "done."
Read the full breakdown →