Palash Sarkar has used Figma daily for years across brand identity work, product UI, and client presentations, and the beginner mistakes he sees most often aren't about missing some advanced feature — they're basic file-hygiene habits that cause real pain down the line. Here's the workflow Palash Sarkar recommends to anyone starting out.
Name Your Layers Like Someone Else Has to Read Them
"Rectangle 47" and "Group 12" are fine until a file has 40 frames and a developer needs to find the right button. Palash Sarkar names every layer with intent from the start — it takes seconds in the moment and saves real time later, especially on handoff, when a developer is scanning the layer panel trying to match design intent to code.
Frames, Not Groups, for Anything That Needs to Resize
New Figma users often default to grouping elements out of habit from Photoshop. Frames behave differently — they support Auto Layout, constraints, and clipping in ways groups simply don't. Palash Sarkar uses frames for almost everything structural and reserves groups for genuinely simple, static collections of elements.
Build Components Before You Need Ten of Them
The moment a button, card, or icon appears more than twice in a file, Palash Sarkar turns it into a component. Waiting until there are already a dozen inconsistent copies scattered across the file means a painful retrofit later — turning something into a component early is nearly free, and turning it into one after the fact is not.
Key Takeaways
None of Palash Sarkar's beginner Figma advice is about hidden power-user features — it's about habits that make a file usable by someone other than the person who built it. Layer naming, frames over groups, and early componentization are the three that pay off fastest.
Book a free consultation with Palash Sarkar at palashsarkar.com/book-a-call — he works with startups, agencies, and global brands from Dhaka, Bangladesh.