AI-Native Transformation Framework
Français

Transition Guide — Employees

Transform your role for an AI-native organization.

1. Guiding Principle

Transforming your role in the age of artificial intelligence is a shared responsibility.

You are an active participant in the evolution of your work. The organization is actively committed to creating the conditions for your success:

  • Clear framework
  • Adapted tools
  • Protected time
  • Structured coaching
  • Constructive feedback

The first individual target: your role operates at Level 2 (AI-Integrated), meaning AI is an integral part of your workflows.

Level 2 is the minimum operational requirement.

Progression toward Level 3 (AI-Native) happens gradually, through experimentation and continuous improvement.

For engineering, the target is Level 3 directly via the AI Lab.

The guiding principle is simple:

Move from "the human produces" to "the human defines the specs → the system produces."

This principle elevates the human contribution toward more judgment, more discernment, more strategic value.

2. Transformation Layers

Your transition comprises four transformation layers. Each layer represents a stage of learning and progression.

Your manager supports you through this progression.

Layer 1 — AI Literacy (prerequisite)

You must:

  • Understand what the available AI tools can do and cannot do
  • Know how to use at least one AI tool in a structured workflow
  • Understand the difference between one-off experimentation and reproducible integration

Minimum requirement:

  • Be able to identify at least three tasks where AI can deliver a measurable gain
  • Explain those gains to your manager

Organizational support:

  • Access to necessary licenses
  • Internal documentation
  • AI clinics
  • Technical coaching

Layer 2 — Mapping Your Actual Work

Before any transformation, document your reality.

Describe:

  • What you actually do
  • Time spent on each task category
  • Repetitive or predictable tasks
  • Tasks requiring human judgment
  • Friction points

Objective:

  • Understand before transforming.

The organization supports this step through:

  • Priority clarification
  • Structured discussions
  • Protected time for analysis

Layer 3 — Role Reinvention

For each task category:

  • Should this task exist if AI is available?
  • What part is human?
  • What part can be entrusted to the system?
  • What workflow could be redesigned?
  • What measurable gain can be targeted?

Reinvention is not theoretical. It aims for progressive, observable improvement. The five role evolution patterns — convergence, specialization, elevation, absorption, emergence — can help you diagnose which forces are acting on your role.

Layer 4 — Implementation

You move to action:

  • Build or configure the identified systems
  • Integrate AI into your workflows
  • Measure results
  • Adjust

Every transformation follows a J-curve of adoption:

  • A temporary dip may occur
  • Lasting improvement follows learning

The goal is not immediate perfection. The goal is measurable progress.

2b. Key Steps of the Transition Plan

Your transition brief is built on six key steps.

These steps are not a test. They serve as a shared framework to structure your learning and facilitate coaching.

The organization commits to:

  • Providing concrete examples
  • Offering constructive feedback
  • Ensuring fair evaluation
  • Recognizing progress made

Step 1 — Honest Description of Current Role

Document:

  • Responsibilities
  • Decisions
  • Tasks
  • Time spent

Factual baseline before transformation.

Step 2 — AI-First Vision

Imagine your role in an AI-native organization (the role evolution patterns can help frame this):

  • What tasks disappear?
  • What skills emerge?
  • What human value becomes central?

Step 3 — Gap Analysis

Compare:

  • Your current role
  • Your AI-first role

Identify specific, measurable gaps.

Step 4 — System Design

For each gap:

  • What system can be built?
  • What tool is required?
  • What support is needed?
  • What effort is estimated?

A "system" means a repeatable AI workflow with a clear specification. For guidance on writing effective specs, see the Specification Engineering Guide.

Step 5 — Metrics Definition

For each transformation:

  • Time saved
  • Quality improved
  • Volume increased
  • Errors reduced
  • Turnaround shortened

Metrics serve learning, not punishment.

Step 6 — 30/60/90 Day Plan

  • 30 days: clear mapping, at least one AI workflow active
  • 60 days: 2-3 workflows transformed and measured
  • 90 days: Level 2 demonstrated, gains documented, adjustments underway

Progression is evaluated on trajectory, not on perfection.

3. Transition Plan Quality Rules

A solid plan is:

  • Honest
  • Specific
  • Testable
  • Measured

Evidence facilitates fair and transparent evaluation.

4. Readiness Checklist

Before submission:

  • Actual work documented
  • Three AI opportunities identified
  • Clear understanding of Level 2
  • Concrete systems defined
  • Metrics established
  • 30/60/90 day plan structured

If a point is blocking:

  • Ask for support
  • Identify the element concerned
  • Adjust

5. Evaluation Standard

Progress is evaluated on:

  • Systems built
  • Workflows transformed
  • Gains measured
  • Learning capacity
  • Contribution to the collective

What is not evaluated:

  • Superficial tool usage
  • Experimentation volume without impact
  • Unstructured enthusiasm

6. Diagnosis if Stuck

If you are stuck:

  • Identify the layer concerned
  • Discuss with your manager
  • Use available resources
  • Advance through small iterations, not massive projects

Asking for help is part of the learning process.

7. Support Provided

The transformation rests on a clear organizational commitment.

The organization provides:

  • Adapted AI tools
  • Protected time
  • Manager coaching
  • AI clinics
  • Peer sharing
  • Collaborative review
  • Escalation if structural obstacle

The organization does not provide:

  • A pre-built plan for your role
  • A uniform transformation for everyone

Each role evolves differently.

8. Documentation Standard

Your documents must:

  • Be factual
  • Be measurable
  • Describe concrete systems
  • Be understandable by a third party

9. Boundaries and Vigilance

Avoid:

  • Sacrificing quality for speed
  • Confusing activity with impact
  • Automating what requires human judgment
  • Waiting for the perfect tool

A documented attempt is worth more than cautious inaction.

10. Performance Expectation

You are evaluated on:

  • Plan quality
  • Systems built
  • Gains measured
  • Your ability to learn and adjust
  • Your contribution to the collective culture

The transformation is demanding. It is also a significant opportunity for professional growth.

← Back to home · The reference framework · Manager guide · Glossary