GEMINI POWERED · BUILT IN GOOGLE AI STUDIO
IN SYNC, NO BUILD
EVER WAITS ON A
DRAWING.
IN SYNC, NO BUILD
EVER WAITS ON A
DRAWING.
DISCIPLINE
Product Design · Web App
FOR
Askew In · Architecture & Interiors
YEAR
2026
( WORK 04)
PRODUCT DESIGN
WEB APP
SYNC
SYNC
Askew In needed a console capable of turning a builder’s raw site schedule into drawing
deadlines the studio could actually work to. The challenge wasn’t tracking more drawings—it
was making the timing already buried in the schedule visible before it cost a site day.
Askew In needed a console capable of turning a builder’s raw site schedule into drawing deadlines the studio could actually work to. The challenge wasn’t tracking more drawings—it was making the timing already buried in the schedule visible before it cost a site day.
CLIENT
CLIENT
Askew In · Architecture & Interiors
TIMELINE
TIMELINE
JUL 2026
SERVICES
SERVICES
UX RESEARCH
PRODUCT DESIGN
DESIGN SYSTEM
GEMINI
GOOGLE AI STUDIO
↳
LIVE PROJECT
(OVERVIEW)
Askew In runs two disciplines—architecture and interior design—across concurrent luxury residential and
commercial builds. Every one of those builds rests on a single quiet assumption: that drawings reach site
before the crew needs them. In practice the studio operated in permanent catch-up mode, reacting to site
delays instead of preventing them.
Askew In runs two disciplines—architecture and interior design—across concurrent luxury residential and
commercial builds. Every one of those builds rests on a single quiet assumption: that drawings reach site
before the crew needs them. In practice the studio operated in permanent catch-up mode, reacting to site
delays instead of preventing them.
SYNC was built to close that gap—a single operational hub that translates the builder’s world into the design
office’s world and keeps every discipline reading the same clock. Rather than another file store or task list, it
was framed as a timing instrument: something that makes lead time visible, measurable and defensible
across the whole portfolio. The product was designed and built end to end in Google AI Studio as the
capstone of the Google AI Professional Certificate, carrying it from problem framing through to a working,
AI-powered console.
SYNC was built to close that gap—a single operational hub that translates the builder’s world into the design
office’s world and keeps every discipline reading the same clock. Rather than another file store or task list, it
was framed as a timing instrument: something that makes lead time visible, measurable and defensible
across the whole portfolio. The product was designed and built end to end in Google AI Studio as the
capstone of the Google AI Professional Certificate, carrying it from problem framing through to a working,
AI-powered console.
(THE CHALLENGE)
Three operational failures were compounding into the same outcome. First, the lead-time gap: contractors
hand over Gantt charts listing site activity start dates, but a design office works off drawing readiness dates
that sit seven to ten days upstream. That gap is almost never made explicit, so someone back-calculates it by
hand, project by project, trade by trade. Miss it and site work doesn’t slow down—it stops.
Three operational failures were compounding into the same outcome. First, the lead-time gap: contractors
hand over Gantt charts listing site activity start dates, but a design office works off drawing readiness dates
that sit seven to ten days upstream. That gap is almost never made explicit, so someone back-calculates it by
hand, project by project, trade by trade. Miss it and site work doesn’t slow down—it stops.
Second, operational silos. Architecture, interiors and third-party MEP or structural consultants each worked
in their own tools, file versions and inboxes, with nothing enforcing a single source of truth. A drawing would
be marked final on one side while another team was still working off a stale revision—discovered only once it
was already on site.
Second, operational silos. Architecture, interiors and third-party MEP or structural consultants each worked
in their own tools, file versions and inboxes, with nothing enforcing a single source of truth. A drawing would
be marked final on one side while another team was still working off a stale revision—discovered only once it
was already on site.
Third, invisible staff overload. Workload lived in someone’s head or in a spreadsheet nobody updated, so
there was no live picture of which drafter was buried and which had capacity. By the time overload surfaced,
it had already surfaced as a missed deadline. The problem was never a drawing problem. It was a timing
visibility problem.
Third, invisible staff overload. Workload lived in someone’s head or in a spreadsheet nobody updated, so
there was no live picture of which drafter was buried and which had capacity. By the time overload surfaced,
it had already surfaced as a missed deadline. The problem was never a drawing problem. It was a timing
visibility problem.
(OUR APPROACH)
SYNC was built around four surfaces, each answering one question the old process left open. An AI Stage
Planner, powered by Gemini inside Google AI Studio, takes the builder’s raw schedule exactly as it arrives—
email, WhatsApp transcript or PDF—audits it against standard RCC benchmarks, and derives draft-and-
release deadlines with the seven-to-ten day buffer already built in. The output isn’t a converted date; it’s a
safe one.
SYNC was built around four surfaces, each answering one question the old process left open. An AI Stage
Planner, powered by Gemini inside Google AI Studio, takes the builder’s raw schedule exactly as it arrives—
email, WhatsApp transcript or PDF—audits it against standard RCC benchmarks, and derives draft-and-
release deadlines with the seven-to-ten day buffer already built in. The output isn’t a converted date; it’s a
safe one.
A Dynamic Release Ledger holds every drawing’s version, assignee, check state and release status in one
living record shared across both wings and outside consultants, so the “which file is current” question has
exactly one visible answer. A Staff Workload console maps real-time deployment across architecture and
interiors, surfacing bottlenecks before they become delays. Underneath all three, a durable buffer alarm
watches the distance between drawing readiness and site need, firing the moment any margin drops below
the critical seven-day threshold.
A Dynamic Release Ledger holds every drawing’s version, assignee, check state and release status in one
living record shared across both wings and outside consultants, so the “which file is current” question has
exactly one visible answer. A Staff Workload console maps real-time deployment across architecture and
interiors, surfacing bottlenecks before they become delays. Underneath all three, a durable buffer alarm
watches the distance between drawing readiness and site need, firing the moment any margin drops below
the critical seven-day threshold.
Visually the system was kept deliberately quiet. A restrained teal-and-signal palette, one geometric sans
carrying the hierarchy through weight alone, and monospace reserved strictly for dates, revisions and site
data—so that colour only ever appears when something needs attention.
Visually the system was kept deliberately quiet. A restrained teal-and-signal palette, one geometric sans
carrying the hierarchy through weight alone, and monospace reserved strictly for dates, revisions and site
data—so that colour only ever appears when something needs attention.
(RESULTS & IMPACT)
SYNC turns a silent, slow-building risk into an explicit one. Across the live portfolio it holds a 92% on-time
buffer rate against the studio’s own seven-day rule, while the alert console surfaces every breach as it
happens—four critical risks flagged and traced back to their drawing register on the day of review, rather
than discovered on site.
SYNC turns a silent, slow-building risk into an explicit one. Across the live portfolio it holds a 92% on-time
buffer rate against the studio’s own seven-day rule, while the alert console surfaces every breach as it
happens—four critical risks flagged and traced back to their drawing register on the day of review, rather
than discovered on site.
More importantly, the studio now argues from a shared clock. Release progress, buffer margin and workload
sit on one screen for both wings, so conversations about slippage start from the same record instead of three
competing versions of it. Where the builder’s timeline says “site work,” SYNC says exactly what the design
team needs ready, by when, and who is behind.
More importantly, the studio now argues from a shared clock. Release progress, buffer margin and workload
sit on one screen for both wings, so conversations about slippage start from the same record instead of three
competing versions of it. Where the builder’s timeline says “site work,” SYNC says exactly what the design
team needs ready, by when, and who is behind.
