Assignment - Infographics - 079
These instructions serve as general guidelines. Adapt them as needed to suit the specific requirements of the task or creative vision. Avoid following them rigidly without considering the context.
Objective
Create a fishbone diagram in Canva that identifies why students have difficulty understanding a specific subject. Use ICT in Education as your example, or choose any subject from your B.Ed. program that you find challenging.
What is a Fishbone Diagram?
Look up “fishbone diagram” before starting. It is also called an Ishikawa or cause-and-effect diagram. The problem is placed at the fish head (right side), and causes branch off the central spine, grouped by category.
Instructions
Step 1: Define the Problem
Write this at the head of the diagram, filling in your chosen subject:
“Students have difficulty understanding [subject name]”
Step 2: Identify Cause Categories
Use these as your main bones:
- Prior Knowledge: No background in the subject, topic not covered at school level before
- Content Difficulty: Abstract concepts, technical vocabulary, dense theory
- Teaching Method: Only lecture-based delivery, no practical demonstrations, no real-world examples used
- Student Engagement: Passive listening, not practicing questions, not asking for help
- Learning Materials: Textbook is too difficult, no visual aids, limited internet access for self-study
- Assessment Design: Exams test memorization rather than understanding
Step 3: Add Sub-causes
Add two or three specific sub-causes to each category. Draw on your own experience as a student in this subject.
Step 4: Build in Canva
- Use a fishbone template in Canva or build the structure with lines and text elements.
- Problem statement on the right. Main categories along the spine. Sub-causes on shorter branches.
- One color per main category.
Design Tips
- Name the subject clearly in the problem statement.
- Keep each label to a short phrase.
- Use a wide horizontal canvas so all branches fit without overlapping.
Required Elements
- Subject name written in the problem statement.
- At least 5 cause categories.
- At least 2 sub-causes per category.
- Color-coded branches.
Last updated on