Thank you for this video! As a junior designer and only having worked with QA and Engineers once, it's refreshing to see that even at Uber, there can be design discrepancies in the QA environment. I always felt like I was doing something wrong when the designs didn't look like mine. This is so helpful!
Sometimes I get really frustrated with the developers on my team when they butcher my designs. It made me feel a little bit happy to find out these things happen even in a giant company like Uber :)
Brilliant video. We do something that wasn’t mentioned in your video but I feel is very important to the process. We have an initial design review session with engineering at the beginning of a project. This session allows engineers to feel more involved in the design process and call out any concerns they might have in the implementation of a design. Sometimes this can lead to designs changes which I record in InVision. After all engineering feedback is made to the designs then designs are signed off and over to engineering. I find including engineering early on makes implementation much smoother. Also Im a little shocked when I seen the differences between the design and implementation in this video. It makes me think the engineers are not working off a design framework. In order to limit the amount of design deviations it’s very important to define a design system and have engineering all working off that. That way they can share/reuse components which boosts productivity and maintains overall consistency.
Hi Femke, I have a question regarding how you use JIRA. You mentioned that the engineers will create a ticket to fix the design discrepancy and that you will go in an leave feedback and notes in JIRA. How do you mark off which issues have been fixed on your end? Do you have a separate tool (i.e. figma) you use to track the things that need to be fixed, or do you refer to JIRA to track those fixes after moving onto JIRA? Thanks for this video, its super helpful to see how the process is different and similar in some ways at other companies.
hi! I am a product designer looking to standardize this process in a remote environment and this video really helped! However, I am tight on time as it is so I wanted to ask: does your PM built the time for you to make all these annotations into the project timeline? I could see how this could take hours and some back and forth and that is technically cutting out of your designing time, so I wanted to see how much time you usually have for it and if it is considered in the roadmaps. thank you!
So just agile development... Doesn't everyone do that nowadays? Also, you might wanna specify that this is about IT-engineering (or maybe just call it development) since this might confuse actual engineers.
We let the designers code the visual part of the frontend to remove this arduous process. Downside of that: less time spent designing and more time spent coding. And your designers have to know how to code then.
A step further is having a team doing Lean UX and having a working design system. I currently work in such a team, and it works so well, designers and developers are working so well together that this going back and forth is eliminated, and everyone feels great with each other.
Also downside is you have to find and pay this unicorn accordingly. -- to the other comment. Totally agree... robust design systems can be a great bridge between design and engineering.
Thanks for sharing. I'm an "introvert" UI/UX Designer who often found a lot of struggles and courage to deal with engineers. Plus, the company I worked for was not exactly on Agile/structured workflow. Often I found my only solution is to schedule a time with the exact engineers and sit beside him, "guiding" him to do it on the spot while I can cross off my QA list. That was not a great experience and I don't enjoy doing it. I hope every project manager could appreciate the importance of structured workflow. Jira sounds like a great solution!
Your videos are SO informative. One piece of feedback I have though is that the volume you edit your speaking at could be higher. I had to crank my volume up pretty high to hear you comfortably, and then when the outro music played I almost screamed. Otherwise I can't wait for more of your content
It's so reassuring to see that I'm not the only one who has devs that completely butcher the design. It's even more reassuring to know my method of tackling the design changes is almost similar to yours. P.S I'm an only UX designer in my company
Video is great .... BUT great front end developers should do their own design QA! Designs systems and Figma tell them exactly what things should look like. There shouldn't be more than 3(?) mistakes on a page and they should be small mistakes.
as someone who is new to this field, ma'am let me be honest with you . i really am inspired by your work, and i love your content , they come in so handy . thank you for making such contents.
How do you check if eng fixed the change properly after you put the ticket in Jira? Or do you kind of just trust them to have done it correctly once they mark it as complete?
Hey femke, we use figma for the QA towards the end of design process. For me the communication is still lacking as the development never come out like the design :( thanks for the video, will try the involve engineering from the beginning for smoother flow!
Thanks for the video Femke, for me I have found dropbox very handy in writing my feedback and breaking it down into nitty gritty. The process is not as neat as what you have here but its a combination of using Monosnap to take screenshots and annotations, adding the screenshots in Paper and embedding the figma link also, and rasing some of these are issues on Azure Dev ops. Some of our front end engineers still have some way to go with tidying up some of the CSS styles so I sometimes find myself using Inspect in chrome to check if the style matches the design and guide them on how to write it properly (I have some HTML, CSS and JS knowledge). Thanks for sharing
Hey Femke! Thanks for sharing this :) Have there been any major process changes since you've posted this? How much time do you typically spend in the QA process? Thanks!
This is why visual QA is so important!! Designers immediately see what went wrong during implementation, and we often think, how in the world did they miss this? Hahaha. Yes working in increments is def recommended and we also use Jira for Visual QA, makes the process so much easier.
Thank you for sharing! Just out of curiosity, does your employer know you are sharing the screens and if that is allowed? Another question is, wouldn't the product manager be the one creating the ticket in JIRA and cross checking if Dev has made the right development? We are a bit more old-school and make these nicely presented PDFs that we send off to Devs, there's a lack of communication with the designers and dev but the mainly the Journey Owner (and Product Manager) should be the ones keeping them in check every day.
@@femkedesign I think each company has different tasks for each position. It's just how ours work - they're more like a requirements manager/consultant so they would make sure the changes are made and write tickets for designers/copywriters. But like I said, it's mainly the Journey Owner that dedicate the QA, our PM can answer any questions and add tasks for designers/copywriters. What does your PM do in your company?
Thanks Femke , great content :) We use pretty much the same process in my company (medium size agency). What i also find really efficient and fast is just go and have a sit next to my favourite Front End dev and do some corrections live together , much can be done in just 30 minutes without producing any unnecessary docs, but it doesn't work well for a remote environment...
a simple solution to this is to just be a unicorn that can do ux research, design, code front end, and also give ROI presentations on the changes made. duh. easy enough, considering that's what job requirements expect of people. then none of the designs will have issues in the code /s
love this - thanks for sharing your process with us :) our methods have been pretty silo'd with eng and design, We usually QA after its built but I like that you do it prior to the final AND keep track of it in Jira. I'm curious are your product managers ever involved with implementing new ways with collab with eng?
We share WIP designs with eng so that any major concerns can be expressed upfront, then, at the point of "ready for dev" have a 3 amigos which would typically include design, engineering, product owner to review the designs and kick off the implementation. Once eng has completed a ticket, they'll share their work with us in a catch-up, and I'll give notes on the fly... but having a more formal approach within Jira would make things more transparent and give designers more time to consider the review stage! Great video thanks for the tips :)
Haver you ever tried to QA with Jira? You could actually create the ticket for implementing the feedback and keeping track of it. We had an environment for Design QA in Jira that was super helpful. They we establish our process was by sitting with QA and they were helping us to create the environment. The key thing here is that Developers need one source for feedback.
@@femkedesign Thank you, I'm new to UI/UX with a graphic design and art direction(advertising) background and I find your videos really helpful, especially dealing with the fear of not knowing enough about the UX industry. So thank you
You know, thats really very bad quality engineering. Sorry that you have to police them around... This is definitely not your job to do as a designer... Just a note for newbies who might think this is normal, it is not. If your developer is not able to complete the task they are given properly, you really should talk with them about this and if it keeps happening, you really need to talk with their manager. If they keep on doing this, they will eventually get fired... I mean what kind of developer can't get a font size or color correct? duh..
I'm not sure it's about "can't get it right" but often if you have a broad and/or rapidly growing design system then you might have discrepancies between Figma/Sketch and front end libraries. The button without padding I agree was a big oversight but something like coding a slightly different font weight for a header is a common inconsistency that should be called out designers who know the system well.
@@jacsarah Maybe but the differences between the design and the end version are huge. Obviously the developer who built this, didn't even care to check if he did all according to the design or not. Even a kid would have seen the differences... And if you have such big
![FendiDa Rappa - Clock Dat ft. Shamar Marco [Official Music Video]](http://i.ytimg.com/vi/3NBU8KHdxYY/mqdefault.jpg)
Thank you for this video! As a junior designer and only having worked with QA and Engineers once, it's refreshing to see that even at Uber, there can be design discrepancies in the QA environment. I always felt like I was doing something wrong when the designs didn't look like mine. This is so helpful!
Sometimes I get really frustrated with the developers on my team when they butcher my designs. It made me feel a little bit happy to find out these things happen even in a giant company like Uber :)
Brilliant video. We do something that wasn’t mentioned in your video but I feel is very important to the process. We have an initial design review session with engineering at the beginning of a project. This session allows engineers to feel more involved in the design process and call out any concerns they might have in the implementation of a design. Sometimes this can lead to designs changes which I record in InVision. After all engineering feedback is made to the designs then designs are signed off and over to engineering. I find including engineering early on makes implementation much smoother. Also Im a little shocked when I seen the differences between the design and implementation in this video. It makes me think the engineers are not working off a design framework. In order to limit the amount of design deviations it’s very important to define a design system and have engineering all working off that. That way they can share/reuse components which boosts productivity and maintains overall consistency.
no love this button so just going to say it. Love this.
Hi Femke, I have a question regarding how you use JIRA. You mentioned that the engineers will create a ticket to fix the design discrepancy and that you will go in an leave feedback and notes in JIRA. How do you mark off which issues have been fixed on your end? Do you have a separate tool (i.e. figma) you use to track the things that need to be fixed, or do you refer to JIRA to track those fixes after moving onto JIRA? Thanks for this video, its super helpful to see how the process is different and similar in some ways at other companies.
Awesome video! Thank you very much for sharing this Tutorial Femke! Could you also do the series of how to work with PM? 😊🧡
It looks like an agile framework for developing code works very well connecting the UX design process as well. Great demonstration!
hi! I am a product designer looking to standardize this process in a remote environment and this video really helped! However, I am tight on time as it is so I wanted to ask: does your PM built the time for you to make all these annotations into the project timeline? I could see how this could take hours and some back and forth and that is technically cutting out of your designing time, so I wanted to see how much time you usually have for it and if it is considered in the roadmaps. thank you!
So just agile development... Doesn't everyone do that nowadays? Also, you might wanna specify that this is about IT-engineering (or maybe just call it development) since this might confuse actual engineers.
We let the designers code the visual part of the frontend to remove this arduous process. Downside of that: less time spent designing and more time spent coding. And your designers have to know how to code then.
A step further is having a team doing Lean UX and having a working design system. I currently work in such a team, and it works so well, designers and developers are working so well together that this going back and forth is eliminated, and everyone feels great with each other.
Also downside is you have to find and pay this unicorn accordingly. -- to the other comment. Totally agree... robust design systems can be a great bridge between design and engineering.
Thanks for sharing. I'm an "introvert" UI/UX Designer who often found a lot of struggles and courage to deal with engineers. Plus, the company I worked for was not exactly on Agile/structured workflow. Often I found my only solution is to schedule a time with the exact engineers and sit beside him, "guiding" him to do it on the spot while I can cross off my QA list. That was not a great experience and I don't enjoy doing it. I hope every project manager could appreciate the importance of structured workflow. Jira sounds like a great solution!
Your videos are SO informative. One piece of feedback I have though is that the volume you edit your speaking at could be higher. I had to crank my volume up pretty high to hear you comfortably, and then when the outro music played I almost screamed. Otherwise I can't wait for more of your content
It's so reassuring to see that I'm not the only one who has devs that completely butcher the design. It's even more reassuring to know my method of tackling the design changes is almost similar to yours. P.S I'm an only UX designer in my company
Definitely not alone!
In the throws of my first real UX project and, yep, the developer asked me to create tickets in GitHub. Good to know that happens elsewhere.
Silly question, is more appropriate to call them engeneers or developers? If engeneers why so?
Video is great .... BUT great front end developers should do their own design QA! Designs systems and Figma tell them exactly what things should look like. There shouldn't be more than 3(?) mistakes on a page and they should be small mistakes.
as someone who is new to this field, ma'am let me be honest with you . i really am inspired by your work, and i love your content , they come in so handy . thank you for making such contents.
How do you check if eng fixed the change properly after you put the ticket in Jira? Or do you kind of just trust them to have done it correctly once they mark it as complete?
Hey femke, we use figma for the QA towards the end of design process. For me the communication is still lacking as the development never come out like the design :( thanks for the video, will try the involve engineering from the beginning for smoother flow!
Not all heroes wear capes. But you see this video right here, it will always be on time and Amazing!
Thanks for the video Femke, for me I have found dropbox very handy in writing my feedback and breaking it down into nitty gritty.
The process is not as neat as what you have here but its a combination of using Monosnap to take screenshots and annotations, adding the screenshots in Paper and embedding the figma link also, and rasing some of these are issues on Azure Dev ops.
Some of our front end engineers still have some way to go with tidying up some of the CSS styles so I sometimes find myself using Inspect in chrome to check if the style matches the design and guide them on how to write it properly (I have some HTML, CSS and JS knowledge).
Thanks for sharing
Hey Femke! Thanks for sharing this :) Have there been any major process changes since you've posted this? How much time do you typically spend in the QA process? Thanks!
This is why visual QA is so important!! Designers immediately see what went wrong during implementation, and we often think, how in the world did they miss this? Hahaha. Yes working in increments is def recommended and we also use Jira for Visual QA, makes the process so much easier.
I come back to this and some other videos often and realise something new everytime, like Does Uber not have a design system?
Been doing this since I started my new job ( first job out of college reee ) since the previous guys didn’t...argh x)
Thank you so much for your Videos! Really helps me growing!
Thank you for sharing! Just out of curiosity, does your employer know you are sharing the screens and if that is allowed? Another question is, wouldn't the product manager be the one creating the ticket in JIRA and cross checking if Dev has made the right development?
We are a bit more old-school and make these nicely presented PDFs that we send off to Devs, there's a lack of communication with the designers and dev but the mainly the Journey Owner (and Product Manager) should be the ones keeping them in check every day.
@@femkedesign I think each company has different tasks for each position. It's just how ours work - they're more like a requirements manager/consultant so they would make sure the changes are made and write tickets for designers/copywriters. But like I said, it's mainly the Journey Owner that dedicate the QA, our PM can answer any questions and add tasks for designers/copywriters. What does your PM do in your company?
No way you made this video.
Thanks Femke 😎
Thank you - very helpful!
Thanks Femke , great content :)
We use pretty much the same process in my company (medium size agency).
What i also find really efficient and fast is just go and have a sit next to my favourite Front End dev and do some corrections live together , much can be done in just 30 minutes without producing any unnecessary docs, but it doesn't work well for a remote environment...
Wheres the PO? 😅
a simple solution to this is to just be a unicorn that can do ux research, design, code front end, and also give ROI presentations on the changes made. duh. easy enough, considering that's what job requirements expect of people. then none of the designs will have issues in the code /s
Character In the video It's great, I like it a lot $$
Cool!
love this - thanks for sharing your process with us :) our methods have been pretty silo'd with eng and design, We usually QA after its built but I like that you do it prior to the final AND keep track of it in Jira. I'm curious are your product managers ever involved with implementing new ways with collab with eng?
Thanks for this video Femke your videos always helpful for me. ☺️
Exactly the same thing is happening at our company
A big Thank you Femke 💙💙 u r a good mentor.. 😃🙌 and I'll remember from now ...Design + Content QA Review
Awesome!
We share WIP designs with eng so that any major concerns can be expressed upfront, then, at the point of "ready for dev" have a 3 amigos which would typically include design, engineering, product owner to review the designs and kick off the implementation.
Once eng has completed a ticket, they'll share their work with us in a catch-up, and I'll give notes on the fly... but having a more formal approach within Jira would make things more transparent and give designers more time to consider the review stage! Great video thanks for the tips :)
Thanks for sharing your process! It's so important to show WIP to eng so that you can get relevant feedback early on.
Haver you ever tried to QA with Jira? You could actually create the ticket for implementing the feedback and keeping track of it. We had an environment for Design QA in Jira that was super helpful. They we establish our process was by sitting with QA and they were helping us to create the environment. The key thing here is that Developers need one source for feedback.
@@femkedesign Most probably yes. Now I understand why you were showing the QA example within Figma.
Very useful insight Femke! Thanks.
Is this still your process today? Has much changed since you made this video?
It's still pretty similar, yup :)
Whoop Whoop, this video came in very handy.
yet another banger! nice one femke!
Femke is the best 📌❤️
What camera & do you use, Femke, Love your content
@@femkedesign Thank you, I'm new to UI/UX with a graphic design and art direction(advertising) background and I find your videos really helpful, especially dealing with the fear of not knowing enough about the UX industry. So thank you
We use gitlab tickets. QA is fun :)
Oooh cool!
You know, thats really very bad quality engineering. Sorry that you have to police them around... This is definitely not your job to do as a designer... Just a note for newbies who might think this is normal, it is not. If your developer is not able to complete the task they are given properly, you really should talk with them about this and if it keeps happening, you really need to talk with their manager. If they keep on doing this, they will eventually get fired... I mean what kind of developer can't get a font size or color correct? duh..
I'm not sure it's about "can't get it right" but often if you have a broad and/or rapidly growing design system then you might have discrepancies between Figma/Sketch and front end libraries. The button without padding I agree was a big oversight but something like coding a slightly different font weight for a header is a common inconsistency that should be called out designers who know the system well.
@@jacsarah Maybe but the differences between the design and the end version are huge. Obviously the developer who built this, didn't even care to check if he did all according to the design or not. Even a kid would have seen the differences... And if you have such big
@@arvin8 She said that it wasn't the end version
So you do QA for unfinished work... hmmm... interesting hobby... :)