1) The document discusses the importance of technical leadership from system engineers in program management. It outlines three roles - management team, SE&I team, and builder teams - that require system engineering leadership to succeed. 2) As a leader, the system engineer must bridge communication across the teams, translate requirements, and make technical tradeoffs. They serve as an integral part of management decisions and influence component implementation by builder teams. 3) Strong system engineering skills like critical thinking, technical knowledge across disciplines, and programmatic understanding are needed to move complex programs forward through leadership, problem solving, and vision setting.

1. PM Challenge
2012
A Call for Leadership
Technical Leadership
is not Optional for System Engineers
John A. Thomas
President-Elect INCOSE (2012)
Senior Vice President & Chief System Engineer
Booz Allen Hamilton
Gary L. Brown (Presenter)
Program Manager, Constellation Technical Support Contract
Principal & Certified Chief Systems Engineer
Booz Allen Hamilton
NASA PM Challenge 2012
Orlando, Florida
February 2012

2. PM Challenge
2012
WANTED
(System) Engineers with Moxie **
** C4ISR Journal, January 1 2010 “Commentary by John A. Thomas”
2

3. Three Roles Required for any Program to Succeed
PM Challenge
− The System Engineer is found in each Role − 2012
Executed by a Management Team
Executed by a SE&I Team • Program Manager
• System Engineer • System Engineer
• Subject Matter Experts • Cost & Schedule Manager
• Engineers & Scientists • Contracts Officer …
• Builder Representatives…
Defn &
Integration Mgt Role
Role
Executed by Builder Teams
• Component Builder
Build • Management Representatives
Component Role (Program Manager)
• SE&I Representatives (System
Engineer …)
3

4. The Systems Engineer Serves As A Leader Who
Bridges Within--And Translates Across--All 3 Teams
PM Challenge
2012
Correlates – Technical
Technical Interpreter Scope with Work
of Requirements Management Team Activities
Architect for
Integration Manager Requirements
& Strategist Driven Design
Systems
Engineer
Sets Technical Brake
Arbitrator for Trades
Vision and Standards
across Components
for Analysis
SE&I Team Build Component Teams
4

5. Leadership (As Exercised By The System Engineer) Is
Critical To The Success Of Each Program Role
PM Challenge
2012
System Engineer – The leader of the SE&I Team
System Engineer – A
leader within the
Management Management team
Team
System System Engineer – A
Engineer leader partnering with
Build the Build teams
SE&I Team Component
Teams
Remember the old saying – “If nobody is following, you ain’t leading”
− What skills and experience will it take to lead within a dynamic like this? −
5

6. SE As A Leader - Peer Within The Management
Team …
PM Challenge
2012
The SE is an integral element of the decision making process balancing delivery risk
against mission capability, cost, and schedule
The Systems Engineer must be knowledgeable in:
• Acquisition & Contract Management
• Technical & Schedule/Cost Management
Management • Conflict Management
Team • Decision Making Methods
• Real World and Life Cycle Support
To be influential, the Systems Engineer must be seen as:
System • A leader who is influencing decisions deemed critical
to users, investors, and implementers
Engineer
• Resulting in acceptable risk of delivery in capability
and performance within investment constraints
• … Whose technical voice is heard as differentiated
counsel as a member of the management team
6

7. SE as a Leader - Partner of the Build Teams …
The SE participates in (local and global) decision making processes, PM Challenge
2012
balancing constraints (as defined by contracts) of a builder and the needs of
the system design
• The Systems Engineer must be knowledgeable in:
• Implications from allocation of system design to
builder teams
• Internal dynamics/strengths/weaknesses within and
across builder teams
System • Limitations imposed by builder contracts
Engineer • Conflict management and communication techniques
• To be influential, the Systems Engineer must be seen as:
Build • A leader who is influencing component
implementation decisions consistent with system
Component baselines
Teams
• Resolving issues within the scope of the component
implementation contracts
• … Leveraging the esteem of builders as an SE who is
1. technically competent; 2. thinks about the win/win;
and 3. ensures equitable and fair treatment to all
voices
7

8. SE as a Leader - Visionary within the SE&I Team …
The SE leads decision making, trading requirements across the PM Challenge
2012
system and its interfaces -- resulting in an implementable, mission
relevant capability
• The Systems Engineer must be knowledgeable in:
• Mission domain & mission operations
• Development lifecycles appropriate for the system and
its components
• Design and integration methods
System
Engineer • Breadth of multi-disciplinary skills required to define,
analyze, and build a system
• To be influential, the Systems Engineer must be seen as:
• A leader who is driving technical decisions in context
SE&I Team with real world constraints
• Ensuring data (for contract packages and decision
making) has integrity and consistency
• … Inspiring and focusing teams to produce and
integrate data (technical and programmatic) within the
timelines needed of program planning and execution
cycles
8

9. The Skills of a System Engineer are Critical for Moving
Program Decisions Forward:
PM Challenge
2012
Problem Solver
Craftsman
Critical Thinker,
Processes, System Thinker,
Methods, Associative Thinker
Techniques, Ability for Abstraction
Tools Skills of a
System Engineer with Moxie
Environmental
Functional Understanding
Depth as well as Tailor Development Lifecycles,
Multidisciplinary Knowledge of Technologies,
Breadth Knowledge of Mission,
Knowledge of Domains
Programmatic Leadership
Understanding
Presence under Stress,
Acquisition Planner, Conflict Manager,
Contract Planner, Decision Maker,
Cost Estimator, Communicator,
Schedule Estimator Team builder,
Visionary,
Mentor
9

10. Example of a System’s Problem That Required System
Engineering Leadership to Resolve – Needed to Determine
an Attitude Solution for Early Stages of ISS Assembly PM Challenge
2012
ISS XVV Z-Nadir Attitude
10