Module 03 · 12 minutes

Data Readiness

Check data readiness, model capability, uncertainty, and the choice to build or use an existing service.

Written and edited by Cahyanto Arie Wibowo. Last reviewed 2026-08-24 · version 1.2.

What does “Data Readiness” mean in practice?

Here, Product Thinking asks what Data Readiness changes for the person making, reviewing, or living with a decision. Place Data Readiness inside a workflow you already know. Who provides the input, who uses the result, and who needs to review it? You will turn Data Readiness from an abstract idea into a choice with an owner and a review rule.

A visual model for “Data Readiness” in Product Thinking: relationships matter as much as individual parts.

After this lesson

Here, Product Thinking asks what Data Readiness changes for the person making, reviewing, or living with a decision.
Use the idea of “Data Readiness” to interpret one realistic situation.
Explain the limits of the concept and the information that still needs to be checked.

Start with the situation

Understand the situation first. The label can come later.

A valuable idea can remain infeasible when representative data and feedback loops are missing. This lesson uses the idea of “Data Readiness” to examine that situation without treating a single term as the answer to every problem.

Here, Product Thinking asks what Data Readiness changes for the person making, reviewing, or living with a decision. Check data readiness, model capability, uncertainty, and the choice to build or use an existing service. Connect the term to a decision someone genuinely needs to make.

See how the decision unfolds

Move from the situation to a choice others can review.

Situation

Decision

A valuable idea can remain infeasible when representative data and feedback loops are missing. Identify the part of the situation most closely connected to the idea of “Data Readiness”. Use the case as a thinking tool, not as proof that one solution fits every context.

Review

A vendor demo does not prove performance on your data and constraints. This mistake often appears when a label is used before the problem is understood. Write down your assumptions so another person can review them.

Do not rush the choice

Two ways to look at Data Readiness

Useful when

Here, Product Thinking asks what Data Readiness changes for the person making, reviewing, or living with a decision.
Use the idea of “Data Readiness” to interpret one realistic situation.
Here, Product Thinking asks what Data Readiness changes for the person making, reviewing, or living with a decision. Check data readiness, model capability, uncertainty, and the choice to build or use an existing service. Connect the term to a decision someone genuinely needs to make.

Pause and check

A vendor demo does not prove performance on your data and constraints. This mistake often appears when a label is used before the problem is understood. Write down your assumptions so another person can review them.
Explain the limits of the concept and the information that still needs to be checked.

The stronger choice is the one whose evidence, owner, and limits can be explained, not simply the more sophisticated option.

Visual model

Map the parts before choosing what to do.

A visual model for “Data Readiness” in Product Thinking: relationships matter as much as individual parts.

Read the diagram as a map of Data Readiness: begin with the context, follow the connections, and inspect the highlighted point before making a decision.

Pause for a moment

What evidence could change this decision?

Answer before opening the discussion. Name one fact and one assumption.

Open the discussion

A tempting shortcut

A familiar term can still lead us to the wrong decision.

Why this can seem reasonable

How to check it

Place Data Readiness inside a workflow you already know. Who provides the input, who uses the result, and who needs to review it? Begin with what can be observed, then separate facts, assumptions, and open questions.

Try it on your work

Try it with one small piece of real work.

Choose one real situation related to Data Readiness.
Separate what you can observe from what you are assuming.
Write one decision, its owner, and the evidence needed to review it.
Name the signal that would make you stop or change direction.

Write two examples that fit Data Readiness and one that does not. Explain the difference in your own words. The larger module activity is: Review the feasibility of one AI idea using the evidence available. Keep the first version small enough for another person to review in a few minutes.

Quick practice

Summary

Here, Product Thinking asks what Data Readiness changes for the person making, reviewing, or living with a decision.
Use examples and evidence to test your understanding.
Record the limits, risks, and conditions that should trigger another review.

Continue from here

Model Capability: Continue the idea from Assessing AI Feasibility with a closely related example.
Workflow Decomposition: Connect this lesson to Applied AI and test the idea in another context.
Regression: See how the same decision changes when viewed through Data Literacy.

Sources and further reading

Rules of Machine Learning: Google for Developers · official-guidance. Primary reference for the definition, evidence, or limits discussed in “Data Readiness”.
Data on the Web Best Practices: W3C · web-standard. Further evidence and context for checking the explanation in “Data Readiness”.
Artificial Intelligence Risk Management Framework: NIST · official-framework. Further evidence and context for checking the explanation in “Data Readiness”.