Software Delivery: it’s all about Flow
Last Updated on 16 June 2025 at 19:22
When we discuss software delivery, we are essentially talking about how ideas move from conception to value for users. Better value for customer users means better sales and superior market positioning.
Imagine the chaotic streets of a big city at rush hour — like in Geneva or Zurich. Cars and taxis honking, aggressive bikers weaving through cars, and pedestrians crossing wherever they please. Now, picture a serene country road, empty and peaceful at dawn.
The key difference ? Flow.
The Kano Model suggests that the longer an idea or need goes without being experienced or tested, the less excitement and potential impact it generates. Therefore, the flow of value must be efficient and continuous. However, several misconceptions and practices often disrupt this flow.
The Pitfalls of Projects Oversight, Utilization, and Speed
One of the major dysfunctions in software delivery is the overemphasis on constant oversight, team utilization, and speed.
Leaders and project managers often believe that providing constant direction and maintaining 100% team utilization will improve outcomes. Reality check: holidays, illnesses, and unforeseen crises happen. This approach is akin to a backseat driver in a traffic jam incessantly giving directions to advance at all costs, even at the cost of crashing other cars and pedestrians.
Keep in mind that productivity is not about being busy all the time but about being effective. The relentless chase for speed, driven by the need to get things done ASAP, usually ends in disaster. When things go wrong (and they will), the fallout is catastrophic. Quality and meaningful outcomes get sidelined, leading to a lousy user experience and unhappy team members. And customers notice.
The Chaos of Inadequate Enterprise Practices, Incomplete Work, and Agile Misconceptions
Another set of dysfunctions arises from rigid adherence to enterprise practices, the illusion of “quick and dirty” work fixes when such an approach is unnecessary, and often misunderstandings about agility.
Enforcing strict enterprise processes when exceptions and frequent status updates are needed creates a “stop-start environment” that hinders progress. It’s like stopping every kilometre from reporting the existing location, which is inefficient and frustrating for long-term projects.
Similarly, the notion of work being “temporarily fixed” with a quick-and-dirty approach perpetuates a cycle of unfinished tasks and messy handovers. Why ? Without a clear, binary definition of “done,” the delivery teams are left in limbo. So, make “done” a binary state. It’s either done, or it’s not. Be ruthless about this. Clear, crisp milestones lead to less ambiguity and more progress.
While designed to enhance flexibility, agile methodologies often lead to chaos when changes are implemented without a clear understanding of the underlying problems. This incomplete approach unpredictability disrupts roadmaps and increases rework, counteracting the very benefits agility promises.
Steering Towards Efficient Flow
Much like managing traffic, successful software delivery is about maintaining flow. Balance structure with freedom, prioritize quality and reduce dependencies. Here are some practical approaches:
- Empowerment. Forget micromanaging — think like a coach, not an incompetent dictator. When the situation allows, trust your field teams to chart their own course. Give them the reins and watch the beauty of self-organization to deliver real results. Clear the roadblocks and allow room for creative detours.
- Optimize Utilization. Even if there are similarities, stop thinking like a factory manager. So, replace regular status meetings with smart dashboards. Let data talk and free up your teams to focus on the real work. Autonomy within a framework can lead to interesting results.
- Prioritize Quality, Risk Management, and Speed. Don’t be the driver who runs and disrespects every red light in traffic. Focus on the journey and a safe arrival at the destination. Prioritize user delight over just boxes. Besides, a well-paced journey often reaches the destination faster.
- Incremental Delivery. Break it down and deliver it in bite-sized chunks. When well done, Smaller, more frequent releases keep the risks low. Be agile but with a purpose. Each change should have a clear rationale. Planned flexibility trumps random and chaotic pivots.
- Control Dependencies. Bring closer cooperation because the fewer the dependencies, the smoother the ride. Reorganize and restructure teams, refactor the code when needed, and minimize friction. Simplify, simplify, simplify.
Consider software delivery as similar to orchestrating traffic in a city. Strive for the tranquillity of a country road rather than the chaos of rush hour. However, if chaos does occur, be prepared to manage it. By prioritizing the flow, you can turn deadlocks into a seamless journey for all stakeholders.
#FinTech #SwissTech #SoftwareDelivery #AgilePractices #ContinuousImprovement #ProductivityOptimization #SoftwareDevelopment
FinTech Wealth Management expert with 30 years of successful track record, from Unicible/BCV to Odyssey and Temenos, plus hundreds of important banks across EMEA, APAC, and NAM.
► Background — from C-language code to C-suite in 30 years
• WealthSuite Triple’A Temenos TAP Plus expert
• crisis & change management
• complex multi-level project – program – portfolio management
• process architecture & governance, process optimization, BPO
• financial services software engineering FS FinTech
Career start as an innovative software engineer in startups ► to strategic advisory & turnaround for Tier1 & Tier2 Banks at senior C-level.
• T-shaped mastery of the latest key technologies, business, and operational practices in retail banking, asset management, core banking, PMS.
• Keen focus on improving productivity, client retention, and revenues through expertise in Program Management, Process Governance, and Optimized Delivery, augmented by know-how in complex issue resolution and value-driven E2E end-to-end implementations in FinTech WealthTech.