Industry
Headquarters
Baltimore, MD
Founded
2010
Company Size
Key Markets
1M+ users globally
Growth Stage
ARR $8M by 2023
Website
Use case
Timeline planning, task dependencies, scheduling
Overview
TeamGantt grew with a small team. For most of that growth, I was the only designer.
The constraint was real: limited design bandwidth, increasing product complexity, and a growing user base.
The risk was fragmentation — one-off decisions, inconsistent patterns, and a product that slows down as it grows.
The goal was to scale clarity without scaling design headcount.
Highlights
Established timeline as the core product surface
Enabled scalable UX with one primary designer
Increased consistency across workflows
Supported growth across thousands of active projects
Understanding the Problem
This was not a feature problem. It was a systems problem.
One designer supporting a growing product surface
Increasing complexity as usage scaled
Risk of inconsistent UX across features
Pressure to ship quickly without degrading usability
Shipping fast without structure creates debt. Shipping with structure creates leverage.
Strategic approach
The approach was to treat design as infrastructure.
Focus on the core workflow. Build patterns once. Reuse everywhere.
Building systems instead of screens
Design effort was concentrated on the planning workflow, not edge cases.
Reusable interaction patterns were defined early and applied across features. Instead of designing each screen independently, the system defined how interactions should behave.
Engineering partnership was critical. We shipped in steps, validating patterns in production and expanding from there.
The product evolved through extension, not reinvention.
Principle: When resources are constrained, systems create scale.
Key Initiatives
Core workflow prioritization
The product surface was expanding faster than design capacity.
What I did
Focused design on the timeline and planning workflow
Reduced attention on non-critical surfaces
Aligned product decisions around the core use case
What changed
The timeline became the center of the product
User value concentrated around a clear interaction model
Less fragmentation across features
Reusable interaction patterns
Designing each feature independently would not scale.
What I did
Defined repeatable interaction patterns for task creation, editing, and scheduling
Standardized behavior across similar workflows
Built consistency into the system, not into individual screens
What changed
Design became faster to produce and easier to maintain
Users experienced consistent behavior across the product
Engineering could implement patterns with less ambiguity
Incremental shipping with engineering
Large redesigns were not feasible with limited resources.
What I did
Partnered closely with engineering to ship in phases
Validated patterns in production before expanding them
Balanced speed with structural integrity
What changed
Features shipped consistently without breaking the system
Iteration cycles stayed fast
The product evolved without accumulating unnecessary rework
Additional improvements
Reduced one-off design decisions
Increased consistency across the product surface
Strengthened collaboration between design and engineering
Built a foundation for future design system expansion
Cross-Functional Collaboration
Worked directly with founders and engineering to prioritize what mattered. Design decisions were tied to shipping reality.
Tradeoffs were explicit.
The focus stayed on delivering usable outcomes, not perfect artifacts.
Financial Impact & Business Enablement
This work allowed the product to scale without scaling chaos.
One designer could support a growing system because the system carried the load. Consistency improved. Speed held. The product stayed usable as complexity increased.
Faster feature delivery with limited design resources
Reduced rework through reusable patterns
Improved product consistency and usability
Supported growth from early product to scaled SaaS
Takeaway
Strong systems reduce the need for constant intervention. They let small teams build products that scale cleanly.
Role
Head of Product Design and Design Systems
Owned product UX during early growth. Defined core workflows, built reusable interaction systems, and partnered with engineering to ship incrementally while maintaining clarity and consistency.
Related Case Studies
Reducing onboarding friction by restructuring how users reach first value.
Making dependency behavior predictable in a visual planning system.
Scaling a product with limited design resources by building systems, not screens.
Lowering early drop off by restructuring how users reach first value.
Keep the product focused on the planning model, not expanding features.
Making product decisions that preserve control and predictability.
Designing scheduling behavior that feels powerful without becoming unpredictable.
Using direct observation to guide product decisions when analytics are incomplete.
Turning design from a service into a system tied to delivery outcomes.
Driving adoption and executive buy-in through phased, measurable impact.
Turning design into a decision driver by making its impact visible.
Turning fragmented research into a system that guides product decisions.