Lesson 1: Taking a Readiness Position
Lesson 1: Taking a Readiness Position
Module 6, Lesson 1 of 3. About 12 minutes.
Orientation
Every module so far has added a distinction: what a passport is, whether it applies to you, what it has to contain, how it works, when it becomes mandatory. None of that is worth anything until it is turned into a position: a statement of where your organisation actually stands, for one product, that someone senior could act on. Not a slide deck, not a maturity score bought from a vendor questionnaire. A position you can state out loud and defend when someone in the room disagrees with it.
This lesson is about producing that position for the first time. It will feel underpowered compared with the five modules behind it, because a first readiness position is supposed to feel underpowered. It is a starting point, not a verdict.
From Module 5: which parts of your preparation work survive even before a delegated act is published, and which parts wait on it?
Show the answer
The work that is independent of the specification survives: naming a stable identifier, assigning attribute ownership, auditing where data already lives, and starting the supplier conversation. The work that genuinely depends on the specification, mapping to a fixed field list, choosing a data carrier format, building the public facing view, has to wait, because building it early means building it twice. Module 5 treated this as a fact about delegated acts. This lesson treats it as the reason a readiness position can be written honestly today, without waiting for a date that has not arrived.
Learning Objectives
By the end of this lesson you should be able to:
- M6-O1Produce a first readiness position for one product line and defend it.
- M6-O3Identify your single biggest data gap and the evidence for it.
What a Position Actually Contains
A readiness position is not a single number. Readiness is not one thing, and collapsing five different kinds of readiness into a single traffic light is how a steering group ends up confident about the wrong half of the problem. A defensible position names where you stand on each dimension separately: regulatory understanding, data quality, process, technology and organisational ownership. It is entirely normal, and expected, for one product to be strong on one dimension and weak on another.
The position also has to be evidenced, not asserted. “We think our data is roughly complete” is not a position, it is a hope with a sentence structure. “We hold two of the six attribute groups we expect to need in the product data system, one exists only as PDFs on a shared drive with no owner, and three have never been requested from the parties who actually hold them” is a position, because someone else could go and check it.
The common misreading is to treat a readiness position as a maturity score to be improved, like a certification level. It is not that. It is a diagnostic snapshot, written to drive the next three decisions, and it is expected to look worse than people hoped. A position that comes back comfortable almost always means the audit was not done at the level of the individual attribute. Look for the gap you were not looking for, not confirmation of the one you already suspected.
Naming your single biggest data gap is the sharpest test of whether the position is honest. Most organisations can name several gaps in general terms; far fewer can point to one, say why it is the biggest, and cite the evidence that made them conclude that rather than another candidate. The evidence is usually mundane: a count of attributes with no confirmed source, a contradiction between two systems that nobody has reconciled, a supplier who has never once been asked for composition data. Mundane evidence is the strongest kind, because it cannot be argued with the way an opinion can.
A tieback framework describing seven stages of readiness, from awareness through regulatory and product understanding, data assessment, governance, supplier collaboration, team readiness, and a roadmap. Each stage consumes the output of the one before it: governance written before the data assessment governs imagined data, and technology chosen before governance encodes decisions nobody has made.
Use it when you need to state, for one product, which stage you have actually reached rather than which stage you assume you are at because the technology conversation feels advanced.
Where it fails: it will not tell you what your specific attributes are or when your deadline falls. It is a diagnostic lens for sequencing preparation work, not a substitute for the product scoping and data work Module 2 and Module 3 covered.
Read the readiness model section in full, then the data and governance sections. The five dimensions table near the top of the article is the one to keep open while you write your own position.
Read: How Should Organisations Prepare for Digital Product Passports? (15 min read)
Sections that carry this lesson:
- The Digital Product Passport Readiness Model
- Understanding Your Data
- Preparing Product Governance
The article is the source of record. Where this lesson and the article differ, the article is correct.
Regulatory understanding: moderate. The trimmer, the battery pack and the textile strap are known to sit in different regulatory conversations, but nobody owns tracking how each one is progressing.
Data readiness: weak, and this is the biggest gap. Three internal systems hold three conflicting identifiers for the same product. Composition data for the battery pack sits with the contract manufacturer in Vietnam, who has never been asked for it. Of the attributes a passport is likely to need, roughly a third exist in the product data system, a third exist only as PDFs on a shared drive, and the remainder are effectively unrecorded.
Process readiness: weak. No one has a defined route for approving a change to a published attribute.
Technology readiness: comparatively strong. A QR pilot exists and resolves correctly to a page.
Organisational readiness: weak. No single accountable owner exists across product, compliance and IT for the S2 specifically.
The position in one sentence: the S2 has proven it can print and scan a code, and has not yet established who owns its data, where the true values live, or how they would be kept current. That sentence is uncomfortable and it is also the correct starting point for Lesson 2.
Take one real product line. Score each of the five dimensions from the table in the canonical article as strong, moderate or weak, one sentence of evidence for each. Then write, separately, one sentence naming your single biggest data gap and the evidence that makes it the biggest rather than merely a gap.
Keep this. You will sequence actions against it in Lesson 2 and compress it into a brief in Lesson 3.
Knowledge Check
3 questions. Feedback is immediate, nothing is graded, and this does not gate your progress.
Takeaways
- A readiness position names five dimensions separately: regulatory, data, process, technology and organisational readiness.
- It must be evidenced, not asserted: someone else should be able to check each claim.
- Strong technology readiness with weak data and governance readiness is the most common and most misleading pattern.
- Naming your single biggest data gap, with evidence, is the sharpest test of whether the position is honest.
If you remember one thing: a readiness position is a diagnostic snapshot for the next decision, not a score to defend.
Sources
How Should Organisations Prepare for Digital Product Passports?, sections The Digital Product Passport Readiness Model, Understanding Your Data and Preparing Product Governance.
Module 6 · Lesson 1 of 3
Checking this device for saved progress.
Progress is saved on this device.