08 Jun 2026 7 min read product · series · practice · seeing ·

Getting Back Up to Speed – Again

The path is never straightforward.

You are back on a product you stepped away from – a week of leave, a month on another initiative, a quarter inside a programme that ate your calendar. The stand-up runs. Someone references a decision you half remember. The roadmap has new lanes. A Slack thread from Tuesday already has forty replies and a ✅ emoji that means “we’re done arguing.” You nod. You skim. You promise yourself a proper read tonight. Tonight does not come.

That friction – context switching dressed up as “I’ll catch up async” – is not a discipline problem. It is a missing reorientation practice.

What we pretend catching up looks like

Most of us treat re-entry as consumption: read the board, scroll the channel, watch the recording, open every doc linked in the ticket. The theory is that more information will get you up to speed.

That confuses information with knowledge. What you glean from Confluence or Jira or whatever your system is (Google Docs perhaps?) is mostly information – that you will skim at 10pm. What you need to act is knowledge – real, relational, tied to who was in the room when the project moved. Tickets (or Gemini notes) record events; the team holds what they mean. Files (again, Gemini notes) record what happened; people hold the shared picture everyone else has been updating while you were away. Asynchronous catch-ups effectively transfer information. It is weak at rebuilding the real picture.

Product-first teams already bias the other way. The contrast is stark on a single slide: less ticket/spec writing, more context sharing (a one-pager, a shaped bet, a mission brief); less “research done before it reached the team,” more dedicated discovery that keeps running while delivery ships. When you return to a team like that, the gap hurts twice: you are behind on delivery and on the discovery stream that decided what delivery was for.

In practice you get coverage without comprehension. You know that pricing changed; you are fuzzy on why. You saw the initiative move lanes; you cannot yet argue what should move next. Dual-track teams feel this as a split screen: the delivery track advanced in public; the discovery track (interviews, bets killed, assumptions retired) lived in heads, Figma, and side threads. You are in the meeting but off the pace – which reads as hesitation when it is lag.

The cost is not only your time. Teams interpret slow re-entry as low conviction. Stakeholders repeat context you were supposed to absorb. You compensate by being louder before you are clearer. That is how “getting back up to speed” turns into performance instead of practice.

A practice, not a binge

Reorientation is a deliberate practice: a bounded set of moves that rebuild shared picture, test your understanding, and surface what changed while you were away – without pretending you can re-read the entire history of the product.

It is the companion to last week’s frame. Product is social practice; re-entry is how you rejoin that practice without demanding the room replay the film.

Three constraints keep it honest:

1. Time-box it. If you have a day, you do not get a week of reading. If you have ninety minutes, you do not get a day. The box forces prioritisation – which is the skill. Shaping and betting teams already live this instinct: fixed time, variable scope. Reorientation is the same move applied to context: you are not excavating a backlog; you are choosing what must be true before you speak in the betting conversation.

2. Conversation beats archives. The fastest signal on what matters now usually lives in two or three people, not in every ticket comment since March. Reorientation is listening for delta, not performing a recap: draw the shift from others before you narrate it back in strategy language. A short live conversation beats a pile of links, exports, or AI summaries of channels you missed.

3. Output is a question list, not a summary deck. You are not producing a recap for the team. You are producing the gaps you still need resolved to act well – a written position with a date, not a polished deck that flatters your diligence.

Much of PM work sits in the complex domain: requirements, politics, and partial information do not yield to “read more until certain.” The useful habit is probe–sense–respond: short loops, then adjust. Binge-reading is a pretend plan in a domain that does not reward pretend plans. Reorientation is the probe.

Try this week: the 90-minute reorientation

Block ninety minutes within your first two days back. Put it on the calendar with a title your team recognises – “Reorientation: [product name]” – so it is legitimate, not stolen focus.

Step 1 – Ten minutes: what changed the world (15%)

Open only what answers: What would embarrass me if I did not know it in today’s room?

