Decide what to do with a declining task
Choose an appropriate response when technology reduces demand for a task but not all skills in the role.
Month-end close has changed: automation reduced routine invoice coding time by 55%, but exception disputes and vendor questions have doubled. WORKFORCE DECISION What should Priyanka do first? Map routine coding, exception disputes, error review, and vendor explanation as separate tasks before changing roles. Strong. This separates shrinking work from growing adjacent work and reveals which skills can move. Reduce headcount now because the original task takes less than half the time. Weak. It treats task decline as role decline and ignores the growing exception workload. Pause the automation because new disputes mean the tool is probably failing. Weak. Disputes may…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in