TeamGanttProduct design2022–2025

TeamGantt, end to end: a construction pivot, a platform rebuild, and the design system behind them

Role

UX/UI Designer

Team

a ~25-person company, with PMs and engineering

Timeline

Dec 2022 – Sep 2025

Platform

Web, with a mobile confirmation screen for external users

Scope

Construction features, New Gantt, design system, plan gating, checkout, and billing

TL;DR

The stake

TeamGantt pivoted to construction and needed key features built to support new workflows.

What I did

As the only designer, I designed the construction features, the New Gantt rebuild, a token-based design system, plan gating, checkout, and billing, and organized ongoing customer research.

How I led

As the only designer, I tied features to business strategy with Jobs To Be Done, ran the customer research loop, and negotiated the checkout approach with engineering.

Results

15× construction plan sales.

Construction plan sales

+1,413% after six construction features launched.

Customer value

customer lifetime value

revenue per account

NPS

Conversion and activation

onboarding completion

purchase conversion after New Gantt

plan upgrades from the billing dashboard

Outcomes

Behind the numbers.

These figures come from my resume. They reflect product releases I designed and the whole team shipped.

  • 6 construction features behind the 15× sales growth, closing key workflow gaps for contractors and builders.

  • New Gantt, a platform-wide rebuild of the UI, navigation, filters, dependencies, and time tracking.

  • The first account and billing dashboard, which also cut support tickets 1.7%.

  • A token-based design system, with dark mode built in, that made design-to-development about 40% faster.

01 · Context & problem

A Gantt tool, pivoting to construction.

TeamGantt is Gantt-based project management software. When the company pivoted to construction, it needed key features to support new workflows. Those features had to cover materials, costs, dependencies, short-range lookaheads, and schedule confirmations.

At the same time, the checkout flow was outdated, inconsistent, and confusing. We were losing customers during purchase and fielding unnecessary support tickets.

02 · Constraints

One designer, an established product, tight timelines.

  • One designer. I was the sole UX/UI designer at a company of about 25 people. Research, design, systems, and handoff were all mine.

  • An existing product. New construction features had to fit an established Gantt product and its current users.

  • Tight timelines. The checkout redesign had about a month.

03 · My role & influence

Sole designer, from research to handoff.

I joined as a Junior UX/UI Designer and was promoted to UX/UI Designer in April 2023. As the sole designer, I owned the flows and designs for every project here. I worked directly with PMs and engineering, and I adopted the Jobs To Be Done framework to tie features to user motivations and business strategy.

04 · Strategy

A shared system first, then workflows, then revenue.

I built a design system so every new screen would ship consistent and fast. On top of it, I focused on the construction workflows that mattered most, then connected them to how the company made money. Construction features drove the pivot. Plan gating and a clearer checkout turned that value into revenue.

05 · Key decisions & trade-offs

Six decisions across the product.

1. Construction features that match job-site workflows.

I designed Advanced Dependencies, Cost Loaded Scheduling, Material Lead Items, Lookaheads, an Issues Report, and Schedule Confirmations. For confirmations, I added a dedicated column with mini badges, a popover, and an external mobile screen. I changed the dependency modal to a table with clear “Set lag” and “Add dependency” actions.

2. Show premium value in context.

I added upsells where users meet advanced features: locks on the cost scheduling tab, the lookaheads chip, and the cost column. Advanced filtering and dependency menus got their own prompts. Each prompt sits where the user meets the locked feature.

3. Compromise with engineering on checkout.

The developers pushed back on how I’d specified the checkout component, because it had to work across several screens. I partnered with them to merge my design priorities with their technical needs. We streamlined the flows and kept the experience consistent.

4. A billing center where none existed.

Before this project, TeamGantt had no account or billing dashboard. I designed one that shows account status, billing, invoices, and plan details, and lets users manage subscriptions. I moved from low-fidelity wireframes to high fidelity, then rebuilt the screens in design-system components.

5. A design system built for theming.

TeamGantt’s UI had drifted and carried real technical debt. I audited the inconsistencies, then built a token system in three tiers: foundation, type, and modifier. The color scale has 10 shades per hue and inverts for dark mode. Every component was rebuilt on those tokens, which made design-to-development about 40% faster.

6. New Gantt, a platform-wide rebuild.

New Gantt replaced the UI across almost every area of the product: side navigation, filters, the view menu, dependencies, task creation, assigning people, time tracking, discussions, and checklists. I kept each release scoped to a roadmap so new ideas didn’t stall what was already in flight.

06 · Research

Customer calls, about every three weeks.

I organized recurring calls with the Inner Circle, a customer research panel. From April to September 2025, I sent call schedules about every three weeks. I also ran user calls and design labs, and synthesized UX tests. A beta feedback log from May 2024 captured findings such as auto-advancing from the start-date to the end-date calendar and greying out invalid actions.

07 · Reflection

Two lessons I still use.

Two lessons from this work still shape how I lead. There is always a tradeoff, so I compare options with the user and other teams in mind. There is always another idea, so a roadmap and clear scope keep a project from drifting.

Next case study