Start with a person, not a finished concept
A self-initiated project can begin with almost anything: a visual style you want to explore, a subject you care about, or a skill you want to practice. The freedom is useful, but it can also make decisions feel arbitrary. When there is no client brief, defining who the work is for gives you a way to judge whether each choice helps the project.
You do not need to invent a detailed character with a name and life story. Begin with a group of people who might realistically encounter the thing you want to make. If you are designing a guide to local walking routes, for example, you might focus on residents looking for short outings rather than trying to serve every possible visitor. That choice affects the language, route information, format, and level of detail.
Separate your audience from your goal
Personal projects often have two legitimate purposes. You may want to learn a tool or show a particular skill in your portfolio. The project itself may also be intended to help someone find, understand, choose, or do something. These purposes can support each other, but they are not identical.
Write down both before you begin: “I want to practice information design” and “This guide should help a first-time visitor compare three walking routes.” The first statement tells you why the project matters to you. The second helps you decide what information belongs in it. If a visually striking feature makes the routes harder to compare, you can reconsider it without abandoning your learning goal.
If the work is primarily an experiment, it is fine to say so. You can still choose an audience, such as other designers interested in the technique. What matters is being honest about the project’s purpose rather than presenting an exercise as a solution to needs you have not investigated.
Choose a useful level of specificity
“Everyone” is usually too broad to guide a project, while an extremely narrow imagined persona can give you false confidence. Aim for a description that changes the decisions you make. Consider what the audience is trying to do, what they may already know, where they will encounter the work, and what might get in their way.
For a recipe collection, “busy home cooks who want to use a small set of ingredients” is more useful than “food lovers.” It suggests choices about recipe length, shopping lists, and substitutions. You do not need to assume every member of that group has the same preferences or circumstances. Treat the description as a working focus, not a claim that you know an entire audience.
It can also help to state who the project is not mainly for. A beginner’s introduction to a design tool may not need to satisfy experienced users looking for advanced shortcuts. Setting that boundary keeps the scope manageable and makes it easier to explain why you included some features and left out others.
Turn the audience into a small brief
Once you have a focus, write a short brief you can return to while making the project. Include the intended audience, the situation in which they would use the work, the task it should support, and one or two practical constraints. For example: “This mobile-friendly route guide is for residents choosing a short walk on a free afternoon. It should make distance and starting points easy to compare, and it should be readable on a phone.”
That brief does not have to settle every design question. Its job is to make trade-offs easier. When deciding between a large atmospheric photograph and a compact route summary, you can ask which one better serves the stated task. You might use both, but the brief helps you decide what needs prominence.
Keep a note of assumptions you are making, especially about people’s access, knowledge, or preferences. An assumption is not necessarily a problem; treating it as a verified fact is. If you can show a rough version to someone in the intended audience, ask what they would expect to find and where they hesitate. Use their response to improve the work, without presenting one person’s view as universal.
Let the audience shape the portfolio story
Defining an audience makes a personal project easier to discuss after it is finished. Instead of displaying only polished images, you can explain the problem you chose, the boundaries you set, and how those choices influenced the result. That gives a portfolio reader more insight into your thinking than a list of tools or aesthetic references alone.
Be clear about what was self-initiated and what you were able to check. If there was no client, do not imply that there was. If you did not test the finished work with its intended users, describe the audience as your chosen focus rather than a validated market. A thoughtful account of your decisions is valuable on its own.
The audience can change as the project develops. If your first version reveals that you are trying to serve too many needs, narrow the focus and update the brief. A self-initiated project does not need a perfect audience definition at the start. It needs one specific enough to help you make the next useful decision.
