Even after all that you read our system moves forward, expecting to meet varying levels of often justified resistance. Interviews with and surveys of product teams — particularly from product owners — reveal themes of size, priority, and momentum.
Here are some of the concerns that we've heard.
"Malty is too big!"
Some see Malty as a beastly monolith. That’s reasonable: it’s a big library!
Yet, Malty is modular. It has lots of small parts. Some parts can be prioritized and adopted independently, others ignored as irrelevant. Adoption isn’t an all-or-nothing, all at once.
"Malty is not Important… enough."
Product teams have a backlog bursting with features, optimization, and defects.
What else do they have? Built buttons, massive modals, and cards with content. Don’t they already have all the system offers?
In Malty cohesiveness is a feature, both within products and even more across a portfolio.
"Malty will slows us down!"
A team’s velocity and momentum towards objectives are paramount. Malty will not get in the way. Admittedly, Malty's adoption can hinder the short-term momentum of feature development.
Take the long view.
Product teams will speed up gradually to a new level by ceding small solutions to a shared effort. You’ll also achieve benefits like accessibility, and that's something that you shouldn't refuse!