Write a portfolio walkthrough that shows your role

Which project should the walkthrough cover?

Choose a project whose useful evidence you are allowed to show. The most visually elaborate piece is not always the best explanation of your work. A small artifact with a clear decision can support a more credible walkthrough than a large project whose key details must remain hidden. Write the viewer’s question at the top: what should this person understand about your contribution after the video?

Select a single route through that project. You might explain why a navigation choice changed, how you organized an illustration series or how you prepared a recording plan. These are different stories and do not all need to fit in the same introduction. Keep the project’s broader history in the linked portfolio. The video should make one important part of the work legible rather than reciting every step you completed.

How do you separate your role from the team’s work?

Name your responsibility directly and identify important shared contributions. “I designed the three layout options; the researcher supplied the interview notes” gives the viewer a useful boundary. “We created the whole experience” may be true but leaves individual responsibility unclear. Avoid using a team result as evidence of a task you did not personally perform.

Prepare a contribution note before writing the script. Include what you made, which decisions you owned, who approved them and what material came from others. You do not need to speak every credit in the opening, but the spoken account should remain accurate when someone checks the full project. The evidence-based case study guide helps distinguish observed results from interpretation. A portfolio walkthrough has a narrower job: show what this artifact reveals about your work.

What artifact makes the explanation concrete?

Choose a view that lets the audience inspect the decision you describe. A before-and-after layout can show an organizational change, while a planning sheet can show how you structured a sequence. Identify the relevant part in words instead of relying only on a cursor circling the screen. Keep decorative context secondary to the evidence the viewer needs.

For example, a fictional designer might show two versions of a workshop sign. The useful detail is the placement of the room name, not the entire wall mockup. Describe the difference precisely: “I moved the room name above the schedule so it is the first label in this layout.” That explains an observable design change. It does not prove visitors found the room faster unless the project includes evidence for that separate outcome.

What could a worked walkthrough sound like?

Use a sequence of context, role, decision, artifact and boundary. Here is an original fictional example: “This is a sign system for an imaginary workshop. I designed the room-label layout from a brief supplied by the organizer. In the first version, the room name sat below the schedule. I moved it to the top and used the same position across the set. The two drafts show that change. This was a design exercise, so I do not have visitor testing results.”

Continue with a useful next step: “The full set and the alternate layout are in the linked portfolio.” That ending lets a reviewer inspect the work without inflating the video into a complete project archive. Replace every fictional detail with your actual project facts before using the structure. Do not borrow the example’s role or evidence boundary if they do not describe your circumstances.

How should you narrate the visual evidence?

Say which artifact is visible and what the viewer should notice before moving on. Give the view enough time for that inspection. “This version puts the room name at the top” is more useful than “You can see what I mean here.” If the key detail is small, prepare a separate close view instead of making the audience search through a full desktop.

W3C’s description guidance explains describing relevant visual information. Apply that principle to the project details carrying your argument. You can name a changed position, a sequence or a visible relationship in the main narration. The visual-information script guide offers a fuller method. The goal is to make the decision understandable even when the viewer cannot inspect every small element on screen.

What if the strongest work is private?

Use only material the relevant owner permits you to disclose. If the actual artifact cannot be shown, choose an approved redacted view or a clearly labeled reconstruction. State the boundary so the viewer knows whether they are seeing project evidence or an explanatory stand-in. A reconstruction can illustrate your reasoning, but it should not be presented as a client deliverable or a tested result.

Remove private details before recording rather than planning to notice every problem in the edit. Check filenames, browser tabs, comments and document history visible in the captured view. If you cannot show enough evidence to support the intended claim, choose a different project or narrow the claim. The walkthrough should remain honest when inspected frame by frame, not merely sound convincing during a quick listen.

How do you finish with a useful next step?

Point the viewer to the artifact or portfolio section that expands the exact decision you explained. A vague invitation to “check out my work” gives less direction than “The linked project includes the alternate layouts and my contribution note.” Confirm that the destination is available to the intended audience and that the video does not promise private material they cannot access.

Review the complete take against four questions: is the project identifiable, is your role clear, is the claimed decision visible and are the limits stated? If the answer to any one is missing, revise that passage rather than adding a longer biography. Use the short spoken-script pillar to keep the route focused. A concise introduction to inspectable work gives the audience a reason to continue without asking them to accept unsupported outcomes.

EasyLines is preparing to launch. It focuses on reading a script and recording your delivery, with adjustable text and pace. Finishing work belongs in your chosen editor. If that upcoming workflow fits your needs, join the EasyLines waitlist; availability will be confirmed at launch.