In Systems
I do not work on systems from the outside. I enter them.
I pay attention to how they are lived, where tension gathers, and what allows them to hold.
This page is an atlas of systems I have been part of, with named entries for the shifts that became visible from within.
QVC
Jan 2018 - Nov 2018
I was hired as a release engineer, but what I was actually doing was staying with system strain long enough to understand it from within.
This is where I first recognized that strain in a system rarely comes from lack of effort. It comes from how that effort is organized—and whether the system can hold coherence, or asks individuals to carry it instead.
QVC
I was hired as a release engineer, but what I was actually doing was staying with system strain long enough to understand it from within.
This is where I first recognized that strain in a system rarely comes from lack of effort. It comes from how that effort is organized—and whether the system can hold coherence, or asks individuals to carry it instead.
Understanding the System
The system operated at the intersection of speed, coordination, and constant visibility. Releases moved through tightly coupled timelines, with multiple teams—engineering, QA, product, and program—working in parallel but not always in sync.
Day to day, this meant navigating shifting priorities, last-minute changes, and dependencies that only became visible once something was already in motion. Much of the work relied on individuals holding pieces of the system in their heads—tracking what was moving, what was blocked, and what might break—rather than the system itself making that visible.
There was a strong sense of urgency around delivery, but less structural support for how decisions traveled across teams or how trade-offs were made collectively. Tension showed up as accumulation—misaligned expectations, repeated rework, and coordination gaps that had to be manually bridged each time.
As I stayed with it, what felt like chaos revealed itself as unheld complexity. Different teams were operating with different definitions of readiness, completion, and risk. Work was moving, but alignment wasn’t being carried with it.
Communication was happening, but it wasn’t always landing with shared meaning. The same update could be interpreted differently depending on where someone sat in the system. Issues surfaced late—not because they were invisible, but because they weren’t being held in a way that made them collectively actionable early.
The system depended heavily on individuals to maintain coherence—connecting dots, surfacing risks, translating across teams—rather than coherence being embedded into how the system functioned.
Impact of Presence
As the work moved through the system, coherence began to shift from something individuals had to carry to something the system itself could hold.
Alignment became more explicit—shared definitions, clearer visibility into dependencies, and earlier surfacing of risks before they compounded. Instead of coordination happening reactively, it began to happen as part of how work moved.
Conversations that were previously fragmented started to converge. The right perspectives came into the room earlier, allowing decisions to reflect the system as a whole rather than isolated parts.
I was brought into leadership spaces not because of role, but because I could hold the system in its full complexity and translate what was happening in a way that supported informed decision-making.
The system didn’t become slower; it became steadier. Fewer surprises at release. Less rework driven by late-stage misalignment. More predictability—not through control, but through clarity.
How This Showed Up Across the System
Cross-team alignment & shared meaning
What the system was like: Teams were communicating frequently, but not always with shared understanding. Definitions of readiness, completion, and risk varied across engineering, QA, and program. Alignment depended on interpretation rather than structure.
What became visible: Communication gaps weren’t due to absence, but inconsistency in meaning. The same information traveled differently across layers, leading to delayed recognition of issues and misaligned expectations.
What shifted: Shared definitions and expectations became more explicit. Alignment was carried forward with the work, rather than reconstructed at each stage. Issues surfaced earlier, while still actionable.
Release pipeline & prioritization structure
What the system was like: Multiple teams shared the same release pathways, each with competing priorities and timelines. Coordination often required negotiation or escalation, with no unified structure to hold trade-offs.
What became visible: The pipeline itself was undefined as a system. Without a shared structure, prioritization conflicts were inevitable, and strain was redistributed rather than resolved.
What shifted: The release pipeline became a shared system with visible variables and constraints. Trade-offs could be navigated collectively, reducing conflict and increasing predictability across teams.
Echoes from within
“I know I can trust you to hold complexity, represent what’s happening across teams, and help leadership make informed decisions.”
“You changed the way teams work together here—you’re leaving very big shoes to fill.”
Reflection
Sahana Inc.
Timeframe: [Placeholder]
[Optional reflective bridge placeholder: one to two lines.]
Sahana Inc.
[Optional reflective bridge placeholder: one to two lines.]
Understanding the System
[Placeholder: describe the ecosystem, core tensions, and lived system realities.]
Impact of Presence
[Placeholder: describe what changed in the system's functioning and coherence.]
How This Showed Up Across the System
[Surface title placeholder 1]
[Placeholder: describe what became legible about structure, relationships, and system behavior.]
[Surface title placeholder 2]
[Placeholder: describe another manifestation surface and what changed there.]
Echoes from within
“[Placeholder excerpt from within Sahana Inc.]”
“[Placeholder excerpt from within Sahana Inc.]”
Reflection
The Sahana Movement
Timeframe: [Placeholder]
[Optional reflective bridge placeholder: one to two lines.]
The Sahana Movement
[Optional reflective bridge placeholder: one to two lines.]
Understanding the System
[Placeholder: describe the community system context, where care and complexity interacted, and what needed holding.]
Impact of Presence
[Placeholder: describe what shifted toward greater support, alignment, and continuity.]
How This Showed Up Across the System
[Surface title placeholder 1]
[Placeholder: describe what patterns or structural dynamics became visible from lived participation.]
[Surface title placeholder 2]
[Placeholder: describe another manifestation surface and what changed there.]
Echoes from within
“[Placeholder excerpt from within The Sahana Movement.]”
“[Placeholder excerpt from within The Sahana Movement.]”
Reflection
Yahoo
Timeframe: [Placeholder]
[Optional reflective bridge placeholder: one to two lines.]
Yahoo
[Optional reflective bridge placeholder: one to two lines.]
Understanding the System
[Placeholder: describe the structural context, lived pressure points, and how work moved across teams in this system.]
Impact of Presence
[Placeholder: describe the meaningful shifts in coordination, clarity, or system stability.]
How This Showed Up Across the System
[Surface title placeholder 1]
[Placeholder: describe what became visible through relational and structural observation from within.]
[Surface title placeholder 2]
[Placeholder: describe another manifestation surface and what changed there.]
Echoes from within
“[Placeholder excerpt from within Yahoo.]”
“[Placeholder excerpt from within Yahoo.]”