Define the brand job before the logo

A brand is a memory system for a business, project, or person. The logo is only one piece of that system. This lesson asks you to make a one-paragraph brand job, not a vague creative preference. The output should be specific enough that Claude, Canva, Adobe Express, Claude Design, or a designer can use it without guessing.

Here is the before and after: Before, Claude gives you generic logo ideas because it does not know what the brand must help people believe. After, the brand job names the audience, promise, proof, and places where the brand has to work. For example, a solo service brand should show who it helps, what promise it makes, what proof supports that promise, and where the identity must appear first. A company brand should add rules for collaborators, templates, and repeated use.

Now try it: Write the brand job before asking for names, logos, colors, or visual directions. Make one choice before asking Claude to write: audience, promise, reference, asset type, tool, launch context, or review risk. That choice keeps the work from turning into generic brand inspiration.

The lesson is done when the artifact can guide a real brand asset and survive one honest review.

Interview me one question at a time so we can define my brand job. Cover audience, promise, proof, where the brand will appear, competitors, what it must not feel like, and what action the audience should take.

If any input is missing, ask me up to three questions before producing the artifact. Then return five sections: Finished Artifact, Realistic Brand Example, Assumptions To Check, What I Should Use In The Next Lesson, and One Risk If I Use This Publicly Without Fixing It. Keep the answer practical enough that I can paste it into my brand working doc.

Finished Artifact:
- a one-paragraph brand job
- Why it matters: it gives the brand system a concrete thing to inspect instead of a vague intention.
- Use it next: paste this artifact into the next lesson before asking Claude to write, build, import, publish, or review anything.

Reality Check:
- The artifact names the user, input, decision, owner, or proof it depends on.
- The weakest assumption is visible.
- The next step can be completed in one sitting.

What good looks like

• The audience is specific.
• The promise is concrete.
• The proof is real or honestly marked missing.
• The use cases name where the brand must appear.

Without rereading the lesson, explain why a one-paragraph brand job matters in three bullets. Then apply it to a second brand example: [describe a different solo brand, company, or project]. Return What Changed, What Stayed The Same, What To Check Before Public Use, and the exact next action.

Transfer Check:
- What changed: the second example has a different audience, input, or delivery context.
- What stayed the same: a one-paragraph brand job still needs a source, a review check, and a next step.
- Before trusting it: inspect the brand review check that would catch a wrong assumption.
- Next action: run the check once, then carry the revised artifact into the next lesson.

What good looks like

• You explained the lesson idea from memory before applying it again.
• The second example changes the artifact instead of copying the first answer.
• The public-use check names a real risk.
• The next action can be done in one sitting.