Composition is not a headcount. On the named operator side of an EHR cutover, the questions we ask in week one sound like headcount questions — how many informatics nurses, how many physician champions, how many super-users — and they are not headcount questions. They are asked against the readiness list. Every named seat has to close a cell. If you staff by title without naming the cell, you have a roster and not a team. The composition you sign against in week zero is the composition you read against in week eight, and the one you thin against in week twelve. Three windows, three shapes, one readiness list.
Pre-cutover is the densest window, and the composition is shaped against the readiness list rather than the org chart. The named clinical informatics lead sits on every cell that crosses a workflow, and the named clinical informatics lead is paired, on the parallel-run cell, with the named analytics staff member who will carry that cell through cutover week and into sign-off. Dual-named ownership of the parallel-run cell is not redundancy — it is the named handoff pattern that keeps two functions reading the same cell across the cutover boundary. Physician champions are named against the named workflows they actually run, not against the specialties on the marketing slide. Super-users are named against the units they will be on in week one, not the units they were drafted from. The pre-cutover roster reads as a cell-by-cell ledger, with the named analytics staff member carrying a measurable adoption figure into the cutover period — the same figure the readiness list was signed against on day one. If you cannot read the roster against the readiness list, you do not have a composition; you have a list of titles.
Cutover week changes shape. The composition does not get larger; it gets denser on the floor. Physician champions move from the steering cadence to the unit cadence — they are visible on the clinical floor, walking the order sets with the named frontline operators they paired with in week two. Super-users are physically on the unit, not on a call schedule — the named unit super-user is the named person the floor walks to when the order entry does not match the workflow they were trained against. The embedded FDE liaison is on the floor alongside the named clinical informatics lead, and the two of them are read against the same cell on the readiness list. Analytics staff move out of the reporting lane and into the parallel-run reconciliation lane — the named analyst is reconciling the cell-by-cell data the integration produced against the cell-by-cell data the named frontline operators are recording on paper, and that reconciliation is the cell the readiness list was built to hold. The composition in cutover week is a floor composition: named people, named units, named cells, named handoffs.
The 90-day stabilization window thins the composition, but the shape of the thinning is specific. Super-users step out of floor presence and into unit ownership — the named unit super-user becomes the named owner of that unit's adoption cell, holding the cell against the readiness list rather than walking the floor. Named physician champions move into the named-cell-five review, the Friday read against adoption and integration that is the cell the readiness list was built to surface. The embedded FDE liaison is still on the floor, but the read has changed: the liaison is reading adoption against the readiness list rather than walking order sets, and the change capacity the liaison is measuring against is the change capacity the named client-side owner will hold when the engagement closes. Analytics staff carry the parallel-run cell through the stabilization boundary — the named analyst closes the cell with the same figure they carried into pre-cutover, against the same cell-by-cell ledger. The composition at day ninety is thinner. It is also more named.
The composition fails on a specific shape: too thin to hold parallel-run data integrity and end-user adoption at the same time. The failure mode is predictable, and it is the mode we walk into on roughly half the cutovers we see where the named roster was approved without being read against the readiness list. The trade the team gets pushed into is the trade that loses one of two cells: hold the data integrity in the parallel-run cell and the readiness list drifts on adoption because the named analytics staff are absorbed into reconciliation; hold adoption against the readiness list and the parallel-run reconciliation slips because the named analyst has been pulled onto a reporting lane the named physician champions need. Stable adoption but losing data integrity, or hold data integrity but losing adoption. The two are symptoms of the same root cause: a composition that was approved by title and not signed by name. If the named seat is not on the floor in week one, it cannot close the cell in week twelve.
The composition is the readiness list. Every named seat is a named cell. When you sign against a cutover, sign the composition against the readiness list rather than the org chart, and read the signed composition against the floor in week one. The same composition question shows up on the integration conflict that appears at week three, the same composition question shows up on the 90-day post-go-live walkthrough into cell five, and the same composition question — who is named on the floor and which cell they hold — is also where the frequently asked questions on the FAQ page live. Sign the roster. Walk the floor. Read it against the readiness list on the same Friday.