Embedding Systems Engineering Into Organizations

Explore the issues involved in implementing Systems Engineering in an “organization” that is associated with engineered products and wants to or could gain value from the application of Systems Engineering.

Visit our members-only inet page

Working Group Purpose & Mission

Mission:

The mission of the working group is to produce guidance for members of INCOSE on how to embed Systems Engineering into an organization.

The Working group will look at organizations and produce guidance to help ensure that Systems Engineering is done appropriately, in terms of toles, processes, tools and interfaces with other disciplines in order that the value from a systems approach can be achieved. Will need to recognize that given the diverse range of domains, solutions produced and organization types (and the wide potential applications of Systems Engineering) there cannot be any single recommended organizational solution. 

Transformation Enablers

TechOps Domain

10

Members

2024

Established


Chair

Richard Beasley

Co-Chair(s)

Jo Vassallo

Sarah Sheard


Inquiries


Scope

 

The scope of the Working Group is organizations and how best to set them up to do Systems Engineering.  This will rely on and use existing descriptions of how Systems Engineering is done or what Systems Engineering is. 

The range of organizations in the scope of consideration of the working group covers

  • Any domain or solution type, or organization size– all that matters is if the systems approach could be of benefit.  
  • Any level of existing systems capability – from total unawareness to those doing it explicitly (and even well) who want to get better.
  • Varying levels of “cultural” acceptance of the systems approach in principle.

Keenness_Understanding_Grid

The scope covers how Systems Engineering is done inside the organization and so is not limited to just Systems Engineering activities or simply the role of those called “Systems Engineers” – it will consider how the systems approach is a part of the whole, and so consider the integration with the whole organization, including activities that are often not to be considered engineering activities.

Enterprises are not excluded from the scope - but it was felt organization was a broader term.

The term “embed” is taken to mean making Systems Engineering part of the way the organization works and so not be dependent on a particular individual advocate or expert.


Goals

 

The goal of the working group is to thoroughly understand the issue of Embedding Systems Engineering into an organization, and how to tailor both the approach and the organizational implementation to suit.  This will involve exploring:

  • How to determine the level / style of Systems Engineering (and associated description) appropriate to an organization (in any domain / working culture).
  • Barriers / resistance / problems inherent in introducing and embedding Systems Engineering into either a team or a whole organization.
  • Measurement and assessment of the state of Systems Engineering and so the way to identify the next steps to take, and to validate how well changes have been embedded.
  • Advice on implementing changes within the organization.

The WG aims to fill a gap in guidance INCOSE provides.  Most of the current material is aimed at the specifics of "Systems Engineering". The goal of this working group is to go beyond that and provide guidance (to a Systems Engineering advocate / capability owner) on how to achieve the right / most appropriate environment in the organization so that the value of Systems Engineering can be realized.

ESEIOgaptofill

 

Outcomes

    The final product of the WG is expected to be an interactive guide that allows a systems advocate in any organization

  • Determine the state of the organization with respect to systems engineering capability.
  • Understand options regarding appropriate level of Systems Engineering practice needed for the nature of the solutions the organization addresses, and how to communicate / describe the systems approach in an appropriate manner to various parts of the organization.
  • Understand different potential organization constructs that embed systems practice.
  • Identify the most appropriate change or interventions to make on a “journey” to embed Systems Engineering into the organization.
  • This final outcome will take some time to research and then produce – and so the Working Group intends to produce a number of interim reports helping illustrate the issues associated with embedding Systems Engineering.  These will include:

    1. A report on the common themes faced when embedding Systems Engineering – to help any systems advocate / capability owner aware of issues that could apply.
    2. A guide to explaining the “what and why” of Systems Engineering.  This will draw on (the wide range) of existing material / definition produced by INCOSE (and others) and give guidance on the pros and cons of different parts given the different audiences within an organization, and the different levels of understanding and attitude to Systems Engineering that may exist.
    3. Descriptions of measures of the state of Systems Engineering in an organization (equivalent to project leading indicators).
    4. Descriptions and models of different organization constructs that embed Systems Engineering in different ways, and the pros and cons (depending on circumstance) of each.
    5. Guidance on making the changes needed in an organization.

 

In 2025 the planned activities and outputs are:

  1. Conduct an industry-wide survey to help us understand how organizations implement systems engineering practices. The results will guide the activities and products of the working group (survey to be launched in February at IW25 and returned by April 2025).  Either scan below, or §http://www.surveymonkey.com/r/ESEIO 

ESEIOsurveyfeb25

The survey (https://www.surveymonkey.com/r/ESEIO) takes about 25 minutes to complete, and all responses will be kept strictly confidential. Only non-identifiable data may be published by the working group. By participating, you'll contribute to developing guidance that could benefit your organization and the wider systems engineering community.

 

Please feel free to redistribute to colleagues and others in your organization. All responses are due April 1, 2025.

  1. Complete report on themes of problems encountered embedding Systems Engineering.
  2. Review different organization solutions and investigate / consider the different interfaces between systems engineering and other disciplines.
  3. Investigate best / most relevant organization change approaches and investigate factors to decide actions to embed and improve Systems Engineering in an organization – looking beyond the role of a Systems Engineer in organization, recognising the transdisciplinary nature of Systems Engineering.

ESEIOwheredoesSEfit

   5. Gather and recommend best ways to use various descriptions and explanations of Systems Engineering to different organization

State of WG progress and activity at IW 2025

Progress made identifying the problem themes encountered when embedding Systems Engineering.

ESEIOproblemthemes

Three WG sessions at IW 25

  1. An update on the status of WG activity, introduction to potential new members, and discission of details / issues to address in proposed work products.
  2. Session to look at what work from other WGs is relevant – both to address / illustrate the problem themes identified, and to input to the WG product.
  3. Work on initial products – moving them forward and forming writing teams.

A survey will be launched to gather more data on the experience across industries of embedding Systems Engineering into different organizations.

Watch this space for progress reports

Planned Activities

Planned Work Products

The planned work products from the working group are a series of interim reports:

  1. A report on the common themes faced when embedding Systems Engineering – to help any systems advocate / capability owner aware of issues that could apply.
  2. A guide to explaining the “what and why” of Systems Engineering.  This will draw on (the wide range) of existing material / definition produced by INCOSE (and others), and give guidance on the pros and cons of different parts given the different audiences within an organization, and the different levels of understanding and attitude to Systems Engineering that may exist.
  3. Descriptions of measures of the state of Systems Engineering in an organization (equivalent to project leading indicators).
  4. Descriptions and models of different organization constructs that embed Systems Engineering in different ways, and the pros and cons (depending on circumstance) of each.
  5. Guidance on making the changes needed in an organization.

It is intended to produce these products as stand-alone reports, and then communicate / disseminate them by a range of methods – website, webinars, technical papers, articles for SEBoK etc.

These will lead (eventually) to a final outcome which is an integrate portal that will guide the systems advocate / capability manager wanting to embed Systems Engineering.

 

Yammer is INCOSE's social media platform for members. Use your INCOSE-issued Microsoft credential to login and join the conversation. INCOSE credentials are in the form of [email protected] or [email protected].   

Contact Us