IN SYNC, NO BUILD

EVER WAITS ON A

DRAWING.

IN SYNC, NO BUILD

EVER WAITS ON A

DRAWING.

PROJECT

SYNC- AI Workflow app

ROLE

Product Designer · UX · AI Product Development

INDUSTRY

Architecture & Interior Design

YEAR

2026

( WORK 04)

( WORK 04)

PRODUCT DESIGN

PRODUCT DESIGN

WEB APP

WEB APP

SYNC

SYNC

Architecture and interior design projects are shaped by constantly evolving site schedules, deadlines, and interdependent tasks. SYNC explores how AI can help design teams anticipate what needs to be prepared next before a site requirement turns into a last-minute drawing request.


The product concept is informed by my experience working as an architect and is designed for architecture and interior design firms seeking a more proactive approach to project coordination.

Architecture and interior design projects are shaped by constantly evolving site schedules, deadlines, and interdependent tasks. SYNC explores how AI can help design teams anticipate what needs to be prepared next before a site requirement turns into a last-minute drawing request.


The product concept is informed by my experience working as an architect and is designed for architecture and interior design firms seeking a more proactive approach to project coordination.

INDUSTRY

Architecture & Interior design studios

Architecture & Interior design studios

BUILT WITH

BUILT WITH

Google AI studio and ChatGPT Codex

Google AI studio and ChatGPT Codex

SERVICES

SERVICES

UX RESEARCH

UX RESEARCH

PRODUCT DESIGN

PRODUCT DESIGN

DESIGN SYSTEM

DESIGN SYSTEM

GEMINI

GEMINI

GOOGLE AI STUDIO

GOOGLE AI STUDIO

CONTEXT

CONTEXT

Developed as the capstone project for the Google AI Professional Certificate on Coursera, using Google AI Studio to take the concept from problem framing and product design to a working AI-powered web application.

↳

VIEW LIVE PROJECT

VIEW LIVE PROJECT

(OVERVIEW)

(OVERVIEW)

Having worked in architecture, I saw how often design teams were left reacting to changes on site. A shift in the construction schedule could quickly become a last minute drawing request. SYNC explores how AI can help teams stay ahead by connecting project schedules with the design work that needs to happen next.

I designed and built the product in Google AI Studio as the capstone for the Google AI Professional Certificate on Coursera, taking it from an industry problem to a working AI powered web app.

Having worked in architecture, I saw how often design teams were left reacting to changes on site. A shift in the construction schedule could quickly become a last minute drawing request. SYNC explores how AI can help teams stay ahead by connecting project schedules with the design work that needs to happen next.

I designed and built the product in Google AI Studio as the capstone for the Google AI Professional Certificate on Coursera, taking it from an industry problem to a working AI powered web app.

(THE CHALLENGE)

(THE CHALLENGE)

Three connected problems were making project coordination reactive.

1. Timing was disconnected.
Construction schedules showed when work would happen on site, while design teams worked to their own drawing deadlines. There was no clear connection between the two, leaving teams to work out priorities manually.

2. Information was fragmented.
Architecture, interiors, and consultants often worked across different tools, files, and versions. There was no shared view of what was ready, what was changing and what was still at risk.


3. Workload was hard to see.
Much of the team’s workload lived in spreadsheets, inboxes, and people’s heads. By the time an overloaded team member was identified, a deadline had often already been missed.

The problem was not simply getting drawings out. It was having the right visibility early enough to act.

Project coordination was often reactive. Construction schedules, design deadlines, consultant updates, and team workloads lived across different tools, making it difficult to see what needed attention and when. By the time a delay became visible, the team was already catching up. The real challenge was not producing drawings, but having the right visibility early enough to act.

Project coordination was often reactive. Construction schedules, design deadlines, consultant updates, and team workloads lived across different tools, making it difficult to see what needed attention and when. By the time a delay became visible, the team was already catching up. The real challenge was not producing drawings, but having the right visibility early enough to act.

(THE APPROACH)

(THE APPROACH)

I designed SYNC around a simple idea: give design teams enough visibility to act before a project falls behind. Instead of treating site schedules, drawing deadlines and team workload as separate pieces of information, the product brings them together into one connected workflow.

The core experience is built around three areas. Planning uses AI to interpret construction schedules and translate site activity into realistic design deadlines. Release tracking gives the team a clear view of drawing versions, status and upcoming deliverables. Workload visibility helps surface capacity issues early, so teams can understand where work is building up before it affects a deadline.

The challenge was to make all of this feel useful without making the interface feel complex. I kept the experience focused on the information people need to make decisions, using clear hierarchy, restrained visual language and purposeful use of colour to bring attention to changes, risks, and actions.

