Lessons from a Failed Project

Every designer has that one project that reshapes the way they approach their work. For me, it was a project that seemed promising at first but ultimately failed—not because of a lack of skill, but because we skipped essential steps in the design process.

I was tasked with designing for a field I had no prior experience in. Taking on a challenge like this can be exciting, but only if the right steps are followed. Unfortunately, due to tight deadlines and decisions beyond my control, we bypassed nearly all of them.

For a project like this, the ideal process would have included:

1. Understanding the domain – Conducting research to grasp the workflows, pain points, and goals of the users in this field.

2. Stakeholder interviews – Speaking with users and industry experts to gather insights and clarify expectations.

3. Mapping workflows – Analyzing how tasks are performed to ensure the design aligns with real-world needs.

4. Competitive analysis – Looking at existing solutions to learn from best practices and common mistakes.

5. Wireframing and testing – Starting with low-fidelity designs to validate ideas and iterate based on feedback.

Instead, we jumped straight into creating high-fidelity designs based on ambiguous documents and assumptions. Many of our questions went unanswered, and we lacked the context needed to make informed decisions.

The result? The designs looked great but solved none of the actual problems. We didn’t win the client, and it was clear why. Without understanding the workflows or pain points, we created something visually appealing but functionally useless.

That project taught me a hard but valuable lesson: skipping the discovery phase, especially in unfamiliar domains, is a recipe for failure. A beautiful design is never enough if it doesn’t address real user needs. Research, iteration, and validation aren’t just optional steps—they are the foundation of a successful product.