Reinventing How We Work: Building a Scalable Framework for Managing Initiatives
In fast-paced, high-impact organizations, ideas are never in short supply. But turning those ideas into measurable, repeatable outcomes? That’s where most teams struggle.
As part of our journey within the Compensation, Equity & Mobility (CEM) function, we were facing an increasingly common challenge: managing an ever-growing pipeline of initiatives without a shared operating rhythm.
So I created a solution we now call Way of Working (WoW) — a structured methodology that standardizes how we plan, build, launch, and scale new projects. It’s a flexible, repeatable, and human-centered approach to initiative management. More than just a project framework, WoW is a mindset — and it’s fundamentally changed how our team collaborates, prioritizes, and delivers impact.
🔍 Why We Built the “Way of Working”
Our team was experiencing growing pains. We had brilliant people and bold ideas, but our process was reactive and fragmented:
- Different teams were using different intake methods
- Roles and responsibilities weren’t always clear
- Workday enhancements were getting delayed due to unclear requirements
- Documentation lived in silos
- We lacked a consistent way to prioritize and track initiatives
The stakes were high — we supported global HR processes with real impact on people’s experiences. We needed a scalable operating model that would bring clarity, alignment, and momentum to every initiative.
🧠 The WoW Framework: Turning Ideas into Impact
The Way of Working framework is built around four key phases and twelve structured steps. Every initiative — big or small — follows this journey from intake to closure.
📍 Phase 1: Understand & Prioritize
This phase focuses on creating alignment from the very beginning. We don’t rush into execution — we invest time in deeply understanding the “why” behind the work.
1. Intake & Initial Alignment
Each new initiative begins with a standardized intake form. This captures context, objectives, pain points, stakeholders, and desired outcomes.
2. Feasibility Assessment
We evaluate whether the initiative is technically feasible, given the timeline, dependencies, and available resources.
3. Prioritization & Sequencing
Using a prioritization matrix, we evaluate initiatives based on impact, effort, and urgency. This helps us build a transparent roadmap.
4. Planning
We define scope, risks, timelines, and milestones. A kickoff plan is developed and roles are clarified using a RACI model.
⚙️ Phase 2: Design & Build
This is where co-creation takes center stage. We believe that the best solutions are built collaboratively — and WoW provides the structure to make that happen.
5. Requirements Definition
We host deep-dive sessions to document functional and technical requirements. Pain points are mapped directly to proposed solutions.
6. Development & Configuration
Whether we’re configuring Workday or building a new digital solution, this phase involves iterative development with feedback loops.
7. Testing & Defect Management
Structured testing ensures quality. We execute user acceptance testing (UAT), document defects, and refine before launch.
📣 Phase 3: Enablement & Execution
Too many projects fail during the last mile. This phase ensures that users are informed, trained, and ready before anything goes live.
8. Communication & Training Strategy
We define who needs to know what — and how. Tailored communication and enablement plans ensure smooth change management.
9. Documentation
All solutions come with user guides, admin SOPs, and process flows. Everything is housed in a shared repository for easy access.
Get Jason Gonzalez Jimenez’s stories in your inbox
Join Medium for free to get updates from this writer.
10. Go Live
We follow a Go/No-Go checklist to ensure readiness. This includes a rollback plan, success criteria, and final alignment from all stakeholders.
🚀 Phase 4: Support & Learn
We don’t just launch and walk away. WoW includes a robust post-go-live strategy focused on adoption and continuous improvement.
11. Hypercare
We provide enhanced support post-launch. That could mean daily check-ins, ticket triage, or training refreshers.
12. Closure & Recognition
We conduct retrospectives, capture lessons learned, and recognize contributors. Every project is formally closed and archived.
📊 Templates, Tools, and Playbooks
We didn’t just design the framework — we equipped the team to use it.
To make WoW actionable, I created a set of tools that every project team can use:
- 📁 Documentation Hub (Excel): Centralized tracker for all initiatives, including metadata, phase status, metrics, owners, and timelines
- 📘 WoW Playbook (PowerPoint): Step-by-step breakdown of each phase with responsibilities, inputs/outputs, and best practices
- 📄 Intake Form: Structured form that feeds directly into resource planning and prioritization
- ✅ Go Live Checklist: Covers technical readiness, communication, risk mitigation, and user support
Every element of the framework is designed to be modular, so teams can scale it up for enterprise-wide programs or scale it down for quick wins.
📍 Case Study: Fixing Global Processes in Workday
One of our early applications of WoW was optimizing the Global People Enterprise Services process in Workday — a process critical to moving talent across countries.
🔎 The Problem:
- Roles and responsibilities were unclear
- Manual documentation created bottlenecks
- The process was inconsistent across regions
🔧 What We Did with WoW:
- Conducted a stakeholder impact analysis
- Defined clear Workday configuration requirements
- Co-created solution options and signed off the SFR
- Tested, trained, and deployed the new workflow with hypercare support
The result? Faster processing, fewer errors, and a better experience for HR teams and relocating employees.
🏆 Outcomes and Adoption
Since launching WoW:
- Over 70 initiatives have been tracked and delivered using the framework
- Our Go Live success rate improved by over 50%
- Stakeholder satisfaction increased (measured via follow-up surveys)
- We’ve built a culture of co-creation, transparency, and accountability
Most importantly, the team owns it. This isn’t “Jason’s framework” — it’s how we work.
