Suppose you want to publish a portfolio before a hiring cycle. It is easy to draw a six-week timeline with “write case studies” in the middle. The useful version tells you which stories you can publish, when a reader can give feedback, and what you will cut if an approval comes late. These seven steps turn a goal into a project plan you can revise.
1. Describe the finished result

Imagine a hiring manager opening the portfolio and finding two clear examples of your work, each with the problem, your role, and what changed. This gives the project a concrete finish line. It also reveals decisions to make early. Can you publish the material? Which examples show your work best? What would a reader need to understand without you there?
Then picture the work between now and that moment. In an exam study, Lien Pham and Shelley Taylor found benefits from mentally rehearsing the study process. To borrow the idea for a project, walk through one real work session. Picture which file you will open, what you will draft, and how you will tell whether the draft is ready to share. [1]
2. Write a goal with an acceptance test
Here is one way to write it. “Publish two portfolio case studies by the last Friday of next month. In each, a test reader should be able to identify the problem, my role, and the result without an explanation from me.” The number and date define the scope. The reader’s ability to answer three questions gives you a practical quality check.
If you have never built a portfolio, begin with one rough case study and one reader. Use the first session to find out whether your material works. That evidence will improve your estimate more than polishing a statement on an empty planning page.
3. Record the goal and the constraints together
Keep one planning note with the deliverable, the date, your weekly availability, and the work you are prepared to defer. Include two assumptions, such as having permission to show a particular screenshot and getting comments within three days. Write each as something you can confirm or revisit. The next time you open the plan, the decisions are visible along with the goal.
If two projects compete for the same evening, give each a real slot before committing to both. A written plan can make a conflict visible early enough to change the deadline or scope.
4. Break the work into deliverables
A task is easier to schedule when you know what it should produce. “Work on portfolio” might mean choosing a case, drafting an outline, or asking someone for permission. Give each task a separate finish condition.
- Gather. List three candidate projects and mark which material you can share.
- Draft. Write a problem, contribution, and result for each chosen story.
- Review. Ask one reader to answer the three acceptance questions from the drafts.
- Publish. Make corrections, check the links and images, and open both pages on a phone.
Mark the dependencies. You can outline a case before approval arrives. You may need permission before sending the draft to a reader or publishing any screenshots. Put the uncertain dependency near the beginning and identify a substitute case you can legally share.
5. Estimate the timeline from past work
In planning fallacy experiments, Roger Buehler and colleagues found that people tended to underestimate completion time for their own tasks. Participants used past experience more effectively when explicitly asked to connect it to the prediction. Look up how long a comparable draft or approval actually took. Budget separate time for waiting, writing, and rework. A calendar with empty space before the deadline gives you a place to put surprises. [2]
For example, if a draft usually takes three sessions, two drafts require six sessions before review. With two sessions per week, allow three weeks for drafting and reserve additional time for feedback and corrections. If your deadline is in four weeks, book the reader now and have a smaller format ready.
6. Give the first task a start cue
A work block works better when it begins with a concrete move. “After dinner on Tuesday, open last year’s project folder and list three possible cases” provides both a cue and a finish condition. Put the folder link in the calendar event. If Tuesday falls through, use the next open block or do the five-minute inventory on Thursday before tackling the outline. This applies the cue-and-response structure studied in implementation-intention research. [3]
7. Review the plan while changes are still cheap
At the end of the first week, compare completed deliverables with the plan. Ask which tasks happened, which dependencies changed, and what has become the biggest risk. Progress-monitoring research suggests that recording progress can support attainment. A project review also needs a decision that follows from the record. [4]
If you have two drafts and no approval, move the shareable case first. If a reader cannot explain your role, fix the story before changing the typography. When the goal and quality standard still make sense, adjust the order or scope of the remaining tasks. Once the original reason for the project disappears, revisit the deliverable itself.
A planning note for this week
Outcome and deadline. First deliverable. Next scheduled work block. Dependency to confirm. Evidence to bring to the review. Scope to cut if time runs short.
For a longer cycle where the priority itself may change, see the eight-step goal review.
References
- Pham & Taylor (1999). From thought to action.
- Buehler, Griffin & Ross (1994). Exploring the planning fallacy.
- Gollwitzer & Sheeran (2006). Implementation intentions and goal achievement.
- Harkin et al. (2016). Does monitoring goal progress promote goal attainment?
Further reading
Read the original guide from Lucid.

