Nick Anthony
Siemens US E&A — CX Strategy & Operations

First 90 Days

A starting point for conversation. Grounded in the Siemens E&A US CX Strategy, the LTTS Support Requirements, and CXM@Siemens standards — with honest acknowledgment of what I don't yet know.

The Approach

Three phases, six workstreams

These tracks run concurrently across all three phases. They're connected but not blocking — each can move forward even when another is still in discovery mode.

Days 1–30
Focus

Listen, learn, and understand what's actually true on the ground before forming strong opinions.

Output

A situation assessment — what I've learned, what I'm still figuring out, and where I think the early opportunities are.

Days 31–60
Focus

Start building the operating structures — governance, measurement, and process design — based on what I've learned in Phase 1.

Output

LTTS working cadence in place. VoC process designed. KM platform direction decided. First journey map draft in TheyDo.

Days 61–90
Focus

Deliver the first things people can see and use — proof that the function is operating and producing outcomes, not just plans.

Output

Support baseline shared with leadership. Customer 360 prototype in stakeholder hands. First journey map presented. Early wins documented.

1. Stakeholder & Org Intelligence2. Support Operations3. Customer Portal4. Journey Mapping & VoC5. Customer 360 & Data6. AI & Knowledge Management
The Plan

90-day milestone summary

TimingMilestoneSuccess signal
Day 1Meet Seymour: working style, decision authority, 90-day success definitionPriorities, budget, headcount, and expectations documented
Week 1Meet key stakeholders: Brian Dula, Brandon, Matan Marom, Accenture lead, LTTS lead, Salesforce adminCalendar of all stakeholder meetings set
Day 14Written stakeholder and influence mapDocument shared with Seymour
Day 21Mission definition alignment: 'intelligent, seamless, value-driven' defined in writingWorking definitions captured for ongoing reference
Day 30SieOps data quality audit completeGap report: fields populated, missing data identified, remediation plan started
Day 30Support case data pulled and analyzed: volume, type, resolution time by product lineSupport baseline established
Day 30Situation assessment shared with SeymourWritten assessment: data, risks, gaps, and Phase 2 priorities
Day 30TheyDo access provisioned; Persona Library reviewedTheyDo provisioned; first workshop scheduled
Day 45CSAT surveys activated at case closure in SieOpsFirst CSAT data begins flowing
Day 45LTTS governance model designed: shared KPI dashboard, escalation protocol, weekly sync cadenceDraft governance model shared with Seymour
Day 45Workshop 1 complete: Spare Parts journey with frontline staffFirst-draft Spare Parts journey map in TheyDo
Day 45VoC closed-loop process designed; NPS strategy draftedDesign doc shared for input
Day 60LTTS governance model live; first weekly sync completedLTTS governance cadence operating
Day 60KM platform decision made; content governance process documentedPlatform decision made and documented
Day 60Business value metrics defined and baselines established with BrandonMetrics baseline ready for Q3 stakeholder report
Day 60Workshop 2 complete: CarePlan journeyTwo draft journey maps in TheyDo
Day 60Customer 360 dashboard data model designed and approved by SeymourDesign doc complete
Day 60Data cleaning and standardization plan initiated with Salesforce adminPlan logged in Jira as user stories
Day 75Spare Parts journey map internally reviewed and refinedRefined map in TheyDo
Day 75MVP portal customer feedback structured and collectedMVP customer feedback summary complete
Day 90Spare Parts journey map presented to cross-functional stakeholdersStakeholders have seen the map and shared reactions
Day 90Support baseline report delivered to leadership: actual case numbers, resolution times, CSATFirst support performance picture — real numbers, honestly told
Day 90Customer 360 prototype piloted with 2+ stakeholdersFeedback collected; improvement backlog started
Day 90AI self-support assessment complete; 1–2 pilot opportunities identifiedRoadmap document complete
Day 90Situation report 2 to Seymour: what was learned, what changed, FY26 Q3/Q4 planRevised plan grounded in what I've actually learned
Working Draft — v1.0 · Prepared for Seymour, May 2026. This is a starting point for a conversation, not a final plan. I've called out open questions throughout because those are the things I'd want to learn from you and the team before moving forward.

Nick Anthony · nbanthony1@gmail.com · July 2026