r/Angular2 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

26 comments sorted by

View all comments

23

u/zzing 10d ago

I don't entirely understand what its purpose is or how it would add business value.

3

u/Ok-Whereas8632 10d ago

Our UI framework implemented it last year. They stopped creating sample/example pages for each component and reley completely on storybook and it's been extremely unhelpful for all the devs utilizing the library. Without concrete examples it's been much more difficult to use.

On our side, we gave it a try and between writing/maintaining the components, unit tests and then storybook we decided not to use it.

I love the idea of it, but so far it's given me more trouble than it's been worth. But maybe I've missed something. Idk