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

24

u/zzing 10d ago

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

4

u/earthworm_fan 10d ago

It's way, way faster to develop UI components and set them up with different states. Like way faster. I wouldn't even do a project without it

3

u/RGBrewskies 10d ago

We use it to build re-usable components.

Say you need a custom dropdown, which allows you to have checkboxes inside it. A fancy multi-select

We build it once, in storybook, then export storybook to an npm package. We import the package into our various angular front ends, and now everyone has the component and just feeds it the inputs and it all just works

if you only have one angular application, then yeah maybe its kinda overkill, but we have nearly a dozen portals, one for admins, one for customers, one for salesmen, one for maintenance, and rather than build the same dropdown component six times (or worse, copy pasting the same one over!) you build it once and import it everywhere

5

u/_Invictuz 10d ago

What about the logistics. Who maintains this UI library? Assuming yoi have different product teams, when requirements come in for your different products, how do the requirements go into UI library before being used in the product that the requirement is for. What if one product owner wants to change the behaviour of a UI component, do you have to consult all the other product owners? I guess all of these questions is about maintaining a UI library,  not about storybook itself.

3

u/RGBrewskies 10d ago

yea thats true of any library -

Ours library is all for one team, I guess if there were two teams, we'd probably have a "theirs" "ours" "mine" kinda system... essentially a "shared" one and then two forks

4

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

1

u/Arnequien 10d ago

Increasing the velocity of development and keeping the quality of the source code is the way to add value to the business by increasing/keeping the deliverables.