<--- Score
59. What information do users need?
<--- Score
60. Whom do you really need or want to serve?
<--- Score
61. How do you recognize an objection?
<--- Score
62. How do you recognize an Basic Email Security objection?
<--- Score
63. Is it clear when you think of the day ahead of you what activities and tasks you need to complete?
<--- Score
64. As a sponsor, customer or management, how important is it to meet goals, objectives?
<--- Score
65. Who needs to know?
<--- Score
66. What would happen if Basic Email Security weren’t done?
<--- Score
67. When a Basic Email Security manager recognizes a problem, what options are available?
<--- Score
68. Who should resolve the Basic Email Security issues?
<--- Score
69. What are the clients issues and concerns?
<--- Score
70. What is the smallest subset of the problem you can usefully solve?
<--- Score
71. Are there regulatory / compliance issues?
<--- Score
72. Are employees recognized or rewarded for performance that demonstrates the highest levels of integrity?
<--- Score
73. Are losses recognized in a timely manner?
<--- Score
74. How much are sponsors, customers, partners, stakeholders involved in Basic Email Security? In other words, what are the risks, if Basic Email Security does not deliver successfully?
<--- Score
75. What do you need to start doing?
<--- Score
76. What extra resources will you need?
<--- Score
77. Who defines the rules in relation to any given issue?
<--- Score
78. Are employees recognized for desired behaviors?
<--- Score
79. Who else hopes to benefit from it?
<--- Score
80. What are the expected benefits of Basic Email Security to the stakeholder?
<--- Score
81. Where is training needed?
<--- Score
82. How do you take a forward-looking perspective in identifying Basic Email Security research related to market response and models?
<--- Score
83. Think about the people you identified for your Basic Email Security project and the project responsibilities you would assign to them, what kind of training do you think they would need to perform these responsibilities effectively?
<--- Score
84. How can auditing be a preventative security measure?
<--- Score
85. Did you miss any major Basic Email Security issues?
<--- Score
86. Will Basic Email Security deliverables need to be tested and, if so, by whom?
<--- Score
87. What are the stakeholder objectives to be achieved with Basic Email Security?
<--- Score
88. What is the problem and/or vulnerability?
<--- Score
89. Have you identified your Basic Email Security key performance indicators?
<--- Score
90. Where do you need to exercise leadership?
<--- Score
91. What do employees need in the short term?
<--- Score
92. Would you recognize a threat from the inside?
<--- Score
93. Is the quality assurance team identified?
<--- Score
94. Do you need different information or graphics?
<--- Score
95. Do you need to avoid or amend any Basic Email Security activities?
<--- Score
96. What are your needs in relation to Basic Email Security skills, labor, equipment, and markets?
<--- Score
97. Consider your own Basic Email Security project, what types of organizational problems do you think might be causing or affecting your problem, based on the work done so far?
<--- Score
98. Who needs budgets?
<--- Score
99. What are the minority interests and what amount of minority interests can be recognized?
<--- Score
100. Who needs to know about Basic Email Security?
<--- Score
101. Are controls defined to recognize and contain problems?
<--- Score
102. Will a response program recognize when a crisis occurs and provide some level of response?
<--- Score
Add up total points for this section: _____ = Total points for this section
Divided by: ______ (number of statements answered) = ______ Average score for this section
Transfer your score to the Basic Email Security Index at the beginning of the Self-Assessment.
CRITERION #2: DEFINE:
INTENT: Formulate the stakeholder problem. Define the problem, needs and objectives.
In my belief, the answer to this question is clearly defined:
5 Strongly Agree
4 Agree
3 Neutral
2 Disagree
1 Strongly Disagree
1. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
2. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
3. Is it clearly defined in and to your organization what you do?
<--- Score
4. Does the team have regular meetings?
<--- Score
5. What is out of scope?
<--- Score
6. What would be the goal