What changes in work, and what still needs judgment
Updated
BeginnerWhat you'll learn
~11 min- Name the difference between software that follows rules and a system that works toward a stated outcome
- Decide which parts of a piece of work stay with a named person
- Ask three questions that show whether a purchased tool has changed anyone's work
You leave this lesson with: a short note naming who decides, who supplies the information and who checks the result, for one recurring piece of work you oversee.
From following rules to working toward an outcome
Most software you have bought follows rules someone wrote down. A payroll system applies the pay rules. A workflow tool routes a form to the next approver. If the rules are wrong or missing, the software does the wrong thing or nothing.
The systems in this course work differently. They are AI tools that write, analyze and, when connected to other software, take actions, from plain-language instructions. You state an outcome in ordinary language, and the system reads material, compares options, drafts a document, writes a program or carries out a sequence of steps toward that outcome. It does not wait for every step to be written in advance.
That is a change in delegation. You can hand over a piece of work without specifying every step. Rule-following software such as payroll needs checks too. With AI, a convincing answer can still be wrong, so decide how results will be checked before people rely on them.
What a person still owns
Four things stay with a person, whatever the system produces.
- The outcome. Someone decides what the work is for and what a good result looks like.
- The boundary. Someone decides what data the system may read and what it may change.
- The check. Someone with the knowledge to spot an error reviews the result before it is relied on.
- The accountability. Someone’s name is on the decision that follows.
A system can draft a grant budget, summarize case files or propose a change to an application. It cannot be the person who answers for the budget, the case decision or the change.
Licenses alone do not show that work changed
A tool that is bought but not wired into how decisions are made, what data is reachable and how output is reviewed leaves the work as it was. Buying licenses does not establish that work improved.
Check what changed in one workflow after the tool became available: the work completed, the checking required and the elapsed time. A purchase record cannot answer those questions.
Why can a purchase leave the work as it was? Data access is limited to protect privacy. Review is slow to protect quality. Decision rights sit high to protect accountability. The leader’s job is to ask who is able to adjust each one for a specific, low-risk piece of work, and how long that takes today.
The sourced adoption figures are in AI-Powered Development, Module 1 Lesson 1.
A department bought seats for a research assistant tool for all its faculty. After the purchase, the principal investigators still send literature searches to graduate students, because the licensing terms limit who may connect the tool to the university’s journal subscriptions and no one owns the request to change that.
The licensing limit protects the publishers’ terms. In that group the seats were not the constraint. Data access was, and nobody held the request to ask what the terms allowed.
Three questions for one workflow
Pick one workflow you are responsible for and ask your team:
- Who may change what the tool can read for this work, and how many days would that take?
- Who reviews the output, and do they have the time and the knowledge to catch an error?
- Before the tool, how many days did this workflow take, and how often did work come back to be redone (its rework rate)? That written record is the workflow’s baseline, and Lesson 2.1 shows how to take one.
A department has bought licenses for every staff member. Which fact best shows that the work has changed?
Key takeaway
- LEADERSHIP DECISION
- Name one workflow and one person who may change its data access, review step and decision rights.
- IMMEDIATE ACTION
- Ask the team the three questions above for that workflow, and record the answers in one line each.
- SUCCESS MEASURE
- Calendar days from request to reviewed result for that workflow, with rework rate no higher than before.