Running a programme

Groups #

Put people into groups that match how you actually report — by team, by cohort, by intake. The temptation is one big group holding everyone; resist it for the same reason a school should not put two classes together. Every number you read from a mixed group is an average of two populations and describes neither.

Assigning work #

You assign a module to a group with a deadline. The deadline is the part that does the work: training that is "available" gets done by the people who were going to do it anyway.

The two reports #

They answer different questions and it is worth knowing which you are asking.

• The group view — is the programme moving? Read this weekly. A flat week is something you can still act on; a flat quarter is a report you write afterwards.
• One person's report — what is going on with this individual? Open it when a name keeps appearing at the wrong end of the group view.

Marking #

The principle Carna holds to: the AI suggests, a person decides. Nothing is graded and filed under your organisation's name without a human having the last word. If you are evaluating Carna against a tool that marks silently, this is the difference to test.

Speaking and writing practice #

Practice is in beta. It is worth trying and worth telling your people it is new — ask us where it stands before you build a programme milestone on it.

Getting people in #

The same invites an admin uses. See Adding people with invites.