A clearer starting point for the work.

1. Choose a small, recurring problem.

   Describe a specific handoff or decision, such as welcoming a new customer. Note what starts the work and what should happen at the end.

2. Identify the context and its owner.

   List the people involved and the documents or systems they use. Mark assumptions and missing information so they can be reviewed.

3. Agree what better would look like.

   Name a useful result and a way to recognize it. For example, every new customer has a named owner and a reviewed onboarding checklist.

Preparation guidance from GREVVY. Product availability and actual delivery scope are established separately.

1. Describe the result in plain language.

   Explain who will use the result and what it should help them do. Keep the initial scope small enough to review as a whole.

2. Make constraints visible.

   List dependencies, access requirements, timing and ownership. Distinguish requirements from preferences and leave unresolved questions explicit.

3. Write observable acceptance criteria.

   Describe checks a reviewer could perform: a customer can access the workspace, the required tasks are visible, and the owner receives handoff notes.

Preparation guidance from GREVVY. Product availability and actual delivery scope are established separately.

1. Make an inventory.

   Record each relevant system, its business purpose and the person responsible for the account. A tool name alone does not identify the right workspace.

2. Separate the permission decisions.

   Workspace membership, permission to inspect records and permission to change a system are different. Identify who can authorize the specific work.

3. Define the evidence and review.

   Agree which observations can support a finding, who reviews it and how any proposed improvement would be verified. Decide on changes after the assessment.

Preparation guidance from GREVVY. Product availability and actual delivery scope are established separately.

1. Identify the records and their purpose.

   List source record types, their owners and the process they support. Establish which records are in scope before preparing a transfer.

2. Review the mapping and exceptions.

   Map source fields to target meanings, including lifecycle stages and ownership. Flag missing or conflicting values instead of silently guessing.

3. Plan validation and recovery.

   Agree source-to-target reconciliation, exception handling and acceptance checks. Establish what to do if the migration does not meet the agreed result.

Preparation guidance from GREVVY. Product availability and actual delivery scope are established separately.