LeadMastery mode

Governing AI-Assisted Discovery Before the Team Normalises It

A lead-owned Discovery Norm Map — paste, recap, pack, escalate — before habits become law.

Ihor NesterenkoIT System Analyst5 min read · Sep 14, 2026
Policy was still in review. The team's habits were already law. AI-generated cover image — Author.
Policy was still in review. The team's habits were already law. AI-generated cover image — Author.

Most delivery organisations ask for an enterprise AI policy before anyone "officially" uses generative tools in discovery. The requirement sounds responsible. The reality on a hot programme is different. By the second week, someone has pasted a client sample into a chat model, a Copilot recap is already the unofficial minutes, and a fluent discovery pack is circulating as if the workshop closed. Legal's deck is still in review. The team's habits are already the working standard.

That gap is where lead governance either arrives on time — or arrives after normalisation has already voted.

Normalisation — How Silence Becomes Policy

Call the failure mode Silent Normalisation: AI-assisted discovery becomes "how we work" without a named provisional rule, because nobody owning the loop said otherwise.

If the phrase is new, keep this version: delay is not neutral. Delay elects the fastest paster as legislator.

I watched it on a logistics ERP discovery. Monday: junior analyst pastes ASN samples "just to structure the questions." Wednesday: workshop Copilot notes land in chat and get forwarded unchallenged. Friday: the pack looks complete — process boxes filled, decisions tidy — and the sponsor asks when build starts. Nobody was malicious. Nobody owned the verification loop either. Two weeks later, "everyone uses Copilot now" was the only policy the room could cite.

Governance playbooks are blunt that without clear roles and policies, risk management becomes subjective across the organisation. You do not need a forty-page deck to hear that. You need a lead who refuses to leave the subjectivity unnamed while the deck is unfinished.

Anticipate the pushback: "We are waiting for Legal." Waiting is a choice. It preserves the fiction that nothing is happening while the paste already happened. Personal habits help one analyst. A team paste agreement helps at the moment of commitment. Neither binds the whole discovery loop unless a lead maps them together and says: this is provisional law until superseded.

The Discovery Norm Map

Call the instrument a Discovery Norm Map: a dated, lead-owned one-pager that covers four lanes of AI-assisted discovery — paste, recap, pack sign-off, escalation — before the team invents informal versions of each.

Plain version: one page, four lanes, named owner, review date. Not a policy programme.

Lane 1 — Paste. What may enter a model, under what scrubbing, with whose sign-off. This is where a team paste agreement lives. Personal habits before policy still matter for the analyst modelling the bar — the map makes them team-visible, not private virtue.

Lane 2 — Recap. AI meeting summaries are claim sheets, not minutes. Absentees run a Claim Sheet Pass before building. People who were in the room still refuse Recap-as-Record for decisions that will shape the backlog. Vendor guidance itself says validate before you act.

Lane 3 — Pack sign-off. Fluent AI-assisted discovery packs get three examinations — source, silence, commitment — before the workshop is treated as decided. Trustworthy requirements practice is clear: AI proposes; engineers verify, and stakeholder evidence must stay attached. The map points to that critical-thinking audit; it does not re-teach it.

Lane 4 — Escalation. When transcript is missing, when Legal blocks a recording, when a constraint sits above the team — stop and name the owner. Habit without an escalation lane becomes moral pressure. Escalation without a date becomes theatre.

The holistic picture is the point. Paste alone leaves workshop recaps ungoverned. Recap checks alone leave client context unprotected. Pack audits alone arrive after the junior already pasted. Escalation alone is a poster. Four lanes on one page is the lead's job: bind the loop before Silent Normalisation finishes the vote.

Keep the page ugly and short. Scope of discovery work covered. Tools in use (named, not "AI"). Excluded uses. Review date within thirty days. Accountable lead. That shape matches short responsible-AI team sessions that end with owners and a next review — not with deployment authorisation.

One Week to Install

Experience, not theatre.

Day 1. Draft the four lanes in a shared note. Put your name and a review date. Tell the team it is provisional — supersedes nothing Legal will later require; binds desk practice now.

Day 2. Paste lane: circulate or reuse the five-line agreement. If none exists, write it before the next paste.

Day 3. Recap lane: announce Claim Sheet Pass as the absentee standard; ban forwarding raw AI notes as minutes.

Day 4. Pack lane: name who runs source/silence/commitment before any "workshop closed" email.

Day 5. Escalation lane: list two stop conditions (no transcript; client data without scrub). Dry-run one of them in standup.

By Friday the map exists. It will be incomplete. Completeness is not the goal. Naming the lanes before habits harden is the goal. Generative AI risk profiles treat govern as a lifecycle function, not a once-and-done slide. Your one-pager is the smallest govern artefact that still changes Friday's paste.

Where the Lead Map Stops

The Discovery Norm Map does not replace Legal, InfoSec, records retention, or a formal AI policy when the organisation requires one. It does not authorise a pilot. It does not settle model procurement. It does not replace Spoken Accept when two people are live on a review and one is prompting.

It answers a narrower question: while those artefacts are unfinished, what is this team's provisional law for AI-assisted discovery?

When Legal's deck lands, supersede explicitly. Date the map "retired." Do not leave two competing standards. When InfoSec owns tool approval, the map defers — and still owns verification behaviour the tool approval will never write.

The lead who waits for perfect policy arrives after Silent Normalisation. The lead who publishes a dated four-lane map arrives while the vote is still open.


Publish the map while the habits are still soft — or inherit the habits the room already voted in.

Related

← Back to hub