Back

Increasing the value of Halp beyond a single team

Increasing the value of Halp beyond a single team

Company

Role

Halp (acquired by Atlassian)

Lead Designer

As Halp gained more customers, it became evident that teams were using the platform for various purposes beyond its original design – for IT Service Desk teams within Slack. To expand Halps usefulness across departments like People Ops, Design Ops, and Dev Ops, we introduced “Queues” as a new structural feature within the product architecture.

The original system, built with a single-layer of configurations, was reliant on automations (we called them “Recipes”), which struggled to handle more complex workflows of these new departments. Queues were created to add an additional layer of control and help automate routing of tickets efficiently.

Domain model before Queues

Domain model before Queues


Domain model after Queues


Customer journey and resulting architecture in the new domain model with Queues


Queue creation wizard, onboarded account

Have questions?

There's a lot more here than meets the eye. If you'd like to learn more about how we worked on this project—cross-functionally, the design process, etc.—feel free to get in touch, I'd be happy to dive deeper together!

©

2024

Jesse Litton

©

2024

Jesse Litton

©

2024

Jesse Litton