Davies Meyer – home
    Strategy3 min read

    Briefing

    A briefing clarifies a task and establishes a shared basis for work. It connects context, objective, audience, requirements and available resources. In English, the brief is the document and the briefing is the process of communicating and discussing it; German usage often calls the document a Briefing too.

    Briefing explained

    What should change because of the project? Start with this question before ordering a list of formats. A film, website or is initially an output of the work. The task that output should fulfil for people and the business needs its own explanation.

    Record the main decisions concisely: purpose, relevant people and situations, intended change, substantiated message, budget, timing and mandatory requirements. Add decision owners and evaluation criteria. Technical specifications, sources and extensive background can sit in supporting material. No page count is right for every project.

    A completed document does not yet establish shared understanding. Discuss the task with those doing the work and explicitly record unresolved points. Separate evidence from assumptions and decisions. If strategy development is itself the task, brief it accordingly; an unknown positioning must not appear as a settled instruction.

    For Creative Engineering, feasibility belongs in the early discussion: available content and rights, data, interfaces, quality requirements and ongoing maintenance. AI can organise information or prepare questions. The responsible people need to check the material and make decisions. Changes to objectives or scope should be documented visibly and assessed against effort and timing.

    Examples

    Hypothetical application

    A provider initially asks for a new website. During , it emerges that enquiries often lack necessary information. The team clarifies what prospects should understand and supply, which systems need connecting and how enquiry quality will be assessed. The actual design remains part of the subsequent concept work.

    Key Points

    • Clarify the task and intended change before formats.
    • Make facts, assumptions and unresolved decisions visible.
    • Discuss the document together.
    • Assess changes against scope, effort and timing.

    Practical application

    Express the task in a few understandable sentences, add evidence and constraints and resolve open questions through discussion. Keep the agreed version and subsequent changes accessible to the whole team.

    Useful measures

    Shared understanding

    Whether client and delivery team can describe the task, boundaries and evaluation consistently.

    Open decisions

    Unresolved points with an owner and planned resolution time.

    Reasons for revisions

    Whether changes follow new learning, changed requirements or avoidable misunderstandings.

    Common mistakes

    • Treating a format order as a complete task definition.
    • Leaving budget, decisions or required interfaces unresolved without marking them as open.
    • Changing objectives during work without agreeing consequences with the people involved.

    Sources and context

    Frequently Asked Questions about Briefing

    As concise as possible and as complete as necessary to understand the task. Keep central decisions in the main document and link supporting detail. A fixed page count does not establish clarity.

    Loading related terms…

    All Terms