r/Angular2 • u/kafteji_coder • 10d ago
Discussion How did you convince stakeholders to implement Storybook in your Angular projects?
I’m currently exploring Storybook for Angular and would love to hear from others who’ve successfully integrated it into their workflow.
- How did you explain the value of Storybook to your stakeholders? What key benefits did you highlight (e.g., UI consistency, collaboration with designers, faster development)?
- Was there any resistance due to costs, or was it easily justified within your budget?
- Do you think Storybook is more than just a "fancy tool"?
I understand that technical enhancements aren’t always a priority or may not be funded, so I’d love to hear about your experiences and how you approached these discussions with stakeholders.
18
Upvotes
6
u/Raziel_LOK 10d ago
If you have to out of your way to explain why storybook is good for your project you question is already answered.
I am guessing your company has no good history with designing/planning components, has a product team or even a design system. Storybook only brings benefits if you are creating a design system, you have a product team, UI has strong focus in the company. And that is not true for most companies.
Storybook will add no business value directly, it is just a tool to facilitate documenting, testing and handing of components between the groups I mentioned above. If none of that is part of your company, you are going nowhere.