Here's what typically makes an informal brief informal:
* Less formal language: It uses conversational language and may even include slang or jargon familiar to the recipient.
* Shorter length: It focuses on the essentials, avoiding lengthy introductions or detailed background information.
* Less structure: It might not follow a strict format, but still includes essential information.
* More flexibility: It's open to changes and additions as the project progresses.
* Used for smaller or internal projects: It's often used for smaller projects within a team or for quick tasks.
Think of it as a "heads-up" or "quick summary" of what needs to be done, rather than a detailed plan with every step outlined.
Here's a basic structure of an informal brief:
* Project/Task Name: A clear and concise title.
* Purpose: A brief explanation of the project's goal or the task's objective.
* Key Information: The essential details needed to understand the project/task.
* Timeline: A general idea of the timeframe or deadlines.
* Next Steps: What needs to happen next, who is responsible, and any actions required.
Here's an example of an informal brief:
Project Name: Website Redesign
Purpose: Update the company website with a new look and feel, and improve user experience.
Key Information:
* Target audience: Existing and potential customers.
* Design requirements: Modern, clean, and easy to navigate.
* Content: Update existing content and create new content for key pages.
Timeline:
* Design phase: 2 weeks.
* Development phase: 4 weeks.
* Testing and launch: 1 week.
Next Steps:
* Design team to create initial website mockups.
* Development team to build the new website.
* Marketing team to plan the website launch.
Remember: Even though it's informal, the brief should still be clear, concise, and contain all the necessary information to ensure everyone is on the same page.