Enterprise Content Prioritization via Organizational Hierarchy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users face difficulty in managing and identifying important or relevant content within a large volume of enterprise emails, documents, and social media posts, often overlooking critical information from higher-ranking users due to the lack of effective prioritization mechanisms.

Innovation Solution

A management service utilizes an organizational hierarchy to categorize and prioritize content by obtaining user identifiers, generating an enterprise map that links users based on their hierarchical structure, and organizing content on client devices using this hierarchy, allowing users to focus on messages and posts from superior or relevant users.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If emails are arranged to show the most recent emails, then the recency of content is improved, but the importance based on user hierarchy deteriorates

Engineering Contradiction:
Improverecency of contentVSAvoidimportance of content
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent segments the email list into multiple sections based on user hierarchy levels. Direct reports appear in a first section, while other senders appear in a second section. This segmentation allows recent emails to be highlighted within each section while maintaining the overall hierarchical structure, thus preserving both recency and importance.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a new dimension for organizing emails by adding hierarchical level as an organizing principle alongside chronological order. Instead of a single-dimensional chronological sort, emails are organized in a two-dimensional space: first by hierarchical section, then by recency within each section. This resolves the contradiction by satisfying both recency and importance simultaneously.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If users manually organize emails or other content, then the relevance to user is improved, but the complexity of operation deteriorates

Engineering Contradiction:
Improverelevance of contentVSAvoidmanual organization effort
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system automatically performs the organization task that would otherwise require manual user intervention. By detecting user hierarchy information and automatically arranging emails according to hierarchical sections, the system provides self-service organization. This maintains high relevance without requiring manual user effort, thus resolving the contradiction between relevance and ease of operation.

Inventive Principle:
Principle #25Self-service

3Reliability

If senders use urgent or high priority flags, then the urgency of content is improved, but the control over prioritization deteriorates

Engineering Contradiction:
Improveurgency of contentVSAvoidcontrol of recipient
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

Instead of relying on senders to mark urgent emails (sender-controlled prioritization), the patent inverts the approach by using recipient-controlled prioritization based on user hierarchy. The system automatically determines importance by examining the hierarchical relationship between sender and recipient, giving control to the recipient without requiring manual intervention. This resolves the contradiction by providing reliable prioritization while maintaining recipient control.

Inventive Principle:
Principle #13The other way round (Inversion)

Data Source

PatentUS11663240B2Categorization using organizational hierarchy
Publication Date: 2023.05.30 OMNISSA LLC
  • US11663240B2 patent drawing
  • US11663240B2 patent drawing
  • US11663240B2 patent drawing

AI summary

Disclosed are various examples for categorization using an organizational hierarchy. In some examples, a client device receives an enterprise map comprising a plurality of user identifiers, each being associated with a hierarchy level of an enterprise hierarchy. Enterprise content is received. The enterprise content includes data associated with a user identifier from the enterprise map. The enterprise content is associated with a category based on a hierarchy level of the user identifier. A user interface is generated to include the enterprise content and a visual design element based on the category.