ABC’s design teams were shipping brilliant work faster than they could tell its story. Case study creation had become a fragmented scramble that drained designer hours delayed approvals and cost the business its most valuable marketing asset proof of great work.

Every case study passes through a designer who has to write it, a manager who has to approve it, and an admin who has to keep it organized and easy to find. Each of them needed something different, and designing for one risked failing the other two. With only two weeks on the clock, there was no time to get this wrong.

The goal was never just a feature, it was a single system that could give the designer speed, the manager confidence, and the admin control, without any one of them winning at the expense of the other two. If it worked, less time would go into writing about great work, and more time would go into creating the next piece of it.

Designers, approvers, and admins each came with their own list of complaints, but not all of them carried equal weight. Visuals and collaboration were friction. Writing, structuring, and remembering project details was the real bottleneck, that was the one thing quietly costing the most time and the one insight every design decision had to answer to.

Two weeks isn’t enough room for wrong turns, so I front-loaded the thinking. So the first move wasn’t a wireframe, it was a map of the requirement, the questions worth asking, and the full workflow across all three roles. Everything that followed was just refining a structure that already made sense in the whiteboarding.

With the workflow mapped, I ran a structured set of questions across all three roles, covering everyday challenges, comfort with generative AI, and reactions to early platform ideas. Analyzing the responses side by side is what separated real blockers from small annoyances, and gave the design a clear order of priority to build against.

With priorities set, design moved forward alongside early scoping for build, rather than waiting for a full handoff. Instead of forcing everyone into one shared screen, I designed separate dashboards for creating, reviewing, and governing, each tailored to how that role actually works day to day, but all pulling from the same underlying data and workflow.

Instead of pitching the design as something new, I walked stakeholders through it using the exact problems they had described earlier, showing them the moment their own pain point turned into a screen. When people see their own complaint reflected back as a solved problem, the conversation stops being about convincing and starts being about next steps.

SuitCase turns that whiteboard thinking into a guided flow, where a designer’s prompt becomes a structured, brand-styled draft in minutes instead of days. Approvers work from a dashboard built for triage, and admins govern the whole repository from one view, so the same system that once took a team days to coordinate now runs itself.

For designers, SuitCase meant less time writing and more time designing, for approvers, faster reviews without losing quality control, and for admins, a repository the business could finally search, trust, and scale. Together, that shift was designed to turn case studies from a hidden cost center into a reliable engine for new business, directly strengthening the ROI the whole project was built to protect.