What is in scope?
<--- Score
15. Why are you doing Systems health and what is the scope?
<--- Score
16. In what way can you redefine the criteria of choice clients have in your category in your favor?
<--- Score
17. Is the Systems health scope complete and appropriately sized?
<--- Score
18. Is Systems health linked to key stakeholder goals and objectives?
<--- Score
19. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?
<--- Score
20. Who are the Systems health improvement team members, including Management Leads and Coaches?
<--- Score
21. How do you gather the stories?
<--- Score
22. The political context: who holds power?
<--- Score
23. Has a high-level ‘as is’ process map been completed, verified and validated?
<--- Score
24. If substitutes have been appointed, have they been briefed on the Systems health goals and received regular communications as to the progress to date?
<--- Score
25. How do you catch Systems health definition inconsistencies?
<--- Score
26. Is there any additional Systems health definition of success?
<--- Score
27. Will team members regularly document their Systems health work?
<--- Score
28. What system do you use for gathering Systems health information?
<--- Score
29. What key stakeholder process output measure(s) does Systems health leverage and how?
<--- Score
30. How and when will the baselines be defined?
<--- Score
31. Have all basic functions of Systems health been defined?
<--- Score
32. How do you manage unclear Systems health requirements?
<--- Score
33. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?
<--- Score
34. What knowledge or experience is required?
<--- Score
35. Is there a critical path to deliver Systems health results?
<--- Score
36. When are meeting minutes sent out? Who is on the distribution list?
<--- Score
37. Have the customer needs been translated into specific, measurable requirements? How?
<--- Score
38. How do you build the right business case?
<--- Score
39. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?
<--- Score
40. Has/have the customer(s) been identified?
<--- Score
41. Are the Systems health requirements complete?
<--- Score
42. What are the Systems health use cases?
<--- Score
43. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?
<--- Score
44. What scope to assess?
<--- Score
45. Is Systems health currently on schedule according to the plan?
<--- Score
46. Is the improvement team aware of the different versions of a process: what they think it is vs. what it actually is vs. what it should be vs. what it could be?
<--- Score
47. What are the rough order estimates on cost savings/opportunities that Systems health brings?
<--- Score
48. Is it clearly defined in and to your organization what you do?
<--- Score
49. What gets examined?
<--- Score
50. Have all of the relationships been defined properly?
<--- Score
51. What sources do you use to gather information for a Systems health study?
<--- Score
52. Is Systems health required?
<--- Score
53. What is the worst case scenario?
<--- Score
54. What is the context?
<--- Score
55. How was the ‘as is’ process map developed, reviewed, verified and validated?
<--- Score
56. Is the team equipped with available and reliable resources?
<--- Score
57. What are the Systems health tasks and definitions?
<--- Score
58.
