Plan Your First Avatar: A Practical Creative Brief

Start with one destination

Write the name of the application where the finished avatar must work, together with the device you expect to use. Identify whether you need a still image, a video, a rigged model or a platform-specific upload. Do this before collecting tools. A beautiful rendered portrait does not contain a skeleton or wearable clothing merely because it looks three dimensional. Use the destination documentation to identify the supported workflow, then keep its link beside the brief. If you have several destinations, make the first one the acceptance target and describe the others as later adaptations.

Describe an identity through observable choices

Choose three visual qualities you can explain without a celebrity reference: calm, geometric and outdoors-inspired, for example. Translate each into a decision about silhouette, color or texture. Specify the approximate shape of the hair, the outline of the outfit and the role of one distinctive accessory. Avoid collecting many incompatible adjectives. A collaborator should be able to tell which features matter most when time is limited. Separate essential identity features from optional decoration, so a smaller version remains recognizable if the original design proves too complex.

List actions before buying details

Write down the character actions your first release needs: speaking, turning the head, sitting or raising an arm. Add the camera distance and likely background. A detailed sleeve can look convincing in a still frame yet intersect the torso during a gesture. A tall head accessory may disappear outside a portrait crop. Make each action a review task rather than a promise that a tool will automatically handle it. The list becomes a small acceptance sequence you can repeat after each revision, including on the actual target device.

Define exactly what you will receive

A deliverable list might include one editable project, one platform export, a neutral preview image, a list of included third-party assets and a short readme. Record which items you can edit yourself and which depend on another application or a licensed component. Name the file formats only after checking the destination. Specify whether the creator will upload the result or whether you will complete that step. Account access is a separate question from possession of a model file; a delivery process should not require sharing your password.

Make the first version deliberately finishable

Use a small release boundary: one outfit, one hairstyle and a limited set of required expressions. Keep a second list for attractive additions. Decide what you will check at the end of the first working session, such as whether the model imports and displays in the right orientation. A brief is successful when it allows a clear decision to continue, change direction or stop. It does not need to predict every later feature. Save the original brief and note approved changes instead of silently moving the goalposts.

Worked example

For an illustrative reading-club host, the destination is a desktop streaming application, the framing is chest-up, and the visual brief is a dark jacket with a pale collar and one small pin. Required actions are a head turn, blinking and a speaking expression. The first acceptance review uses a light background and a dark background, with the camera at the intended crop. The handoff contains the editable project, a supported export and a component list. A second outfit and elaborate hair physics stay on the later list. This makes a restrained first version a completed project rather than an unfinished version of an ambitious one.

Your working checklist

Checkmarks stay in this browser when storage is available. They do not submit a form or complete a booking.

• Destination and device
• One-page brief
• Owned or licensed references
• Review action list

Put it into practice

1. Write the destination and required output type in the first two lines. Open the official import or creation documentation and record the workflow you will follow.
2. Choose three visual priorities and sketch a simple silhouette. Describe each priority in ordinary words so another person can recognize it.
3. Define a small set of actions, deliverables and acceptance checks. Separate required files from optional screenshots or additional outfits.
4. Review the first working version against the original brief, record changes and keep a dated copy with the project files.

Common questions