Frontend Engineers, how are you able to manage never ending design reviews?
We have had new designers recently in the team which have made our life hell. Only thing they want is pixels perfect design to be made due to which our projects deadlines have stretched a lot and bothered our work life balance. Introducing new designers to a team can bring fresh perspectives, but it seems these individuals might be focused heavily on perfectionism. Their insistence on pixel-perfect designs is causing delays and affecting our team's workflow and deadlines. While their dedication to detail can be commendable, I think it's essential to strike a balance between quality and efficiency to maintain a healthy work-life balance. Also these folks are making everything so design heavy that we also have had CVR drops. New design looks flashy and barely good to use for normal users. Thoughts?
Talking product sense with Ridhi
9 min AI interview5 questions
As long as they keep doing it. You have your job my boy. Keep stretching like they do
Becomes monotonous after a while. Seems like I am doing nothing apart from changing CSS the whole day.
It’s called Job for a reason. It’s repetitive.
I had to google what cvr was, my dumb ass thought it had to do something with a laggy experience. On a side note, my manager understands that even minimal designs can drive a lot of numbers.
For others like me: CVR stands for Conversion rate. Google: It shows how many people do what you want them to do on a website
That is the reason why most e-commerce have a very minimalistic design. At the end of the day it’s usability that matters. No user cares 60 fps animation if the button is not clickable at all
If CVR is dropping, then your their awesome design isn't worth a single penny.
Get your manager and someone owning the CVR metric from the business side involved to resolve this.
Hard luck, going through the same stuff. They keep on bringing new variants or spacing/sizes without any discussion and keep on increasing the code that needs to be maintained and followed across the app. Then while testing and evaluation goes on to make further changes and ruins the entire process.
Further someone else from other teams might show up and give suggestions resulting in re-creating these fancy designs.
I don't think there's any particular way to stop this because a lot of these designs might be approved by the product/leadership team and further discussions are not fruitful.
Exactly. Now to meet their requirements unnecessarily conditions needs to be added in the components through props which makes all these components bloated.
Design parity shouldn't block a release. You can create a ticket for that next sprint to pacify them. Say you'll pick it after picking next sprint's tasks. Rinse and repeat
Idk how would a IC influence them. Some senior or manager+ should put some sense into them. One should not block a feature release just bcoz it’s not pixel perfect.