Because aligning network automation with business goals and managing delivery friction determines whether enterprises capture the promised efficiency gains and ROI.
The Network Automation Nerds podcast episode features host Eric Cho and senior engagement manager Matt Rimkkey of Network to Code, discussing real‑world network automation projects and the bridge between technical execution and business objectives.
Rimkkey explains his role as a “project delivery orchestrator,” emphasizing the need to translate engineering details into business‑focused results, break down silos, and maintain risk‑aware timelines. He draws on a varied background—from early‑stage startups like Art.com to operations roles—highlighting how process‑fixing instincts translate to large‑scale automation initiatives.
A vivid example is a recent migration of a legacy on‑prem application to a cloud‑based version for a major client. The design phase consumed four months of approvals, followed by six months of “hurry‑up‑and‑wait” migration work, leaving engineers frustrated despite the eventual success. Notable quotes include, “They don’t care about VLANs; they care about delivering business results,” and the analogy that “reps matter just like in athletics.”
The discussion underscores that successful automation hinges on clear communication, realistic scheduling, and continuous incremental improvements. Enterprises that align technical delivery with business metrics and adopt a disciplined, iterative approach are more likely to achieve measurable ROI and avoid costly delays.
Comments
Want to join the conversation?
Loading comments...