docs: present AI strategy as a diagram-first story
Build and publish Eldorado documentation / build (pull_request) Successful in 40s

This commit is contained in:
jarvis-at-skic committed 2026-10-04 12:23:41 +00:00
1 parent 7f40de708c
commit 794f2aa2d6
30 files changed
+2496 -4

No files matched your search

+21
View File
@@ -2,11 +2,28 @@
id: skills-adoption
title: Skills adoption
description: Workflow-led coaching, client choice, feedback, manual path.
hide_table_of_contents: true
---
import ArchifyDiagram from '@site/src/components/ArchifyDiagram';
<div className="strategy-content">
**TO-BE · Target operating model — not installed controls or company results.**
## When should a pilot become a team workflow?
Expand only when a bounded canary produces independently accepted work and useful feedback. Teach people to verify artifacts and recover without AI, not merely invoke a skill.
<ArchifyDiagram name="strategy-adoption" title="Choose a workflow, coach a canary, verify outcomes and improve before expansion" story />
- **Team-led:** the departmental owner defines the outcome; People &amp; Administration Squad supports learning.
- **Choice within support:** qualify the client path instead of promising identical agent behavior.
- **No adoption quotas:** retain a manual path; rejected suggestions and non-use are feedback, not poor performance.
<details>
<summary>Onboarding responsibilities, coaching and feedback safeguards</summary>
**TO-BE · Target operating model.** Introduction depends on the [roadmap gates](./roadmap.mdx); these pages do not describe installed controls or measured company results.
Start with a small set of useful workflows chosen by the existing teams. Product Management and the departmental owner identify the outcome; Data & AI helps turn it into a skill; Quality Engineering establishes acceptance; Platform & IT qualifies the client path; Architecture & Security clears the data boundary. People & Administration Squad coordinates learning and accessible feedback.
@@ -17,4 +34,8 @@ Use short worked examples, peer pairing, office hours and a clear catalog search
No developer rankings, individual productivity scores, minimum invocation quotas or inference of effort from token counts are part of this strategy. Report cohort-level evidence with privacy protection and balanced quality, flow, risk and cost. A participant may reasonably stop using a skill that creates more work or uncertainty.
</details>
**Next:** [Measure accepted outcomes, not activity →](./measurement.mdx)
</div>