synthetic-narrative-plan

To generate synthetic data for stakeholder demos with realistic FLW personas, use a narrative planning approach that replaces generic defaults with named frontline worker archetypes—rockstar, steady, struggling, and new hire—tailored to your opportunity's geographic and language context. This produces a story-driven manifest compatible with downstream synthetic data generation tools.

A synthetic data manifest is a structured configuration file that defines the specific personas, anomalies, and coaching arcs needed for ACE Phase 7 demos. It creates a compelling, followable data narrative for stakeholder review by aligning synthetic data with an opportunity's specific intervention design, app structure, and success metrics.

To add deliberate anomalies to synthetic data tied to real app field paths, author a manifest that seeds 2-4 realistic measurement outliers, missing visits, or photo quality drops. These create visible, reviewer-friendly signals in demo data that highlight specific app field paths for stakeholder review.

Yes, you can create coaching arc transcripts for struggling FLW personas that show a clear improvement loop. The narrative manifest drafts realistic coaching transcripts paired with KPI configurations pulled directly from the opportunity's PDD success metrics, demonstrating anomaly resolution over a specified timeline.

Yes, this synthetic narrative planning approach requires an active ACE Connect opportunity run. It scopes specifically to opportunities where operators need synthetic data aligned with the intervention design, app structure, and success metrics to create compelling, followable demo narratives for Phase 7 stakeholder review.

The best way to scope synthetic data generation to match a specific intervention design and success metrics is to author a tailored manifest that pulls KPI configurations directly from the opportunity's PDD. This ensures the generated data narrative aligns with the app field structure and intervention goals.