Add 90-day onboarding plan to TPM job description

[Copilot]

Integrates a structured 90-day onboarding plan into the Technical Product Manager job description. The plan establishes clear expectations and progression milestones for new hires.

Changes

Added "90-Day Plan" section positioned between responsibilities and skills, containing:

• Days 0–30: Learning phase (product, architecture, team dynamics, backlog state)
• Days 31–60: Alignment phase (priorities, execution cadence, delivery flow, refinement)
• Days 61–90: Execution phase (backlog ownership, roadmap visibility, shipping value)

Each phase includes:

• Theme and primary objective
• 4 activity areas with concrete deliverables (12 total)
• Success signals for phase completion

Goal statement: Progression from learning → alignment → execution → shared backlog ownership with engineering leads.

Preface: "We believe setting clear expectations enables new teammates to thrive. Here's what success looks like in your first 90 days at FlowFuse:"

---

109 lines added to src/handbook/peopleops/job-descriptions/technical-product-manager.md

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• catalog.flowfuse.com
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/website/website/node_modules/.bin/eleventy --dryrun grep -l PM (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Integrate a well-structured 90-day plan for the Technical Product Manager (TPM) role into the new job description, using the provided draft. The plan should be added as a clearly marked section, after the responsibilities and before requirements/qualifications. Ensure formatting and tone are consistent with the rest of the document. Preface the section with: "We believe setting clear expectations enables new teammates to thrive. Here’s what success looks like in your first 90 days at FlowFuse:". The draft content is as follows:

FlowFuse TPM 90-Day Plan

Goal: Ramp from learning → alignment → execution → shared backlog ownership with engineering leads.

---

Outcomes by Day 90

By the end of the first 90 days, the TPM will:

• Understand FlowFuse’s platform, users, and architecture
• Be fully embedded with engineering leads and delivery rituals
• Drive clarity on “What’s Important Now” (WIN)
• Actively manage and prioritize the backlog alongside engineering leadership
• Own execution flow from discovery → refinement → delivery → feedback

---

Days 0–30: Learn, Map, Build Trust

Theme: Context before control

Primary Objective

Establish deep understanding of FlowFuse’s product, users, architecture, and team dynamics.

Key Activities

Product + Customer Immersion

• Review product positioning and roadmap
• Understand primary personas (developers, platform teams, enterprise admins)
• Sit in on customer calls or review recordings

Deliverable:
✅ FlowFuse User + Value Map

---

Technical Architecture Familiarity

• Walk through platform components with engineering leads
• Identify areas of leverage vs fragility

Deliverable:
✅ Architecture mental model + glossary

---

Team Integration + Operating Rhythm

• Build relationships via structured 1:1s
• Observe sprint planning, refinement, release process

Deliverable:
✅ “How FlowFuse Ships” overview

---

Backlog Current State Review

• Audit backlog structure and hygiene
• Identify quick wins in clarity and organization

Deliverable:
✅ Backlog health assessment

---

Success Signals by Day 30

• Strong relationships with engineering leads
• Clear understanding of product + customer value drivers
• Backlog structure understood, not yet owned

---

Days 31–60: Align, Clarify Priorities, Start Driving

Theme: From understanding → influence

Primary Objective

Begin shaping execution through alignment, backlog clarity, and problem definition.

Key Activities

Define “What’s Important Now” (WIN)

Partner with leadership + engineering to establish top quarterly priorities.

Deliverable:
✅ WIN priorities + narrative

---

Establish Execution Cadence

• Weekly backlog refinement with engineering leads
• Sprint goal alignment and dependency surfacing

Deliverable:
✅ Shared working agreement + operating rhythm

---

Improve Discovery → Delivery Flow

• Problem framing before solutioning
• Clear acceptance criteria and feedback loops

Deliverable:
✅ Updated Epic/PRD template

---

Lead Backlog Refinement

• Break initiatives into deliverable slices
• Ensure tickets are actionable

Deliverable:
✅ Engineering-ready epic(s) owned end-to-end

---

Success Signals by Day 60

• TPM is driving clarity, not just observing
• Engineering leads trust prioritization inputs
• Backlog shifts from messy → execution-ready

---

Days 61–90: Execute, Own Backlog, Drive Delivery

Theme: Shared ownership and momentum

Primary Objective

Operate as the active execution owner: prioritizing, managing backlog, and shipping with engineering.

Key Activities

Backlog Ownership with Engineering Leads

TPM co-owns priority ordering, sprint readiness, and tradeoff decisions.

Deliverable:
✅ Backlog actively managed weekly

---

Roadmap Execution Visibility

• Sprint goal tracking
• Outcome-based roadmap updates

Deliverable:
✅ Now / Next / Later execution view

---

Ship Meaningful Customer Value

Drive at least one major platform or customer-facing improvement to release.

Deliverable:
✅ Release + feedback capture

---

Institutionalize Collaboration

Solidify shared operating model and continuous learning loops.

Deliverable:
✅ FlowFuse Product Delivery Playbook v1

---

Success Signals by Day 90

• TPM + engineering leads jointly run backlog prioritization
• Sprint planning is outcome-driven
• Execution cadence is faster and clearer

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[netlify]

✅ Deploy Preview for flowforge-website ready!

Name	Link
🔨 Latest commit	ff2555b
🔍 Latest deploy log	https://app.netlify.com/projects/flowforge-website/deploys/6982481e0407bf00080b48a9
😎 Deploy Preview	https://deploy-preview-4501--flowforge-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 84 (🟢 up 23 from production) Accessibility: 80 (no change from production) Best Practices: 100 (🟢 up 8 from production) SEO: 92 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[ZJvandeWeg]

@copilot Remove the emoji please, and style this document like other job descriptions in the handbook.

[ZJvandeWeg]

I'm missing a reference to the Iteration value we probably want to capture here.

[lbeau]

Can you clarify what you mean? Or feel free to suggest an edit

[ZJvandeWeg]

My understanding is that a TPM is embedded in a team. As such they're to be a bridge between "Engineering and Product" and on the other side "Sales & Customer Success"?

[lbeau]

true though in an org like this I would not want to keep a TPM away from informing sales/customer success on upcoming changes to experience, for example.

[ZJvandeWeg]

Would be nice to move it below line 21, as it's the same topic