Acquia's 30+ teams lacked visibility into who was working on what. Jellyfish gave them a cross-sectional view that surfaced overworked engineers, compared deliverables, and sorted work into growth, customer, and maintenance buckets. Executives could finally see compliance and cost-of-goods work too.
Chapters
I started to work with Jellyfish, my previous company, and the problem set was the same as Acquia, which is what is everyone working on? You had 30+ teams at the time and little visibility and little transparency and consistency across those teams. I knew from my previous job the tool that could allow us to see what all these teams are doing. When you hook up Jellyfish to the system, you can within days begin to kind of get a good cross-section of all the things that teams are working on. From a development standpoint, it allows us to see where engineers are spread too thin. So right now, for instance, we have a couple of deliverables that are of major focus and we can see a real side-by-side comparison. We had ownership that was interested, executives that were interested, and within a short period of time we were able to not only say yes, this is a product feature that's focused on growth versus a customer versus, you know, maintenance. We were also able to now really gain visibility into compliance and COGS-related work. We worked closely with customer success team members to absorb the data quickly, be able to within weeks start to see something that gave us value. And since then it's just been— we have a Slack channel with Jellyfish, we have constant communication with the team. We have feature requests that they get and turn around for us. We have frequent calls with them. Like, professionally, I don't want to ever go to another role where I don't have this level of visibility.
