Taming the Gantt (and moving it from Angular to Vue)

The short version

Problem: The Gantt is the heart of Dayshape. It carries a lot of information, and the front end behind it was moving from Angular to Vue.

What I did: Improved UX flows in the Scheduling team, helped convert elements from Angular to Vue, introduced new UI components and helped maintain the design system.

How I worked: Day to day with developers, with my line manager on priorities and critique, and with the VP of Product on direction.

The problem: a Tetris board where the pieces are people

Dayshape is resource management software for professional services firms. The Gantt is where planning happens: timelines, resources, dependencies and constraints in one view. Get it right and a planner spots an overbooked team at a glance. Get it wrong and someone is double-booked on a Friday afternoon. That is a lot to ask of one screen, and it was changing underneath: the front end was moving from Angular to Vue. A migration is a rare chance to improve how something works, not just how it is built.

Three jobs, one chart

Improving the flows. I reworked how some scheduling features behave, aiming for fewer steps, clearer feedback and screens that stay readable when the chart gets busy.

Carrying the design across. As elements were converted from Angular to Vue, I worked with developers so states, spacing and behaviour came across intact, not approximated. My front-end background helps me check a spec against how it will really be built.

Building the toolkit. I introduced new UI components where the Gantt needed them and helped maintain the design system, so what is built once can be reused.

Working with everyone, not just pixels

I work day to day with developers on feasibility and detail, with my line manager on priorities and critique, and with the VP of Product on direction. Translating between those groups is a big part of the job, and it suits a tool whose whole purpose is getting people lined up in the same direction.

What it looks like

Three image frames: a before and after of a scheduling flow; the new components in the design system; a short prototype clip.

Results

I am still early in this role, so I am not going to invent a tidy percentage. What I can share is the direction: fewer one-off patterns, more shared components and clearer handoff between design and engineering.

Reflection

Designing for a live enterprise product means every change has to earn its place. I am enjoying the craft of small, careful improvements to something people use all day. Next, I want to put more of this in front of real planners and see what it changes.