Vation Ventures establishing CM strategy, stakeholder map, and communication governance.
Overall project progress
Phase: Discovery & Initial Evaluation · Pilot go-live target: Oct 2026
What this engagement covers
Vation Ventures role
Change management support — not technical implementation. Vation owns adoption strategy, stakeholder readiness, communication governance, department champion activation, and reinforcement. Nexus owns the technical work.
Why it matters
14 staff surveyed flagged naming inconsistency, data loss fear, and tool anxiety as top concerns. Poor prior rollouts (Teams, phones) created a trust deficit. This engagement addresses the people side of migration to prevent repeat of that pattern.
Nexus project timeline at a glance
Phase 1 (Pilot): Jan – Oct 2026 · Phase 2 (full file server): Nov 2026+
Top staff concerns from survey (14 respondents)
Informs CM priorities
Current pain points
Concerns about migration to cloud
Key risks requiring leadership attention
High · Change fatigue
Teams rollout shadow
Prior poor rollouts created a trust gap. This migration requires explicit acknowledgment that the approach is different — not assumed goodwill from staff.
High · Technical
Excel link-breaking risk
Finance and Accounting use heavy S-drive Excel linking. These files cannot migrate until Nexus validates the link-breaking remediation plan.
Medium · Timing
CIS and SharePoint overlap
CIS implementation and SharePoint go-live both target October 2026. Customer Relations and Finance face simultaneous system changes — monitor change fatigue.
Upcoming milestones
PWSD SharePoint Migration — CM Dashboard
CM week
1
Planning phase
Nexus phase
Discovery
Cleanup deadline: May 4
Staff surveyed
14
Named · 8 departments
Open risks
10
5 high · 4 med · 1 low
CM deliverables
0
of 15 complete
Project phases
Nexus Phase 1 (Pilot) · Jan – Oct 2026 · Vation CM support: Apr – Aug
✓
Project Planning
Jan – Feb
→
Discovery & Initial Evaluation
Feb – Apr
3
Analysis & Understanding
Apr – Jul (current state)
4
Planning & Requirements
Jul – Aug (future state)
5
Infra Design & Dev
Aug – Sep
6
Migration & Validation
Sep – Oct
7
Cut Over & Go Live
Oct 2026
Vation Ventures CM engagement: Apr – Aug 2026 · Covers Phases 2–5 (Discovery through Migration prep). Nexus continues Phase 6–7 (Migration & Go-Live) after Vation handoff in August.
Vation Ventures role: CM support to Nexus — not project management. Nexus leads technical implementation and project coordination. Vation Ventures owns the people side: adoption approach, stakeholder readiness, communication governance, champion activation, and reinforcement.
Top survey pain points (14 respondents)
Department adoption readiness
This week
Week 1 · Planning
Deliverables
Engagement progress
1
of 16 wks
Week 1 of 16
CM phase: Discovery & Initial Evaluation
Nexus: Discovery & Initial Evaluation
Deliverable status
CM adoption KPIs — at a glance
Formal deliverables
9 deliverables · update status as each advances
CM adoption KPIs
From PWSD Technology Roadmap · tracked throughout engagement
Scope of services — activity log
Track what's been delivered against the engagement scope
Activity
Scope area
Week
Status
CM Week-by-Week Tracker
Parker Water & Sanitation District · Vation Ventures
CM week-by-week tracker
16 weeks · Apr 13 – Aug 2026 · click tasks to mark complete
Click any task to mark it complete. Progress saves automatically in your browser. Use the week selector, numbered dots, or Previous/Next buttons to navigate.
Tag key:Strategy — stakeholder mapping, CM document work, adoption planningComms — drafting or sending communications to PWSD staffRelationship — check-ins, briefings, and stakeholder engagementTracking — logging observations, risks, adoption signalsNexus coordination — syncing with the technical implementation teamTraining — training design, job aids, education support
0%
Week focus
Project Timeline
Nexus project timeline
Jan 2026 – Oct 2026 (source: Nexus Schedule Update 1)
Phase details — Nexus Phase 1 (Pilot)
Source: Kickoff deck slide 13 · Schedule Update 1
Project PlanningJan – Feb 2026Complete ✓
Pre-project planning and alignment. Teams defined: PWSD Project Team, PWSD Technical Team, Stakeholder Groups. Nexus access and account setup.
Migration Planning & Alignment · Information Architecture · SharePoint Development · Finalize Inventory Mapping
Migration & ValidationSep – Oct 2026Upcoming
Stakeholder Training — migration related · Migration Support (Nexus) · Validation and Progress Monitoring (PWSD Tech Team) · Stakeholder Training — content owners related
Cut Over & Go LiveOctober 2026Upcoming
All Company Training (all employees) · SharePoint Go Live Checklist (Nexus) · File Server Go Live Checklist — decommission (PWSD Tech Team) · Post Implementation Support (Nexus) · Decision on future phase migration plan and order
Full file server migration across all remaining business units. Each unit follows the same cycle: Planning & Requirements → Infrastructure Design & Dev → Migration & Validation → Cut Over & Go Live. Scope and sequencing determined at end of Phase 1.
Vation CM alignment to Nexus phases
Vation CM activities mapped to Nexus phases
CM Wks 1–3 (Apr) ↔ Discovery & Initial Evaluation Attend Apr 14 kickoff, CM stakeholder conversations, build stakeholder map, draft CM strategy document, identify champion candidates
CM Wks 4–10 (May–Jun) ↔ Analysis & Understanding Attend analysis sessions, build comms package, activate champions, finalize training plan and job aids, department change summaries
CM Wks 11–14 (Jul) ↔ Planning & Requirements Attend future state sessions, deliver executive readiness session, staff update communications, support training design
CM Wks 15–16 (Aug) ↔ Infra Design & Dev begins Transition & handoff — finalize sustainment plan, document champion model, transfer all CM artifacts to PWSD TS team · Vation engagement closes Aug 2026
Nexus continues independently through Migration & Validation → Cut Over & Go Live (Sep–Oct). PWSD TS team and champions carry adoption support forward after Vation disengages.
Key dependencies
Training cannot be scheduled without knowing migration sequence from Nexus
Communications cannot go out without knowing what has been deployed
Vation attends Nexus analysis sessions to inform adoption approach by dept
Vation and PWSD TS team coordinate weekly on status and priorities
Adoption data feeds from PWSD TS team to Vation for Phase 3 tracking
Survey Results — 14 Respondents
Survey respondents
Mar 30 – Apr 7, 2026 · Named PWSD staff · Click any card for detail
These are real PWSD staff responses — names, verbatim quotes, and concern patterns. Each card shows ADKAR baseline and CM risk level. Use this as the primary stakeholder readiness reference.
Q1 — Current file server challenges
Multi-select · 14 respondents
Q3 — Satisfaction with current structure
Q9 — What would improve document management?
Q10 — Biggest worries about moving to SharePoint
Impact Map & ADKAR Baseline
Stakeholder influence vs. disruption map
Survey respondents + key leaders · Click any dot
X-axis: Influence on others' adoption decisions — organizational reach, decision-making weight, peer trust. Y-axis: Personal workflow disruption from the migration — file complexity, prior rollout experience, manual workaround burden. Top-right = highest CM engagement priority. Scores are practitioner-assessed.
All 17 stakeholders shown — 14 survey respondents plus Ron Redd, Jared Mann, and Rebecca Tejada from discovery context. Click any dot for full profile. Dot size reflects pain score. Scores are practitioner-assessed.
ADKAR baseline by respondent
Based on survey responses (14 respondents) and discovery context
Name
Role
Team
Awareness
Desire
Knowledge
Ability
Reinforcement
CM priority
Department Champions
Department champion roster
Peer support model · activated Wks 4–7
Champion role: A trusted peer within each team — not a trainer or IT resource. Champions answer routine questions, explain the "why," surface concerns to Vation Ventures, and model the new behavior. They receive materials one week before wider distribution and have a direct line to Vation Ventures for escalations.
Status — Week 1: No champions formally designated. Identification happens in Wks 1–3 through CM stakeholder conversations with PWSD TS team guidance. Candidates below are based on survey signals and discovery interviews. No individual is named a champion without a direct conversation.
Activation plan
Wks 1–3 · Identify
CM stakeholder conversations confirm champion candidates. PWSD TS team guidance on who is trusted and respected by their team is the primary input — not technical skill.
Wks 4–7 · Brief & activate
Brief each champion on their role. Provide communication package, FAQ, and direct line to Vation Ventures for escalations. Champions receive materials before wider distribution.
Wks 8–16 · Sustain
Champions feed the resistance and question log. Included in lessons-learned at close of engagement. Internal ownership model established for post-engagement sustainment.
Governance: Vation Ventures drafts and governs messaging. PWSD TS team approves before any communication is sent. PWSD Communications (two-person team) distributes via internal channels. Field team communications receive a shorter-format version — different from office staff. No announcement goes out without alignment on timing relative to Nexus project activity.
Risk Register
Risk register
10 open
Level
Risk
Area
Mitigation
Status
Weekly Reports
Parker Water & Sanitation District · Vation Ventures
Weekly reports
Running record · formal deliverable to PWSD leadership
This tab contains two things: the weekly activity log (running internal record of what happened each week) and status reports (formal weekly updates sent to PWSD leadership). Status reports are added here by Vation Ventures each week after they are sent. Use Print / Export to share any entry as a PDF.
Activity log
Most recent first
Saved status reports
0 saved
Status reports are generated by Vation Ventures each week alongside the activity log.
Field Logs
Parker Water & Sanitation District · Vation Ventures