NISHIO Hirokazu[Translate]
(5.2.6.2) A group that can make a nameplate is a good group
To write a good explanation on the nameplate, you should not classify pieces at the group organization phase. Suppose you think that "this is a cause of the problem, this is also a cause of the problem." What nameplate is attached to this group? Since there is only a relation those are all the cause of the problem, you make a nameplate says "cause of the problem." However, with this nameplate, you do not understand the contents of the group at all.

The reason why you can not make a good explanation is that there was not any relation other than "these are all cause of the problem" in those pieces. To make those pieces into a group is not good.

You can not get the skill of group organization by reading books. You need to try it. After you made a group, you can verify it is a good group or not, by making a nameplate. You can realize the difference between a group that can summarize the contents well and a group that is not so. By doing this exercise, you gradually acquire the skill to organize good groups.
en
[<<< Previous:(5.2.6.1) Merits and demerits of nameplate making] [Next: (5.2.6.3) Making a nameplate when we have a huge number of pieces >>>]

Engineer's way of creating knowledge > (5) How to organize information > (5.2) How to organize too much information > (5.2.6) Bundle and attach a nameplate = compress > (5.2.6.2) A group that can make a nameplate is a good group

"Engineer's way of creating knowledge" the English version of my book is now available on [Engineer's way of creating knowledge]

(C)NISHIO Hirokazu / Converted from [Scrapbox] at [Edit]