Don't start designing landing pages in Figma. Begin with an unstructured "brain dump" of all copy, ideas, and data in a text document. First, organize this content into sections (Hero, Problem, etc.), then build the visual wireframe. This prevents design constraints from prematurely limiting your content strategy.
Related Insights
AI-powered "vibe coding" is reversing the design workflow. Instead of starting in Figma, designers now build functional prototypes directly with code-generating tools. Figma has shifted from being the first step (exploration) to the last step (fine-tuning the final 20% of pixel-perfect details).
To increase the "memobility" of your ideas so they can spread without you, package them into concise frameworks, diagrams, and stories. This helps others grasp and re-transmit your concepts accurately, especially when you can connect a customer pain to a business problem.
The "Fool's Cap Method" combats the paralysis of starting a big project. Forcing yourself to outline the entire arc—beginning, middle, and end—on one page eliminates complexity and builds confidence. It distills the project to its essentials before you get lost in details.
The data-driven prototyping approach separates the UI from the content. This enables rapid iteration, allowing you to generate entirely new versions or localizations of a prototype (e.g., a trip to Thailand instead of Paris) simply by swapping a single JSON data file, without altering any code.
Canva operationalizes big ideas using a "chaos to clarity" framework. An initial chaotic idea is progressively clarified through small, tangible steps—starting with writing it down and culminating in a vision deck. This process makes amorphous concepts real, shareable, and easier to build.
Instead of providing a vague functional description, feed prototyping AIs a detailed JSON data model first. This separates data from UI generation, forcing the AI to build a more realistic and higher-quality experience around concrete data, avoiding ambiguity and poor assumptions.
Before starting a project, define its intended feel with key adjectives (e.g., "techie," "classical," "sharp"). This vision becomes a powerful filter, helping you make consistent decisions and resist the temptation to chase trends or get discouraged by other designers' work.
A powerful but unintuitive AI development pattern is to give a model a vague goal and let it attempt a full implementation. This "throwaway" draft, with its mistakes and unexpected choices, provides crucial insights for writing a much more accurate plan for the final version.
Instead of immediately building, engage AI in a Socratic dialogue. Set rules like "ask one question at a time" and "probe assumptions." This structured conversation clarifies the problem and user scenarios, essentially replacing initial team brainstorming sessions and creating a better final prompt for prototyping tools.
When exploring UI solutions, use a tool like Magic Patterns and its "Inspiration Mode" to generate multiple, distinct design approaches from a single prompt. By asking the AI to "think expansively and make each option differentiated," product managers can quickly explore a wide solution space and avoid getting stuck on a single initial idea.
