Rubrics für Concept Maps: Verständnis bewerten statt nur schöne Diagramme

Diese deutsche Fassung ist für Lernende, Lehrkräfte und Teams geschrieben, die Concept Maps nicht nur erstellen, sondern fair beurteilen wollen. Entscheidend ist nicht, ob die Map hübsch aussieht, sondern ob sie tragfähige Beziehungen sichtbar macht.

For orientation, use vollständigen Leitfaden, explore Vorlagenbibliothek and compare structures in Concept Maps vs. Mind Maps. For classroom use, also see Leitfaden für Lehrkräfte; for long-term review, combine it with verteiltes Wiederholen mit Concept Maps.

Useful external references include Concept map, Rubric and the Carnegie Mellon guide to rubrics. They help separate assessment of content, structure, and performance.

"Eine Rubric sollte Propositionen, Hierarchie, Querverbindungen und Evidenz belohnen. Wenn 60 Prozent für Optik vergeben werden, messen Sie Geschmack statt Verständnis."
— Hommer Zhao, Wissenskarten-Forscher

Warum Concept Maps eine Rubric brauchen

A concept map can look organized while still hiding gaps. It can also look simple and reveal strong thinking when the links are precise. Assessment should therefore check 6 signals: focus, accuracy, linking phrases, organization, evidence, and usefulness.

Use the assessment to answer practical questions:

• A map answers 1 clear focus question.
• It uses 15-35 relevant nodes instead of collecting every possible fact.
• At least 80% of important links have labels.
• It includes 2 or more cross-links.
• It can support review, explanation, decision, or action within 5 minutes.

Die 5 Kriterien

Criterion	1	2	3	4
Focus	Missing or vague	Topic is broad	Clear question	Precise question for transfer
Concepts	Many gaps	Core ideas only	Mostly accurate	Accurate and selective
Links	Unlabeled	Some labels	Readable propositions	Causal, comparative, conditional
Structure	Loose list	Basic clusters	Clear hierarchy	Strong cross-links
Evidence	None	Few examples	Good examples	Evidence plus next actions

A score from 15 to 20 points usually indicates a usable map. From 10 to 14 points, the map normally needs clearer links or stronger evidence. Below 10 points, it still works more like a list of terms.

"Fünf unklare Verbindungen durch präzise Verben zu ersetzen verbessert eine Map oft stärker als zwanzig neue Knoten."
— Hommer Zhao, Wissenskarten-Forscher

Drei Vorlagen zum Kopieren

Study map rubric

Focus question
-> key concepts
-> precise linking verbs
-> 2 common misconceptions
-> 2 examples
-> 1 review action

Use this for exams, chapters, and difficult subjects. A strong study map should help someone explain the topic aloud in 3 minutes and rebuild the main branches after 1 day.

Teacher feedback rubric

One strong relationship
One missing concept
One weak link to revise
One transfer question

This keeps feedback short. Instead of writing a long comment, choose 1 visible strength and 1 concrete revision that can be completed in 10 minutes.

Team knowledge rubric

Purpose
-> actors
-> constraints
-> dependencies
-> evidence
-> 3-5 next actions

Use this in retrospectives, onboarding, support analysis, research synthesis, and process improvement. The map should reveal blockers or decisions, not just summarize a meeting.

Einsatz im Lernen, Unterricht und Team

The practical workflow is simple:

1. Write the focus question before mapping.
2. Build a rough draft with 15-30 nodes in 20 minutes.
3. Score the 5 criteria quickly.
4. Improve the lowest criterion first.
5. Test transfer with 1 unfamiliar example.

For students, that may mean mapping a biology chapter, scoring weak links, then using the map for retrieval practice after 1 day, 3 days, and 7 days. For teams, it may mean mapping a slow onboarding process and turning the strongest dependencies into 3 actions.

"Der schnellste Test ist Transfer: Geben Sie 1 unbekanntes Beispiel und lassen Sie es 3 Minuten lang durch die Map erklären."
— Hommer Zhao, Wissenskarten-Forscher

Häufige Fehler

• Rewarding a large map simply because it has 50 or more nodes.
• Giving too much credit for color, spacing, or icons.
• Forgetting the focus question and treating every missing detail as a flaw.
• Leaving links as "related to" instead of using verbs like causes, limits, supports, or contrasts.
• Using the same wording for a study task, a project review, and a research synthesis.
• Scoring once and never asking for a targeted revision.

The best correction is usually small: rewrite 5 weak links, remove 20% of low-value nodes, or add 3 evidence notes.

FAQ

What is a concept map rubric?

A concept map rubric is a scoring guide. A practical version uses 5 criteria and a 1-4 scale, for a total of 20 points.

How many criteria should it include?

Five criteria are enough for most settings: focus, concepts, links, structure, and evidence. More than 8 criteria often slows feedback.

Should visual design count?

Yes, but usually only 10-20% of the score. Readability matters, but understanding matters more.

How many concepts should be in a map?

For many tasks, 15-35 concepts is a strong range. More than 50 nodes often needs sub-maps.

Can teams use this rubric?

Yes. Teams should score purpose, coverage, dependencies, evidence, and action. A useful team map should produce at least 3 next steps.

How often should a map be revised?

One focused revision after each score is enough. For durable learning, review after 1 day, 3 days, and 7 days.

Beginnen Sie mit einer besseren Map

Start with one live topic, one focus question, and the 5 criteria above. Build a draft in the kostenlosen Editor, adapt a layout from Vorlagenbibliothek, and use the rubric before polishing the design. For help adapting the workflow to a class, project, or knowledge base, use Kontakt.