Portfolio Build
The Situation
After more than 10 years in operations across multiple industries, a resume alone was not telling the full story. The roles were varied, the path was unconventional, and the strategic thinking behind the work was not always visible on paper. A portfolio was needed to help close that gap.
The Problem
How do you scope, build, and launch a professional portfolio that demonstrates strategic thinking and execution capability, while treating the build itself as a strategy and operations project?
The Approach
The portfolio build was treated as a real project from day one.
A project brief defined the problem, context, goals, constraints, and success criteria. A decision log captured the major choices, including platform selection, site structure, case study sequencing, data approach, dashboard tools, and launch scope. A workback timeline mapped the project against a target launch date. A retrospective documented what held, what changed, and what would be done differently.
Within the decision log, each major decision was documented with context, options considered, rationale, and trade-offs.
What Shaped the Work
Five decisions helped to shaped the outcome.
1) The portfolio needed a realistic launch scope. Launching with too many case studies would have delayed the site and reduced its usefulness during an active job search. Launching with only one case study would have made the portfolio feel too thin. The decision to launch with three complete case studies created enough substance for Phase 1 while keeping the project manageable.
2) Choosing Squarespace prioritized speed, clarity, and ease of execution over a higher design ceiling. Framer offered more flexibility, but Squarespace better matched the project’s constraints and timeline.
3) Defining the analytical framework before writing helped avoid the most common failure mode in this kind of work: producing a summary of public information instead of an analysis with a clear point of view.
4) The visual standard mattered more than expected. The site, project brief, decision log, workback timeline, and case study materials needed to feel connected. A consistent look and feel helped signal that the work was intentional, not a collection of disconnected pieces.
5) The process itself needed to be visible. The project brief, decision log, workback timeline, and retrospective were not treated as behind-the-scenes documents. They became part of the portfolio. That was a deliberate choice, because those documents show how the work was scoped, how decisions were made, and how the project moved from idea to execution.
Together, these decisions kept the project focused. The goal was not to build the biggest possible portfolio before launch. The goal was to build a credible first release that could support active job applications and create a structure for future work.
The Recommendation
Treat the process as part of the work.
For this project, the portfolio was not only the final website. It was also the planning, decisions, constraints, trade-offs, and sequencing that shaped how the website was built. Making that process visible turned the build itself into evidence of strategy and operations capability.
A project brief, decision log, workback timeline, and retrospective are not extra paperwork. They create clarity, expose trade-offs, and make the work easier to explain. They also help separate work that was intentionally built from work that simply came together.
For personal projects, the same rule applies as it does in business: the final output matters, but the thinking behind it is often what makes the work credible.
Supporting Documents
The case study above summarizes the project. The documents below show the planning, decisions, timeline, and reflection behind the build.
Project Brief
Defines the purpose, scope, constraints, success criteria, risks, and timeline for the portfolio build. It set the foundation for the project and clarified what belonged in the first release.
Decision Log
Captures the major choices made during the project, including platform selection, site structure, case sequencing, data approach, and launch scope. It shows how key decisions were evaluated and why they were made.
Workback Plan
Maps the project from scoping to launch, including key milestones, dependencies, and release priorities. It shows how the work was sequenced against a target launch date.
Retrospective
Reviews what held, what changed, and what would be done differently. It captures the lessons from the build and how the project evolved from plan to launch.
Together, these documents show that the portfolio was not only designed as a final product, but managed as a strategy and operations project from scope to launch.
