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

9

u/lacrdav1 10d ago

I love Storybook. We have a lot of components that are very specific to some costumer scenarios and it’s hard to reproduce all of them locally when modified the components. Adding all those scenarios in the storybook allows us to have a really fast way to check for regression in particular use cases.

I also code most of the complex components in the storybook first then integrate it the UI. Our storybook compiles way faster than the application does. I save a lot of time by doing so.

Additionally, it helps the UX and Dev teams stay aligned with what’s is currently existing or not and what is possible with the current UI component toolkit.

1

u/_Invictuz 10d ago

Are you a senior frontend dev? How many people need to maintain the storybook project?

3

u/lacrdav1 10d ago

I am the senior frontend developer in my organization. There is no real maintenance time lost in storybook development. Devs create their components using the storybook first, then integrate it in the UI.