Build A Living Profile For Every Team

Own roadmap priority and enterprise tier packaging for SSO readiness.

Also fields contract-language questions that belong to Legal.

Launch Enterprise SSO · enterprise tier packaging.

Same outcomes, plus ad hoc pricing exceptions for pilot accounts.

SSO in enterprise tier · Q3 roadmap lock.

SSO packaging slipped one week waiting on a Legal redline.

Linear roadmap · pricing model doc.

Linear roadmap · pricing doc · a shared contract tracker in Notion.

Sales → Product: pilot criteria · Engineering → Product: GA evidence.

Same pairs, plus an unpublished Slack thread with Legal on contract copy.

Who signs off on final enterprise tier packaging?

Unresolved — Legal and Product both edit the same contract doc.

Own enterprise authentication build and delivery readiness.

Same mission, carrying elevated load from cross-team SAML requests.

SAML integration · IdP connectors · audit log export.

Same outcomes, plus unplanned Security remediation work.

Ship SAML connectors · pass threat model review.

Connectors on track; threat model review queued behind Security's backlog.

Auth service repo · IdP connector library.

Auth service repo · IdP library · an ad hoc Security review spreadsheet.

Security → Engineering: threat model · Sales → Engineering: pilot list.

Same pairs; the Customer Success handoff is still informal.

Does Security's 48h review SLA hold under Launch pressure?

No — the last two reviews took 4+ days with no escalation path.

Own the approval gate and residual risk for enterprise authentication.

Same mission, but now the only checkpoint before any SSO deploy.

Threat model sign-off · IdP compliance block list.

Same outcomes, plus informal incident triage for auth issues.

Clear the SSO threat model backlog · define IdP compliance rules.

Backlog growing — no second reviewer to share the sign-off load.

Threat model template · compliance checklist.

Same tools, tracked in a personal doc instead of the shared system.

Security → Engineering: 48h review SLA.

SLA missed twice this quarter; no published escalation path.

Who backs up Security sign-off when the lead is out?

No backup approver is documented anywhere.

Own enterprise contract language and data processing addenda.

Same mission, sharing packaging language ownership with Product.

Enterprise terms block · DPA for audit retention.

Same outcomes, plus repeated redlines on Product-authored copy.

Finalize the SSO terms block · align DPA to audit retention plan.

Redline cycle stretched to two weeks from duplicate edits.

Confluence terms page · DPA template.

Confluence terms page — Product also edits the same page directly.

Legal → Product: terms block · Legal → Sales: redline turnaround.

Same pairs; the turnaround SLA was missed once this quarter.

Who is the single primary owner of customer-facing contract language?

Open — Product and Legal both claim it in different systems.

Own pilot account commitments and enterprise renewal expansion.

Same mission, committing dates ahead of confirmed Engineering capacity.

Pilot account list · renewal commitments.

Same outcomes; pilot dates set before an Engineering capacity check.

Lock the Week 3 pilot go-live · protect renewal pipeline.

Week 3 go-live conflicts with Engineering's Week 4 peak load.

CRM pilot stage · renewal forecast sheet.

Same systems; no visibility into the capacity horizon page.

Sales → Engineering: pilot list · Sales → Product: eligibility.

Sales → Customer Success handoff is still informal Slack.

Should pilot dates require an Engineering capacity check first?

Not currently — no gate exists in the process.

Own customer migration cutover and rollout communications.

Mission holds on paper; no active work is happening against it.

Migration playbook · rollout comms · cutover window.

None of these outcomes have a published owner right now.

Draft migration playbook · prep rollout comms.

Blocked — waiting on a Security → CS interface that was never published.

Support ticket queue · rollout comms templates.

Same systems; no linked runbook from Engineering yet.

Engineering → CS: draft runbook · Security → CS: missing.

Zone empty on the Launch field — no published interface exists.

Who owns customer migration cutover today?

Nobody — this is the empty zone on the ownership field.