The result is a workflow that shifts the team from asking, “What have we missed?” to “What needs to happen next?”

I designed SYNC to bring project schedules, drawing deadlines, and team workload into one connected workflow. AI helps translate site activity into actionable design deadlines, while the product gives teams a clear view of upcoming releases, capacity, and potential bottlenecks. The experience is intentionally simple and focused, using clear hierarchy and subtle visual cues to surface what needs attention and help teams act before delays happen.

I designed SYNC to bring project schedules, drawing deadlines, and team workload into one connected workflow. AI helps translate site activity into actionable design deadlines, while the product gives teams a clear view of upcoming releases, capacity, and potential bottlenecks. The experience is intentionally simple and focused, using clear hierarchy and subtle visual cues to surface what needs attention and help teams act before delays happen.

(RESULTS & IMPACT)

(RESULTS & IMPACT)

SYNC turns project risk into something teams can see and act on earlier. By bringing release progress, schedule buffers, and workload into one view, it creates a shared understanding of what needs attention and where delays may emerge.

The biggest shift is from reacting to missed deadlines to anticipating them. Instead of discovering a problem on site, teams can see what is at risk, understand why, and act before it becomes a delay. The project demonstrates how AI can bring greater clarity and predictability to a traditionally reactive design workflow.

SYNC turns project risk into something teams can see and act on earlier. By bringing release progress, schedule buffers, and workload into one view, it creates a shared understanding of what needs attention and where delays may emerge.

The biggest shift is from reacting to missed deadlines to anticipating them. Instead of discovering a problem on site, teams can see what is at risk, understand why, and act before it becomes a delay. The project demonstrates how AI can bring greater clarity and predictability to a traditionally reactive design workflow.

SYNC turns project risk into something teams can see and act on earlier. By bringing release progress, schedule buffers, and workload into one view, it creates a shared understanding of what needs attention and where delays may emerge.

The biggest shift is from reacting to missed deadlines to anticipating them. Instead of discovering a problem on site, teams can see what is at risk, understand why, and act before it becomes a delay. The project demonstrates how AI can bring greater clarity and predictability to a traditionally reactive design workflow.

(VISUAL FOUNDATION)

Calm at a glance. Clear when it matters.

I used quiet neutral surfaces and consistent cards to keep dense project information manageable. Stable patterns reduce relearning, while stronger emphasis is reserved for urgent work. The aim is to make priorities clear without making the entire workspace feel urgent.

THE VISUAL FOUNDATION
01

A stable workspace

Consistent navigation and aligned cards keep the surrounding interface familiar.

02

Visible priorities

Overdue releases carry stronger colour, explicit timing, and a direct action.

03

Connected decisions

Drawing identity, ownership, dates, and next steps stay together.

NEUTRAL CANVAS → STRUCTURED CONTENT → PURPOSEFUL EMPHASIS

Overview exhibit

SYNC overview mockup

(COLOUR SYSTEM)

Every colour has a job.

Green identifies primary actions, blue orients time-based information, and amber and red distinguish approaching and missed deadlines. Colour communicates meaning, not decoration. Labels and milestone shapes reinforce those signals so priorities can be interpreted without relying on colour alone.

COLOUR / SEMANTIC ROLESSYNC FOUNDATION
Studio green#087F5B

Brand · primary action

Release drawing
Signal blue#2563EB

Information · Today

Today, 4 Nov
Deadline amber#F59E0B

Approaching deadline

Due soon
Critical red#DC2626

Missed release deadline

Overdue
#F2F5F4Workspace canvas
#FFFFFFContent surface
#C8D3CCStructure & borders
#172B23Primary text

Colour is a supporting cue: “Overdue” remains readable as a label, and the timeline uses different milestone shapes. Green’s brand and status roles are distinguished by their labels and context.

(TYPOGRAPHY)

Readable detail. Deliberate hierarchy.

DM Sans gives drawing names, dates, and controls a consistent visual voice. A 18px primary / 14px supporting scale separates key decisions from metadata without excessive type variation. The intended result is readable detail and a predictable scanning order.

TYPOGRAPHY / DM SANSREGULAR · MEDIUM · SEMIBOLD
DM SansAa
ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789 · → / +
PAGE HEADINGYour practice, in sync.Clear entry point
PRIMARY CONTENT / 16PXRoof truss connection detailsDrawing names and actions
SUPPORTING / 14PX

MON-002 · Rohan Mehta

Identity, owner, and dates
Roof truss connection details

MON-002 · Monsoon Pavilion

Overdue

Release overdue by 2 days

01 / Identity02 / Urgency03 / Action

