Is it a 10-day job?

1. 01How much people time does this process take each week, across everyone who touches it?

   Under 20 hours20 to 60 hours (half a person to 1.5 people)60 to 120 hours (1.5 to 3 people)More than 120 hours
2. 02How many teams does it pass through?

   One teamTwo teamsThree or more
3. 03Could someone explain how it should work in under an hour?

   Yes, and it's written downYes, but it lives in people’s headsNot really. People disagree on how it should work
4. 04Where does the information for it come from?

   Exports, spreadsheets, documents or emailA mix, including reading from live system screensOnly from inside a live system, with no way to export it
5. 05Does the fix need to update SAP or another core system in real time?

   No. The outputs are reports, files, tasks or approvalsA batch upload that a person checks would be fineYes, it must write straight into the core system
6. 06Is there one person who can make decisions about it?

   Yes, and they can give it two hours over the fortnightYes, but they are hard to get time withNo clear owner
7. 07Does your organisation run Microsoft 365?

   YesNo, we use Google Workspace or something elseNot sure
8. 08How long has it been on the list of things to fix?

   Less than three monthsThree to twelve monthsMore than a year
9. 09Has anyone tried to get it fixed through a project?

   No, nobody has askedYes. It was too small to get fundedIt is sitting in a program backlog
10. 10What happens if it is still broken in six months?

    It is annoying, but containedIt costs money or rework every weekIt risks compliance, payroll, safety or customers

0 of 10 answered. Your result appears here when you finish.