R6-02 & R6-03 — Quick Overview
What They Are
Two technical specifications that formalize the R6 organizational alignment methodology, developed by IOD Ingénierie since 2006.
They are structured according to the ISO Harmonized Structure—the same architecture as ISO 9001, 27001, 42001, and 14001. They are auditable, can be integrated into any integrated management system, and are designed to work regardless of who conducts the engagement.
Why Two Documents
Because there are two parties in an alignment engagement, and each has its own requirements.
R6-02 is for the consulting organization—the firm or consultant conducting the engagement. It specifies how to scope, collect data, analyze, report, and support implementation. It is the practitioner's "how to do it."
R6-03 is for the client organization—the company engaging in the process. It specifies how to receive the diagnosis, build the action plan, integrate the alignment cycle into day-to-day governance, and become autonomous. It is the executive's "how to use it."
The two documents mirror each other point by point. R6-02 tells the consultant to transfer competencies; R6-03 tells the organization to acquire them. R6-02 requires interview anonymity; R6-03 requires leadership to guarantee it.
What's Inside
R6-02 — Consultant Side
- Scoping: three intervention scenarios (coherence diagnosis, transformation, targeted reinforcement), engagement letter, respondent sampling.
- Data collection: standardized critical incident interview protocol across all three S-O-I levels (Strategic, Organizational, Individual).
- Analysis: incident coding, double coding, mandatory S-O-I triangulation, misalignment mapping.
- Reporting: structured report, action plan co-construction with the leadership team.
- Ethics: diagnostic objectivity, guaranteed anonymity, non-normativity (no "correct" absolute level), acknowledgment of competency boundaries.
- Joint engagements: framework for cooperation with specialized partners (DATA/AI, security, environmental management).
R6-03 — Organization Side
- Governance: executive sponsor, alignment lead, integration into existing governance bodies (no additional committee).
- Diagnosis: organization obligations during data collection (access, time, no pressure on content), formal validation of the alignment profile.
- Alignment plan: misalignment prioritization, S→O→I sequencing (clarify strategy before reorganizing, reorganize before training), resource allocation.
- ISO integration: the R6 cycle plugs into an existing management system clause by clause—not a parallel apparatus.
- Maintenance cycle: recommended cadence (comprehensive diagnosis every 18–24 months, streamlined checkpoints every 6 months), progressive autonomy.
- Specific risks: instrumentalization of the diagnosis, inaction (diagnosis without follow-through), overload, consultant dependency.
What It Is Not
It is not an ISO standard. IOD is not a standards body. These are proprietary specifications—similar in status to what ISO/TS 16949 or the British PAS documents were before formal adoption. They have the rigor and structure of a standard, but they are issued by IOD.
It is not a best-practices guide. Both documents use the verb "shall." They specify verifiable requirements, not suggestions.
It is not an individual assessment tool. The R6 model diagnoses the coherence of the system (strategy–organization–competencies), not the worth of individuals.
Who It's For
- Executives who want to understand why their strategy isn't translating into results, and who need a methodical framework to address it.
- Quality and IMS managers looking to integrate the human and organizational dimension into their management system.
- Organizational consultants who want to structure their diagnostic practice around an auditable framework.
- HR directors and talent development leads who need a competency model articulated with strategy, not a generic checklist.
How to Access
The R6-02 and R6-03 specifications are available in French and English.