Page 389 - CyberSecurityEssentialsEnglish

Staff need early involvement in designing the use. They know the exceptions, the unwritten
routes, and the friction points that do not appear on a process diagram. Involvement does
not mean that everyone holds a veto, but it surfaces practical risks, builds trust, and helps in

choosing what is automated and what stays human. It also reduces resistance to change,
which usually arises from ambiguity and fear rather than from a rejection of technology.

Monitoring the quality of the system must be separated from monitoring the employee. If a

user feels that every interaction is used to assess them personally, they may hide errors,
avoid reporting, or manipulate the indicators. Make clear which data you collect, why, who
sees it, and how long you keep it, with protection for reporting and learning channels.

New roles also appear: knowledge owner, output evaluator, test designer, agent supervisor,

assurance specialist, and translator between the domain and the technology. Not everyone
needs to become a developer, but the organization needs learning paths that let domain
experts influence system design rather than leaving technical decisions disconnected from

professional reality.

Leading Change and Culture
A responsible culture allows people to say “I do not know” and “the system was wrong”
without fear. If an organization rewards only fast adoption, problems will be hidden. And if

it penalizes every experimental error, learning will stop or move into the shadows. Teams
need a controlled space to experiment, clear limits, a way to report near misses without
blame, and real consequences for negligence or for deliberately going around the rules.

Leaders must model disclosure and review. When a manager uses an automated output in

a decision or a presentation, they should ask about the source, the assumptions, and the
limits, rather than requiring that only staff comply. Exaggerated messages such as “we will
automate everything” or “the tool will change no job” should also be avoided; both weaken

trust. Honest communication states what we know, what we do not, and what we will
measure.

? Question to consider: how will the next generation learn?
Which tasks are the ones through which a newcomer learns in your organization? If they
were fully automated, how would the next generation build the capability needed to

review the system’s outputs?

● Remember: Section summary
• Key idea: The question is not what the machine can do, but how work is redesigned so
that human capability grows.
• Practical decision: Protect the tasks through which people learn, and name the
responsibilities that must stay with a person.

388