# Founder source-to-angle handoff

Record: `figma-field-patel-worked`  
Owner: Unknown

## Source

- Source ID: AD-FIGMA-FIELD-PATEL
- Source type: public sponsored post
- Speaker: Dylan Field, recounting an interview with Jeetu Patel
- Relationship: Field conducted the public interview; Patel described the Cisco design-review change
- Source date or ID: LinkedIn Ad Library 1499184766
- URL or reference: https://www.linkedin.com/ad-library/detail/1499184766
- Permission: public
- Supports: Field's public account of the prior review chain, six-week delay and move to direct IC presentations
- Does not support: campaign results, the private interview workflow or permission for new adapted copy

> When Jeetu started design reviews at Cisco, teams were presenting to their VP, then their SVP, then their SVP’s boss. It took six weeks for a design review to show up on his calendar, so he reworked the process. ICs started presenting directly to execs.

## Interpretation

A decision bottleneck is a more concrete topic than a broad design-leadership claim because the buyer can inspect the review process.

State: `unreviewed`

## Angle candidates

- A1: Frontline authority | Buyer: design leader | Problem: work travels through management layers | Decision: who should present the work | Promise: inspect who presents | Hook: The people closest to the work should present it. | Basis: exact_passage | State: candidate
- A2: The six-week review chain | Buyer: design leader | Problem: review latency hides the work | Decision: remove layers from the review path | Promise: inspect the six-week review path | Hook: What changed when Cisco removed three layers from a design review? | Basis: interpretation | State: candidate
- A3: Culture through process | Buyer: design leader | Problem: craft loses attention in the review process | Decision: change who shows the work | Promise: inspect how review design affects craft | Hook: If you want people to care about craft, change who gets to show the work. | Basis: interpretation | State: candidate

## Selected angle

- ID: A2
- Label: The six-week review chain
- Buyer: design leader
- Problem: review latency hides the work
- Decision: remove layers from the review path
- Promise: inspect the six-week review path
- Proposed hook: What changed when Cisco removed three layers from a design review?
- Basis: interpretation

## Approval

- Owner: Unknown
- State: pending
- Version: None
- Approved hook: None
- Approved supporting point: None
- Decision date: None

## Recording brief

- Speaker: Source owner to confirm
- Format: direct-to-camera explanation with review-path diagram
- Orientation: 9:16 master
- Target duration: 45 seconds
- Delivery: Unknown
- Required visual: before/after review path
- Prohibited claims: campaign performance, business results, unapproved Patel or Field wording
- Reviewers: None listed
- Finished media review: not_run
- Destination: Unknown
- CTA: Unknown
- Launch owner: Unknown

### Scenes

- No complete scene plan.

## Readiness

- Draft: **Hold**. Ask the source owner whether the selected interpretation preserves their meaning.
- Launch: **Hold**. Complete: delivery direction, CTA, launch owner, scene plan, reviewers, finished media review, working HTTPS destination.

## Unresolved requests

- `hold_ambiguous_interpretation`: Ask the source owner whether the selected interpretation preserves their meaning. Owner: source owner.
- `hold_missing_owner`: Name the person who can approve the source interpretation and final attributed wording. Owner: marketer.
- `hold_launch_inputs`: Complete: delivery direction, CTA, launch owner, scene plan, reviewers, finished media review, working HTTPS destination. Owner: launch owner.