Summary

0. Properties - Meeting Date: Unknown - Meeting Type: 1x1 - Note Type: Summary - Attendees: Scott Warner; Vera Rodehutscord

1. Meeting Summary We walked through the OKR-KPI tracking workbook I drafted, focusing on how to make it a reliable source of truth and simple enough for data owners to use without breaking anything. We agreed the template that includes alignment to the RISE strategy is our baseline going forward. The key tabs are: - Dictionary tabs to define items and IDs (KPI Dictionary and OKR Dictionary). - Monthly Updates as the single working input sheet. - A basic dashboard concept to be replaced later by Power BI or a similar tool once we stabilize the data model.

We aligned on structure and governance: - Rename the Registry to OKR Dictionary and keep it as a non-changing reference. Move any fields that require ongoing updates out of the dictionary and into Monthly Updates. - Keep the parent-child link model via Parent ID so we can roll up and trace contributions from department goals and OKRs into corporate goals and corporate KPIs. - Retain the code-based Item IDs by level (e.g., CG, CKPI, DG, OBJ, KR), but recognize numbering across the year will not remain perfectly chronological. We will rely on filters and IDs rather than sequential order. I will explore minor structural changes or formulas to reduce risk of numbering errors. - Add Owner (ELT owner) and a separate Data Owner. I set up VLOOKUPs so Data Owner can auto-populate in Monthly Updates based on entries in the dictionaries. - For metrics, keep Actual as the raw monthly value; use Measurement Type to indicate percent, dollar, manual, etc.; and Target Text for non-numeric targets. Is Active flags items by quarter as needed. - Progress Score will be 0 to 1 (e.g., 0.7 = 70) to avoid percentage formatting issues. Primarily for key results. We may auto-calc when numeric, but we will likely hide calculations to avoid user math. - Red/Yellow/Green will apply to KPIs only for now. We will not apply RYG to OKRs this cycle to avoid complexity.

On process, we will not share the full master file broadly. Vera will publish a controlled working file in the Organizational Strategy folder for data entry and then copy values back to the master. We will color-code input fields for clarity. Vera will conduct monthly check-ins with KR owners and fill progress during those meetings.

Separate operational items: - Logistics safety matter: Diana confirmed she is safe and plans to return. If she does not show, we will initiate a wellness check. I coordinated with HR, Steve, Nathan, and Tamara on response. - ELT compliance: Robert has not entered his KPI data or this month's ELT Health Index. I will address it directly with him first and escalate to Matt Howard if needed. - RISE OKRs: Vera will review with Clint tomorrow, then route to Matt, and target Mooncamp entry by mid-March per HQ's alignment timeline. - Travel: We will align on IMM flights before Friday to avoid last-minute issues with Tosundra.

2. Attendee List - Scott Warner - Vera Rodehutscord

3. Action Items - Scott: Rename Registry to OKR Dictionary and remove any dynamic fields from the dictionaries that do not belong there. - Scott: Remove the duplicate KPI ID column that is not used; keep Parent ID as the prime linkage. - Scott: Add and finalize VLOOKUPs so Data Owner auto-populates in Monthly Updates; rename KPI Owner to Owner and keep Data Owner separate. - Scott: Add concise readme guidance in the workbook and share examples of inputs, including how to use Actual, Measurement Type, Target Text, Is Active, Progress Score, and RYG. - Scott: Explore a simple control to reduce numbering errors when adding new items; consider formula-based checks or a light script, then propose. - Scott: Color-code user input fields in Monthly Updates to guide data owners. - Scott: Work with Lars on his tools, given he is not engaging with Robert. - Scott: Speak with Robert about missing KPIs and ELT Health Index; secure completion and set clear expectations. Escalate to Matt Howard if behavior does not change. - Scott/HR: If Diana does not return as stated, initiate a wellness check in coordination with HR. - Vera: Stand up a controlled working Excel for data owners in the Organizational Strategy folder with monthly columns; restrict master file access. - Vera: Define and confirm Data Owners across KPIs and KRs where missing; communicate the process and cadence. - Vera: Conduct monthly check-ins with OKR owners and enter progress directly during those calls. - Vera: Prepare Q1 KPI numbers (Jan-Feb now, March as completed) to present at the next ELT. - Vera: Meet with Clint tomorrow on RISE OKR results and comms; route to Matt for sign-off; ensure Mooncamp updates are submitted by mid-March. - Vera: Price and propose IMM flights and run by Scott; book before Friday to avoid last-minute issues.

4. Relevant Timelines - Mid-March: HQ alignment meeting - RISE OKRs must be in Mooncamp by then. [Vera] - This week: Begin collecting Jan and Feb KPI data so Q1 is ready to show at the next ELT. [Vera] - Tomorrow: Vera to meet with Clint on RISE OKRs and route to Matt after. [Vera] - Friday: Finalize and book IMM flights. [Vera] - Tomorrow morning: If Diana does not return as stated, file wellness check. [Scott/HR] - Ongoing monthly: Vera to run check-ins with KR owners and update progress in Monthly Updates. [Vera]

5. Additional Notes - Governance: Protect the master file. Distribute a values-only working copy for monthly inputs; copy back into the master to preserve formulas and structures. - Data model: Parent-child relationships are the backbone. IDs matter more than sequence. Avoid over-optimizing numbering; filtering and linking will do the heavy lifting. - Metrics handling: - Use 0 to 1 progress to avoid formatting issues. Subjective scoring allowed for non-quantitative items; numeric items can be auto-derived and hidden. - Use RYG only for KPIs for now. Consider defining RYG for OKRs in a future cycle once the framework stabilizes. - Measurement Type and Target Text support dashboards and mixed data types. - Dashboard: Power BI or a scripted approach (Python/R via Christine) will be fine once the data is clean. The near-term priority is data integrity and ease of input. - Resourcing: Tanner is already helping with safety onboarding, which should relieve some EHS/logistics load. - Compliance and culture: ELT participation must be consistent. Address non-compliance promptly to keep cadence and credibility intact.