U-M DPSS · Intelligence Group workspace
A shared view is useful only when it gives the right people the right context.
I designed and prototyped a workspace for the DPSS Intelligence Group: one place to take in requests, work a case, and hand it off for review. The hard part wasn't the screens. It was making sure each person could see where work stood without seeing more than they should.
Role
UX research, design and prototyping
Team
With Aaron Tucker and the Intelligence Group
Built in
Google Apps Script, then handed to the team's own server
Status
In use by the team

A case in the workspace: the original request, where it stands, and what's next, on one screen. Synthetic demo data.
The problem
Requests came in through email, calls and spreadsheets. Nobody had one picture of what needed attention.
The team already had monitoring apps they relied on, and I wasn't going to replace those. The gap was everything around them: taking a request in, working it, and handing it off without losing the thread.
Three calls that shaped it
Inside the workspace

Intake: one form for a new request, with priority, a needed-by date and the people involved.

The public front door: a guided chat with an anonymous option and a 911 reminder before anything else.

Cases at a glance: what's open, what's overdue, and what to pick up next.

The link board: how cases, people and places connect, so related work doesn't get worked twice.
Where it landed
The team uses it. It didn't replace their tools; it made the work between them easier.
Prototyping in Apps Script meant we could test real workflows early and safely. Once it held up, the team started building it on their own server. Screens here use synthetic data only.