Member Avatar for graphixter

I belongs to a Website Design and Development Company. Always find people debating on the issue that whether a designer's job is important or a developer's...?

What do you say...?

Edited by Narue because: Snipped self-promotion link
  • 7 Contributors
  • 9 Replies
  • 128 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by somrita

Dani AI

Generated

This debate usually frames roles as opponents, but the practical question is which role solves the immediate problem for the product or business. Early-stage teams often need engineers to ship an MVP; scaling or retention-focused teams often need designers to tighten flows, reduce friction, and increase conversions. That reflects 's marginal-utility point and complements observations from , , , and about teamwork and the customer.

Use data to decide. Prioritize design when analytics show high bounce, low task completion, repeated usability complaints, or poor conversion funnels — these are UX signals that call for research, flows, and prototypes. Prioritize development when you see frequent outages, slow page loads, or growing tech-debt that blocks features — those are engineering signals. Run performance and accessibility audits with Google Lighthouse and align accessibility work to W3C WCAG. Complement quantitative data with quick usability tests or session replays.

A simple collaboration workflow that reduces the argument: agree goals and measurable acceptance criteria up front; designers produce low-fidelity flows then interactive prototypes; developers implement accessible, component-driven UIs and expose clear APIs; pair on edge cases and release criteria; automate performance and accessibility checks in CI; iterate with A/B tests and analytics. Adopt a living design system or component library so both sides share assets and a common language.

One person can wear both hats, but expect trade-offs in depth and speed. When assigning roles or hiring, look for process artifacts: research and prototypes for designers; readable, tested code and architecture notes for developers. Stop debating titles — measure impact, prioritize the bottleneck, and align both disciplines on measurable outcomes.

Recommended Answers

All 9 Replies

Member Avatar for Narue

Both are important. Duh.

commented: Lol +0
Member Avatar for pritaeas

They should rather spend their time debating on how they both can best work together to please the customer, as that is the one paying their salaries.

Member Avatar for graphixter

They should rather spend their time debating on how they both can best work together to please the customer, as that is the one paying their salaries.

I was talking about out there...general in communities...:)

Member Avatar for pritaeas

Narue is still right, one cannot work without the other. The discussion is pointless.

Edited by pritaeas because: n/a
Member Avatar for jwenting

Any developer you see working without a designer at his side is trying to make up his own designs (and is thus acting in 2 roles at once).
Some may be capable of doing this, most aren't.

Same with designers trying to make things without a developer to do the technical stuff.

commented: I agree +0
Member Avatar for Rashakil Fol

There is really no such notion of absolute utility of a position, there is only marginal utility. At some points on the (# developers, # designers) plane, adding a designer would give more benefit, while at others adding a developer would do so. For example, we might argue that at (0,0) it makes more sense to add a developer, since there'd be no hope of a project working with just a designer. However at some point like (10, 0) you really won't be helped by another developer but a designer would help a lot. Similarly, at (0, 1) it would certainly be better to add a developer instead of another designer, assuming making useful things brings value to the firm.

Member Avatar for xiÇŽo

I find this a really interesting debate, obviously you can't have one without the other. I do both at my work and would like to think, as I studied them both for a long time that I am capable of both. However it's apparent to me that regardless you will still have one that you are better at. I prefer designing over the developing side of it because my skills are stronger there. But in business I personally think that the developers role is more important. The designer in essence makes the shop window bringing in initial customers, but site can't perform it will completely ruin the effort you put in getting the customer there. Nobody likes an unstable and unreliable site and are unlikely to stay on it long enough or return. If you do a really good job on either side then the contribution is equal but if you both do a bad job I think that the developers work would have a worse impression. There are plenty of websites which are designed poorly but do the job, it's a waste but it's not something you couldn't overlook if the site does what it's meant to

Member Avatar for somrita

Nobody likes a poorly designed website.Similarly,good coding is required to make the website do its job.Both are important.

Member Avatar for somrita

Both equally important

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.