👋 Hi {{first_name|there}},
Last week I told you I started a new job, and I promised to share how I am ramping up. Here it is: a second brain, two prioritization frameworks, and a council.
It’s also the system that would have made my job search far less chaotic. When you are searching, the hard part is rarely the work. It is the context. Which company was I talking to. What did the recruiter say about comp. Which story did I already tell the hiring manager. What was I supposed to follow up on, and when.
Lose that thread and you look flaky to people you actually impressed. Keep it, and you look like the organized, on-top-of-it PM they are trying to hire.
How I am using it at work
I am on day 9 of my new role. I am already contributing to sprint planning and core project work, making design decisions, and writing responses to support tickets and idea requests from the CS team. That is not because I am fast. It is because I am not starting from zero every time someone asks me something.
Everything lives in one Claude project:
Second brain: every 1:1 note, team doc and open question goes in the same day. Before a meeting, I ask it what I already know about that person and what I promised them.
Prioritization: the Eisenhower matrix for my own week, so onboarding does not swallow the few things that actually matter. Evidence Guided by Itamar Gilad is loaded in as context for feature building and sprint planning, so I ask “what is the evidence?” before “when can we ship?”
Council: before a plan goes anywhere, I test it against four people: my VP, Elena Verna, Lenny Rachitsky and Marty Cagan. Would my VP see the business case in the first line? Would Elena ask what it does to activation? Would Marty say I am describing output, not an outcome?
Build it for your job search
Same three parts, pointed at your search.
1. The second brain
Five parts, one home. Build it in a Claude project or an equivalent AI workspace if you can. It saves you keeping a dozen docs aligned by hand, and it is real practice with the AI tools interviewers are starting to ask about. A plain doc is fine if that is where you will actually start.
A sourcing list.
Not “every job with product in the title.” A short list of companies you would actually want, the specific roles, and one line on why you are a fit. Add who you know at each one. This is where the search starts, and it is the part most people skip on their way to mass-applying.
Track: Company | Role | Why I am a fit | Who I know
An application board.
A simple kanban: sourced, applied, in process, interviewing, decision. Every role is a card with its next action and a date. One glance tells you where everything stands, which is the exact question that keeps you up at 2am.
Track: Role | Stage | Next action | Due date
A conversation log.
Every recruiter call, HR screen and interview round gets a few lines, written within the hour while it is fresh. By your third round the patterns show up, and the next round usually builds on the last.
Track: Date | Company | Round | What they asked | What I learned about the loop | Comp signal | Next step
A story and practice log.
Your three or four strongest stories, written down, each tagged to the kind of question it answers. Then your reps: record yourself saying them out loud, listen back once, note the one thing to fix. Writing a story is half the work. Practising it until it sounds like you, not a recital, is the other half.
Track: Story | Questions it answers | Last told to | One fix from my last rep
A follow-up list.
Who you owe a thank-you, who you are waiting on, who to nudge and when. The search is not won by the person who applies most. It is won by the person who follows through.
Track: Person | What I owe or am waiting on | Nudge date
A pro tip: Ask your second brain what you can do vs what it can do and schedule for you using connectors
2. Prioritization
Every Monday, sort your search tasks into the Eisenhower matrix:
Do now (urgent and important): follow-ups that are due, prep for this week’s interviews.
Schedule (important, not urgent): sourcing, practising your stories, warm outreach. Most offers come from this box, and it is the one people skip.
Shrink (urgent, not important): low-fit roles with a closing deadline, recruiter pings for jobs you do not want.
Drop (neither): refreshing LinkedIn, mass-applying.
3. The council
Pick three or four voices. At least one could be a real person who knows the job you want: a mentor, a former manager, or a PM a level above you. Then add two or three thought leaders whose work fits the role. Going for growth roles? Elena Verna. Want sharper product sense answers? Lenny’s interview episodes. Discovery-heavy role? Marty Cagan.
Before a story, cover letter or take-home goes out, run it past them. Would my mentor believe this? Would Marty call this output or an outcome? Fix what they would catch, then send.
Your homework this week
Create the project, or the doc. Paste in every live application, put each one on the board with its next action, then sort this week’s tasks into the four boxes. Twenty minutes.
You will feel the difference the first time someone asks "so where are you in the process?" and you actually know.
If you want the full version, how to translate your experience, target the right roles, and build the stories you will practise, it is all in my book, Already a PM.
If you want a second set of eyes on your search, where your evidence is thin, which stories to lead with, what your board is missing, my free 30-minute clarity call is open.
Talk soon,
Stef
P.S. The best system is the one you open before every call. Mine is open in a tab right now.