Skip to content
Godwin LawsonBUILDING WITH PURPOSE

Career & Mentorship

How Should You Prepare Your Portfolio for a Mentor to Review?

How Should You Prepare Your Portfolio for a Mentor to Review?

The practical answer

Select a small number of relevant projects, explain your contribution and the decisions behind the work, check access and ask specific questions. Remove private information and make it easy for the mentor to understand what you want reviewed.

A portfolio review is more useful when the mentor can understand the work before spending most of the session finding links, requesting access or guessing what you contributed.

To prepare your portfolio for a mentor review, organise evidence around the skill or decision you want help with. You do not need to pretend every project is complete. You do need to present its state honestly.

This preparation supports personal mentorship by giving the conversation a concrete starting point and making the feedback easier to apply afterwards.

State the purpose of the review

Explain whether you want feedback on technical execution, design reasoning, analysis, project presentation or readiness for a particular kind of opportunity.

“Please check my portfolio” leaves the mentor to choose the scope. “I need help explaining my contribution to these two group projects” identifies a more useful task.

Your purpose should fit the reviewer’s relevant experience. Ask about a specialised area before assuming every mentor can assess it in depth.

Select a few relevant projects

Choose work that shows the ability you want to discuss. A large collection of similar tutorial exercises may make the portfolio harder to review without adding much evidence.

Include a project that reveals your decisions, constraints or revisions. A partly completed project can be useful if you identify the current question and show what you have attempted.

Keep additional material available, but do not make the mentor search through an entire archive to find the priority work. Agree the number and depth of projects within the review scope.

Write a short project brief for each example

Information What it helps the reviewer understand
Purpose The problem or task the project addresses
Audience Who the work is intended to serve
Contribution What you personally did, including group roles
Approach Important decisions, tools and constraints
Current state What works, what remains incomplete and what needs help
Review question The specific feedback you want

A concise explanation can be more useful than a long description filled with tool names. Focus on what the work demonstrates.

Be precise about your contribution

Distinguish your work from a tutorial, template, collaborator’s contribution or generated assistance. Using support is not the same as independently producing every part of a project.

Explain what you changed, why you changed it and what you can reproduce or defend. If you followed a lesson closely, identify it as learning work and describe the extension you attempted.

Do not present a fictional practice project as paid client work. A well-explained practice project can still show useful skills without an invented client story.

Open the supplied links as an intended reviewer would. Confirm that the live demonstration works, the document can be read and the project does not depend on an account the mentor does not have.

Where access is restricted, agree a suitable review method. Provide a safe demonstration account only where appropriate, and do not send administrative credentials casually.

Prepare a short walkthrough for work that cannot be shared publicly. Screenshots or a recorded demonstration can provide context, but explain what they do and do not show about actual behaviour.

Remove private and unnecessary information

Inspect screenshots, datasets, recordings and project files. Look for real customer records, applicant details, passwords, access tokens and private internal material.

Use fictional or properly prepared demonstration data where the review does not need real records. Obtain the necessary permission before sharing confidential client work, even in a private mentorship conversation.

Keep the review focused on your contribution. The mentor generally does not need unrelated business information to assess a layout, analysis method or explanation.

Prepare questions that invite useful feedback

Ask about a decision, difficulty or standard. “Can a first-time user understand this next step?” is more useful than asking only whether the design looks nice.

For development work, explain the expected behaviour and the problem observed. For analysis, distinguish the question, method and conclusion. For design, show the need and the reasoning behind the proposed solution.

Prioritise the questions. A limited session may not support a complete technical audit, redesign and career discussion at the same time.

Record feedback as actions

After the review, organise feedback into corrections, improvements and questions requiring further investigation. Confirm anything you did not understand before beginning a large revision.

Keep a version of the original work so you can explain what changed. A revision note can show how you responded to feedback and where your judgement developed.

Return to the agreed goal. The purpose is not to collect compliments or an overwhelming list of changes. It is to understand the next useful improvement in your work.

Frequently asked questions

Can I ask for a review before a project is finished?

Yes, if the stage and review question are clear. Early feedback can help with an important decision before you invest further effort.

Should I include only my strongest project?

Include work relevant to the purpose of the review. A project with a well-defined difficulty may be more useful for learning than a polished example with no question attached.

Is a public portfolio website required?

No. A well-organised document or set of accessible project links can support a review. Choose a format that makes the work and your contribution understandable.

Make the work easy to examine

Bring a clear goal, selected evidence and honest explanations. That preparation gives the mentor a better basis for feedback and gives you a more usable record of what to improve.

Discuss your next step

Preparing for a portfolio review? Share your learning goal, the type of projects involved and the feedback you need. We can discuss a focused mentorship review that fits your stage.

Explore personal mentorship

  1. Start on WhatsApp
  2. Send an enquiry through the contact page
  3. Email [email protected]
  4. Call +234 703 799 7791
Lawson Godwin Hezekiah

About Lawson Godwin Hezekiah

Technology entrepreneur, website developer and founder of Mita School and Techmita. I work with businesses, educational institutions, government organisations and NGOs.

Read my story ↗

Keep exploring

Let us work together

Put the ideas into practice.

If your website or digital strategy needs attention, let us discuss a useful next step.