OutbuildProduct design2026

Lookahead 2.0: redesigning a dense construction planning workflow

Role

Senior UX/UI Designer

Team

Lookahead Project Manager, Vice President of Product and Engineering

Timeline

Feb 2026 – present (launched June 30, 2026)

Platform

Web, iPad, mobile

Scope

Redesign of the entire module end to end, plus ongoing feature improvements

Structure
00 / 05
Schedule
WK 01 / 05
Today · 00%

TL;DR

Goal

Increase Lookahead adoption, our north star. It worked: monthly tasks created by paying customers more than doubled.

The stake

Leadership flagged Lookahead usability as urgent. Support tickets showed users struggled to understand it.

What I did

I drafted several concepts, iterated with the team through feedback cycles, and built AI-coded prototypes as the handoff. Engineering built from them.

How I led

I set the strategy to rebuild on the Weekly Work Plan, co-proposed key interactions with the PM, and replaced static specs with coded prototypes.

Results

Lookahead adoption more than doubled.

Lookahead tasks created per month

By paying customers, Sep 2025 to Oct 2026.

Monthly active editors

Paying customers, Sep 2025 to Oct 2026.

Right-click menu

Adoption six weeks after launch.

Outcomes

What else changed.

  • 2 fewer clicks per export from the new PDF defaults.

  • In Series B reference calls, one general contractor said it tested Oracle Primavera Cloud and still chose Outbuild, because the interface removed training friction.

  • Another reference customer said foremen who found P6 hard to use adopted it without friction.

  • The release also added TV Mode, Focus Mode, more style controls, and SIR icons in the Gantt.

01 · Context & problem

Dense, and flagged as urgent.

Outbuild is construction scheduling and lean-planning software. The Lookahead is where teams plan the next few weeks of work, in a table beside a Gantt chart. It is dense, and support tickets showed users struggled to understand it.

02 · Constraints

Keep inline editing fast, in two linked views.

  • Inline editing had to survive. Experienced users edit directly in the table. Any new interaction had to keep that speed.

  • Two linked views. Every change had to work in both the table and the Gantt chart.

  • Many changes at once. The redesign touched almost every table and Gantt interaction.

03 · My role & influence

I led the design end to end.

I led the design with the Lookahead Project Manager and the VP of Product and Engineering. I ran design reviews with the team, later async with recordings and live prototype links.

04 · Strategy

One structure for planning and commitment.

I chose to redesign the entire Lookahead on top of the Weekly Work Plan, which meant focusing heavily on the chart. Planning and weekly commitment would share one structure instead of feeling like separate tools.

05 · Key decisions & trade-offs

Four decisions in the redesign.

1. Hand off with a coded prototype.

There were too many differences to explain in static specs. I built a coded Lookahead prototype flow so engineering could see each change in context. It covered a new WBS reference and popover, floating action buttons on task cells, and right-click interactions in the table and Gantt.

2. Put actions where the work is.

Actions appear on hover and on right-click, right next to the task. With the PM, I proposed an activity-card interaction that keeps inline editing while making the card easier to open. Hidden actions risk being missed. Six weeks after launch, the right-click menu had 45% adoption.

3. Calm the chart.

I lightened the grays, fixed grid misalignment, made the today cell square, and added a date-range top border. Dense screens need quiet structure.

4. Explore broadly, then align the language.

The goal for Weekly Work Plan commitments was better adoption, through transparency into what is committed and an email reminder. I explored four concepts: the WWP as another view of the Lookahead, a Gantt chart, a block chart, and a card chart. Alongside it, I aligned UI terminology from “Company” to “Project Partner” across Lookahead, Roadblocks, the WWP, and exportables. One term now means the same thing in every team-ownership module.

06 · Follow-on releases

It kept shipping after launch.

  • Task card. Redesigned from the ground up for information density and usability. My branch work added a summary tile, replaced separate tabs, and made days clickable to open a day view. Live for all users October 26, 2026.

  • Bulk actions and grouping. I mocked up bulk actions and designed grouping in the table.

  • PDF export. In Series B reference calls, customers said printing lagged MS Project, and one docked two points from its rating for it. I rebuilt the export modal on design-system checkboxes, radios, and inputs, and removed unneeded headers. I added a date-range selector, a header and footer, and a preview. We set default print settings that match how customers print, saving 2 clicks per export. Shipped October 2026.

07 · Field Forward, Q3 2026

Then the Lookahead went to the field.

The Q3 2026 Field Forward release took the Lookahead to iPad and mobile. My main piece was the Parking Lot, which shipped on all three platforms on September 28, 2026. That work has its own case study: Field Forward.

08 · Reflection

Decisions now live in code too.

Coded prototypes changed how this team hands off design. Decisions now live in code as well as Figma. Next, I am breaking further Lookahead improvements into shippable versions that can each be measured.

Next case study