Task Experience Discovery via Vector Embeddings

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for identifying potential collaborators with relevant experience are inefficient and inaccurate due to the lack of consideration for project context and collaboration history, leading to manual and time-consuming searches through directories and documents.

Innovation Solution

The technology automatically identifies potential collaborators by comparing an active task to similar tasks within a project context using vector embeddings and collaboration networks, providing task insights that include relevant tasks, collaboration history, and availability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual searches are conducted through directories and documents to identify potential collaborators, then users can find people with relevant experience, but the process is inefficient and time-consuming

Engineering Contradiction:
Improveaccuracy of collaborator identificationVSAvoidtime required for manual search
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system automatically performs collaborator identification by comparing active tasks with historical task data and generating embeddings, eliminating the need for manual searching while maintaining accurate results through automated relevance assessment

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

Manual mechanical searching through directories and documents is replaced with an automated computational system that uses vector embeddings, similarity calculations, and collaborative filtering algorithms to identify relevant collaborators efficiently

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Quantity of substance

If general metadata is used to associate people with experience, then directories can store collaboration information, but the metadata is not fresh and lacks project context

Engineering Contradiction:
Improveamount of collaboration data storedVSAvoidproject context and recency information
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The system transforms static general metadata into dynamic contextualized information by generating vector embeddings that capture project-specific context, task descriptions, and temporal recency, allowing the same collaboration data to convey different levels of relevance based on current project needs

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system pre-processes and stores vector embeddings for historical tasks and collaborator profiles in advance, so that when a new active task arises, the system can quickly compare and identify relevant collaborators without needing to process raw metadata in real-time

Inventive Principle:
Principle #10Preliminary action

3Productivity

If search systems identify people with debugging experience, then potential collaborators are found, but the system fails to consider specific software, code language, or contextual factors

Engineering Contradiction:
Improvespeed of collaborator identificationVSAvoidrelevance of identified experience
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

Instead of treating all debugging experience as uniform, the system applies local quality by creating specialized vector embeddings that capture specific contextual attributes such as software type, code language, and project domain, allowing the system to identify collaborators with locally-relevant expertise rather than generic experience

Inventive Principle:
Principle #3Local quality

4Measurement precision

If users manually review documents to confirm potential collaborator experience, then accurate identification is possible, but the process increases I/O operations and computing resource usage

Engineering Contradiction:
Improveaccuracy of experience verificationVSAvoidcomputing resources and I/O operations
Core Design Contradiction:
Measurement precisionVSUse of energy by moving object

Solution Approach 1:

Instead of requiring users to read and verify original documents, the system creates vector embedding copies that capture the essential semantic meaning of task descriptions and collaborator experiences, allowing for rapid similarity comparisons without accessing the full original documents

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20240403829A1Task-experience discovery
Publication Date: 2024.12.05 MICROSOFT TECHNOLOGY LICENSING LLC
  • US20240403829A1 patent drawing
  • US20240403829A1 patent drawing
  • US20240403829A1 patent drawing

AI summary

The technology described herein identifies a user or user group with relevant experience for a yet to be completed task that is part of a project. The technology described herein improves on past efforts to identify users with relevant experience by considering the project context of an active task and a collaboration history of the user or user group. The technology builds a project-context oriented task description that includes the task description of the active task along with the task descriptions of other tasks within the project. The project-oriented task description is used to generate a vector embedding, which are used to identify similar tasks. Once a similar task is identified, the user or user group associated with the similar task are candidates to provide relevant experience. A collaboration network may be used to identify users who worked together previously on a task or project.