As designers, we often face the challenge of translating abstract requirements into tangible solutions. Over the years, one pattern I’ve observed—not just in others, but in my own workflow—is the tendency to jump headfirst into a design, work on it from start to finish, and then present it to stakeholders in its near-final form. This approach, while tempting, can often lead to a frustrating cycle of rework and missed opportunities for valuable early feedback.

One of my most significant learnings has been the importance of breaking down large goals into smaller, actionable checkpoints and involving stakeholders early in the process. Here’s why this matters and how it’s transformed my approach to design.

‍

The Trap of Perfectionism

In the past, I found myself pouring weeks of effort into fleshing out detailed designs for major features or applications before showing them to anyone. I believed that presenting a polished concept would demonstrate my dedication and expertise. However, the reality was often different. Stakeholders would point out issues, suggest changes, or introduce new constraints that hadn’t been considered. This often meant undoing significant portions of my work.

For smaller features, this approach might work. Quick turnaround and limited scope can sometimes make a fully-formed design a viable starting point. But for larger features or big ideas, it’s a different story. Waiting too long to share your designs can result in a significant misalignment between what you’re building and what stakeholders or users truly need.

‍

Breaking Down the Process

The shift came when I started treating design as a series of iterations rather than a one-time delivery. Instead of aiming for a perfect solution upfront, I began dividing my goals into smaller checkpoints and focusing on achieving one milestone at a time.

Take, for instance, my experience designing the MVP (Minimum Viable Product) for a speech-to-note application. The project was complex, with multiple flows and functionalities to consider. Instead of trying to build and refine the entire app in one go, I honed in on the recording flow as my first checkpoint.

Once I had a rough, low-fidelity draft of the recording flow, I shared it with the team—stakeholders, developers, and even potential users. This early feedback loop was invaluable. It highlighted constraints I hadn’t considered and opportunities to enhance the user experience that I might have overlooked.

‍

Why Early Feedback Matters

When you share your designs early:

1. Stakeholders Become Users: As soon as your ideas take visual form, stakeholders can start seeing the product from a user’s perspective. This shift often brings up critical insights that might not emerge from abstract discussions alone.

2. You Stay Aligned: Early feedback ensures that your designs remain in sync with the overarching goals and constraints of the project. Misalignment caught early saves time and effort later.

3. It Encourages Collaboration: Sharing drafts fosters a sense of collaboration and ownership among team members. Everyone feels involved in shaping the final outcome.

4. It Reduces Rework: By addressing potential issues at smaller checkpoints, you avoid the need for extensive revisions later in the process.

‍

Building Checkpoints into Your Workflow

Here’s how you can implement this approach in your own design process:

Divide Big Goals: Break down your project into smaller, manageable chunks. Focus on one feature, flow, or interaction at a time.

Share Rough Drafts: Don’t wait for perfection. Share low-fidelity prototypes or sketches to gather initial impressions.

Seek Diverse Feedback: Include stakeholders, team members, and users in your feedback loop. Each group brings a unique perspective.

Iterate Quickly: Use the feedback to refine your designs and move on to the next checkpoint.

‍

A Final Thought

Design is an iterative process, and perfection is a moving target. By embracing feedback early and often, you not only save yourself time and effort but also create better products that truly meet user and stakeholder needs.

The next time you sit down to design, remember: you don’t need to finish everything before you share it. Start small, share early, and iterate. It’s a habit that has transformed the way I work—and it might just do the same for you.

‍