Playbooks
How do I run a CluedIn project?
Project leads, delivery teams and consultants.
Delivery methodology rather than product reference: how to scope a CluedIn project, sequence the work, and get to production. Playbooks link to the product documentation for the mechanics.
In this section
- Project deliverysectionHow to scope and run a CluedIn project: what to decide before you start, how to sequence the work, and what has to be true before you go to production.
- Data ingestion playbooksectionHow to decide what to ingest and in what order.
- Data engineering playbooksectionWhere CluedIn sits in a wider data architecture, and how far you should extend it before you should build around it.
- Data transformation playbook how-to
- Data export playbook how-to
- Resources for Data Steward reference
- Go live in 14 days with CluedIn — step‑by‑step playbook how-to
- Implement CluedIn with AI how-to
Table of contents
- Project delivery - How to scope and run a CluedIn project: what to decide before you start, how to sequence the work, and what has to be true before you go to production.
- Data ingestion playbook - How to decide what to ingest and in what order.
- Data engineering playbook - Where CluedIn sits in a wider data architecture, and how far you should extend it before you should build around it.
- Data transformation playbook
- Data export playbook
- Resources for Data Steward
- Go live in 14 days with CluedIn — step‑by‑step playbook
- Implement CluedIn with AI