Related Posts
What do u prefer

Additional Posts in UX and UI designers 🚀
6 articles you must read if you are starting as a UI/UX Designer
📍How to become a self‑taught UI/UX designer
https://lnkd.in/dUgxXwjP
📍The ultimate Figma resource archive (2021)
https://lnkd.in/dQUgAdJc
📍A step-by-step guide to your first UX case study
https://lnkd.in/d5BB2wPW
📍All you need to know about colours in UI Design — theory & practice
https://lnkd.in/dTC-5mGy
📍The UX Designer’s Guide to Typography
https://lnkd.in/dmUxKhtc
📍Design / UX: Getting That First Job
https://lnkd.in/dJhnVPMQ
👇Let me know in the comments if you found this helpful :)
New to Fishbowl?
unlock all discussions on Fishbowl.




I'd say, do it in stages. When you upgrade gradually-modules wise, you'll see its impact on other modules and the overall image of the product.
Also, doing it in modules makes things clearer and easy to navigate.
Most commonly, you create the style guide and components, and then have them implemented by a front end dev team. Then, choose the highest priority pages - those used the most and critical to customers - and start with them. Once you have all of the critical, high priority pages ready, push them as as a Beta or EAP. Get feedback, revise as needed. Then move on to the lower priority pages.
Whether the General Release is done all at once or in stages depends on the size of the product. If it is smaller, it might make sense to wait until the whole thing is done before final release. If it is a large product, then staged releases - release the new pages as they are complete - might be better.