Your class votes on favorite fruit: apple 9, banana 5, grape 7, orange 3. Written as a list, you have to read every number and compare. Draw a bar for each fruit, as tall as its number of votes, and you can see in one look that apple has the tallest bar and orange the shortest. Nothing about the data changed. The picture just makes the pattern easy to see.
Different questions need different pictures. To compare groups, like fruits or pets, use a bar graph with one bar per group. To show how something changes over time, like a plant's height each week, use a line graph: dots joined in order, so you can see the line climb or fall. Every graph needs a title, labels on both sides and a scale with even steps, such as 0, 2, 4, 6, so the bars can be read correctly.
A graph is not the same as one number. The average number of votes per fruit, 24÷4=6, is a single number that sums up the data; the bar graph shows every fruit. A fancier graph is not always clearer, either. A 3D bar graph with shadows can make it harder to tell which bar is taller. The best graph is the one where the answer jumps out.
Think of it like this. A graph is like a map of your data. Reading a list of street names would not tell you where the park is, but a map shows it at a glance. A bar graph shows which group is biggest the way a map shows which town is closest. A map can be drawn badly, though, and so can a graph, so always check the labels.
Core idea. Data visualization shows data as a graph so patterns jump out that a table would hide.