Engineer a UI performance scientist role charter blending instrumentation, research, and…
- User
Engineer a UI performance scientist role charter blending instrumentation, research, and cross-team enablement.
- Assistant
Hmm, the user is asking for a charter for a UI Performance Scientist role that blends instrumentation, research, and cross-team enablement. This is a strategic role that needs to bridge technical depth with organizational influence.
I should structure this as a formal charter document with clear sections: mission statement, core responsibilities broken into instrumentation, research, and enablement pillars, success metrics, collaboration model, and tools/expectations. The tone should be authoritative yet practical, emphasizing both technical rigor and cross-functional impact.
The instrumentation part needs to cover both passive (telemetry) and active (synthetic testing) monitoring, while research should tie performance to business outcomes. Enablement must focus on scalable knowledge sharing—maybe a tiered model (self-serve docs, workshops, embedded support). Metrics should balance infrastructure health (e.g., LCP) with adoption (team engagement) and business impact (conversion rates).
Avoid making it too tool-specific; emphasize principles over platforms. Stress that this role isn’t just about debugging but shaping a performance-first culture.
UI Performance Scientist – Role Charter
1. Mission Statement
To systematically elevate user experience and business outcomes by establishing a culture of performance-driven design and development through rigorous instrumentation, actionable research, and scalable cross-functional enablement. This role transforms UI performance from a reactive troubleshooting task into a proactive, measurable, and owned component of product excellence.
2. Core Pillars & Responsibilities
Pillar A: Instrumentation & Observability (The "How We See")
- Design & Govern Performance Telemetry: Define and maintain the core set of Core Web Vitals (LCP, FID, CLS) and custom, business-critical metrics. Establish standards for instrumentation (e.g., RUM setup, API timing, user interaction marking).
- Build the Performance Data Backbone: Own the primary dashboards (e.g., in Datadog, Grafana, Looker) that provide real-time and historical visibility into performance health across devices, networks, geographies, and user segments.
- Correlation & Context: Enrich performance data with business context (e.g., page type, user cohort, A/B test variant, release version) to enable meaningful root cause analysis.
- Toolchain Stewardship: Evaluate, recommend, and manage tools for synthetic monitoring (Lighthouse CI, SpeedCurve), field data (RUM), and lab testing (WebPageTest, Chrome DevTools Protocol).
Pillar B: Performance Research & Analysis (The "Why & What If")
- Impact Quantification: Conduct correlation and causation studies linking performance metrics to key business KPIs (conversion rate,session length, support tickets, NPS). Answer: "What is the ROI of a 100ms improvement?"
- Opportunity Identification: Proactively analyze data to identify high-impact performance debt (e.g., "Top 10 slowest product pages for mobile users on 3G").
- A/B Test Design & Analysis: Partner with Product and Data Science to design experiments where performance is the independent variable or a key covariate. Analyze results to prove/disprove performance hypotheses.
- Technology & Pattern Assessment: Research the performance impact of new frameworks, libraries, design patterns (e.g., hydration strategies, image formats), and third-party scripts. Publish "state of our performance" reports.
Pillar C: Cross-Team Enablement & Culture (The "How We Improve")
- Performance-by-Design Advocacy: Embed with product/design teams during discovery and design phases to influence architecture and UX decisions with performance implications (e.g., "This infinite scroll pattern may harm INP on low-end devices").
- Tiered Knowledge Sharing:
- Tier 1 (Self-Serve): Maintain a central "Performance Hub" (Confluence/Notion) with playbooks, best practices, diagnostic guides, and metric definitions.
- Tier 2 (Collaborative): Lead regular "Performance Clinics" and office hours. Conduct targeted workshops for engineering teams (e.g., "Optimizing React Hydration").
- Tier 3 (Embedded): Act as a dedicated consultant for high-priority initiatives or crisis troubleshooting.
- Process Integration: Define and socialize Performance SLAs/SLOs for new features. Advocate for performance criteria in the Definition of Done and launch checklists.
- Executive Translation: Regularly communicate performance health, risks, and opportunities in business terms to leadership and product management.
3. Success Metrics (How This Role is Measured)
- Infrastructure Health: Improvement in primary [Core Web Vitals] percentiles (P75/P90) for key user journeys.
- Adoption & Impact: # of teams actively using primary dashboards; # of performance requirements in PRDs/launch docs; reduction in performance-related bug reports.
- Business Value: Quantified correlation between performance improvements and target KPIs (e.g., "Faster checkout flow led to X% increase in conversion").
- Knowledge & Culture: Attendance/feedback from workshops; citations of the Performance Hub in RFCs/design docs; emergence of "performance champions" in product teams.
- Proactive Influence: % of major initiatives with performance consultation in the design phase.
4. Collaboration Model & Stakeholders
- Primary Partners: Engineering (Frontend, Platform, Mobile), Product Management, UX/Design, Data Science.
- Key Stakeholders: Engineering Leadership, Product Leadership, Business Analytics, Customer Support.
- Operating Principle: "You build it, you own it" (with support). The UI Performance Scientist provides the tools, knowledge, and consultation. The product engineering teams are empowered and accountable for the performance of their features.
5. Tools & Artefacts (Non-Exhaustive)
- Dashboards: Datadog/Google Analytics 4/Amplitude for RUM; SpeedCurve/Lighthouse CI for synthetic.
- Analysis: Jupyter Notebooks/R for deep-dive correlation analysis; Chrome DevTools, WebPageTest for lab debugging.
- Communication: Regular "Performance Pulse" newsletters; executive slide decks; detailed post-mortems for regressions.
- Governance: Performance scorecards per product area; RFC review for high-impact changes.
6. Expectations & Profile
- Mindset: Hybrid of Data Scientist (rigorous analysis, statistics), UX Researcher (user-centricity, storytelling), and Developer Advocate (teaching, simplifying complexity).
- Skills: Fluency in web performance APIs, JavaScript, and browser internals. Strong statistical knowledge. Exceptional communication—able to explain INP to a product manager and runtime performance to a React engineer.
- Output: Not just reports and tickets, but clear recommendations, validated designs, and educated teams. The ultimate goal is to make the role obsolete by making every team a performance team.
Charter Approval:
Role Sponsor: Head of Engineering / VP of Product
Key Stakeholder Sign-off: All Product & Engineering Directors
Review Cycle: Bi-annually"We don't measure performance to find fault. We measure it to find opportunity."
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.