Prioritize felt needs using matrix ranking or paired comparisons before verification¶
Strategy · All strategies
Evidence · no claims cited
Description¶
To select the first tentative problem area for a staff development plan, the workbook teaches two group prioritization techniques for felt needs. In matrix ranking, individuals rank needs from high to low and group totals are charted; in paired comparisons, each individual compares every felt need with every other one and the most important item of each pair is circled, with circulations tabulated. The workbook states that "Two ways o ranking felt needs are "Matrix Ranking" and "Paired Comparisons"", and that if the top-ranked need is not verified by data, the next ranked felt need is subjected to the same verification process.
Design Implications¶
Context¶
Requirements¶
- A set of felt needs identified by individuals or a staff development committee
- a group process for tallying individual rankings or paired choices
Constraints¶
- Ranked needs are merely perceived, not data supported, until they pass through the verification step
Target Learners¶
- school and district staff development committees
Target Learning Goals¶
- identify and prioritize educational problem areas for staff development planning
Related Strategies¶
Examples¶
-
Key Sources¶
- Huenecke, Dorothy M.; Stansbury, George W. (1975). A Systems Approach to Staff Development. Georgia State Dept. of Education. https://eric.ed.gov/?id=ED123751
Page metadata
| Field | Value |
|---|---|
type |
strategy |
id |
matrix-ranking-paired-comparisons-needs |
title |
Prioritize felt needs using matrix ranking or paired comparisons before verification |
description |
To select the first tentative problem area for a staff development plan, the workbook teaches two group prioritization techniques for felt needs. |
status |
review |
generated |
by process:wiki-ingest on 2026-09-26 |
trust |
unverified — no one has confirmed this page's content |
sources |
1 — huenecke-1975 |
Frontmatter is the page's machine-readable record — see the Schema & Guide.