I work for a small startup, and I'm the sole UX designer, responsible for a couple of products. I also have the duty of ‘product owner’ managing the sprints and epics we tackle every two weeks. I’ve implemented a UX design process, that has been in place since the start that the stakeholders and team understand clearly. There is full transparency into this process, the documentation, the UI and the prototypes. For example if we have an idea, or we have an hypothesis. I research the idea. I make sure it aligns with our target audience (via persona’s). I build out scenarios and user flows. The I go to wireframes and/or prototyped and/or design - depending on the scope. For larger epics we do user testing.

The issue I’m having is with the expectation from a developer that the designs be 100% complete and accurate. I feel this is not reasonable given the size of the company we are, and the breadth of duties I (and all of us) have. I’ve worked with companies in the past, where if there were a gap in the design or UX, it’s brought up with myself or my team, and we provide the solution then and there. Problem solved, we all continue moving forward.

This is becoming frustrating - as it’s beginning to erode the teams moral a bit. For instance, when there is a QA bug or gap, which I identify, the usually response is “…it should have been in the design then”.

Looking for ideas and advice on how to mitigate this. Thanks in advance.

  • 4
    That's not a 'UX question' but a 'how do I work together with my team' question. You could try an introspective to find out what went wrong and how it can be done better in the next sprint. Communication is key, so tell your team that you can't do both jobs 100% right at 50% of time (product owner and UX Designer) and that you need their support instead of finger-pointing.
    – Mischa
    Jan 21, 2018 at 13:03
  • 1
    Also voting to close. It's a relevant question for the designers themselves, but it doesn't have anything to do with UX. I wish you luck in your attempts to bridge the gap between developer expectations and your work though. I've been in similar situations and it's very frustrating when people don't treat it as a continuous team effort, but a 'throw it down the fence' thing. Jan 22, 2018 at 8:26

1 Answer 1


It's called a team for a reason.

I used to work for a financial startup as a developer. We had only 1 UI/UX designer and 3 devs for over a year. Within that time we built over 200 websites. This would never have been possible if us devs didn't help the designer in improvements or ideas of a design during development.

A dev can't just blindly follow a design and not think about some of the implications a design may have.

  • That has been my experience before, and oddly enough this has been something I've communicated, re:help the designer. Thanks for input though. Jan 21, 2018 at 5:32

Not the answer you're looking for? Browse other questions tagged or ask your own question.