Designing 0→1 Systems Inside a Legacy Enterprise

CA Technologies · Principal Product Designer, Entrepreneur-in-Residence · 2017–2019

---

Context

CA Technologies operated one of the largest enterprise software portfolios in the world, heavily concentrated in mainframe and legacy infrastructure systems.

While these products remained profitable, the company faced a structural challenge: its future growth depended on technologies and developer ecosystems that existed outside its core customer base.

The internal incubator was positioned as a space for innovation, but functioned more critically as a mechanism to explore and de-risk emerging technologies without disrupting the existing business.

---

The Problem

Innovation inside the organization was constrained by the success of its legacy systems.

Teams encountered:

• difficulty aligning new technology investments with existing revenue models
• skepticism toward early-stage ideas lacking immediate enterprise validation
• fragmented ownership of innovation across business units
• lack of pathways to take concepts from exploration to productization

The company had technical capability and resources, but no reliable system for building what came next.

---

Intervention

I operated as a foundational design and systems partner within the incubator, working across multiple ventures to shape early-stage ideas into viable product directions.

The focus was not on individual products, but on creating a repeatable approach to 0→1 system design inside a legacy environment.

This required introducing structure into ambiguity, helping teams define not just what they were building, but why it should exist within the company’s future portfolio.

This structure was applied across multiple ventures simultaneously, requiring rapid evaluation of which ideas should advance, which should pivot, and which should be stopped entirely.

Key areas of work included:

• Emerging technology incubation
  Guided early exploration across containers (in their infancy), YAML / no-YAML configuration models, AI-assisted collaboration tools, predictive network monitoring, and IoT systems involving real-world sensors and automation.

• 0→1 product framing
  Translated raw technical ideas into coherent product narratives, defining user value, system boundaries, and potential market fit.

• Founder and team coaching
  Worked directly with internal “startup” teams to improve clarity, usability, and long-term system viability.

• Internal evangelism and alignment
  Presented and advocated for incubator work across the organization, including executive audiences and external conferences, building credibility for non-traditional product directions.

• Risk deconstruction
  Used the incubator as a controlled environment to test technologies that would otherwise be too risky to introduce into the core product portfolio.

---

Constraints

The work operated within:

• a legacy revenue model tied to mainframe and existing enterprise customers
• organizational skepticism toward early-stage, unproven technologies
• unclear ownership of innovation across business units

This created tension between long-term strategic exploration and short-term business priorities, requiring constant translation between experimental work and enterprise expectations.

This also required balancing executive visibility with experimental autonomy, ensuring that early-stage ideas could evolve without being prematurely constrained by enterprise decision-making processes.

---

Outcome

The incubator evolved from a loosely defined innovation effort into a functional system for exploring and shaping new product directions.

Observed outcomes included:

• multiple ventures advanced from concept to viable product direction, with several supporting Series A–level outcomes
• increased organizational awareness and acceptance of emerging technologies, including containers and AI-assisted systems
• stronger alignment between technical exploration and product viability
• establishment of a repeatable model for internal innovation and experimentation

Critically, ideas that would not have survived traditional enterprise scrutiny were able to be explored, validated, and positioned as part of the company’s future strategy.

Teams that previously lacked a path to build new products within the organization were now able to operate with a clearer framework for exploration, validation, and advancement.

---

Result

CA Technologies gained a mechanism to look forward without destabilizing its core business.

The incubator did not replace the legacy portfolio. It created a parallel system for discovering what should come next.

The system shifted from:

“Does this fit our current business?”

To:

“What would it take for this to become part of our future?”

This work established a foundation for thinking about innovation not as disruption, but as structured, intentional exploration within a complex enterprise system.