Case Study · Creative Operations

One page, and the project can start.

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.

01
Details
→
02
Brief
→
03
Timeline
→
04
Support

Jill Honig · Senior Project Manager

01 · The Challenge

Projects stalled before design started.

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.

Slow starts

The basics took weeks of back-and-forth.

Scope creep

Scope changed after kickoff.

Missing style guides

Brand rules arrived late, or never.

Waiting on assets

Designers stalled on copy, imagery and flows.

02 · Two Versions

From a questionnaire to a form you can finish.

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.

Page one of the first intake brief: open questions under Goal, Users and Scenarios

Version 1 · Two pages

The UX questionnaire

Thorough, but slow to fill in.

  • Goal, and the problem it solves
  • Users, their roles and key data points
  • Scenarios, repeat and one-time tasks
  • Scope, phases and timelines
  • Screens and flow, style guide, prototypes and testing
The one-page intake brief with Details, Brief, Timeline and Support sections

Version 2 · One page

The intake brief

Quick to fill in, and enough to start.

  • Contacts, task, target users and competitors
  • A short description, with links to existing flows and screenshots
  • Four dated milestones, set at kickoff
  • Yes / no / to-be-provided checks for every asset

Studio name blurred.

03 · The Brief

Four sections, each one closing a gap.

01

Details

Who’s who on both sides, the task, the end date, the target users and the competitors. No more chasing basics by email.

02

Brief

The project in a few lines, plus links to any wireframes, flows or screenshots that already exist.

03

Timeline

Kickoff, UX flow and wireframe, design draft, final mockups. Four dates agreed before work starts, so scope has a frame.

04

Support

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

What I owned.

Wrote both versions

The full questionnaire first, then the one-page brief that replaced it.

Cut it to what matters on day one

Kept the fields a project needs to start, and dropped the long-form answers.

Tied it to the schedule

The four milestones on the brief became the project’s timeline.

Made it the standard

Rolled it out as the way every short-term project started.

05 · The Outcome

The standard way every project started.

2 → 1
pages to start a project
4
milestones set at kickoff
4
assets checked up front
1
studio standard

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.