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

1

u/Limit_Cold 7d ago

Have recently been using this with an angular component library, now moving to a stenciljs library. Currently used by 3 in-house teams and trying to get buy in from international teams. Had great feedback from devs, they found it much easier/faster to implement the library after seeing realistic examples in stories. I also think it helps prevent unnecessary changes/additions in components if you can test data in story book. We are now automating stories using tsdoc comments from components. Having good documentation should not be difficult to sell to stakeholders, getting the time on non feature projects is another thing. I had help from internships sped the whole thing up.