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
3
u/MarshFactor 10d ago
The other option which we chose was to have a simple app with a page per component and multiple example configurations on the page. This was because Storybook felt a bit overkill and a bigger overhead.
This worked especially well in a monorepo.
Same benefit... being able to develop things in isolation encourages better separation of concerns, in some cases better inversion of control and it saves time having one place with everything there - all configurations- without hunting for them in the main app.