OutbuildWeb · iPad · mobile2025–2026

Field Forward: taking the weekly plan from the office to the job site

Role

Senior UX/UI Designer

Team

PM, web, iPad, and mobile engineering, additional designers

Timeline

Oct 2025 – Oct 2026

Platform

Web, iPad, iOS and Android

Scope

New field workflows · One concept fitted to three platforms

TL;DR

The stake

The plan lived in the office. The superintendents and trade partners who do the work needed to see and update it from the job site.

What I did

I designed field workflows on three platforms: fast progress logging on mobile, a touch Lookahead on iPad, and the Parking Lot, where trade partners propose work for approval.

How I led

I designed each feature once and fitted it to three screens, argued against placements that would bury key features, and raised field realities like shared iPads.

Results

2.1× mobile monthly active users.

Mobile monthly active users

After the February 2026 launch. Nearly half of new users returned the following week.

iPad monthly active users

Up 24% after the mid-2026 redesign.

Parking Lot

platforms live on the same day, September 28, 2026

perspectives in one feature: owner and project partner

Outcomes

What the release changed.

  • Pull-planning prep: 1–1.5 hours to 15–20 minutes for one customer, after iPad progress tracking closed their biggest gap with Excel (Series B reference call).

  • Trade partners received the Parking Lot well at on-site trainings, per customer success.

  • An enterprise customer chose Outbuild in October 2026 partly because the Lookahead, mobile, and iPad tools were field-friendly, per sales.

These numbers describe the apps as a whole. Product, engineering, and other designers share the credit.

01 · Context & problem

The plan lived in the office.

Outbuild is construction scheduling and lean-planning software. The Lookahead plans the next few weeks of work. The people who carry out that plan are superintendents, foremen, and trade partners, and they are rarely at a desk.

The mobile app was scoped as a field execution tool for fast data entry: logging daily progress, attaching photos, and completing task checklists, in a vertical layout made for one hand. The iPad app carries the full Lookahead to the site. In Q3 2026, the Field Forward release moved the weekly work plan into the Lookahead on all three platforms.

02 · Constraints

Three platforms, short sessions, two roles.

  • Three platforms, one mental model. A task, a roadblock, and a commitment had to mean the same thing on web, iPad, and a phone.

  • Short sessions on site. Field users update the plan between other work. Each flow had to finish in a few taps.

  • Two roles, different needs. The general contractor owns the plan. Trade partners contribute to it and wait for approval.

  • A crowded toolbar. Every new field feature competed for the same space in the Lookahead.

03 · My role & influence

Field workflows on three platforms.

Before the mobile launch, I designed the mobile task card, the status flow, and the roadblock screens, and I built the mobile design-system components: buttons, icon buttons, slider, sheet, and form inputs. For Field Forward, I designed the Parking Lot on web, iPad, and mobile, the iPad flows to commit and close out a week, and the cross-platform experience for voice updates. Another designer later extended the mobile task screens.

I built and maintained the iPad and mobile prototypes in code, so the team could review each flow on a real device.

04 · Strategy

Design once, then fit it to every screen.

Design each feature once as a concept, then fit it to each screen. The web Lookahead stays the planning surface. The iPad is the Lookahead in the field. The phone is for the day’s work.

05 · Key decisions & trade-offs

Six decisions for the field.

1. One Parking Lot, two perspectives.

A project partner opens a full-screen Parking Lot that shows pending approvals and lets them add tasks. An owner sees the Parking Lot as a panel on the left side of the Lookahead chart, next to the plan it feeds. The iPad prototype had a switch to view either perspective, so reviewers could test both.

2. Keep it visible.

I explored combining the Parking Lot with other inbox-style features. I decided against it, because it would hide an important feature too deeply. These features matter enough to surface clearly.

3. A small first version on the phone.

I removed “add to daily work” from the mobile Parking Lot to keep version one focused. I added a full-screen mode to the mobile prototype so reviewers could open it in a phone browser and have it feel native.

4. Name the action for what it is.

For progress on mobile, “Submit” sounded too permanent and “Completed” sounded like the task was finished for good. The user is logging progress, so the button says “Log.”

5. Place voice where the stakes are low.

Voice updates began as an engineer’s hackathon idea. I designed how they work on mobile, iPad, and web. A floating control fits the iPad, where it feels low-risk. On the web Gantt, I argued against a floating button and weighed the toolbar instead, which was already crowded. AI drafts the update, and the user reviews and confirms it.

6. Question personalization on shared devices.

When per-user preferences were proposed for iPad, I raised a field reality: one iPad is often passed between people. Different preferences on one device can create confusing, inconsistent experiences.

06 · Release

From first users to every account.

  • February 2026. Mobile app released to the first external users, after two days of internal testing.

  • June 2026. Engineering added offline viewing, single sign-on, and real-time sync with web.

  • September 28, 2026. The Parking Lot went live for all users on web, iPad, and mobile, with an in-app tour and an email.

  • October 2026. Field Forward rolled out to all accounts: the weekly work plan in the Lookahead, daily progress and crew size on every platform, and voice updates on iPad and mobile.

07 · Reflection

What didn’t land: an icon without a label.

The first on-site trainings showed that the iPad Parking Lot icon was unclear without a label. An icon that reads well in a design review does not always read on a job site. Next time I would test labels with field users before release.

Next case study