5 minutes
Naming Conventions Turn naming conventions into a more respectful, usable decision.
What you’ll be able to do Ask about household, identity, naming, and belonging without assuming that a community pattern describes a person. Compare the responses to this question and explain your choice: What keeps the learning useful instead of turning it into a stereotype? Document a next step for Naming Conventions: Use Naming Conventions as a hypothesis in one live plan; verify the relevant detail with the affected person or a named community partner, then record the change, owner, review date, and report-back. Naming Conventions Somali names often do not match first-middle-last. A common pattern is given name, father’s name, grandfather’s name. There may be no “family surname” as the database understands it. Women do not necessarily take a husband’s name.
What the form invents The form that demands a last name will invent one. That invented name then follows the person through MHCP, child welfare, and school. It is a gate.
Islamic names are common (Mohamed, Ahmed, Fatima, Amina, Abdi, Hassan). So are Somali names (Hodan, Waris, Degmo, and many others). Pronounce them. Ask. A shortened name for your convenience is a closed door.
Three people in one household may not share a “last name” the way a Swedish Minnesota form expects. That is a naming system. It is not fraud until you have a reason.
Put naming conventions to work What you can change You control whether naming conventions is treated as a question to explore or a label placed on someone.
What to watch for Ask how to say it. Do not invent a last name because the screen requires one. That invented name becomes a gate.
Your next step Use this evidence as a hypothesis in your next plan, then confirm the relevant detail with the person or the community partner you named.
Practical cards Naming Conventions
Real example: Somali names often do not match first-middle-last. A common pattern is given name, father’s name, grandfather’s name. There may be no “family surname” as the database understands it. Women do not necessarily…
Leader action: Ask how to say it. Do not invent a last name because the screen requires one. That invented name becomes a gate.
I do not need a cultural performance from a professional. I need the process to make room for my name, my people, my questions, and the way I actually need to participate.
Composite public perspective — illustrative · Somali Minnesota · Household, identity, and belonging Fictional working example
Let the person explain the name fields This fictional person gives the name Hodan Yusuf Ali. The example does not establish a naming rule for everyone; the person's explanation drives the entry.
1
Name as provided Hodan Yusuf Ali — please use Hodan when speaking with me.
Examine this clause Keep the provided spelling while confirming pronunciation and preferred use. Do not shorten the name for staff convenience.
2
The form's assumption First name / middle name / family surname are mandatory fields.
Examine this clause The labels assume a structure the person may not use. Ask how their names should be recorded and check the system's approved filing guidance.
3
Before saving Read back the proposed entry and explain how it will appear in the relevant record.
Examine this clause Resolve a field constraint through the appropriate support route. Do not invent a family surname or change other household members to match.
Try it with the work Which question belongs before entering Ali as a family surname?
Draft a respectful confirmation question and a note describing the field constraint to resolve.
Carry this forward Naming Conventions provide context to test, not a label to assign.
The person, household, Nation, or named community partner remains the authority on what fits.
Ask how to say it. Do not invent a last name because the screen requires one. That invented name becomes a gate.
Completion is shown by a scenario decision, review of a practical artifact, and a saved one-minute commitment.
Use Naming Conventions as a hypothesis in one live plan; verify the relevant detail with the affected person or a named community partner, then record the change, owner, review date, and report-back.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
