Lesson 4 of 6
Manage the Work: Owners, Reviews and the Next Cycle
Managing the work means deciding who owns each part of a recurring data cycle and when it happens: collecting, reviewing, acting and checking the next round. For a small team, name an owner, a reviewer and a data steward, set a review date for each cycle, turn every finding into one action with a check date, and keep definitions stable so the next cycle can be compared.
You will make: An owner, reviewer and next-cycle checklist for one workflow.
Builds on: The context you wrote down in lesson 3.
THE METHOD AT A GLANCE
- Name three roles: owner, reviewer and data steward.
- Put the cycle on a calendar: collect, review, act, check.
- Run a short review meeting with a fixed agenda.
- Turn each finding into one action with an owner and a check date.
- Keep the next cycle comparable, and log every change.
Who does what on a small team?
In short: Three roles cover most workflows. On a team of two or three, one person may hold more than one, as long as they know which job they’re doing at the time.
ROLE
Owner
Runs the workflow: sends the forms, chases follow-ups and carries out agreed actions.
Training example: course coordinator.
ROLE
Reviewer
Checks findings before they’re shared: recomputes numbers, reads comments, confirms limits.
Training example: delivery manager.
ROLE
Data steward
Looks after IDs, definitions and access. Approves any change to a definition and logs it.
Training example: operations lead.
What does one cycle look like?
In short: Each cycle has four steps, each with a date and an owner. Put them on the calendar when you plan the program, not after the data arrives.
01 · COLLECT
Intake, exit and 30-day follow-up go out on schedule · Owner
02 · REVIEW
Findings checked within a week of the wave closing · Reviewer
03 · ACT
One change agreed, with an owner and a check date · Team
04 · CHECK
Next cohort compared on the same definitions · Reviewer
One cycle for the training team (illustrative).
How do you run the review meeting?
In short: Keep it short and fixed: what came in, what it shows, what’s missing, and what you’ll do. Thirty minutes is usually enough for one workflow.
- Coverage: who responded and who didn’t. A missing reply stays unknown, not “no”.
- Findings: the numbers, each with its denominator and wave.
- Explanations: what open-ended answers and coach notes suggest, treated as leads, not proof.
- Decision: one change to test, or a decision to keep things as they are.
- Changes to log: any definition, question or access change since the last cycle.
How do you turn a finding into action?
In short: Pick one change your team can actually make, give it an owner and decide in advance how you’ll judge it.
In the training example, several learners say they struggle to find time to practise. That suggests a question to investigate, not a fact about everyone. The team decides to test a short practice session after the next course.
ONE-PAGE ACTION PLAN (ILLUSTRATIVE)
How do you keep the next cycle comparable?
In short: Change the program, not the measurement. Keep the question wording, definitions and timing the same unless there’s a good reason, and record it when you change them.
- Use the same follow-up question and the same definition of “used the skill”.
- Send the follow-up in the same window (day 25–35).
- Record who received the change and who didn’t.
- Keep the old result. Correct errors openly instead of replacing numbers silently.
- Note the staff time the cycle took. If it’s more than the team can sustain, simplify before expanding.
A higher rate in the next cohort would be encouraging, but it wouldn’t prove the practice session caused it. Groups, response rates and circumstances differ. Lesson 5 shows how to define the measure so the comparison is fair.
What should a handover include?
In short: Someone else should be able to run the next cycle from your notes alone.
Keep one page with the roles, the calendar, where each form and record lives, the current definition versions, the change log and any access or IT dependencies. Test it: ask a colleague to walk through the next cycle without asking you.
Where does Sopact Sense fit?
In short: In Sopact Sense, each new cohort’s responses land on the same IDs and definitions, so the comparison is ready when the data arrives. The AI Assistant can compare cohorts and flag response gaps with cited responses, and your own team manages forms, access and changes. The decisions stay with your team.
For Sopact’s full review-and-action method, see The Loop.
Add this to your plan
Open your working evidence plan ↗
Name the owner, reviewer and data steward for your workflow. Put the four cycle steps on a calendar with dates. Write one action plan for your most recent finding, including its decision rule.
Check your reasoning
For the training example: coordinator owns the cycle, delivery manager reviews, operations lead stewards definitions. The practice session is tested on the next cohort with the same 30-day question in the same window. The team keeps the session only if skill use rises and attendance is workable, and records that the groups differ.
Frequently asked questions
How often should we review our data?
Match the review to the decision. If you decide monthly, review monthly; if each cohort is a cycle, review within a week of each follow-up wave closing. A review with no decision attached is usually a sign the cycle is too frequent.
Can one person hold every role?
Yes, on a very small team. What matters is knowing which job you’re doing: running the work, checking a finding or changing a definition. Where possible, have a second person review findings before they’re shared.
What should go in the change log?
Every change to a question, a definition, a survey wave or access: what changed, why, who approved it and from which date. The log lets you explain any break in a trend later.
How do we know if an action worked?
Decide in advance what you’ll check and when, and keep the measurement the same. Even then, a change in the numbers isn’t proof the action caused it; groups and circumstances differ. Lesson 5 covers how to define a measure you can defend.
When do we need IT help?
For system access, integrations or security settings that your team can’t change itself. Record those dependencies in the handover page so the workflow doesn’t stall when someone is away.