Friction is often the hidden enemy of efficient software delivery. At Prodacity, Karen Martin tackled value stream transformation, explaining how unintentional friction—miscommunication, misalignment, and delays—creates chaos and slows down mission outcomes. Her core message? Stop optimizing in silos and start thinking systemically.
Why Friction Slows Software Development
In software engineering, friction is rarely intentional—yet it shows up everywhere:
- Loss of time – Delays between development, testing, and deployment.
- Miscommunication – Lack of clarity on requirements, leading to rework.
- Workload imbalance – Some teams working ahead while others are stuck waiting.
These inefficiencies don’t just waste money—they slow down innovation. A study by McKinsey found that software teams spend up to 42% of their time dealing with technical debt and inefficiencies instead of delivering new features.
Martin emphasized that the root cause of these problems isn’t people—it’s the system they work within. Instead of blaming individuals, organizations should examine the structures, processes, and workflows that contribute to delays.
Optimizing the Whole, Not Just the Parts
One of the biggest modernization mistakes? Optimizing a single process without considering its impact on the larger system.
Martin illustrated this with an example from healthcare:
- In the 1980s-2000s, hospital labs reduced test turnaround times, expecting this to speed up patient discharge.
- However, emergency departments remained overcrowded—because faster lab results didn’t solve bottlenecks elsewhere in the system.
This siloed optimization problem happens in software too:
- Developers may write perfect code, but if it’s stuck in a testing queue, delivery speed doesn’t improve.
- Automating deployments won’t help if upstream bottlenecks in feature planning still exist.
- Improving one team’s efficiency doesn’t mean the entire system will run better.
The lesson for developers and engineering leaders: Look at the entire value stream, not just isolated processes.
What Is a Value Stream?
Martin differentiated between value streams, processes, and steps:
- Value Stream – The entire workflow from request to delivery.
- Processes – The major components within the value stream (e.g., coding, testing, deployment).
- Steps – The individual tasks needed to complete a process.
Understanding the full value stream provides visibility into bottlenecks. A Value Stream Mapping (VSM) approach—which involves storyboarding and visualizing workflows—can reveal unseen inefficiencies.
According to industry research, companies that implement value stream management frameworks improve software delivery speed by up to 30% while reducing waste and rework.
Eliminating Friction: The Continuous Improvement Loop
Value stream transformation isn’t a one-time fix—it’s a continuous cycle:
- Map the current state – Identify where bottlenecks and delays occur.
- Design the future state – Define how work should flow more efficiently.
- Measure improvement – Track key metrics to ensure progress.
- Iterate and refine – Continuously optimize workflows to sustain long-term efficiency.
Martin emphasized that visualizing friction makes it actionable—once you see where the system is breaking down, you can fix it.
Analyst Takeaway: Why Value Streams Matter for Developers
For developers and engineering teams, value stream thinking is critical to delivering software faster and with fewer obstacles.
Key Implications:
- Stop optimizing in silos. A high-performing development team means nothing if downstream workflows slow things down.
- Remove hidden inefficiencies. Seeing the full value stream helps eliminate redundant steps and optimize workflows.
- Continuous improvement is the goal. Software modernization isn’t about a one-time fix—it’s about making systems evolve smoothly over time.
Final Thought
Software delivery shouldn’t feel like a game of whack-a-mole—fixing one problem only for another to emerge. By eliminating friction, improving workflow visibility, and embracing value stream transformation, teams can deliver better software, faster.
When developers, testers, and operations teams work at the same pace, toward the same goal, modernization stops being chaotic—and becomes an enabler of mission success.
Cisco Live 2025: Enabling AI-Driven Development with Scalable and Secure Infrastructure
The News At Cisco Live Amsterdam 2025, Cisco introduced a range of AI-ready solutions aimed…