Balancing automation and control

Designing scheduling behavior that feels powerful without becoming unpredictable.

Work Delivered:

Product Strategy
Interaction Design
Workflow Systems
UX Tradeoffs
Visual Feedback Design
Information Architecture

Balancing automation and control

Designing scheduling behavior that feels powerful without becoming unpredictable.

Work Delivered:

Product Strategy
Interaction Design
Workflow Systems
UX Tradeoffs
Visual Feedback Design
Information Architecture

Balancing automation and control

Designing scheduling behavior that feels powerful without becoming unpredictable.

Work Delivered:

Product Strategy
Interaction Design
Workflow Systems
UX Tradeoffs
Visual Feedback Design
Information Architecture

Industry

Project Management SaaS

(SaaS) Project Management

Headquarters

Baltimore, MD

Founded

2010

Company Size

1-25 employees

Small (1-25) employees

Key Markets

1M+ users globally

Growth Stage

ARR $8M by 2023

Use case

Timeline planning, task scheduling, team coordination

Overview

Scheduling is a tradeoff. Users want speed — and they also want control.
Automation helps move faster. Control helps people trust what they are doing.
In TeamGantt, both existed. The challenge was how they worked together.

Highlights

  • Balanced automation with direct user control

  • Improved clarity of dependency behavior

  • Increased trust in timeline interactions

  • Reduced confusion during schedule edits

Understanding the Problem

The system supported two modes at once: direct manipulation and automated adjustment.

  • Users could drag and edit tasks directly

  • Dependencies automatically adjusted related schedules

  • Too much automation created confusion

  • Too little automation increased manual effort

The tension was constant: speed versus clarity.

Strategic approach

The solution was not to choose one. It was to align both.

Making automation predictable

Users do not reject automation. They reject surprises.

The focus shifted to making system behavior visible and understandable. Dependencies were clarified. Visual indicators showed how tasks were connected.

Interactions were refined so that drag and resize actions communicated their impact.

Automation remained, but it became legible. Users stayed in control because they could see what would happen.

Principle: Automation works when users can predict the outcome.

Key Initiatives

Dependency clarity and indicators

Users did not fully understand how tasks influenced each other.

What I did

  • Improved how dependencies were displayed

  • Made relationships easier to identify in the timeline

  • Aligned visuals with system logic

What changed

  • Users could see how schedules were connected

  • Automation became easier to follow

  • Less confusion during edits

Interaction refinement for predictability

Dragging or resizing tasks created unexpected changes.

What I did

  • Refined interaction behavior to better reflect system outcomes

  • Improved feedback during edits

  • Reduced ambiguity in how changes propagated

What changed

  • Users understood the result of their actions

  • Editing felt more controlled

  • Confidence increased when adjusting schedules

Additional improvements

  • Reduced friction in schedule editing

  • Lowered support issues tied to automation behavior

  • Strengthened user mental models

  • Maintained balance between speed and control

Cross-Functional Collaboration

Worked closely with product and engineering to align behavior, interaction design, and system logic. Ensured that improvements preserved technical integrity while improving usability.

Financial Impact & Business Enablement

The timeline became both powerful and understandable.

Users could move quickly without losing control. Automation supported them instead of surprising them.

  • Reduced support volume related to scheduling confusion

  • Improved retention through increased trust

  • Faster user adoption of advanced features

  • More efficient scheduling workflows

Takeaway

Automation is not the feature. Predictability is.

Role

Head of Product Design and Design Systems

Led UX strategy for scheduling workflows. Balanced automation and control through interaction design, improving clarity, predictability, and overall usability of the timeline system.

“Brandon is open to ideas from the dev team that influence design, and also responds well to the needs of the development team regarding design. I know that if I have a design need, Brandon will be able to respond even if it requires extra work from him. He has a willingness to help.”

TeamGantt Teammate

Development Team

“Brandon is open to ideas from the dev team that influence design, and also responds well to the needs of the development team regarding design. I know that if I have a design need, Brandon will be able to respond even if it requires extra work from him. He has a willingness to help.”

TeamGantt Teammate

Development Team

“Brandon is open to ideas from the dev team that influence design, and also responds well to the needs of the development team regarding design. I know that if I have a design need, Brandon will be able to respond even if it requires extra work from him. He has a willingness to help.”

TeamGantt Teammate

Development Team

Related Case Studies

Reducing onboarding friction by restructuring how users reach first value.

Workflow Architecture
Workflow Architecture
Usability Validation
Usability Validation
Onboarding
Onboarding

Making dependency behavior predictable in a visual planning system.

Workflow Clarity
Workflow Clarity
Research & Validation
Research & Validation
Dependencies
Dependencies

Scaling a product with limited design resources by building systems, not screens.

Design Systems
Design Systems
Workflow Architecture
Workflow Architecture

Lowering early drop off by restructuring how users reach first value.

Onboarding Redesign
Onboarding Redesign
Workflow Simplification
Workflow Simplification

Keep the product focused on the planning model, not expanding features.

Roadmap Prioritization
Roadmap Prioritization
Product Strategy
Product Strategy

Making product decisions that preserve control and predictability.

Product Judgment
Product Judgment
Roadmap Influence
Roadmap Influence

Designing scheduling behavior that feels powerful without becoming unpredictable.

UX Tradeoff Decisions
UX Tradeoff Decisions
Visual Feedback Design
Visual Feedback Design

Using direct observation to guide product decisions when analytics are incomplete.

Workflow Analysis
Workflow Analysis
Customer Insight Synthesis
Customer Insight Synthesis

Turning design from a service into a system tied to delivery outcomes.

Metrics Architecture
Metrics Architecture
DesignOps
DesignOps
System Design
System Design

Driving adoption and executive buy-in through phased, measurable impact.

Design System Strategy
Design System Strategy
DesignOps
DesignOps
Cross-functional Alignment
Cross-functional Alignment
a computer screen with a bar chart on it

Turning design into a decision driver by making its impact visible.

Product Alignment
Product Alignment
Metrics Strategy
Metrics Strategy
Executive Communication
Executive Communication
black flat screen computer monitor
black flat screen computer monitor

Turning fragmented research into a system that guides product decisions.

Persona System Design
Persona System Design
Research Synthesis
Research Synthesis
UX Strategy
UX Strategy

A better system makes everyone’s day less stupid. Clarity pays for itself.