Read More
Bio
hello@untangld.co
View Website
Scroll

We use cookies to make sure you have the best experience on our website. Fear not, we don’t sell your data to third parties.

AGREE & CLOSE
AGREE & CLOSE
REJECT ALL
REJECT ALL

Design First, Dev Later? Consider these 5 factors

by Rachel Bruins

4 min read

Before skipping developer input, weigh the pros and cons of a design-led approach

If you’re gearing up for your next digital project, you might be unsure of where to start. Should you jump into design right away, or get developers involved from the beginning? It’s a common question teams have when looking to expedite deliverables and streamline processes, whilst still wanting to deliver a great user experience.

Typically, UX designers and developers collaborate closely to balance creativity with technical feasibility. But what happens when design moves forward without developer input? To help navigate this approach, here are five considerations for those out there weighing this option.

1. Creative freedom vs Feasibility

Designers have a lot more room to innovate without worrying about stringent technical limitations, which can lead to more user-focused designs. On the other hand, some ideas may be more difficult or costly to implement without early developer insights, resulting in delays or re-work.

✨Tip: Try to check in developers for design reviews early to ensure technical feasibility.

2. Speed vs Implementation challenges

Designers can move faster without waiting for developer feedback – however, when developers eventually get involved, the team might hit some feasibility roadblocks, slowing the project down.

✨Tip: Schedule regular check-ins to address potential technical challenges early and estimate scope effort for future planning.

3. User-centric designs vs Technical debt

Designs made solely with users in mind offer great experiences. However, without technical oversight, these designs could introduce issues that lead to longer-term technical debt.

✨Tip: Have developers review key designs and processes to avoid potential costly technical complications. Collaboration and balance is key.

4. Short-term gains vs Long-term scalability

Without developers at the table, you can prioritise design needs and ship faster – great. But neglecting scalable solutions early on could lead to difficulties growing the product as user needs evolve (and naturally, they will).

✨Tip: Ensure the team is considering future scalability to prevent issues with product growth.

5. Innovation vs Business alignment

Design often pushes creative boundaries, but without technical input, sometimes those designs may not line up with business resources or goals.

✨Tip: Ensure design and development teams collaborate on aligning creative solutions with practical business objectives. Early and often!

 

Final Thoughts

While UX design without developers sparks creativity and user-centred innovation, ensuring technical feasibility through collaboration is ultimately essential for a smooth implementation phase. The key is to balance innovation with practicality for the best outcomes.

Have a question for Rachel?

Get in touch
Get in touch

Rachel Bruins

→ Rachel’s expertise lies in driving customer-focused initiatives, with a strategic data-driven business mindset. With over 11 years in advertising and consulting roles, Rachel has acquired a unique skillet working across a diversified portfolio of clients and programs spanning across OOH, Experiential, Digital, Web, Personalisation, CX and UX. She’s had the opportunity to work on transformative brand programs such as the Honda portfolio, Samsung, Parmalat, Ripley’s, Amex, Smirnoff and more.

Read Rachel
Read Rachel