The work behind work that just works
Figma feels simple because someone made the hard calls underneath. What the team’s behind-the-scenes video teaches the rest of us about hiding complexity.
Words: There’s a line in Enrico Tartarotti’s behind-the-scenes video with the Figma team that should probably be printed out and taped to the wall of every studio, product room and marketing department:
Users don’t care about your rules. They care that it works how they expect. And they’re not the same thing.
That’s the whole game.
A lot of organisations think good design is what happens when a system is clean, logical and well documented. That helps. But people don’t experience your internal logic. They experience the thing in front of them, usually while trying to get something done.
If the system is technically correct but behaves in a way that feels wrong, it’s wrong.
The video is fascinating because it shows Figma’s simplicity isn’t magic. Figma feels simple because a huge amount of design, engineering and product judgement has been pushed behind the surface.
Early in the video, Enrico says:
The products that seem so simple and magical, the ones that just work, are actually the ones that hide the most complexity. You just never get to see it.
That’s a good way to think about almost any brand or digital project.
The hard part is deciding what the surface shouldn’t have to explain.
Simple isn’t the same as basic
Figma is a powerful tool. It handles multiplayer collaboration, design systems and now AI-assisted work on the canvas.
But the interface doesn’t open by shouting all of that at you.
That restraint is deliberate. In the video, the team talks through tiny behaviours that most users would never consciously notice: what happens when you paste an object into a frame, which layer moves when one object sits visually above another, how alignment behaves when several selected items belong to different groups, and why undo should sometimes undo a selection mistake even though the file itself didn’t change.
One of the Figma team members says:
Copy and paste is a whole other mess in terms of rules, but because we spent so much time deciding what the rules are… it now mostly does the right thing.
That phrase, “mostly does the right thing,” is doing a lot of work.
It’s different from “follows the rule.” In fact, the video shows cases where following the pure rule would create a worse experience. If an object is pasted according to exact coordinates but lands out of view, the system may be accurate, but the user is lost.
So Figma bends the rule to protect the experience.
That’s design maturity.
It comes down to judgement.
The best work hides the argument
Good creative work often feels obvious after it exists.
The line, the homepage structure and the sales deck all feel obvious.
But obvious is usually the result of decisions that weren’t obvious at all.
The Figma team says it plainly:
The best products and the best product decisions are ones that lead to simplicity. Getting to the simplicity is the hardest part.
That applies well beyond software.
A brand system should hide the argument that produced it. A campaign shouldn’t make the audience sort through the meeting notes, and a pitch deck shouldn’t prove how hard the team worked by showing every possible detail.
The work should arrive with the right amount of confidence.
Stripping everything back until it’s plain can be lazy. The aim is to do enough thinking behind the scenes that the person using the thing gets a cleaner path.
At Qualls, this is where our “useful by design” bias comes from. The work should be noticed, yes. But it should also help someone understand faster or take the next step without needing a guided tour.
The undo button is a brand lesson
One of the smallest examples in the video is also one of the best.
In most tools, undo reverses a change to the file. But in a design tool, a misclick can be expensive even if it doesn’t alter the file. You lose a careful selection and have to rebuild the state you were in before the mistake.
A Figma team member describes the feeling:
Most tools don’t allow you to undo a selection. Like, that wasn’t worth undoing. And I’m like, ‘No, that was worth undoing. Please just undo this for me.’
That’s such a small thing. It’s also exactly the kind of small thing that makes people trust a product.
The system understands the human cost of the mistake.
Brands have their own version of this.
A customer shouldn’t have to re-explain context every time they move from sales to service. A marketer shouldn’t have to rebuild a layout from scratch because the brand system only works in the original presentation.
The technical rule might be defensible. The experience may still be wrong.
Progressive complexity beats forced complexity
The video also gets into one of the hardest product design problems: how to make something powerful without making it scary.
Figma has serious depth. Components, variables and design systems can get sophisticated quickly. But the product still lets someone start by drawing and moving simple objects.
One quote captures the attitude nicely:
Do you want to use a design system? Cool, use a design system. Do you just want to duplicate your frame 10,000 times and edit every border by yourself? That is okay, too.
That’s progressive complexity. Let people enter at the level they’re ready for. Let the system reveal more power as the user’s need becomes more specific.
This matters for websites and content systems too.
A good CMS shouldn’t punish a marketing team for wanting control, and a good brand system shouldn’t force every user to understand the entire architecture before they can make one decent asset.
Power should be available without being dumped on the table all at once.
AI makes the old design problems new again
The last section of the video looks at Figma’s AI work. This is where the piece turns to the next wave of interface design.
AI introduces a strange challenge: the user can ask for almost anything, but the system still has to decide what the request means inside a specific working environment.
A Figma team member gives a simple example:
If I say make this centered, does that have a right answer? Yes. But something like make this title pink, does that have a right answer? That depends.
That’s the new design problem in a sentence.
AI increases the need for product judgement. The system has to understand intent, context and what the user probably meant but didn’t spell out.
This is why the easy AI story, “just prompt it and it works,” is too thin.
The AI products that last will understand where the user is, what they’re trying to do and how much control they need before the system becomes annoying.
In the video, Figma experiments with where the assistant should live on the canvas, when it should disappear and how it can borrow interaction patterns people already know from comments.
That’s the detail that matters.
Where does it live?
What does it know?
How does it recover when it gets the wrong idea?
Does it preserve flow, or become another panel to manage?
Those are design questions before they’re technology questions.
What we take from it
Very few of our clients need a product interface as deep as Figma.
But every organisation has some version of the same problem: complexity behind the offer, the internal process and the sales conversation.
The question is where that complexity should go.
Bad work hands it to the audience. Good work absorbs it.
That’s the lesson from Figma. The surface can feel simple because somebody cared enough to make the hard decisions underneath it.
It’s a good standard for any brand or digital work.
Make the important thing easier to see and the next step easier to take. Hide the complexity where it belongs.
The work underneath can stay complicated.
The experience should feel simple.