Five Questions to Ask in a Portfolio Meeting

The goal of a portfolio meeting is not to pick the most impressive image. It is to understand how the work was done.

Visuals create a quick impression, but scope, roles, timing, and review criteria shape the actual collaboration. These five questions make the conversation more useful.

1. What was your role?

Ask whether the person handled planning, design, development, production, or operations. In team work, separate their decisions from the parts owned by others.

2. What was the original goal?

The problem behind the result matters more than its shape. Ask who the work was for and what would count as success.

3. What changed during the work?

Ask about changes in budget, timing, technology, or approval. The useful signal is how those changes were recorded and handled.

4. How was completion checked?

Look for observable criteria: user response, working features, delivered files, or operational readiness.

5. What would you check first for our project?

Your project does not need to be identical. Ask whether the person can identify the important differences and propose a sensible first check.

A simple record

• Role: what they owned

• Goal: what was meant to change

• Change: what conditions moved

• Completion: how the result was checked

• First check: what matters first for your project

Conclusion

A good portfolio creates both interest and a useful starting point for collaboration. Recording the answers helps separate a strong impression from practical fit.