Rationale for How to Categorize<\/strong><\/h3>\nThe purpose of categorizing is to eliminate redundancies by collapsing related items into clusters or\u00a0chunks (<\/em>a\u00a0scientific term). A label or term that captures the title for each cluster can be more easily re-used in matrices and other visual displays. Frequently we refer to the labels as “triggers” because they rely on a a single term for triggering back to the meaning and definition behind it. For example, “budgeting” refers to the activities and resources required to project, track, and balance accounts. When focused on “budgeting” the group is less likely to focus on the details of “accounts payable” “accounts receivable” or other discrete clusters. Categorizing also makes it easier for the team to analyze complex relationships and their impact on each other.<\/span><\/p>\n![\"When](\"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2011\/09\/When-Facilitating-How-to-Categorize-300x250.png\")
<\/a>How to Categorize<\/strong><\/span><\/p><\/div>\nMethod\u00a0for How to Categorize<\/strong><\/h3>\nCategorizing can take little or much time, depending on how much precision is required, time available, and importance. The underscoring method suggested below is quick and effective. The other methods may also be effective, but probably not as quick.<\/span><\/p>\nUnderscore Common Nouns<\/em><\/span><\/h4>\nTake the raw input or lists created during the ideation step and underscore the common nouns<\/em><\/strong>\u00a0<\/span>(typically the object in a sentence that is preceded by a verb).\u00a0<\/i>Verbs typically precede the object<\/em> in a sentence as in “pay bills”. Use a different color marker for each group of nouns. By pointing to the underscored terms, ask the team to offer up a term, simple phrase, or label that captures the meaning of each cluster.<\/span><\/p>\n(O<\/em>ptionally<\/em>)<\/em><\/h4>\nFor verification or to manage items that are not underscored, ask \u201cWhy _____?\u201d \u00a0The logic and secret behind categorizing follows.<\/span><\/p>\nNOTE: Items that share a common purpose likely have a common objective and can be grouped together. Verify that each item is WHAT they are doing and not HOW it gets done. Ask \u201cWHY do you do this?\u201d. Write the purpose next to the item. Continue with the next pairing\u2014if it has the same purpose, then it will group together. When a number of activities relate\u2014due to common purpose\u2014have the group name the cluster. Put a visual box around the name for the cluster.<\/em><\/span><\/p><\/blockquote>\nTranspose<\/em><\/span><\/h4>\nAsk for a volunteer to take the underscored items and create a new statement or gerund that combines, integrates, and reflects the sentiment of the commonly underscored items. Write the new statement or gerund expression that signifies a grouping on a new and separate page. The terms may be more fully defined and illustrated with the list of all items that belong to each cluster. Notice how salt, mustard, and chutney may be grouped as “condiments’ because they share a common purpose. Use the MGRUSH <\/span><\/i>Definition<\/em> tool to build a consensual and robust definition if required.<\/span><\/p>\nNOTE:\u00a0Format clusters as \u201cgerund-like phrases.\u201d That is, a noun followed by a gerund (a verb acting as a noun and usually ending with \u201cing\u201d, \u201cment\u201d, \u201ction\u201d, or \u201cble\u201d including \u201cable\u201d and \u201cible\u201d). Examples are \u201cOrder Processing\u201d or \u201cAccount Management\u201d or \u201cResource Generation\u201d or \u201cAccounts Payable\u201d.<\/em><\/span><\/p><\/blockquote>\nAvoid vague terms such as \u201cManagement Reporting\u201d\u2014that have no specific goal. If the group includes a number of challenging processes, write these as a side list of \u201cconcerns\u201d and continue with additional activities. Revisit the problem areas or concerns later, after the group has developed some momentum.<\/span><\/p>\nAvoid letting the group simply define their organization. For example, insurance companies have a tendency to define their \u201cprocesses\u201d as Underwriting, Claim Adjusting, and Operations. What they do from a process perspective (regardless of how they are organized) is Risk Assessment, Claims Payment, Portfolio Balancing, etc.<\/span><\/p>\nTransposing requires artful patience. Remain highly fluid and flexible. Activities may move around and processes may be re-labeled. There is no universally correct answer. Seek the terms that work best for the group that you are serving. And as always, seek to understand rather than be understood.<\/span><\/p>\nScrub<\/em><\/span><\/h4>\nGo back to the original list and strike the items that now collapse into the new terms created for each cluster in the Transpose<\/em> step above. Allow the group to contrast any remaining items that have not been eliminated and decide if they require unique terms, need further explanation, or can be deleted.<\/span><\/p>\nHere is another example of using activities for creating the processes that support the function of Mountaineering.<\/span><\/p>\n
<\/a>How to Categorize<\/strong><\/span><\/p><\/div>\n Categorizing can take little or much time, depending on how much precision is required, time available, and importance. The underscoring method suggested below is quick and effective. The other methods may also be effective, but probably not as quick.<\/span><\/p>\n Take the raw input or lists created during the ideation step and underscore the common nouns<\/em><\/strong>\u00a0<\/span>(typically the object in a sentence that is preceded by a verb).\u00a0<\/i>Verbs typically precede the object<\/em> in a sentence as in “pay bills”. Use a different color marker for each group of nouns. By pointing to the underscored terms, ask the team to offer up a term, simple phrase, or label that captures the meaning of each cluster.<\/span><\/p>\n For verification or to manage items that are not underscored, ask \u201cWhy _____?\u201d \u00a0The logic and secret behind categorizing follows.<\/span><\/p>\n NOTE: Items that share a common purpose likely have a common objective and can be grouped together. Verify that each item is WHAT they are doing and not HOW it gets done. Ask \u201cWHY do you do this?\u201d. Write the purpose next to the item. Continue with the next pairing\u2014if it has the same purpose, then it will group together. When a number of activities relate\u2014due to common purpose\u2014have the group name the cluster. Put a visual box around the name for the cluster.<\/em><\/span><\/p><\/blockquote>\n Ask for a volunteer to take the underscored items and create a new statement or gerund that combines, integrates, and reflects the sentiment of the commonly underscored items. Write the new statement or gerund expression that signifies a grouping on a new and separate page. The terms may be more fully defined and illustrated with the list of all items that belong to each cluster. Notice how salt, mustard, and chutney may be grouped as “condiments’ because they share a common purpose. Use the MGRUSH <\/span><\/i>Definition<\/em> tool to build a consensual and robust definition if required.<\/span><\/p>\n NOTE:\u00a0Format clusters as \u201cgerund-like phrases.\u201d That is, a noun followed by a gerund (a verb acting as a noun and usually ending with \u201cing\u201d, \u201cment\u201d, \u201ction\u201d, or \u201cble\u201d including \u201cable\u201d and \u201cible\u201d). Examples are \u201cOrder Processing\u201d or \u201cAccount Management\u201d or \u201cResource Generation\u201d or \u201cAccounts Payable\u201d.<\/em><\/span><\/p><\/blockquote>\n Avoid vague terms such as \u201cManagement Reporting\u201d\u2014that have no specific goal. If the group includes a number of challenging processes, write these as a side list of \u201cconcerns\u201d and continue with additional activities. Revisit the problem areas or concerns later, after the group has developed some momentum.<\/span><\/p>\n Avoid letting the group simply define their organization. For example, insurance companies have a tendency to define their \u201cprocesses\u201d as Underwriting, Claim Adjusting, and Operations. What they do from a process perspective (regardless of how they are organized) is Risk Assessment, Claims Payment, Portfolio Balancing, etc.<\/span><\/p>\n Transposing requires artful patience. Remain highly fluid and flexible. Activities may move around and processes may be re-labeled. There is no universally correct answer. Seek the terms that work best for the group that you are serving. And as always, seek to understand rather than be understood.<\/span><\/p>\n Go back to the original list and strike the items that now collapse into the new terms created for each cluster in the Transpose<\/em> step above. Allow the group to contrast any remaining items that have not been eliminated and decide if they require unique terms, need further explanation, or can be deleted.<\/span><\/p>\n Here is another example of using activities for creating the processes that support the function of Mountaineering.<\/span><\/p>\nMethod\u00a0for How to Categorize<\/strong><\/h3>\n
Underscore Common Nouns<\/em><\/span><\/h4>\n
(O<\/em>ptionally<\/em>)<\/em><\/h4>\n
Transpose<\/em><\/span><\/h4>\n
Scrub<\/em><\/span><\/h4>\n
![\"\"](\"https:\/\/mgrush.com\/blog\/wp-content\/uploads\/2011\/09\/Categorizing.png\")
<\/a>