Name the workflow
You pick a single repeatable field-service workflow to build first and state plainly why the others wait.
Help me pick the one field-service workflow this pack builds first, and write the decision down. Start by asking me for my list of candidates. Do not suggest candidates yourself — wait for mine. For each one I name, ask me: how many times it happens in a normal week, who does it today, what the finished thing is at the end, and whether it currently runs through the live worker, the temporary twelve-field form, or neither. Then apply this decision rule and show your working: 1. Does it run several times a week with roughly the same shape each time? 2. Can a person look at the finished result and tell whether it is good in under a minute? 3. Can one full run be done without writing over live job data? Pick the candidate that clears all three. If two clear all three, pick the one operators already do by hand today, because the comparison is free. If nothing on my list clears all three, say so plainly. Do not pick the least-bad option. Instead name the single thing I should count or watch this week to break the tie, and tell me to come back with it. If my preferred pick fails the rule, say that once, in one short paragraph, with the reason. If I still want it after hearing you, go with my call and note the risk in the write-up. Finish with a short page I can paste into the next step: the chosen workflow in one line, my answers to the three questions, and one sentence per rejected candidate giving the real reason it waits and what would move it up the list.






