Collaborative Object for Project Information Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current task management systems fail to effectively track tasks across projects, associate relevant communications and information, and share these resources for future projects, leading to disorganization and inefficiency.

Innovation Solution

A collaborative object system that integrates task lists with associated documents and communications, allowing users to interact and share project-related information, with customizable permissions for access control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If task lists are embedded within communications between individuals, then task tracking is integrated into existing workflows, but it becomes difficult for users to track tasks for a particular project and access related information

Engineering Contradiction:
ImproveTask tracking accessibilityVSAvoidProject-related information association
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The system segments project information into distinct components: task lists, communications, and related information are separated into individual elements that can be independently managed yet collectively associated through the collaborative object structure

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system merges previously separate elements (task lists, communications, and information) into a unified collaborative object that consolidates all project-related content in one accessible location, eliminating the need to search through scattered communications

Inventive Principle:
Principle #5Merging (Combining)

2Adaptability or versatility

If communications and information are scattered across different platforms, then users have flexibility in using their preferred tools, but there is no capability to share task lists and associated information as reusable resources

Engineering Contradiction:
ImproveResource sharing capabilityVSAvoidTime to recreate project resources
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system enables copying of collaborative objects and their associated content (task lists, communications, information) as reusable templates, allowing users to replicate proven project structures and avoid recreating them from scratch

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The collaborative object is designed as a universal container that can hold multiple types of content (tasks, communications, files, notes) and be reused across different projects and contexts, increasing the versatility of project resources

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If a collaborative object integrates multiple project elements, then project management becomes more comprehensive, but the system complexity increases

Engineering Contradiction:
ImproveProject management completenessVSAvoidSystem structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The collaborative object serves as an intermediary container that manages the complexity of integrating multiple project elements, providing a standardized interface for adding, organizing, and accessing diverse content types without exposing users to underlying system complexity

Inventive Principle:
Principle #24Intermediary (Mediator)

4Productivity

If collaborative objects are shared with multiple users, then team collaboration improves, but access control and permissions management become more complex

Engineering Contradiction:
ImproveTeam collaboration efficiencyVSAvoidPermissions management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The permission system is designed to be dynamic, allowing users to flexibly adjust access levels and sharing settings as project needs evolve, enabling efficient collaboration while maintaining secure access control through adaptive permission management

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10586211B2Shared collaboration objects
Publication Date: 2020.03.10 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10586211B2 patent drawing
  • US10586211B2 patent drawing
  • US10586211B2 patent drawing

AI summary

Systems and methods for creating a collaborative object are provided. A collaborative object may be associated with a user interface that enables one or more users to interact regarding various tasks during the planning and execution of a project. In aspects, the collaborative object may include a task list, an associated document, compiled information and/or communications related to a project. In further aspects, the collaborative object, along with associated information, may be shared with other users as a resource for future projects. Permissions may be set on a collaborative object such that recipients may be allowed varying access to the task list, document, compiled materials and/or communications associated with the collaborative object.