Ikssmoon
8 min read
April 21, 2025
The real design process
What actually matters, what doesn’t, and why your first messy project is totally okay.
When you're just starting out in product design, the pressure to “get it right” is real. You’ve seen polished portfolios with crisp UX flows, perfect files, and beautiful handoffs. But behind the curtain? Things are often messy, unclear, and full of course corrections.
This article isn’t about showing you the ideal process. It’s about showing you the real one—what’s essential, what you can skip, and how to keep your head straight when things get chaotic.
🧠 Step 1: Start With Curiosity, Not Confidence
Many new designers believe they need to walk into a project knowing everything. But the truth? Great design starts by asking better questions—not by having answers.
Before you open Figma or start sketching, take a moment to understand what you’re designing and why. Your job at this stage is to absorb, observe, and challenge assumptions.
Here’s how to prepare meaningfully:
1
🗣 Ask smart, basic questions. What’s the main goal of the website or product? Who will use it? What are they trying to get done?
2
🔍 Look around. Research direct and indirect competitors. What do their websites look like? What patterns repeat? What feels off or missing?
3
🧾 Write your insights down. Even if it’s messy—capture what stands out. You’ll reference this when making design decisions later.
🤝 Step 2: Structure Your Work, Even If It’s Just You
The start of a project can feel like stepping into fog—especially when you’re freelancing or collaborating remotely. That’s why a bit of structure goes a long way.
You don’t need formal contracts or big workflows. You just need clarity—on both sides.
Here’s what that can look like:
1
📆 Define a timeline. Agree on key milestones and when to check in. Weekly syncs work well, but even a shared status doc can help.
2
📂 Set scope early. What are you delivering? Pages, prototypes, handoff docs? Make sure everyone’s aligned to avoid surprises.
3
💬 Establish communication norms. Slack, email, Loom videos—whatever works for both parties. Consistency is key.
🔍 Step 3: Research With a Real-World Lens
“Research” can sound intimidating. But it doesn’t need to be a huge process with heatmaps and surveys. It’s really about getting close to the user’s world.
Done right, even a little research brings clarity and depth to your designs.
Here’s what you can do:
1
👥 Talk to people. If you can, speak to a few potential users. Ask them about their challenges, not just their preferences.
2
📝 Walk in their shoes. Try to perform the same task the user would. What’s frustrating? What’s unclear?
3
🌐 Read public feedback. App reviews, tweets, or Reddit threads about similar tools can reveal pain points you wouldn’t discover in a call.
👉 Research doesn’t need to be heavy—it just needs to be real.
✏️ Step 4: Map It Before You Make It
Designers often rush to the fun part: creating high-fidelity mockups. But without understanding the flow first, you risk designing pretty screens that don’t actually work.
Before diving into details, sketch the journey:
1
🧭 Map the user flow. What’s the user trying to accomplish? From entry to outcome, what steps do they take?
2
📐 Wireframe key points. Use boxes and placeholders. Focus on layout, not polish.
3
🎨 Define the visual tone. Build a moodboard or style tile. What emotions should the design evoke—trust, energy, calm?
4
📏 Start creating design components. Buttons, inputs, cards—basic elements that repeat. These will make scaling faster.
👉 The goal isn’t to be flashy—it’s to make thoughtful decisions with structure and consistency.
🧼 Step 5: Polish, Then Prepare for Dev Handoff
You’re “done” when the design can be built. That means preparing your work so it’s understandable and usable by developers or collaborators.
Handoff isn’t about making your Figma file look beautiful. It’s about reducing friction and uncertainty.
Here’s what helps:
1
🧹 Clean and label everything. Group layers, name them clearly, and organize by frames or pages.
2
📎 Leave notes and context. Hover states? Animation ideas? Edge cases? Annotate where needed.
3
📁 Provide assets. Export SVGs, prepare color codes, define spacing, and link fonts.
4
📞 Walk through your file. A quick Loom or call can save hours of back-and-forth.
👉 If someone can pick up your design without asking you 10 questions, you’ve done it right.
📬 Step 6: After the Launch, Keep the Conversation Going
A project doesn’t end at handoff—it just evolves. As the product goes live, you’ll learn more about how it performs in the wild. Stay engaged, even if lightly.
Here’s how to follow up without overstepping:
1
💌 Check in. A week or two after launch, ask how users are responding.
2
🔧 Offer light support. Willing to fix a small visual bug? Suggest a micro-improvement? It goes a long way.
3
🌱 Suggest the next move. Could they benefit from onboarding help? A design system?
4
👉 Being proactive after launch builds relationships—and repeat work.
👉 If someone can pick up your design without asking you 10 questions, you’ve done it right.
💡 Final Thoughts: There’s No One-Size-Fits-All Process
Your first projects might feel clunky. You’ll forget to ask something. You’ll redo work. You’ll hand off files that could’ve been cleaner. That’s not failure—it’s growth.
You’re not here to design perfectly.
You’re here to design intentionally.
The best way to improve? Reflect on what worked, what didn’t, and what you’d try differently next time. That’s the real process.