Skip to main content
Workforce LibreTexts

13: Building and Maintaining an IG Culture

  • Page ID
    66734

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\dsum}{\displaystyle\sum\limits} \)

    \( \newcommand{\dint}{\displaystyle\int\limits} \)

    \( \newcommand{\dlim}{\displaystyle\lim\limits} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \(\newcommand{\longvect}{\overrightarrow}\)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \(\newcommand{\ket}[1]{\left| #1 \right>}\)
    \(\newcommand{\bra}[1]{\left< #1 \right|}\)
    \(\newcommand{\braket}[2]{\left< #1 \vphantom{#2} \right| \left. #2 \vphantom{#1} \right>}\)
    \(\newcommand{\braopket}[3]{\left< #1 \vphantom{#2}\vphantom{#3} \right| #2 \vphantom{#1}\vphantom{#3} \left| #3 \vphantom{#1}\vphantom{#2} \right>}\)
    \(\newcommand{\qmvec}[1]{\mathbf{\vec{#1}}}\)
    \(\newcommand{\op}[1]{\hat{\mathbf{#1}}}\)
    \(\newcommand{\expect}[1]{\langle #1 \rangle}\)
    \(\newcommand{\dfn}[1]{\emph{\textbf{#1}}}\)

    \(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)

    Introduction

    An Information Governance (IG) culture exists when people across the organization consistently make decisions and take actions that protect information value, manage risk, and comply with policies—not because they are forced to, but because it is “how we do things here.” In 2026, this culture must adapt to an environment shaped by AI adoption, hybrid work, accelerating regulation, and stakeholder expectations for transparency and sustainability. Change management models such as Kotter’s 8‑Step Process and Prosci’s ADKAR help organizations move from one‑off projects to enduring behaviors. And newer security and risk guidance—like NIST Cybersecurity Framework (CSF) 2.0 with its Govern function—places leadership accountability and culture at the center of digital risk management. [kotterinc.com], [prosci.com], [nist.gov]

    This chapter offers a practical blueprint: how to win leadership buy‑in, design role‑based and gamified training, incent the right behavior, measure progress with simple dashboards, and future‑proof your IG culture for AI‑enabled and hybrid workplaces. We highlight tools and frameworks from ARMA (IGIM 2.1), NIST (CSF 2.0 and AI RMF), Prosci, Kotter, and Gartner to ensure your approach is defensible and current. [todaysgene...ounsel.com], [nist.gov], [nist.gov]


    The Importance of IG Culture

    Policies and tools are necessary, but culture determines whether people follow them in real situations—naming files intelligibly, classifying data correctly, raising incidents quickly, and using AI responsibly. The NIST CSF 2.0 update formalized this reality by adding a Govern function that elevates board and executive accountability, links cyber/IG practices to enterprise risk, and emphasizes roles, policies, and oversight—core cultural mechanisms. [nist.gov], [gartner.com]

    ARMA’s IGIM 2.1 positions culture as the connective tissue across its eight domains (e.g., Steering Committee, Authorities, Support Functions, Procedural Framework, Lifecycle, Architecture, Infrastructure). These domains institutionalize IG in strategy, operations, and behavior—so that change persists after the project team leaves. [todaysgene...ounsel.com]

    The workplace context matters: Microsoft’s 2025 Work Trend Index shows AI is increasingly woven into knowledge work and decision‑making. Leaders report this is a “pivotal year” to rethink operations, while employees expect clear guidance on hybrid collaboration and AI use. An IG culture provides that clarity: who can use what data, with which tools, under which controls, and how we handle outcomes. [microsoft.com], [assets-c4a...zurefd.net]


    Change Management Models and Strategies

    Sustained culture change requires a structured change approach. Two complementary models are widely used: Kotter’s 8 Steps (organization‑level momentum) and Prosci ADKAR (individual‑level adoption).

    Kotter’s 8‑Step Model (organization momentum)

    Kotter’s model sequences actions leaders take to turn vision into collective behavior: create urgency, build a guiding coalition, craft and communicate the vision, remove barriers, generate wins, sustain acceleration, and anchor new norms in culture. The modern “8 Accelerators” emphasize parallel action and volunteer networks that speed change. [kotterinc.com]

    Key implications for IG:

    • Urgency: Use risk and business value to show why IG matters now—e.g., exposure from ungoverned AI or fines from poor data retention. [kotterinc.com]
    • Guiding coalition: Include Legal, Compliance, IT, Security, Privacy, Data, HR, and business units—plus influential frontline “connectors.” [kotterinc.com]
    • Short‑term wins: Demonstrate outcomes quickly (e.g., 30‑day reduction in retrieval time, drop in policy violations) to fund the next phase. [kotterinc.com]
    • Anchoring: Bake IG behaviors into onboarding, performance goals, and procurement criteria (e.g., vendor data retention clauses). [kotterinc.com]

    Prosci ADKAR (individual adoption)

    ADKAR focuses on outcomes each person must achieve: Awareness (why), Desire (choose to support), Knowledge (how), Ability (do it), and Reinforcement (keep doing it). It is effective for identifying barrier points and tailoring communications, training, and coaching by audience. [prosci.com]

    Practical uses:

    • Map roles (e.g., call center agents, data scientists, records coordinators) against ADKAR to plan role‑specific interventions. [prosci.com]
    • Use ADKAR diagnostics to pinpoint resistance (e.g., low Desire because workflows slow down; low Ability due to tooling complexity). [cdn.prod.w...-files.com]
    • Reinforce with recognition, metrics, and manager one‑on‑ones; ADKAR stresses that sustained change needs visible Reinforcement. [prosci.com]

    Overcoming Resistance and Securing Leadership Buy‑in

    Resistance is often rational—people fear productivity loss, unclear rules, or “tool sprawl.” Use Kotter to build momentum and ADKAR to treat root causes (e.g., insufficient Knowledge or Ability). Executive sponsorship is decisive: the NIST CSF 2.0 Govern function calls for formal roles, risk appetite, and policy oversight—mechanisms only leadership can provide. [kotterinc.com], [nist.gov]

    ARMA IGIM 2.1 operationalizes buy‑in with a cross‑functional Steering Committee (including AI oversight), clear Authorities (policies, laws), and Support Functions (training, comms, project management) that enable scale. [todaysgene...ounsel.com]

    Table: Change Management Phases (Kotter + ADKAR)

    Caption: > 13.1: Change Management for IG Rollouts. Mapping Kotter’s 8 Steps to the ADKAR model with specific examples for implementing Information Governance.
    Phase (Kotter) What leaders do ADKAR focus Examples in IG rollout
    Urgency Frame risk/value; set timeline Awareness “Why IG now” brief referencing CSF 2.0 Govern and AI risk. [kotterinc.com], [nist.gov]
    Guiding coalition Form cross‑functional team Desire Invite respected “informal leaders” to shape pilot. [kotterinc.com]
    Vision & strategy Define future state & priorities Awareness → Desire IG North Star (e.g., “Find any record in 2 minutes”). [kotterinc.com]
    Communicate Cascade messages; 2‑way channels Awareness FAQs, office hours, narrative case studies. [kotterinc.com]
    Remove barriers Fix process/tool friction Ability Simplify classification; auto‑apply labels. [kotterinc.com]
    Short‑term wins Show measurable results Reinforcement 90‑day reduction in violations; share leaderboards. [kotterinc.com]
    Sustain acceleration Scale pilots; improve Desire → Ability Expand to high‑risk BUs; refine policy. [kotterinc.com]
    Anchor in culture Bake into routines Reinforcement Tie IG to performance, audits, vendor evaluation. [kotterinc.com]

    Designing Effective Training Programs

    A strong IG culture depends on consistent, role‑relevant learning. In 2026, training must cover policy basics and new frontiers such as AI ethics and data lifecycle in hybrid settings.

    Mandatory vs. Role‑Based Training

    • Mandatory: Annual or semiannual core training on policy, retention, privacy, acceptable use, incident reporting, and AI usage principles (e.g., sourcing, sensitive data handling, and documentation). NIST AI RMF provides the “why” and “how” for trustworthy AI practices across Govern–Map–Measure–Manage. [nist.gov]
    • Role‑based: Tailored modules for data stewards, frontline staff, developers, marketers, HR, and executives; map to risks each audience influences (e.g., developers on dataset documentation; sales on CRM data quality). IGIM 2.1 recommends aligning support functions (training, comms) with program domains. [todaysgene...ounsel.com]

    Gamification, Microlearning, and “In‑Flow” Learning

    Research shows gamification can improve motivation and engagement, but design quality and autonomy matter; overly intense gamification may reduce perceived autonomy and hurt outcomes. Use light‑weight points/badges/quests for practice and feedback, not for coercion. [link.springer.com], [tandfonline.com]

    Microlearning (5–10 minute modules) is now a leading trend in compliance training: it improves retention, fits hybrid schedules, and is easier to update as rules change. Surveys show growing preference for short, targeted lessons; learning industry analyses highlight the cognitive science behind spaced repetition and reduced cognitive load. Embed just‑in‑time tips in the tools where work happens. [trainingindustry.com], [sai360.com], [elearningi...dustry.com]

    AI Ethics and Responsible Use (Approx. 750 words)

    Creating an IG‑aligned culture of responsible AI use requires a curriculum that teaches employees not only what the rules are but how to apply them in daily tasks. The NIST AI Risk Management Framework (AI RMF 1.0) and its 2024 Generative AI Profile provide the backbone for building this capability by defining governance expectations, trustworthy‑AI characteristics, and risk‑management actions across the AI lifecycle.

    1. Establishing Foundations: Roles, Governance, and Accountability
    Training should begin with the RMF’s Govern function, which emphasizes leadership oversight, accountability, and organizational policies. Employees must understand not only the existence of AI policies but the reasoning behind them — including trustworthy‑AI attributes like safety, security, privacy enhancement, fairness, and transparency. The RMF positions governance as an enterprise responsibility, not a technical afterthought, which aligns well with broader IG culture‑building.

    Learners should also understand the basic division of responsibilities across AI roles — creators, evaluators, operators, end‑users, and managers. Each role interacts with different risks; for example, frontline users must follow acceptable‑use rules, while developers must document model assumptions and limitations. This clarity ensures everyone recognizes where they fit into the governance structure.

    2. Mapping AI Use Cases and Understanding Context
    The next layer of training aligns with the Map function, which requires documenting the purpose, stakeholders, data inputs, intended use, and potential harms of an AI system. Employees should learn to complete short “AI Use Case Profiles” capturing this context. These are lightweight but important: they create traceability and prevent the all‑too‑common problem of teams quietly adopting AI tooling without understanding risks.

    The GenAI Profile expands these expectations specifically for generative systems, noting risks like unintended memorization, prompt leakage, and harmful or misleading content generation. Training should give concrete illustrations: for instance, how a genAI tool might inadvertently reconstruct sensitive training data in its outputs when insufficiently constrained. Employees should practice identifying whether a proposed use case lies in a higher‑risk category requiring additional oversight or testing.

    3. Data Protection, Prompt Handling, and Information Controls
    One of the most critical elements involves teaching employees how to handle data when interacting with AI systems. The Generative AI Profile calls out the importance of capturing prompts and outputs (when appropriate and legally permissible), applying data‑minimization principles, and enforcing strict controls around sensitive or regulated content.

    Training must be very explicit here. Employees need rules of thumb like:

    • Never paste customer PII or confidential business information into external or non‑approved genAI tools.
    • Use redaction or anonymization before prompt entry.
    • Use only approved enterprise connectors and internal models for sensitive tasks.
    • Log prompts and outputs in designated systems when policy or risk level requires it.

    Hands‑on exercises should reinforce this: for example, a scenario where an employee accidentally considers pasting unredacted client data and must choose the correct alternative.

    4. Measuring and Evaluating AI Outputs
    Under the RMF’s Measure function, employees must learn how to evaluate AI behavior for reliability, safety, fairness, and security. They don’t need to become data scientists, but they do need to understand red flags and how to escalate them. For example:

    • Outputs that appear discriminatory or systematically skewed.
    • Hallucinated or fabricated factual claims.
    • Results that violate policy, contain unsafe recommendations, or show adversarial manipulation.
    • Signs of prompt injection, jailbreak behavior, or other genAI‑specific vulnerabilities.

    The Generative AI Profile highlights the importance of security and adversarial evaluation for genAI systems. Training should include simple exercises — such as spotting a subtle prompt‑injection attempt or recognizing when a system has drifted into unsafe output territory.

    5. Managing AI Risks and Responding to Incidents
    The RMF’s Manage function emphasizes ongoing monitoring, incident handling, and mitigation. Employees should learn how to respond when something goes wrong: stopping system use, capturing evidence, reporting through established channels, and engaging AI governance staff. Training should introduce an “AI incident taxonomy” so employees know what qualifies — e.g., privacy exposure, harmful content generation, model malfunction, or security anomalies.

    Scenario‑based drills should require learners to walk through the full path: identifying an issue, documenting it, escalating it, and outlining possible mitigations like adding a human‑review step or tightening model constraints.

    6. Human Oversight and Decision‑Making
    Human oversight is a central theme in the AI RMF and essential to IG culture. Training should make clear that AI outputs are recommendations, not authoritative or self‑executing decisions. Employees must know their oversight responsibilities: reviewing outputs for accuracy, applying professional judgment, and documenting rationale when accepting or rejecting system recommendations.

    Managers need an additional coaching layer: how to review team AI use, check for policy compliance, and reinforce correct behavior. They should learn to ask questions like:

    • “Was this AI‑assisted task performed within approved scope?”
    • “Is there sufficient documentation of inputs, decisions, and outputs?”
    • “Did a human apply meaningful review before finalizing the result?”

    7. Documentation and Audit Readiness
    The RMF and AIRC materials emphasize traceability: documenting inputs, versions, evaluations, and decisions throughout the lifecycle. Training should show employees how to maintain required records — such as prompt logs, data lineage notes, approval memos, and evaluation results — so AI use remains auditable and defensible.

    Diagram: NIST AI RMF core showing Govern, Map, Measure, and Manage functions for trustworthy AI.


    This page titled 13: Building and Maintaining an IG Culture was last modified on Fri, 24 Jul 2026 22:32:34 GMT and is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by .

    • Was this article helpful?