A project brief helps you get aligned on expected outcomes for a user-centered design project.
Often, when a project is beginning, everyone involved has distinct ideas for what the right outcome looks like. In team discussions, it’s possible for people to express their point of view and think they’re all saying the same thing, but actually have very different ideas of what they expect to see. A project brief states directly what goals or expectations should prevail as the main mandate for the work.
The brief, as its name suggests, capitalizes on the cardinal virtue of brevity to distinctly and clearly summarize the overall plan for the project: what you’re doing, why you’re doing it, relevant constraints that will drive your work, and what outcomes you expect. Another bonus of the brief is that by being a short description, it’s more likely that people will actually read it. This creates an opportunity for everyone to agree or, if not agree, at least have a productive conversation about the focus and goals of the project.
Ever done a project brief? If so, how did you involve others on your team?
Post your reply as a comment below by Tuesday, 11/5, midnight PT. The best reply wins a free copy of The User Experience Team of One.
Leave a Reply