Case Study · Creative Operations
A data-app design studio built dashboard UX for clients like Aruba Networks, Teridion and Mist Systems. I turned its two-page questionnaire into a one-page intake brief, and it became the standard way every project started.
Jill Honig · Senior Project Manager
01 · The Challenge
The studio ran short UX projects for enterprise tech clients: dashboards, data visuals and app screens for networking and data products. The design work was quick. Getting a project ready to start was not.
The basics came in over weeks of email, scope moved after kickoff, and designers sat waiting on style guides, copy and flows that nobody had asked for in writing.
The basics took weeks of back-and-forth.
Scope changed after kickoff.
Brand rules arrived late, or never.
Designers stalled on copy, imagery and flows.
02 · Two Versions
The first version asked all the right questions. It was also two pages of open-ended answers, which is a lot to ask of a client who wants the project to start. So I cut it down to the fields a project actually needs on day one.

Version 1 · Two pages
Thorough, but slow to fill in.

Version 2 · One page
Quick to fill in, and enough to start.
Studio name blurred.
03 · The Brief
Who’s who on both sides, the task, the end date, the target users and the competitors. No more chasing basics by email.
The project in a few lines, plus links to any wireframes, flows or screenshots that already exist.
Kickoff, UX flow and wireframe, design draft, final mockups. Four dates agreed before work starts, so scope has a frame.
Style guide, copy, imagery and UX flows, each marked yes, no or to be provided, so a missing asset becomes a dated dependency, not a surprise.
The “to be provided” box is the key: it turns “we’ll send it later” into something with an owner and a date.
04 · My Role
The full questionnaire first, then the one-page brief that replaced it.
Kept the fields a project needs to start, and dropped the long-form answers.
The four milestones on the brief became the project’s timeline.
Rolled it out as the way every short-term project started.
05 · The Outcome
Quick for a client to fill in, and enough for the team to start. It became the studio’s standard intake for short-term UX projects for enterprise clients including Aruba Networks, Teridion and Mist Systems.
The Takeaway
A brief nobody finishes isn’t a brief.
Make it short enough to fill in and specific enough to start from. Ask for every asset by name, with a date, and the project stops waiting on things nobody asked for.