Model: Super-Safe Sidewalk
Accessories: water bottle
Accessories: rear view mirror
Accessories: handlebar tassels
Notice how each bike repeated all the attribute names? No big deal right? What if you now need to add 2 more attributes to each bike, or 4, or 10? You would have a lot of editing in your future.
Don't get ahead of me here but another way to organize this data is with a grid (aka a spreadsheet) which could look like this:
|Owner|| Jan ||Gary ||Dad||Mom|
|Accessories||handlebar tassels||none||speedometer||water bottle|
In this form it becomes easy to add categories and/or bikes; thus maintaining the list in an efficient manner. The problem? Describing this method to a Serial-Sue will confuse them. They'll ask, "Why go to the trouble of creating a grid, all I want is a list?" You might think that it is a simple matter of just do it they way your boss wants. That is fair but there is more to the story. When dealing with a large list of semi-related things, using categories to subdivide the items can be an enormous help in simplifying the organization and can help bring order out of the chaos.
Another clue you are dealing with a serial thinker is if you show her a grid and then have to explain it. It takes a different sort of brain. Much like how some people can't read maps well, go figure. Watch for symptoms of frustration when showing or explaining a grid of data to someone, it could be that you've botched your data, but it could also be a sign of serial thinking.
So, do you work for/with a Serial-Sue?