(COMPONENTS)

One system. Familiar interactions.

Repeated buttons, fields, and status patterns create one interaction language across the workspace. A clear primary action, visible focus, and explicit disabled states communicate what is available. The aim is to reduce uncertainty as users move between tasks.

BUTTONS / ACTION HIERARCHY
DefaultHoverFocusDisabled

One prominent action, with quieter alternatives. A visible focus ring supports keyboard navigation.

FIELDS / SEARCH & VALIDATION

Persistent labels give context; clear validation explains what needs correction. Preview fields only; no product data is submitted.

STATUS / LABEL + COLOUR
On trackDue soonOverdueInformation

Short, consistent terms repeat across the ledger, timeline, and project summaries.

ICONOGRAPHY / CONSISTENT OUTLINE
ProjectsDrawingsCalendarTeamSendApprovalSiteClock

Outline icons support scanning. Important actions retain a text label.

(LAYOUT & HIERARCHY)

The task changes. The hierarchy follows.

The overview is action-first; the timeline is date-first. Each layout gives more space to the information its task depends on, while grouping owners, dates, and actions with their drawing. This aims to shorten the path from scanning to a relevant decision.

OVERVIEW / ACTION-FIRST
Needs your attention

Metrics establish context; priority drawing releases appear before project imagery.

RELEASE TIMELINE / DATE-FIRST
Release → 7 days → Site

Dates become the main content; overview details become supporting context.

SYNC release timeline with labelled milestones and date axis
Date-first view / release timeline
Alignment

A stable left edge connects headings, cards, and detailed rows.

Grouping

Related dates, owners, and actions share the same drawing row.

Progressive disclosure

The timeline guide expands when needed; drawing details open in context.

Project scanning

SYNC projects screen mockup

Date-led hierarchy

SYNC release timeline mockup

(KEY WORKFLOWS)

From noticing a risk to taking action.

Each journey follows notice → understand → act, keeping drawing identity and timing in context. Resetting approval after a new revision avoids carrying an earlier decision into changed work. The intended outcome is clearer handoffs and fewer ambiguities about the next step.

SYNC drawing ledger with drawing identity, owner, release dates and approval status
Drawing ledger / decisions in context
GOAL

Know what needs attention and act on the right revision.

01Overview
02Overdue drawing
03Add revision
04Review approval

The drawing stays connected to its project, owner, deadline, and next action. A new revision resets approval.

Explore this workflow

Detailed drawing ledger

SYNC drawing ledger mockup

(MOTION & RESPONSIVE)

Measured motion. Flexible composition.

Motion explains state; responsive layout preserves meaning. A gentle stagger connects changes, while explicit mobile date cards retain timing when a calendar becomes too compressed. Reduced-motion support keeps the same information available without animation. The aim is continuity across states and screen sizes.

MOTION / TRY THE ENTRANCE

Flow with purpose.

600ms entrance · 100–260ms stagger.
Reduced-motion preferences disable transitions.

Replay the three-step release sequence.

Revision added01
Approval reviewed02
Release recorded03
DESKTOP / CALENDAR CONTEXT
2 NovToday · 4 Nov9 Nov
7-day lead time

The shared date axis makes drawing deadlines comparable.

MOBILE / EXPLICIT DATE CARD
MON-002Overdue

Roof truss connection details

Release by
2 Nov
Site starts
9 Nov
7-day lead time

Compact composition keeps dates explicit and readable.

(ITERATION & LIVE WEBSITE)

Refined through review. Ready to explore.

The comparison makes the reasoning behind stronger contrast, explicit milestones, and separate dashboard modes visible. Refinement is demonstrated; improvement still needs validation. Testing representative release tasks should reveal completion issues, misunderstandings, and navigation problems before better usability is claimed.

Earlier Google AI Studio SYNC overview screenshot
Earlier Google AI Studio build · original overview
Signals that stand out

Brighter status colours and darker text make urgency more visible.

A timeline that explains itself

Named milestones, an explicit date axis, and a Today marker replace ambiguous bars.

Two distinct dashboard modes

The calendar comes first in Release timeline; Overview keeps the broader practice view.

EXPLORE THE PRODUCT

Go beyond the frames.

Explore the dashboard, drawing ledger, and stage planner in the final Codex build.

Explore the hosted final build. Records remain in this browser; external delivery and a shared backend are not connected.
Open final build

Next validation: observe representative users finding an overdue release, interpreting the timeline, and preparing a drawing. Compare task completion, misunderstandings, and navigation paths before making outcome claims.

© 2026 Anush, All rights reserved.

© 2026 Anush, All rights reserved.

© 2026 Anush, All rights reserved.