Skip to content
Arqum Usmani

SaaS · 2025

TODO: replace with current Oak Street Technologies work

TODO: write the one-sentence thesis for the Oak Street Technologies case study here.

Cover image for TODO: replace with current Oak Street Technologies work

Role

TODO: role

Team

TODO: team composition

Timeline

TODO: timeline

Platform

TODO: platform

Domain

SaaS

Year

2025
TODO: replace with current Oak Street Technologies work: gallery image 1
TODO: replace with current Oak Street Technologies work: gallery image 2

Context

TODO: replace this entire case study with current work from Oak Street Technologies. This entry exists as a structural placeholder so the fourth slot in /work and the home page grid render correctly before real content lands. Same frontmatter shape, same section order as the other three case studies, just swap the prose and images.

Problem

TODO: the sharp, specific problem, with evidence (not "the product needed a redesign").

Constraints

TODO

Replace with a real regulatory, technical, or organisational constraint from the Oak Street Technologies engagement.

Research

TODO: method, then what was actually learned. Keep the "then what was actually learned" half; that's the part that's usually missing from case studies.

Key insight

TODO: the single pulled statement that is the sharpest thing learned on this project.

Explorations

TODO: wireframes and at least one rejected direction, with the tradeoff stated plainly (not just "we explored several options").

Solution

TODO: the final UI, annotated with why the decisions were made, not what the decisions were.

Outcomes

TODO

metric one

TODO

metric two

Reflection

TODO: what I would change. Don't cut this section when replacing the placeholder; it's the part that signals seniority.