C: our quarterly planning process was too long, with multiple sources of input and no single source of truth. I was responsible for my area, but this impacted all areas in the org. I decided to take ownership of redefining the process. 
A: I did a deep dive into the various input sources & teams involved. 
I then created a proposal outlining a streamlined planning process end-to-end, including roles & responsibilities, tooling, and communication plan
I assigned designated owners for each backlog-
PM - product backlog
EM - engg backlog
TPM - horizontal backlog
Instituted regular grooming sessions - TPM, PM, eng - prioritize on big rocks -> alignment w. company objectives
Defined a prioritization framework - align with. objectives, customer/financial impact, critical path, any alternative?
Instituted monthly cross-org sessions with partner teams - current & upcoming roadmap, flag requests early
Regular TPM syncs with horizontal TPMs -> alignment on upcoming initiatives + current initiatives
Define top OKRs around groomed backlog/big-rocks list
Communication plan: proactive comm around big rocks, daily comm during planning cycle regarding status
Source of truth (Jira)- multi-layered board,  created custom dashboards & components
Obj ->  area initiative ->  top OKRs ->  milestones
Team level OKRs -> separate view comprising of all teams
aligned w. org leaders
1-pager: breakdown by theme, top above the line & below the line items
R: cut planning lead time by ~40% (3w->1.5w),  enabled right prioritization of cust needs (ex: enabled teams to flag GDPR req in advance), evangelized process to other teams
Long term - replicated this process across other teams