Hierarchical Software Templates for Faster User Onboarding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Complex software systems have a steep learning curve, making it challenging for users to derive value from their features, leading to avoidance of using the software.

Innovation Solution

A system providing prepackaged hierarchical templates with customizable primitives, AI-generated templates based on user needs, and a block data model for efficient organization and sharing of information, along with an AI tool for enhanced functionality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the software system includes comprehensive features and functionality, then the system capability and versatility are improved, but the learning curve becomes steeper and usability deteriorates

Engineering Contradiction:
Improvesystem capabilityVSAvoidusability
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The software system is segmented into multiple hierarchical templates (root template, child templates, leaf templates) that organize comprehensive features into manageable sections. Each template contains specific primitives and functionality relevant to particular use cases, allowing users to access only the features they need rather than overwhelming them with the entire system's capabilities at once.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system provides prepackaged templates with pre-configured primitives, properties, views, and blocks that are ready to use immediately. This preliminary preparation eliminates the need for users to learn how to configure and organize features from scratch, reducing the learning curve while maintaining access to comprehensive functionality through these pre-built structures.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If the software system provides extensive features and functionality, then the system capability is improved, but the time required for users to learn and derive value increases

Engineering Contradiction:
Improvesystem capabilityVSAvoidlearning time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

Comprehensive functionality is pre-packaged into hierarchical templates with all necessary primitives, properties, views, and blocks already configured. Users can immediately utilize extensive features without spending time learning system configuration, as the templates provide ready-to-use structures that embody best practices and common workflows.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses template copying where a root template contains multiple child templates, and child templates contain multiple leaf templates with specific primitives. This hierarchical copying mechanism allows comprehensive functionality to be replicated across multiple specialized templates, each optimized for specific use cases, reducing the time users need to learn different configurations for different tasks.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If the software system offers comprehensive functionality, then the system capability is improved, but users may avoid using the system due to complexity

Engineering Contradiction:
Improvesystem capabilityVSAvoiduser avoidance
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system segments comprehensive functionality into hierarchical templates that present information in an organized, manageable structure. Root templates provide high-level organization, child templates provide intermediate structure, and leaf templates provide specific functionality. This segmentation reduces perceived complexity and makes the system more approachable for users.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The hierarchical template structure acts as an intermediary between the user and the comprehensive system functionality. Templates serve as mediators that translate complex system capabilities into user-friendly, pre-configured structures, reducing the cognitive load on users and making the system more inviting despite its comprehensive nature.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If the system provides prepackaged templates with multiple primitives, then ease of operation is improved, but the device complexity increases

Engineering Contradiction:
Improveease of customizationVSAvoidtemplate structure complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The template structure is segmented into hierarchical levels (root template, child templates, leaf templates) with clearly defined roles and contents. Each level contains specific types of primitives appropriate to its function, organizing complexity in a structured way that makes the system easier to operate despite the comprehensive functionality available.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements nested templates where a root template contains multiple child templates, and child templates contain multiple leaf templates. This nesting organizes complexity hierarchically, with each level providing a different layer of abstraction. Users interact with the system at their appropriate level without needing to understand the entire nested structure, making operation easier despite the comprehensive template system.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS20260073802A1Enabling a user to efficiently discover and utilize a complex software system
Publication Date: 2026.03.12 NOTION LABS INC
  • US20260073802A1 patent drawing
  • US20260073802A1 patent drawing
  • US20260073802A1 patent drawing

AI summary

The system provides a hierarchical template associated with a software system. The hierarchical template includes a root template, which includes leaf templates. A leaf template is a collection of multiple primitives including at least two of one or more properties, one or more views, one or more tutorials, and one or more blocks. A property includes a name and a value. A view includes a view of a database according to a criterion. A tutorial includes an explanation of a use associated with the software system. A block is configured to include content. The system provides a user interface to add a first primitive among the multiple primitives to the leaf template, remove a second primitive in the collection of multiple primitives from the leaf template, add a first template to the hierarchical template, and remove a second template from the hierarchical template.