Keep the method, change the record and decision

The collect, review and improve cycle can support different work without forcing it into one questionnaire or one person-level record. Begin with the decision and identify the appropriate units: people, accounts, organizations, applications, sites, events or anonymous response groups.

In the service example, the team needs an account and reporting period to interpret authorized check-ins. An anonymous employee survey would require a different approach. Copying account-level tracking into that survey would undermine its purpose and confidentiality.

Find the course closest to your work

• Membership & networks: member organizations, chapters, events and reporting periods; a small shared core with local questions.
• Case intelligence: participant records, visits, notes and follow-up; appropriate permissions across staff and locations.
• Training & programs: participation, learning and later practice; matching and coverage that support the intended comparison.
• Applications, awards & grants: submissions, criteria, reviewer evidence and decisions; no assumption that automated scoring removes bias.
• Impact & ESG portfolios: organizations, agreements and returns; comparable definitions without combining incompatible results.
• Partners & suppliers: partner, site and handoff evidence; exceptions with an owner and follow-up.
• Customer experience: service moments, feedback and permitted account history; findings connected to reviewed action.
• Employee experience: appropriate anonymous, confidential or identified collection; careful group reporting and action tracking.

Allow local detail without losing comparability

A federation, multi-site service or partner network may need different collection forms. Agree only the core fields needed for shared questions. Define their meaning, period and unit in the dictionary, and document compatible mappings from local fields.

Do not average or sum measures simply because their labels look similar. “People reached,” “attendance entries” and “completed cases” count different things. Keep them separate unless the data and method justify a particular transformation. Record missing data explicitly instead of silently converting it to zero.

Connect useful history without collecting everything again

Reuse suitable contact or registration information, with an update process for changing details. Decide which later surveys, notes and documents should attach to the same record. Keep participant, organization and reporting-period records distinct when they describe different units.

Existing software may remain part of the process. Check export or integration formats, ownership, update timing and error handling before promising that two systems connect automatically. The course plan should explain who maintains these connections as the workflow changes.

Practice and continue

For your workflow, write four entries: the decision; the unit being followed; the few fields needed for comparison; and the access boundary. Name one local question that should remain flexible. Take this into the pilot lesson and test one complete cycle before expanding.