SPS Global — UI/UX case study.
A document product for teams — reviewing, completing and assigning work, with chat sitting alongside it instead of in another tab.
- Client
- SPS Global
- Role
- Product / UX design
- Sector
- SaaS — document workflow
- Surface
- Web application
Context
SPS Global handles document review, completion and assignment, with built-in chat. Three jobs that usually live in three different tools, deliberately collapsed into one.
The risk in that consolidation is obvious: combining tools tends to produce an interface that does everything adequately and nothing well. Keeping each mode distinct was the whole design problem.
What the design had to do
Keep the document primary
Review is the core task; assignment and chat support it and must not compete for space.
Make ownership unambiguous
Who has this, what state it is in, and what is expected next.
Put conversation in context
Chat is only worth embedding if it is attached to the thing being discussed.
Replace this with the brief in SPS Global’s own words, plus the one constraint that shaped the most decisions — timeline, tech, compliance, an existing design system, or a stakeholder. This is the part a hiring manager reads first.
Process
Consolidating three tools into one is a hierarchy problem before it is a layout problem. Each step below was really about deciding what gets to be primary.
Understand
Separate the three jobs the product merges — review, assignment, conversation — and rank them honestly.
Research
Watch how teams currently move a document between people, including the email and chat workarounds they have invented.
Wireframe
Give the document the majority of the canvas and dock everything else, rather than splitting attention three ways.
Visual design
A restrained interface palette, so document content and status are the only things carrying colour.
Prototype
Test the handoff moment specifically — assigning to a colleague — because that is where multi-tool workflows break.
Handoff & support
A documented component set covering document states, roles and permissions for ongoing build.
The steps above describe what each stage had to solve on SPS Global. What turns that into a case study is the evidence — add, for any two or three of them:
- Who you spoke to, and the one finding that changed the design
- A decision you made, and the option you rejected
- Something that tested badly, and what you did about it
- A wireframe or screen — before and after beats a finished shot
Outcome
The bet with a consolidated tool is that work stops leaking into email, so that is what to measure.
Documents completed per user per week
Share of discussion happening in-product vs. email
Time from assignment to completion
Number of documents stalled with unclear ownership
Put real figures against the four above, or strike the ones you can’t evidence. If SPS Global never shared numbers, a single sentence from the client about what changed is still worth more than a blank. Right now no project on the site states an outcome, and that is the biggest gap in the portfolio.
Working on something like this?
Available for full-time and contract work across fintech, healthcare and SaaS.