Document Processing A Complete Guide - 2020 Edition. Gerardus Blokdyk

How can the value of Document processing be defined?

      <--- Score

      68. What critical content must be communicated – who, what, when, where, and how?

      <--- Score

      69. How do you gather the stories?

      <--- Score

      70. How do you build the right business case?

      <--- Score

      71. Are all requirements met?

      <--- Score

      72. Has the improvement team collected the ‘voice of the customer’ (obtained feedback – qualitative and quantitative)?

      <--- Score

      73. What scope do you want your strategy to cover?

      <--- Score

      74. Scope of sensitive information?

      <--- Score

      75. Are there any constraints known that bear on the ability to perform Document processing work? How is the team addressing them?

      <--- Score

      76. Is there a completed, verified, and validated high-level ‘as is’ (not ‘should be’ or ‘could be’) stakeholder process map?

      <--- Score

      77. Who are the Document processing improvement team members, including Management Leads and Coaches?

      <--- Score

      78. Is there a clear Document processing case definition?

      <--- Score

      79. What is out-of-scope initially?

      <--- Score

      80. Has your scope been defined?

      <--- Score

      81. What are the Roles and Responsibilities for each team member and its leadership? Where is this documented?

      <--- Score

      82. Are there different segments of customers?

      <--- Score

      83. How is the team tracking and documenting its work?

      <--- Score

      84. How did the Document processing manager receive input to the development of a Document processing improvement plan and the estimated completion dates/times of each activity?

      <--- Score

      85. When is the estimated completion date?

      <--- Score

      86. Will team members perform Document processing work when assigned and in a timely fashion?

      <--- Score

      87. 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

      88. Are customer(s) identified and segmented according to their different needs and requirements?

      <--- Score

      89. What baselines are required to be defined and managed?

      <--- Score

      90. How will the Document processing team and the group measure complete success of Document processing?

      <--- Score

      91. What gets examined?

      <--- Score

      92. How do you manage changes in Document processing requirements?

      <--- Score

      93. Do you all define Document processing in the same way?

      <--- Score

      94. What information should you gather?

      <--- Score

      95. How often are the team meetings?

      <--- Score

      96. Is Document processing linked to key stakeholder goals and objectives?

      <--- Score

      97. What is in scope?

      <--- Score

      98. How and when will the baselines be defined?

      <--- Score

      99. Is there a critical path to deliver Document processing results?

      <--- Score

      100. Is the team adequately staffed with the desired cross-functionality? If not, what additional resources are available to the team?

      <--- Score

      101. Do the problem and goal statements meet the SMART criteria (specific, measurable, attainable, relevant, and time-bound)?

      <--- Score

      102. Are required metrics defined, what are they?

      <--- Score

      103. When are meeting minutes sent out? Who is on the distribution list?

      <--- Score

      104. Is full participation by members in regularly held team meetings guaranteed?

      <--- Score

      105. If substitutes have been appointed, have they been briefed on the Document processing goals and received regular communications as to the progress to date?

      <--- Score

      106. Are resources adequate for the scope?

      <--- Score

      107. What are the compelling stakeholder reasons for embarking on Document processing?

      <--- Score

      108. What is the scope of the Document processing work?

      <--- Score

      109. How was the ‘as is’ process map developed, reviewed, verified and validated?

      <--- Score

      110. What is in the scope and what is not in scope?

      <--- Score

      111. How have you defined all Document processing requirements first?

      <--- Score

      112. Does the scope remain the same?

      <--- Score

      113. Is scope creep really all bad news?

      <--- Score

      114. Does the team have regular meetings?

      <--- Score

      115. Who approved the Document processing scope?

      <--- Score

      116. How do you manage scope?

      <--- Score

      117. What specifically is the problem? Where does it occur? When does it occur? What is its extent?

      <--- Score

      118. What Document processing requirements should be gathered?

      <--- Score

      119. Is special Document processing user knowledge required?

      <--- Score

      120. Has everyone on the team, including the team leaders, been properly trained?

      <--- Score

      121. Is data collected and displayed to better understand customer(s) critical needs and requirements.

      <--- Score

      122. Do you