Product design question
Assume users say Figma Weave’s multi-step creation pipeline feels too rigid for experts and too complex for newer users. How would you diagnose where the workflow is breaking down, and how would you decide whether the next investment should go into foundational workflow improvements versus user-facing UX changes?
- Figma
- Product design
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests diagnosing where a multi-step pipeline breaks down for two opposite complaints at once, too rigid for experts and too complex for beginners, and deciding foundational versus UX investment.
How to approach it
- Separate the two complaints by segment: interview experts about where rigidity blocks them, and newer users about where complexity overwhelms them, since these are likely different points in the pipeline.
- Check if experts are blocked by a foundational limitation, like a fixed step order that can't be skipped even when their workflow doesn't need every step.
- Check if newer users are overwhelmed by a UX limitation, like too many configuration choices exposed upfront instead of staged progressively.
- If experts are blocked by structural rigidity, that needs a foundational workflow change, since UX polish alone won't fix an inflexible structure.
- If newer users are overwhelmed mainly by UI complexity, that points to UX investment, progressive disclosure and better defaults, not a rebuild.
- Prioritize the foundational fix first if it's blocking the most engaged expert segment, since structural rigidity compounds over time.
What a strong answer includes
- Treats the two complaints as coming from different root causes rather than assuming one UI fix would solve both.
- Distinguishes a foundational structural limitation from a UX limitation, since they need very different investments.
- Uses segment-specific interviews rather than aggregate feedback, which would blur two opposite complaints into a confusing middle.
Common mistakes
- Assuming both complaints stem from the same cause and building one fix that satisfies neither segment well.
- Prioritizing UX polish for beginners while ignoring a foundational rigidity problem blocking expert depth.
- Reacting to whichever complaint was loudest most recently instead of segment-specific research.
Likely follow-up questions
- How would you sequence the foundational fix and the UX fix if both are needed?
- What would you do if fixing rigidity for experts makes it feel more complex for beginners?
More product design questions
- Figma Weave needs to grow beyond early adopters without losing the depth that power users value. How would you choose the first adjacent user segment to target, what evidence would you use to justify that choice, and what product changes would you ship in the first two quarters to make node-based workflows more approachable for that segment without capping advanced use cases?Figma · Product design · Hard
- Teams need to modify and extend shared workflows in Figma Weave without breaking brand consistency or creative intent. How would you design the abstraction model, such as templates, locked steps, editable parameters, permissions, previews, and versioning, so that teams get flexibility where it matters while preserving reliable, on-brand output?Figma · Product design · Hard
- Pick a core collaborative workflow in Figma, such as co-editing, commenting, or design handoff. How would you identify the highest-value user needs across different personas, simplify the workflow end-to-end, and decide what 'high craft' should mean in the final experience?Figma · Product design · Hard
- Design a TV for a car.Google · Product design · Hard
- Design a refrigerator for the blind.Google · Product design · Hard
- Redesign Twitter for eCommerce.Shopify · Product design · Hard
More questions from Figma
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 7: AI UX and human oversight: design for a system that is wrong sometimes
- Chapter 14: Get the job: the AI PM interview loop