Skip to content

Adoption intelligence

Use this guide to interpret aggregated AI-usage patterns by team, function, role, and tenure band. Adoption intelligence reuses the attributed usage graph, but it reports privacy-preserving cohorts, never individual scores. Each result names its signal basis, threshold, time basis, source coverage, and freshness.

Measured cohorts, bounded interpretation

Adoption intelligence is the second projection of the same attribution graph. It reports the measured cohort metrics described on this page. A claim that a signal predicts a later business outcome requires validation against your own outcome data. All figures are privacy-preserving cohorts; there is no individual scoring.

Use this capability

  1. Confirm the relevant connectors are current and review the coverage state.
  2. Choose a cohort dimension and time basis.
  3. Read the signal basis and active-adopter threshold beside the result.
  4. Treat a visibility gap as missing evidence, not low adoption.
  5. Export the signed adoption board pack only after its suppression and access checks pass.

Cohort-only, by design

Adoption intelligence is cohort-only. Venturi reports adoption by group (team, function, role, or tenure band) and applies a strict minimum-cohort rule:

Minimum cohort size: k = 5

No cohort smaller than 5 members is ever displayed. Sub-k cohorts are suppressed and rolled up into their parent unit, and Venturi prevents reconstruction of an individual by differencing across overlapping cohorts. This rule holds on every cohort read path; sharing a view never reveals a suppressed cohort to a recipient.

This is not an on/off toggle. Individual-level adoption views do not exist. An Admin can raise the threshold for your tenant, but no role or setting can lower it below 5, and the floor is enforced server-side across dashboards, API responses, exports, webhooks, board packs, filters, drill-downs, and shared views.

  • No emotion or sentiment inference. Venturi measures usage patterns, not feelings, and performs no emotion inference of any kind.

The cohort-only posture is what keeps adoption intelligence out of profiling entirely. A DPIA template (GDPR Art. 35) and a works-council pack are included in the onboarding diligence pack for you to adapt, so your privacy and works-council reviews start with the right materials in hand.

Access is role-gated and auditable

Adoption views are reachable only through a dedicated Workforce-Data role, assigned to authorized workforce-data reviewers. The role is read-only with respect to attribution and policies, and like every grant in Venturi it is scoped, auditable, and fails closed: if a role is not explicitly granted the workforce-data scope, the views are not reachable.

When a workforce cohort is shared or appears in a report, it re-renders under each recipient’s own access: a non-workforce recipient sees the cohort suppressed or rolled up, and rows outside the recipient’s residency lane stay hidden. Sharing never escalates privilege.

What the signals mean

Every adoption signal carries its basis so you can judge how much to rely on it:

Signal basis What it reflects
Direct Observed usage from request-level events or first-party logs.
Inferred Adoption inferred from attributed activity where direct signal is partial.
Estimated A weaker, clearly-marked signal where coverage is thin.

Adoption is confidence-normalized, and the dashboard distinguishes operational lag from observability lag, so “low adoption” is never confused with “a visibility gap.” If a team looks quiet because a connector is stale rather than because they stopped using AI, Venturi tells you which it is.

Decision evidence

Every program figure carries the assumption it rests on, every readiness signal names its baseline, and the signed adoption board pack preserves the cohort metrics, signal mix, privacy gates, and calculation metadata in a single artifact.

Adopter cut-lines

There is no hidden definition of “active.” Wherever you see a cost per active adopter, a concentration figure, or an adoption trajectory, the surface shows the active-adopter threshold in effect right beside it, labeled by where it came from:

Threshold provenance What it means
Default (illustrative) A starting threshold Venturi ships so the figure is never blank, clearly marked as not yet tuned to you.
Customer-calibrated A threshold you set for your organization, so “active” means what your leadership agreed it means.

Each figure also shows a threshold-sensitivity band: the same number recomputed at the brackets either side of the active line, so you can see at a glance whether the result is robust or balanced on a knife-edge. When you change the threshold, that change is a recorded calibration event: who changed it, the old value, the new value, the basis, and when, so “active” never shifts silently underneath a previously-reported number. Ask “what counts as active?” and the answer is on the slide.

Readiness baselines

The organizational-readiness signal is never a bare “gap.” It is measured against a named, declared expectation baseline; the surface states the baseline’s method, its inputs, and its confidence. Every cell that reads lower than predicted shows you all four values together:

  • the observed value,
  • the expected value,
  • the baseline method that produced the expectation, and
  • the confidence in that expectation.

When an expectation cannot be computed with enough confidence, the cell says so explicitly: an expectation-unavailable state that is visibly different from genuine low adoption and from a k = 5-suppressed cohort. Venturi never invents a gap to fill a cell. The four values reproduce within a stated tolerance from the same data and baseline version, so a reallocation recommendation built on “this function is under-adopting relative to investment” is one you can stand behind when challenged.

Substitution evidence

Tooling gain/loss draws a clear line between a tool declining and a team having switched to an unsanctioned alternative, because those are very different conversations with very different consequences.

A substitution claim is an accusation, so it must be earned

Venturi surfaces “switched to an unsanctioned alternative” only when corroborating shadow-vector evidence supports it, and that evidence is shown with its signal type and confidence (network and shadow signals are capped at 0.70, and that ceiling is on the surface). Without corroboration, you see a decline with cause unconfirmed, and where the drop lines up with reduced observability, Venturi flags possible observability lag rather than implying anyone went rogue. A board never receives an unevidenced shadow-IT accusation from Venturi.

Signed decision record

When you are ready to present, Venturi produces a signed, reproducible adoption board pack, not a dashboard screenshot. Per cohort, the pack bundles:

  • the metric values themselves;
  • the signal-type mix (how many Direct, Inferred, and Estimated signals stand behind each number);
  • the k = 5 suppression manifest: which cohorts were suppressed or rolled up, so the privacy posture travels with the numbers;
  • the confidence-weighting basis and the observability-vs-operational-lag disclosure;
  • the active-adopter threshold and the readiness baseline the figures rest on;
  • the as-of freshness and the graph and version basis; and
  • a tamper-evident signature.

Reproducible, not a snapshot

Because the live graph keeps moving, a screenshot with a date stamp cannot be reproduced or audited later. The board pack can: it is regenerable from the named version, it carries the cohort-only k = 5 privacy gate (it contains no sub-5 cohort and no individual-level data), and its signature lets anyone confirm it was not altered after the fact. It is the artifact your works-council and DPIA reviews (and your board) can rely on.

Putting it to work

  • Find the gaps. See which functions have meaningfully adopted AI and which have not, by cohort. Identify functions that need enablement investment.
  • Track the trajectory. Watch whether adoption is growing, plateauing, or declining after an initial spike, by team, role, and tenure cohort.
  • Tie spend to traction. Combine adoption cohorts with attributed cost to reason about cost per active adopter, so enablement budget follows the teams actually embedding AI.
  • Report to the board. Present cohort-level adoption and program signals with the same confidence and provenance contract as every other Venturi number (every figure with its active-adopter threshold, every readiness signal with its baseline) and export the whole picture as a single signed, reproducible board pack.
Give feedback on this page

Sign in to send feedback. Opens in a new tab.

Copy page details 
Docs feedback: Adoption intelligence
Page: https://docs.venturi.systems/capabilities/adoption-intelligence/