Identify toil and choose when to automate, eliminate, or tolerate it briefly.
Ask five questions: Is it manual? Is it repetitive? Could it be automated? Does it grow as the service grows? Does it lack durable learning or user-facing value? The more yes answers, the more likely it is toil. Do not automate reflexively. First ask whether the task should exist. Some toil is best deleted by changing an alert threshold, removing a brittle approval step, or fixing a service behavior. Other toil should be automated because the underlying need is real. The professional move is to make the cost visible and choose deliberately.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in