1. Stakeholder Analysis Patrick T. Hester, Ph.D. Assistant Professor Engineering Management and Systems Engineering Principal Researcher National Centers for System of Systems Engineering pthester@odu.edu 757-683-5205 Kevin MacG Adams, Ph.D. Principal Researcher National Centers for System of Systems Engineering kmadams@odu.edu 757-683-5219

2. The Problem Stakeholders lie at the heart of everything we do in systems engineering. Freeman: a stakeholder is someone who "can affect or is affected by the achievement of the organization's objectives" (1984, p. 46). We lack a software tool to help us classify and manage stakeholders 2

3. Stakeholder Classification 3 Stakeholder Typology, adapted from (Mitchell, et al., 1997) 1 Dormant Stakeholder 2 Discretionary Stakeholder 3 Demanding Stakeholder 5 Dangerous Stakeholder 4 Dominant Stakeholder 6 Dependent Stakeholder 7 Definitive Stakeholder 8 Non-stakeholder Power Legitimacy Urgency 1.Dormant (Power, no legitimacy, and no urgency) 2.Discretionary (Legitimacy, no power, and no urgency) 3.Demanding (Urgency, no power, and no legitimacy) 4.Dominant (Power and legitimacy, no urgency) 5.Dangerous (Power and urgency, no legitimacy) 6.Dependent (Legitimacy and urgency, no power) 7.Definitive (Power, legitimacy, and urgency) 8.Non-stakeholder (No power, no legitimacy, no urgency) Undefined Definitive Latent Expectant

4. Stakeholder Attitude Stakeholder's potential for threat to organization HighLow Stakeholder's potential for cooperation with organization High MixedMarginal Low Non-supportiveSupportive adapted from (Savage, et al., 1991) 4

5. The Solution A software tool which can help us to capture stakeholder attitude, classification, and influence Display results in a graphical (network-based) format, as well as a tabular format Key Circle size = Classification Circle color = Attitude Line direction = Direction of Influence Line width = Strength of influence Commander HQ Dept Support Users Admin SPAWAR Staff