What does it mean that cross-cutting categories?

Sometimes you need to classify the same items along multiple independent dimensions.

Example: A product manager maintains a backlog of 200 feature requests. She has been organizing them by product area: payments, onboarding, reporting, integrations. It works until a stakeholder asks: 'Which requests came from enterprise customers?' Another asks: 'Which ones affect our compliance posture?' A third: 'Which ones are quick wins versus multi-quarter investments?' Each question demands a different classification of the same 200 items. She cannot answer any of them by looking at her product-area folders. The folder structure forces each request into exactly one category, and the questions cut across that single dimension. She needs cross-cutting categories: product area, customer segment, compliance impact, and effort size, applied independently to the same items. When she builds a spreadsheet with columns for each dimension, the backlog transforms. She can filter for enterprise-requested compliance features that are quick wins — a view that was invisible when her only lens was product area. The items did not change. Her classification infrastructure did.

Try this: Choose a collection of 15-20 items you currently organize in a single-dimension system — notes in folders, tasks in lists, bookmarks in categories, contacts in groups. Identify three additional dimensions along which those same items could be meaningfully classified. For each item, assign a value on each new dimension. Then generate three cross-cutting queries: find items that share a specific combination of values across two or more dimensions. Write down what the cross-cutting view reveals that the single-dimension view hid. Finally, decide which of these dimensions is worth maintaining permanently versus which was useful only as a one-time analysis.