In XSE you are the Primary System of Interest and...
In XSE, you are both the primary system of interest and the individual responsible for maintaining that system—a role referred to as the sustaining systems engineer. Whether or not this responsibility is consciously accepted, it remains yours alone; it cannot be transferred or delegated.
Because you were not the original designer or developer of your system, it becomes essential to intentionally seek understanding of how it operates. This includes recognizing its foundational components, identifying its subsystems, and understanding how they interact to produce overall performance. Without this awareness, it becomes significantly more difficult to operate effectively within your role or to optimize the system you are responsible for.
As the sustaining systems engineer of yourself, your level of understanding directly influences your ability to maintain, refine, and strengthen your system. A lack of clarity can lead to inefficiencies or breakdowns, while increased awareness supports more effective operation and continued development.
An essential starting point is to begin reverse engineering your own system—observing patterns, identifying inputs and outputs, and developing a clearer picture of how your system functions over time. If you remain open to learning and growth, this process can reveal new levels of capability. As your understanding sharpens, you may find yourself able to operate with greater precision, adaptability, and direction—bringing the concept of XSE Flight into practical reality.
...you are the sustaining systems engineer of yourself...
Sustaining systems engineers—often referred to as support or maintenance engineers—play a critical role in ensuring that complex systems continue to operate effectively throughout their lifecycle. This role is not limited to large-scale industries such as aerospace, healthcare, or technology; it also applies at the individual level when you are the system of interest.
As systems increase in complexity, so does the need for ongoing maintenance, adjustment, and refinement. Interconnected components, evolving conditions, and shifting demands require continuous attention to performance, reliability, and overall system function. In the context of your own system, this includes understanding how different aspects of your life interact and influence one another over time.
The responsibility of a sustaining systems engineer becomes most apparent during the operational phase—when the system is active and producing results. This involves monitoring performance, identifying inefficiencies, addressing issues, and making necessary adjustments to maintain alignment with intended outcomes. For the individual, this translates to observing patterns, learning from feedback, and making intentional changes to improve function and direction.
As environments and technologies evolve, systems must also adapt. Sustaining systems engineering includes recognizing when updates, adjustments, or new approaches are needed to remain effective and resilient. This may involve refining habits, adopting new tools, or re-evaluating strategies in response to changing conditions.
Additionally, risk awareness is a key component of sustaining a system. Identifying potential points of failure, understanding vulnerabilities, and taking proactive steps to address them can help maintain stability and reduce the likelihood of disruption.
Ultimately, the role of the sustaining systems engineer is continuous. Whether applied to large-scale systems or to yourself as the system of interest, it involves ongoing observation, evaluation, and refinement—supporting long-term performance, adaptability, and sustained progress.
...even if you shirk your position over your system.
To deny your position does not remove the responsibility—it only removes your control over it. The system will continue to operate, but without intentional direction, it becomes shaped by default rather than design.
Have you been a good sustaining systems engineer of your own life?
When an individual rejects or avoids responsibility over their own system, the effects are not neutral—they compound over time. Without ownership, accountability begins to fade. Decisions become reactive rather than intentional, and outcomes are increasingly shaped by external forces rather than internal direction.
As personal responsibility diminishes, so does a sense of agency. The ability to actively shape one’s path is replaced with passivity, often leading to feelings of stagnation or lack of control. Without deliberate attention, essential aspects of the system—physical health, mental clarity, emotional resilience, and personal growth—may begin to degrade or fall out of alignment.
In the absence of internal guidance, reliance on external influences often increases. Social expectations, environmental pressures, or default patterns may begin to dictate behavior and direction, limiting the ability to operate with independence and authenticity.
Over time, this lack of engagement can lead to stagnation—or even regression—as the system is no longer being actively maintained, evaluated, or improved. Without reflection, adjustment, and intentional effort, the system may struggle to adapt to change or perform at its potential.
Recognizing your role as the sustaining systems engineer is not about perfection—it is about ownership. When you accept responsibility for your system, you position yourself to observe, adjust, and improve. This shift restores agency, supports growth, and allows for more intentional movement toward your goals and direction.
What does it mean to be the Primary System of Interest?
To be the primary system of interest is to recognize that you are both the system and the one shaping it. Your thoughts, inputs, decisions, and actions are not separate from your outcomes—they are the system producing them.
This begins with awareness. You develop a clearer understanding of how your system functions—your patterns, tendencies, strengths, and areas for improvement. With this awareness comes the ability to observe your system more objectively, rather than operating purely on habit or reaction.
From there, responsibility follows. As the primary SOI, you are not only the system—you are also the one managing it. This includes how you maintain your health, direct your attention, regulate your responses, and engage with the different domains of your life. Your level of involvement directly influences how effectively your system operates.
Being the primary SOI also involves continuous refinement. Systems are not static; they evolve over time. Through ongoing learning, reflection, and adjustment, you begin to improve how your system performs under different conditions. This includes setting direction, evaluating progress, and adapting when necessary.
Equally important is the ability to step back and assess. By reflecting on your inputs, decisions, and outcomes, you gain insight into what is working, what is not, and where adjustments can be made. This process supports alignment between your actions and your intended direction.
Ultimately, to be the primary system of interest is to recognize that you are both the system and the agent influencing it. It is a shift from passive participation to active operation—where awareness, responsibility, and intentional action come together to shape your trajectory over time.
...and what does it mean to be the pilot?
To be the “pilot” of a system is to take an active role in directing its course. It means operating with awareness, making decisions intentionally, and guiding the system toward a defined direction rather than leaving it to drift.
In the context of XSE, this role applies both to the systems you build and to the system you are. Whether engineering something new or sustaining an existing system, the systems engineer functions as the pilot—responsible for navigating complexity, adjusting to changing conditions, and maintaining alignment with intended outcomes.
Being the pilot is not about controlling every variable; it is about maintaining command of direction. This includes setting objectives, monitoring performance, making informed adjustments, and responding to feedback as conditions evolve. It requires attention, judgment, and the ability to remain engaged with the system over time.
With this role comes responsibility. Just as a pilot is accountable for the operation of an aircraft, the systems engineer accepts responsibility for how a system performs under their guidance. This includes the decisions made, the adjustments implemented, and the outcomes that follow.
Ultimately, to operate as the pilot is to move from passive participation to active direction. It is the shift from reacting to circumstances to intentionally navigating them—applying awareness, discipline, and decision-making to guide the system toward its intended trajectory.
Apply XSE to your own system to be a Pilot Systems Engineer
Operating as a Pilot Systems Engineer is not simply a matter of perspective—it requires a deeper level of understanding and capability. Within XSE, this level of operation is grounded in the comprehension and application of the 40 Factors of XSE, which together form the complete framework for analyzing, understanding, and optimizing systems.
These factors encompass both the real components of a system—including the integration of mind, body, and spirit, the gateways through which inputs and outputs flow, and the various spheres and domains in which systems operate—as well as the analytical structures used to evaluate and improve those systems. Together, they provide a comprehensive model for understanding how systems function, interact, and evolve.
To operate effectively as a Pilot SE, one must develop working knowledge of how these factors influence one another. This includes recognizing inputs and outputs, identifying relationships between subsystems, and understanding how decisions and actions propagate through the system over time. Without this level of awareness, it becomes difficult to accurately assess or intentionally guide system performance.
Mastery of the 40 Factors does not imply perfection, but it does require engagement. It is an ongoing process of learning, observing, and applying principles in real-world contexts. As understanding deepens, so does the ability to operate with greater precision, clarity, and adaptability.
Within XSE, true operation as a Pilot Systems Engineer is associated with this level of comprehension—where the individual is not only participating in the system, but is capable of analyzing, navigating, and refining it using the full framework. It is through this progression that the role moves from concept to capability.
Take on the role of being a Pilot Systems Engineer
Understanding the 40 Factors provides the framework—but operating as a Pilot Systems Engineer requires applying that framework in real time. This is where the role becomes active.
Rather than approaching life as a series of disconnected tasks, the Pilot SE begins to operate through the system as a whole. Objectives are not set in isolation, but in relation to the different aspects, gateways, and spheres that influence outcomes. Direction becomes more intentional, informed by a broader awareness of how decisions affect the system over time.
Performance is no longer viewed superficially. Instead, the Pilot SE observes inputs and outputs across the system—recognizing how physical state, mental patterns, environmental conditions, and external interactions contribute to overall function. This allows for more accurate assessment and more effective adjustment.
When issues arise, they are not treated as isolated problems, but as signals within the system. The Pilot SE looks deeper—examining relationships, dependencies, and underlying factors that may be contributing to inefficiencies or misalignment. This approach supports more precise and sustainable solutions.
Adjustments are made with awareness of the system as a whole. Rather than reacting impulsively, the Pilot SE evaluates how changes may influence multiple areas simultaneously, allowing for more controlled and intentional course correction.
Risk is also understood more clearly. By recognizing patterns, vulnerabilities, and points of friction within the system, the Pilot SE can take proactive steps to maintain stability and reduce the likelihood of breakdown.
Through this process, improvement becomes structured rather than accidental. The 40 Factors provide the map—but it is through consistent observation, evaluation, and adjustment that the Pilot SE learns to navigate effectively. Over time, this leads to greater precision, adaptability, and control in how the system is operated.
Being a Pilot Systems Engineer and the SOI Simultaneously
To operate as both the Pilot Systems Engineer and the system of interest is to exist in a unique dual role—one where you are simultaneously within the system and responsible for guiding it.
Unlike traditional systems engineering, where the engineer and the system are separate, XSE places the individual in both positions at once. This requires the ability to observe your system with a degree of objectivity, while still operating within it in real time. It is the balance between participation and awareness.
In this role, decisions are no longer external—they are internal actions that directly influence system behavior. Inputs, reactions, and adjustments are experienced and evaluated simultaneously, creating a continuous feedback loop between action and awareness.
This dual position introduces both complexity and capability. Without awareness, it is easy to become fully immersed in the system and lose direction. With awareness, however, you gain the ability to step back, evaluate, and intentionally guide the system with greater precision.
Operating in this way requires discipline, honesty, and a willingness to observe without distortion. It is not about controlling every outcome, but about maintaining clarity of direction while adapting to changing conditions.
Ultimately, being both the pilot and the system is what makes XSE distinct. It transforms systems engineering from an external practice into an internal one—where the individual is not only navigating complexity, but learning to understand and guide it from within.
You are not outside the system you are engineering—you are within it. The question is whether you are operating it intentionally.
