Shipping design from GMT−3

I have spent fifteen years designing for US companies from Brazil — through agencies, product teams and enterprise SaaS. GMT−3 to Pacific time is a five-hour gap, which everyone assumes is the hard part. It is not. The gap is a feature if you design your workflow around it; the hard part is everything teams pretend a timezone difference does not change.

The overlap window is sacred

My afternoon is a US morning — roughly four hours of real overlap. Those hours are for exactly two things: decisions and disagreements. Anything that needs a yes, a no, or a debate gets scheduled there. Everything else — reviews, feedback, walkthroughs — moves to async by default. Guard the window ruthlessly and a five-hour gap costs you almost nothing.

Ship words, not meetings

The habit that carried me through every US team: write the decision down before anyone asks. A design decision log — what changed, why, what I chose not to do — posted with every significant Figma update. Async work does not fail from lack of tools; it fails from work that arrives without its reasoning attached. A prototype with a paragraph beats a meeting with thirty slides.

Handoff is a design deliverable

Remote across timezones means the engineer picking up your spec might be starting their day as you end yours. There is no "quick question" bridge. So the spec has to answer questions before they are asked: real content, edge states, responsive behavior, and — whenever it moves the needle — working code. Half of what people call timezone friction is actually underspecified handoff.

Distance forces clarity. Clarity, it turns out, is just good design practice with the excuses removed.

The last few years, working on AI products made the async muscle even more valuable: models do not keep office hours either. The designers who thrive remote are the ones who treat communication as part of the craft — which, from ten thousand kilometers away, it very visibly is.