Design Brief Template
Identify the competitive landscape and your company’s relation to it.
About the Design Brief template
What is a Design Brief?
A design brief acts as a bridge between a business and a design agency. The document allows businesses to communicate their needs and desires to a design agency or team. When a business decides to hire a design agency, someone on the marketing team will typically write the design brief. A comprehensive design brief helps guide the design process, communicating what the designer needs to do and elaborating on any constraints.
How to use the Design Brief template
Businesses can expect to have numerous interactions with design agencies. Maybe you have hired a design agency to create your website, or build a landing page. Or maybe you have hired them to completely rebrand your site and marketing materials. Regardless of the project’s size, you will need a detailed marketing plan to work effectively with the agency.
Step 1: Start by discussing your goals. What do you want the design agency accomplish? Do you want them to overhaul your website, or design a new logo? Do you know exactly how you want your site to look, or do you want your agency to do some research and present their ideas? Be upfront about all of this information so your agency can start building a foundation for the project.
Step 2: Give your agency a budget and timeline. Design agencies are often juggling many projects at once. To ensure they complete the project on time and according to your preferences, give them a realistic estimate of your resources and time constraints. Are you looking to launch your website before a conference? Are you trying to create a landing page in time for a product launch? Do you have a limited budget to work with? Let your agency know.
This part of the design brief opens a doorway for a conversation with the agency. If your timeline or budget is unrealistic, then they can tell you about it in time for you to make a contingency plan. If your budget is too high or the project is easier than you anticipated, then you can end up saving some time or money. But your agency cannot have these conversations with you if you do not include the information in the brief!
Step 3: Include your target audience. Your design team is going to make different choices depending on the audience you want to reach. For example, a website designed for high schoolers is going to look a lot different from a website designed for CISOs. If you are not sure about your audience, explain who your ideal customer is. It might help to reference your competitors so the agency can do some research.
Step 4: Lay out the scope of the project. To partner with you, the design team needs clear parameters. Do you want a custom logo, or do you want the agency to adapt an existing template or design? Do you want an online store complete with a shopping cart, or do you just want a brochure site with information about your product?
While you’re defining the scope, think about social networking features and blog integration too. This is your chance to create a holistic experience for your customers, audience, or clients. Draw out this experience in the design brief.
Step 5: Show them what materials are available to them. Maybe you already have a bank of stock photos you’re using for your online content, or maybe you have a logo, a brochure, or photos of your product. Giving the design agency a glimpse at these materials can help them gain insight into your company’s aesthetic.
Step 6: Create a style guide. The style guide is like your narrative voice -- but instead of text, your medium is visual. It can be useful to give the design agency examples of websites with styles that speak to your audience. Tell them what color palettes you like and what kind of ambiance you want your audience to experience. Describe the adjectives and emotions you want your customers to associate with your brand.
Step 7: Enumerate a list of do-nots. If there are certain features you do not want on your site, colors or fonts you do not like, or layouts that are ill-suited to your product, then put that in the design brief.
Why write a Design Brief?
Writing a design brief will ensure an effective partnership between your business and your design agency. If you or your business is working with a design agency on any project, regardless of size, then you need to write a design brief. The design brief allows you to provide guidance to the agency so they deliver your project quickly, on time, and according to your specifications. In short, a good design brief can save you and the agency time and money.
When to use the Design Brief template
Use the Design Brief template any time you’re creating a design brief for a new project. You can use the template to outline the scope of your project, your budget and time constraints, and your preferred style.
Why the Design Brief is important
The design brief is the foundation of any creative project. A comprehensive design brief can serve as a business plan and source of truth. Throughout the project, your business and the agency can reference the brief to ensure everyone is on track, within budget, and delivering according to your timeline.
Visual Story Map
Some people like to think of a visual story map as a stylized to-do list, but it’s a lot more powerful than that. Visual story mapping allows your product management team to visualize multiple dimensions of information. In doing so, you can identify how these parts will come together to create a successful whole. Use the visual story map template to make sure your product managers are aligned and to create a single source of truth about your projects.
A Startup Canvas helps founders express and map out a new business idea in a less formal format than a traditional business plan. Startup Canvases are a useful visual map for founders who want to judge their new business idea’s strengths and weaknesses. This Canvas can be used as a framework to quickly articulate your business idea’s value proposition, problem, solution, market, team, marketing channels, customer segment, external risks, and Key Performance Indicators. By articulating factors like success, viability, vision, and value to the customer, founders can make a concise case for why a new product or service should exist and get funded.
A work plan is essentially a roadmap for a project. It articulates the steps you must take to achieve the desired goal, sets demonstrable objectives, and establishes measurable deliverables. An effective work plan guides you throughout the project lifecycle, allowing you to realize an outcome by collaborating with your team. Although work plans vary, they generally contain four core components: goals, strategy, tactics, and deliverables.
A prototype is a live mockup of your product that defines the product’s structure, user flow, and navigational details (such as buttons and menus) without committing to final details like visual design. Prototyping allows you to simulate how a user might experience your product or service, map out user contexts and task flows, create scenarios to understand personas, and collect feedback on your product. Using a prototype helps you save money by locating roadblocks early in the process. Prototypes can vary, but they generally contain a series of screens or artboards connected by arrows or links.
To-do lists are simple, yet effective tools that can break down large tasks into smaller, concrete steps. They can range from individual daily tasks to broader group goals. You can make a to-do list for any project or deliverable that your team is responsible for. Breaking down tasks into concrete steps helps your team reach your goals with ease. With the To-Do List template, you can customize your to-do list to include photos, images, videos, color-coding, and documents.
A RAID log is a project planning tool that focuses on four key areas: risks, assumptions, issues, and dependencies. Risks are events that could have an adverse effect if they occur, assumptions are things you assume will happen to contribute to the project’s success (and that will have negative consequences if they don’t occur), issues are risks that have already occurred and had a negative impact on the project, and dependencies are things that must start or finish so your project can progress. RAID logs are often used when beginning a new project, but they’re also useful for promoting alignment and sharing status for projects that are already underway.