Delegates in Ramp
Delegation is key when teammates are out of office to keep approvals moving without disruption. I redesigned Ramp’s delegation feature end-to-end, improving both the delegate and delegator experiences to make responsibilities clearer and actions seamless.
Time
1 month, Summer 2025
Role
Product Designer
Understanding the problem
When teammates are out of office, delegating your tasks keeps work moving. But the experience had three big gaps.
Visibility
It wasn’t clear who was covering if someone was away, making approval chains confusing.
Scheduling
People needed a way to set a delegate in advance, like assigning next week’s approvals before leaving for vacation.
Resetting
The user profile needs to have delegation states to remind people to turn delegation off when they return.
User research
The backbone of every project is to talk to many, many users! I started by mapping the user flow for generic user personas (admins) then asked broader questions about general interactions to different user types.
Wonderfully, many answers were surprising and reshaped how I thought about notifications and exposing delegation interfaces.
The solution
From these insights, I developed the following problem statement:
Delegation keeps work moving when teammates are away. Users need a clear, flexible experience to hand off and track responsibilities, whether you’re delegating, covering, or simply trying to see who’s in charge.
Because delegation was an issue universally across every product surface (reimbursements, approvals, home page, email), I created a series of “how might we” questions to guide ideation to guide ideation in a few key areas.
– How might we help users seamlessly return to their normal workflows through the nav bar?
– How might we show who’s responsible when someone is out of office in the approval chain UI?
– How might we make it easy to schedule delegation ahead of time through Google Calendar?
Prototyping & design engineering
A huge part of this project was learning to iterate in code – how do we leverage tools like Cursor and know when to use them v.s when should we learn the fundamentals on our own?
I coded many prototypes to show to frontend engineers and other designers to help get my ideas across, ultimately shaping and improving the final interactions (and pushed some PRs!).
Calendar prototype
Toggle prototype
Banner prototype
Designing solutions
Scheduling redesign
Approval chain redesign
Profile status