A readiness review should end with a decision the team can defend: proceed with a bounded pilot, resolve a dependency, or stop an unsuitable use case.

Start with a funded decision, not a technology inventory

A platform renewal, a stalled personalization program, or an AI proposal can create urgency without clarifying what should change. Begin with one decision: which communication is appropriate for an eligible customer at a particular moment?

Invite a business sponsor, a journey owner, a data or platform owner, and the people responsible for privacy and operational risk where relevant. Ask each to name the outcome, the constraint they cannot relax, and the evidence they would need to proceed. Record disagreements before discussing tools.

Build a map that includes permission and failure

List the trigger, the data required to interpret it, the source of permission, the eligibility rules, the action, and the feedback event. For every connection, record an owner and what happens when the dependency is unavailable.

A unified customer identifier is not itself permission to use every attribute for every purpose. Capture purpose, data categories, recipients, and retention requirements alongside technical interfaces. The Data Privacy Vocabulary is one optional reference for consistent terminology; adopting a vocabulary is not a compliance determination.

  • Trigger: what event starts the decision, and how fresh must it be?
  • Eligibility: who should never receive the action?
  • Inputs: where are they sourced, and who can access them?
  • Action: who approves changes to rules, models, content, or channels?
  • Fallback: what safe behavior applies if data, consent, or a dependency is missing?
  • Measurement: what event demonstrates exposure, response, and an unwanted outcome?

Illustrative work product: renewal reminder decision

This is a hypothetical example, not a Cognelyra client case or delivery result. A subscription business wants to send a reminder before renewal. The purpose is to help an eligible subscriber understand the upcoming renewal and available support.

The decision record names a lifecycle marketing owner. Inputs are the renewal date, current subscription state, preferred channel, and applicable communication permission. It suppresses cancelled accounts and routes uncertain eligibility to no automated send. Missing permission must not be treated as permission granted.

The measurement record distinguishes eligible accounts, reminders actually delivered, support requests, and opt-outs. It specifies an observation window and flags that a change in renewals alone cannot establish causal impact. A controlled experiment requires a separately agreed design and guardrails.

Use a bounded workshop to expose the gaps

Before the workshop, collect a sanitized journey outline, system list, sample event definitions, and existing decision rules. Use synthetic records until access and contractual requirements are agreed.

A practical 90-minute agenda is: 15 minutes for the decision and success measure, 25 for data and permissions, 20 for failure paths and ownership, 20 for evidence gaps and options, and 10 for the next decision. This is a suggested format; complex estates need follow-up work.

Finish with a readiness decision and acceptance criteria

Avoid a single readiness score that hides a critical blocker. Label each dependency ready, unresolved, or unsuitable, with evidence and a named next action. A missing accountable owner or unresolved permission boundary can block a pilot even if the technical integration is easy.

Accept the discovery output when the sponsor and technical owner can explain the map, each unresolved dependency has an owner, and the proposed next step includes scope, test evidence, exclusions, and a stop condition.

  • Proceed: the bounded use case has agreed owners, permitted inputs, tests, and fallback behavior.
  • Resolve first: obtain missing data definitions, permissions, or operational ownership.
  • Stop or re-scope: the intended action has no defensible value, safe boundary, or feasible delivery path.
The takeaway

The first useful deliverable is a shared decision record and a prioritized dependency backlog. More automation should follow evidence, not substitute for it.

References and further reading

This article presents a general architecture and operating perspective. It is not legal, regulatory, clinical, financial, or professional advice, and the appropriate approach depends on the organization’s context.

Back to top