The playbook
Portfolio Website Design: Checklist
Use this portfolio website design checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect relevant project inquiries. Check an actual page or interaction record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
Select work aligned with the projects you want to win. For each example, explain the problem, your role, the constraints, and the delivered result. If other people contributed, state your contribution accurately rather than implying sole authorship.
Before you use the checklist
Name the exact item being checked and its purpose. Gather project, audience, role, result, evidence. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Choose projects that match the clients you want | A dated observation showing how project was verified | website lead |
| Explain your role constraints and delivered work | A dated observation showing how audience was verified | designer or developer |
| Give viewers a clear route to discuss similar needs | A dated observation showing how role was verified | site owner |
Check the failure path
- Look specifically for this failure: showing images without explaining what problem the work solved.
- Add concise project context and verifiable contributions. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check evidence.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Choose projects that match the clients you want,” a meeting about the subject is not the evidence itself. Retain the relevant project and audience, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents present selected work in a way that supports relevant inquiries deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow relevant project inquiries using a consistent definition so later reviews can connect execution quality with useful results.
Use realistic content lengths and assets during review. Short placeholder headings can conceal overflow and hierarchy problems that appear with real service names, prices, or instructions. Check the result after the final content is inserted.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now