RS
Stage 05 · 90-Day Plan

First 90 days on BEYON

A parental-leave cover is a stewardship role. The goal isn't to leave a different product behind — it's to keep the team performing, protect the roadmap, and hand back a slightly better version on day one.

Days 0–30

Listen · audit · protect continuity

  • 1:1s across engineering, project teams, support, finance

    Map the people, the rituals, and the in-flight commitments. The point of a parental-leave cover is to *protect* continuity, not reshape it.

  • Read the backlog, the release notes, and the last 6 months of customer tickets

    Understand what's been promised, what's slipping, and where the friction lives. Sit with the QA leads and read defect trends.

  • Shadow at least two client conversations

    I want to hear how BEYON is described in the room before I describe it in the room. Same posture I used at Roam.

  • Confirm the success criteria for the 14 months

    What does the returning PM need to walk back into? Document it explicitly with the engineering manager and product leadership.

Days 30–60

Plan · align · re-rationalise the backlog

  • Roadmap review with engineering & QA

    Re-rationalise priorities against capacity, technical debt, and customer-stated value. Bring forward anything blocking release confidence.

  • Stakeholder map · communication cadence

    Standing forums with finance, support, and project teams so decisions surface where they belong, not in side-channels.

  • Quality bar review

    Refresh the definition of done, the release checklist, and the post-release review with QA. Small lift, large compounding effect on customer trust.

  • Identify one shippable improvement for days 60–90

    Something visible to a customer, scoped to fit a parental-leave cover — proof of momentum without redirecting the strategy.

Days 60–90

Deliver · measure · hand-off ready

  • Ship the identified improvement

    Through the same release process the team uses today. The win is the increment, not the splash.

  • One client-facing artefact

    A roadmap update, a release note, or a workshop deck — chosen with the account leads — to deepen a relationship while I'm covering.

  • Measure: release health, ticket trends, NPS or equivalent

    Data points the returning PM will appreciate seeing on day one back.

  • Maintain a live hand-off doc from day one

    Decisions, open threads, names of who knows what. The most respectful gift to give the returning PM.

See the Closing Brief →