Fourteen Program Outcomes, Twelve Course Outcomes: Cutting Without Losing Coverage
An undergraduate Information Systems program is preparing for accreditation. Its 14 program outcomes were written by a five-person committee over two meetings. Reviewing them you find: PO4 ('communicate effectively in written and oral forms') and PO9 ('present technical information to diverse audiences') are near-duplicates; PO7 says students will 'appreciate the ethical and social dimensions of computing', with no observable verb; PO11 ('demonstrate lifelong learning') is assessed nowhere; PO13 and PO14 have no course mapped to them. Separately, a 3-credit course, Database Systems, lists 12 CLOs, each assessed by exactly one exam item; the instructor explains that the list grew by one each year a new topic was added. The accreditation framework expects 8-10 program outcomes, each assessed in at least two courses across the program.
1. You are asked to consolidate from 14 program outcomes to 9. State the criteria that govern a defensible reduction, and show how you would handle PO4/PO9, PO7, PO11, PO13 and PO14.
Read the worked answer
Criteria for a defensible outcome:
- Observable and assessable - an action verb plus a condition plus a criterion, or at minimum a construct that can be elicited by some performance.
- Distinct - two outcomes that cannot be separately attained or separately failed are one outcome; keeping both makes attainment uninterpretable.
- Covered - mapped to at least two courses with real assessments, not merely listed.
- Framework coverage - the set jointly covers the required student outcomes of the accreditation body.
Applying them:
- PO4 + PO9 → one communication outcome. 'Present to diverse audiences' is a performance indicator of communicating effectively, not a separate construct. Write: 'Communicate technical information effectively in written and oral forms to technical and non-technical audiences.' Do not delete the audience element; demote it to an indicator.
- PO7 → rewrite, do not delete. Ethics is a framework requirement. Make it observable: 'Identify and evaluate the ethical, legal, and social implications of a proposed system, and justify a course of action.' 'Appreciate' cannot be assessed and is the most common unassessable verb in programme outcomes.
- PO11 → rewrite or delete, decided by coverage. If it is genuinely required, write 'Locate, evaluate, and integrate new technical sources to address an unfamiliar problem', which a project can evidence. If the framework does not require it and it is implicit elsewhere, cutting it is legitimate.
- PO13 and PO14 → delete only if the construct is fully captured elsewhere. Unmapped outcomes are either aspirational or dead; find out which before acting. If they represent a real stakeholder need, the fix is a course, not a deletion.
The reduction rule: cut only when the construct is fully captured elsewhere or unassessable after rewriting. Never cut to hit a number, and always verify the final 9 against the framework's required outcomes.
2. How many course learning outcomes should Database Systems have? Give the argument, not just a number, and state the rule you would impose so the list stops growing.
Read the worked answer
Target: 5, clustered from the existing 12.
The argument is measurement-theoretic, not aesthetic:
- A CLO is the finest grain at which you can (a) teach something, (b) assess it with a distinct instrument, and (c) attribute attainment to it. A CLO assessed by one item cannot support a claim about a student's competence: single-item error swamps the difference between competent and not.
- With 12 CLOs across a 3-credit course, no CLO gets more than one observation, so the per-CLO attainment figures are noise. Fewer CLOs with 3+ observations each produce defensible numbers.
- Practical cost: 12 outcomes cannot be meaningfully communicated to students, so they do not function as outcomes at all - they function as a topic list in disguise.
Imposed rule:
- Each CLO must map to at most two program outcomes.
- Each CLO must have at least three assessment observations per student.
- A new topic enters as a topic under an existing CLO, or it replaces something. Topics do not automatically become outcomes.
- Each CLO states verb + object + standard.
Mapping the 12: normalisation, query design, transaction/concurrency, data integrity and security, and communicating a schema design. Each absorbs the topics that previously generated a CLO.
3. What do you lose when you cut outcomes, and what safeguard prevents that loss?
Read the worked answer
Three real losses, each with a safeguard.
- Framework coverage. Cutting PO13/PO14 may drop a required student outcome. Safeguard: a traceability matrix from the old 14 to the new 9, with an explicit column for each framework requirement and the new outcome that carries it. Any row that becomes empty blocks the cut.
- Stakeholder intent. Some outcomes exist because an advisory board or employer asked for them, not because the framework did. Safeguard: take the merged set back to the same advisory body that informed the PEOs and record their confirmation. A committee cannot unilaterally delete a promise it did not make.
- Curriculum content. Merging can orphan content that nobody then teaches. Safeguard: convert deleted outcomes into performance indicators or syllabus topics and check the curriculum map afterwards for orphaned content.
Additional risk worth naming: consolidation done fast and without the matrix becomes a cosmetic exercise that produces 9 outcomes covering 11 constructs. The matrix is the control that makes the reduction auditable.