Last shipped thing customers can see (release note, changelog, demo link – pick one).
One metric or target the team is actually steering against this sprint – not the OKR poster on the wall.
Any decision explicitly marked “irreversible for now” (pricing, platform bet, date you committed externally).

Write three bullets. If you cannot find them, that is your first question for step 2. Before you opine on the roadmap, know what shipped and whether anyone actually uses it.

Step 2 – Forty minutes: three conversations (45%)

Book three 12-minute chats (async voice notes count if timezone hates you). Same opening line each time:

“I’m reorienting on [product]. What’s the one thing that shifted while I was away that I shouldn’t walk past?”

Talk to:

Engineering – what became harder, cheaper, or riskier technically.
Design or research – what user reality moved (even if the roadmap did not).
Whoever owns the narrative outward – sales, support, or a PM partner – what promise the organisation is now making.

Do not ask for history. Ask for delta. Take notes in their words; resist rewriting into strategy language yet.

Step 3 – Twenty minutes: map the live arguments (25%)

Scan the backlog and roadmap only for items with active disagreement: comments, relabelled priorities, items that jumped lanes twice, epics with “blocked” and no owner.

You are not prioritising. You are listing live questions the team has not settled – the arguments that would still show up at a betting table, not the settled work already in flight. Aim for five bullets max. Each bullet should name a trade-off, not a task (“platform migration vs feature parity for Account X”, not “finish API work”).

A strategy pyramid stress test helps if you are lost: what shifted in purpose (who we serve), strategy (bets we are making), or execution (what we stopped pretending)? You do not need a workshop – three labelled bullets are enough.

Step 4 – Twenty minutes: publish your gaps (15%)

Post a short note in the team channel – five bullets, no polish:

What I believe is true now (three items).
What I am not sure about (two items).
What I will decide or clarify by [date you name].

Separate facts from insights before you post. Facts are attributed and concrete (“Support saw a spike in billing confusion after the 12 March release”). Insights are your provisional read (“We may have traded self-serve clarity for sales-led exceptions”) and belong in the “not sure” line until someone corroborates. Do not smuggle interpretation in as if it were shared history.

That last date is the accountability hook. Good PMs take clear written positions on hard issues; bad PMs stay verbal, vague, and loud in meetings. Five bullets is leverage, not theatre.

What good looks like: you can explain the current bet in one sentence without slides. You know which fights are active and which are settled. You have a dated commitment to resolve your open questions.

What to watch for: the binge reflex (“let me read the whole channel first”); the shame skip (“I’ll stay quiet until I’m sure”); the false summary (a beautiful recap nobody needed); the link dump from a well-meaning colleague who stayed (forty minutes of context sharing that is still information, not your knowledge).

Start small: the 20-minute version

If ninety minutes is fiction this week, do the minimum viable reorientation:

One conversation (twelve minutes - yes, twelve - you read that correctly) with whoever has been closest to the work.
Three bullets: what shipped, what’s contested, what I’ll clarify by Friday.
Post it. Tag one person who can correct you.

Twenty minutes will not rebuild full depth. It will stop you from improvising in the big meeting from a place of polite fog.

When you are the one who stayed

If you did not leave, you still play a role. When a colleague returns, do not “bring them up to speed” with a forty-minute monologue or a folder of links. Offer:

the one delta that matters,
where the argument is live,
where docs are wrong or stale.

That is how a team practises reorientation together instead of making the returning PM perform competence before they have earned it. You are helping them rejoin the live picture, not exporting your inbox.

A line you can reuse

When someone asks if you are across it yet:

“I’m reorienting deliberately – I know what shipped and what’s still contested. Here’s what I’ll decide by Thursday.”

It signals responsibility without pretending you never left.

Seeing practice in the switch

I'm still in seeing practice this quarter – noticing how work actually runs before adding structure. Context switching is a test case. The mistake is treating re-entry as private homework. The practice is social: short loops, named uncertainty, dated follow-through.

You will leave again – another initiative, leave, reorganisation. The team’s memory will move on without malice. Getting back up to speed is not a one-off skill. It is a repeatable habit that respects everyone’s time, including yours.