Outcome-based education (CO-PO mapping) explained for faculty

Outcome-based education (OBE) is one of the most discussed and least loved ideas in Indian higher education. Faculty encounter it as a spreadsheet to fill in before an NBA or NAAC visit: a grid of course outcomes against programme outcomes, numbers from 1 to 3, and an attainment figure calculated at the end of the semester. Done that way, it adds work and changes nothing in the classroom.

OBE is meant to answer a straightforward question: by the end of this programme, what should a graduate be able to do, and how do we know they can? CO-PO mapping is the tool that connects each course to that answer. This guide explains the process in plain terms, with an example, so faculty can use it to improve courses as well as satisfy accreditation.

The building blocks: PEOs, POs, PSOs and COs

The logic flows downwards. PEOs describe the long-term aim, POs and PSOs describe abilities at graduation, and COs describe the contribution of each course. Assessments measure COs, and CO attainment rolls up into PO attainment.

Writing good course outcomes

Most CO-PO problems start with weak course outcomes. A good CO is specific, measurable and pitched at the right cognitive level. Most institutions use Bloom's taxonomy action verbs to make that level explicit.

• Start with an action verb that can be observed and assessed: explain, apply, analyse, design, evaluate. Avoid 'understand', 'know' or 'learn', which cannot be measured directly.
• State the content the verb applies to: 'Analyse the time complexity of sorting and searching algorithms'.
• Keep the number manageable: typically four to six COs per course.
• Cover a range of levels: an introductory course may focus on remember, understand and apply, while a final-year course should include analyse, evaluate and create.
• Make each CO assessable: if you cannot point to a question, assignment or project that tests it, rewrite it.

Building the CO-PO mapping matrix

The mapping matrix records how strongly each CO contributes to each PO and PSO. The common convention is 3 for a strong (high) correlation, 2 for moderate, 1 for slight, and a blank or dash for none.

Illustrative example: in a hypothetical database management course with four COs, the matrix might look like this. The values reflect faculty judgement for this example only.

Three habits keep the matrix honest. First, justify every 3 with a sentence explaining how the course builds that outcome. Second, avoid mapping every CO to every PO; a course that claims strong links to every PO is rarely credible. Third, check the matrix against your assessments: if CO3 is mapped strongly to design but no assessment asks students to design anything, the mapping is not supported.

Calculating attainment

Attainment measures how well students achieved each CO. Institutions usually combine direct assessment (internal tests, assignments, lab work and end-semester examinations) with indirect assessment (course exit surveys).

1. Tag every assessment item to a CO. Each question or rubric criterion should map to one CO, or at most two.
2. Set a target. For example, the institution may decide that a CO is attained at level 3 if a set proportion of students score above a threshold on items mapped to it. Thresholds are set by the institution and should be documented.
3. Calculate direct attainment for each CO from internal and end-semester components, using the weightage the institution has approved.
4. Add indirect attainment from course exit surveys, typically with a smaller weight.
5. Compute PO attainment by combining CO attainment values with the mapping strengths from the matrix.
6. Close the loop. Compare attainment with targets, record reasons for gaps and actions for the next offering.

The final step is the one accreditation reviewers look for and the one most often missing. An attainment figure with no analysis or action does not show continuous improvement.

Making OBE useful in the classroom

When COs are clear and assessments are tagged to them, faculty get practical information. If CO3 attainment is low across two batches, the problem may lie in how design is taught, in the time allotted, or in how it is assessed. That is a teaching conversation worth having at a department meeting. Sharing COs with students at the start of the course also helps them see what they are working towards.

OBE also gives departments a shared language for curriculum revision. When a board of studies meets to update a syllabus, attainment data across several batches shows which outcomes are consistently weak, which courses carry most of the load for a given PO, and where outcomes are mapped but never assessed. That turns syllabus revision from a discussion of topics into a discussion of abilities, which is the shift NEP 2020 asks for.

• Put COs on the first page of the course plan and the LMS.
• Design at least one assessment per CO that requires students to show the ability, not just recall facts.
• Use rubrics for projects and labs, with criteria mapped to COs.
• Review attainment as a department every semester.

How MSM CampusOS can help

MSM CampusOS helps departments write measurable outcomes, build defensible CO-PO matrices, set up attainment calculations and train faculty to close the loop. See our outcome-based education mapping service and related faculty development programmes. Terms used in this article are also explained in our glossary.