agile# How to Use Vision-Driven Investment to Create a Meaningful Definition of Done in Technology Hardware (1/32)
A technology hardware company running Lean with multiple teams of fifty-plus people has a definition of done problem. The company makes enterprise-grade network routers installed in data centers. These routers handle traffic routing, load balancing, firewall rules, and network monitoring. They run embedded Linux. The software covers packet forwarding, routing protocols, security policies, and management interfaces. (2/32)
The company has been around for eighteen years with 2,800 employees. The product development organization has 74 people: one chief product owner, three product owners, one Lean coach, eight development teams, six QA engineers, four performance engineers, three security engineers, two UX designers, two technical writers, and two DevOps engineers. Each development team has six to eight people (3/32)
. They follow Lean practices including value stream mapping, Kanban boards, WIP limits, continuous improvement, and just-in-time delivery.
The definition of done is inconsistent across teams. Team one has six items: code written, code reviewed, unit tests pass, integration tests pass, performance test passes, code merged. Team two has four: code written, code reviewed, unit tests pass, code merged. Team three has no definition of done at all. They ship when the product owner says ship. (4/32)
This inconsistency causes real damage. Last quarter, team two released a firmware update with a memory leak. The leak caused routers to crash after 72 hours of operation, taking 46 data centers offline. The downtime cost $380,000 in service credits. That memory leak would have been caught by team one's definition of done, which includes a 96-hour performance test. Team two's definition had no such test. The definition of done needs to be consistent and meaningful across every team. (5/32)
## The Masayoshi Son Approach
Masayoshi Son built SoftBank on vision-driven investment. His model was straightforward. He had a 30-year vision: information technology would transform every aspect of human life. The vision was specific, long-term, and unwavering. Son didn't chase short-term returns. He invested in companies aligned with that 30-year vision. Every investment decision was driven by it. (6/32)
When Son invested in Alibaba, it wasn't about Alibaba's current revenue. It was about alignment. Alibaba was building e-commerce infrastructure central to the information technology transformation. So Son invested $200 million. It returned $50 billion. (7/32)
Son used the same approach for internal product development. SoftBank's mobile networks were evaluated against the vision. Did the network advance the information technology transformation? Build it. If not, reject it. The vision created a consistent standard that went far beyond does the product work. The standard was does the product advance the vision. (8/32)
For a technology hardware company, the definition of done problem is the same problem Son solved. The fix is a unifying vision that every team references. The vision must be long-term, specific, and shared. The definition of done must reflect that vision. Consistency creates quality. Quality creates customer trust. Trust creates growth.
## The Core Principle (9/32)
Son's approach came down to a simple insight: inconsistency is a vision absence problem. He didn't build SoftBank by letting every team define quality He built it by creating a 30-year vision and evaluating every investment and product against it. That vision set a consistent standard, and that standard drove alignment, quality, and returns. (10/32)
The definition of done in your organization varies wildly. One team has six items. Another has four. A third has none. That inconsistency is what let a memory leak slip through and take down 46 data centers. Son's framework says the answer is a unifying vision that drives a consistent definition of done. That consistency eliminates the gaps where defects hide.
## Five Steps to Apply Vision-Driven Investment to Your Definition of Done (11/32)
### 1. Create a 30-Year Product Vision Like Son Created a 30-Year Investment Vision
Son's 30-year vision was that information technology would transform every aspect of human life. It was long-term, specific, and unifying. Your organization needs the same thing. (12/32)
The chief product owner should work with the three product owners to create a 30-year vision. For a network hardware company, it might look like this: By 2055, every data center will run on autonomous, self-healing network infrastructure that requires zero human intervention.
That vision has three pillars. Autonomy: the network configures, optimizes, and heals itself. Performance: zero packet loss at scale. Security: automatic threat detection, response, and breach prevention. (13/32)
Put those pillars on a board visible in every team area, every standup, every value stream review. When any team discusses a feature, they use the pillars. Does this advance autonomy? Performance? Security? The pillars become the unifying standard. (14/32)
For eight Lean teams of fifty-plus people, this vision should be created in the first month. It takes about four hours. The chief product owner leads it. All eight teams review and approve. For Lean practice, the vision belongs at the endpoint of your value stream map.
### 2. Derive a Minimum Standard Definition of Done From the Vision (15/32)
Son derived minimum investment criteria from his vision. Every investment had to meet baseline standards around market size, technology differentiation, and founder alignment. Anything below the bar was rejected. (16/32)
Your team should derive a minimum standard definition of done the same way. From the three vision pillars, pull concrete criteria. An autonomy test passed: the feature runs in a simulated autonomous environment for 96 hours without human intervention. A performance test passed: tested under peak load of 10,000 concurrent connections per second with no more than one percent degradation (17/32)
. A security test passed: tested against denial-of-service, man-in-the-middle, and injection attacks with automatic detection and response. Plus peer code review covering functionality, security, and performance. Integration tests across all downstream dependencies. Clean merge to the main branch. (18/32)
That's six criteria. Every team meets all six. No exceptions. This minimum standard would have caught that memory leak. Team two would have run the 96-hour autonomy test and found the leak at hour 72 before it ever reached a data center.
For eight Lean teams, derive this standard in the first month. It takes about two hours. The chief product owner leads, all eight teams approve. For Lean, this standard is a requirement on the value stream map. (19/32)
### 3. Add Team-Specific Criteria on Top of the Minimum Standard
Son allowed portfolio companies to add criteria beyond the minimum. The floor was non-negotiable, but companies could layer on requirements specific to their context. (20/32)
Your teams should do the same. Team one works on routing protocols. They add a routing convergence test: under 50 milliseconds after a simulated link failure. Team two works on the firewall module. They add firewall rule validation: 10,000 rules validated for correctness within 10 seconds. Team three works on the management interface. They add WCAG 2.1 AA accessibility testing. (21/32)
Each team has seven criteria total: the six minimum standards plus one team-specific addition. The baseline stays consistent. The team-level additions stay contextual. Together they create a definition of done that's both rigorous and relevant.
For eight Lean teams, add these criteria in the first month. Each team needs about one hour. The product owner for each team leads, the chief product owner reviews. On the Kanban board, these criteria become explicit policies. (22/32)
### 4. Build an MVP Definition of Done and Pivot When the Vision Shifts
Son built an MVP investment thesis and pivoted when the vision shifted. He started focused on software distribution, then moved to mobile networks. The pivot was deliberate and execution-focused.
Build an MVP definition of done the same way. Start with three criteria from the vision pillars: autonomy test, performance test, security test. Implement it across all eight teams. Run it for eight weeks. (23/32)
You'll find gaps. Maybe the MVP misses integration testing and failures start slipping through. Add integration tests as criterion four. Test again. Maybe code review is missing and security vulnerabilities get through. Add it as criterion five. Keep iterating. The definition of done improves with every cycle. (24/32)
If the vision itself shifts, the definition of done pivots with it. If autonomy gives way to sustainability as a priority, swap the autonomy test for an energy efficiency test. The definition of done always reflects the current vision.
For eight Lean teams, build the MVP in the first month. Iterate every eight weeks. Within your Lean practice, this is part of continuous improvement.
### 5. Use Value Stream Mapping to Visualize the Definition of Done Across Teams (25/32)
Value stream mapping is core Lean practice. It visualizes flow, surfaces waste, and identifies bottlenecks. Use it to visualize the definition of done across all eight teams.
The Lean coach creates a definition of done value stream map showing every team's criteria. Use three colors. Green means the criterion is present. Yellow means partial. Red means missing. (26/32)
Team one shows six green criteria. Team two shows four green and two red. Team three shows three green and three red. The inconsistency is visible immediately.
Share the map with the chief product owner. The red areas are gaps. Fill them. Team two adds the missing performance test. Team three adds the missing security test. The map updates. Red turns green. (27/32)
That visibility creates accountability. Accountability creates consistency. Consistency eliminates gaps. And eliminating gaps is what prevents the next $380,000 outage.
For eight Lean teams, create this map in the first month. It takes about four hours. The Lean coach builds it, all eight teams review it, and it gets updated every four weeks.
## Closing on Vision Over Variation (28/32)
Masayoshi Son didn't build SoftBank by letting every portfolio company define success differently. He built it by creating a 30-year vision, deriving non-negotiable minimum criteria from it, letting companies add context-specific requirements on top, building an MVP thesis and pivoting when the vision shifted, and visualizing criteria across the entire portfolio to find and fill gaps before they caused failures. (29/32)
For a technology hardware company running Lean with multiple teams of fifty-plus people, creating a meaningful definition of done requires the same approach. Create a 30-year product vision centered on autonomous, self-healing network infrastructure by 2055. Derive a six-criterion minimum standard including a 96-hour autonomy test, peak load performance testing, simulated attack security testing, peer code review, integration testing, and clean merge (30/32)
. Let each team add specific criteria on top, whether that's routing convergence for the protocol team or firewall rule validation for the firewall team. Start with an MVP of three criteria, iterate every eight weeks, and add requirements as gaps surface. Use a color-coded value stream map to see green, yellow, and red across all teams. (31/32)
That way, the next time a firmware update ships, you'll see the gap before deployment instead of after 46 data centers go offline and your $380,000 bill arrives.
#Lean #DefinitionOfDone #VisionDriven #Agile #ValueStreamMapping #DevOps #QualityAssurance #TechLeadership #EmbeddedSystems #ProductDevelopment (32/32)