As a new graduate designer working at a small marketing agency, I feel a bit lost right now. I've been assigned to create a large website with 14 pages, and the developer has expectations that my Figma designs are essentially 100% ready to go. They're looking for everything from autolayout to responsive design, named variables, and more, so they can just implement it directly. I was left to handle everything on my own—from creating the sitemap and content to the actual design—as I didn't even know what the company does initially! I wasn't allowed to contact other employees for help either; my boss wanted me to rely on Copilot for all the content.
I'm confused about what a "complete" Figma design entails. Does it really mean everything should be easily transferable to Webflow? I feel like I have more of a visual guideline, but I haven't included elements like vh, rem, or other complex styling that developers typically need. Am I missing something here, or are the developer's expectations not reasonable for someone in my position?
5 Answers
It's okay if you feel overwhelmed. Your dev isn't supposed to expect a complete handoff from you when you're new and working solo. Share your struggles with them! A dialogue can lead to better teamwork and lessen the burden on you.
In smaller teams or agencies, designers are often asked to deliver close-to-production-ready designs—like responsive states and autolayout. But what you're facing seems like a lot to handle alone. It's important to communicate with your developer about what they really need. You're practically working solo, and it's tough! Start with one page first and build from there.
Devs typically want a design that outlines the 'what' rather than the 'how'. A strong design system with defined colors, typography, spacing, and component logic makes it easier for developers to implement your vision. If your dev expects a fully coded design in Figma, they might not be seeing the bigger picture of what you contribute!
Try to aim for designs that are as ready for handoff as possible, but it's key to remember that development involves a lot more than transferring design to code. It's perfectly fine if everything isn't coded into Figma yet, just include sufficient details so that the dev won't have to guess your intentions. Clear communication on both sides will help reduce miscommunication and save time.
As a developer, I don't need everything to be pixel-perfect in Figma, but I do appreciate clear visual hierarchy, consistent spacing, and guidance on how elements behave at different breakpoints. What slows me down are missing states (like hover or loading screens) and designs that are perfect for one screen size but lack adaptability for others. Expecting a fully polished Figma from a new graduate working solo is a bit unrealistic, honestly.
Absolutely! Take it one step at a time, that way you can manage expectations better and get some feedback early on.