ENABLEMENT & ORGANIZATIONAL EFFECTIVENESS LEADER
STRUCTURE
IS
Power.
I develop people and build the systems teams need to perform through complexity and change.
See the Work → VIEW RÉSUMÉ
I develop people and build the systems teams need to perform through complexity and change.
See the Work → VIEW RÉSUMÉ
Serious about the work. Equally serious about the playlist. I do not play when it comes to snacks. This is your briefing before the resume.
Ambiguity is where I do my clearest thinking.
Undefined environments. High-stakes problems. Systems that don't exist yet. That's not a liability. That's exactly where I work. Give me a real problem and I'll show you what happens.
80s and 90s. Non-negotiable.
Queen, Stevie Nicks, Bon Jovi, Diana Ross, New Edition, Radiohead. I have seen most of them live. My solo office performances are equally committed. Reality has yet to give them the recognition they deserve.
One velvet loaf. One chaos agent.
My Persian cat is my emotional support system. My Boston Terrier is my chaotic little manager. Together they maintain a full-time supervision schedule and extremely strong opinions about my work hours.
True crime. Always running.
It plays while I build process documentation, design workflows, and map escalation paths. These are not unrelated activities. Pattern recognition is pattern recognition. The genre simply has better examples.
High expectations. Real support.
I come from an Indigenous background that shaped how I show up for people and why community is non-negotiable. I'm the matriarch of a small, close family I carry with intention. I lead the same way I parent. Both things can coexist.
A lifelong devotion. Zero regrets.
Little Debbie has been a constant since childhood and I see no reason to change course now. Some things require no justification. This is one of them.
"You can work hard, care deeply, and still keep your personality intact. I believe in leading by example, not perfection."
Sasha Ortiz · on the work
Meet Sir Hearts, Senior Advisor. He reviews all my work, has never once said good job, and is perpetually unimpressed.
I turn ambiguity into agility.
Nobody asks for the system. They ask for a checklist, a framework, or a training session. I deliver the ask, then look underneath it: What could keep this from working? What will managers need? What can people actually use and repeat?
When the work points to something bigger, I say so. I make the recommendation, align on what comes next, and build it with the people who will carry it forward.
That has been the pattern for ten years.
Lean Six Sigma Black Belt. People leader. Builder of QA governance frameworks, onboarding systems, enablement curricula, and knowledge infrastructure across enterprise environments. My work spans L&D, quality, manager capability, operational enablement, and cross-functional program leadership.
Built from the ground up. Standardized across states, roles, and workflows. Not designed around the person who built it.
Scorecards. Calibration. Coaching models. Escalation logic. Designed for real improvement, not compliance theater.
High-stakes programs across ops, accounting, product, and executive leadership. Accountability built in, not assumed.
Governance models. Taxonomy. Audit cycles. Platform migrations. Built for teams to actually rely on.
Translating ambiguity into executable workflows with clear ownership. Holds up when conditions aren't ideal.
Programming built around how work actually feels day to day. Experiences that outlast the initiative they were built for.
When people feel trusted, supported, and valued, they perform at their best. That is not a philosophy. That is the operating model. Accountability and empathy are not opposites. They coexist in every team I build, every standard I set, and every conversation I have with someone who is trying to grow.
I have led teams through acquisitions, restructures, leadership transitions, and the kind of uncertainty that makes most people go quiet. My job in those moments is to be the steady point: clarity when everything feels unclear and consistency when nothing else is.
Trust over compliance.
A title can require compliance. It cannot create commitment.
I lead with clear expectations, real autonomy, and advocacy. My goal is to develop confident, capable people who know how to make good decisions without waiting for permission at every turn.
Trust does not replace accountability. It makes honest accountability possible.
What it actually looks like to develop someone.
One of the people I led had been passed over for leadership more than once. He knew something was getting in the way, but he did not yet have a clear development path.
I gave him direct, specific feedback. Then I built a path for him to practice.
His development became a leadership apprenticeship: KPI ownership, weekly leadership updates, team huddles, employee-support conversations, operational meetings, scenario-based coaching, and increasing responsibility as he was ready for it.
He became a team lead and eventually succeeded me in leading the team. The routines and systems we built together continued after I moved on from the team.
That is what development as legacy looks like.
Mentorship beyond the org chart.
I keep investing in people even after they stop reporting to me.
One former team member was figuring out her next move. I helped her strengthen her résumé, portfolio, professional brand, and career direction.
When she was initially passed over for a contract opportunity, I asked the hiring manager for specific feedback and shared why I believed she was ready. When the opportunity reopened, she got it.
She did the work. I made sure the door stayed open long enough for her to walk through it.
Culture by commitment, not calendar.
I have helped lead employee culture and engagement efforts since 2016, including through organizational transitions and changing company structures. Not because it was required. Because I believe culture is infrastructure, and infrastructure does not build itself.
Over the past decade, I have designed engagement programs, recognition initiatives, and community partnerships with the American Red Cross and United Way that reached hundreds of employees across departments and locations.
People perform best when expectations are clear, support is real, and their manager is willing to be honest about both the gap and the potential.
“The most meaningful feedback I have ever received has nothing to do with systems or projects or metrics. It is that I helped someone see potential in themselves they did not know was there.”
Sasha Ortiz · Leadership PhilosophyI start with what is needed now. Then I make the hidden gap visible and align the right people around what comes next.
I look beyond the deliverable to the conditions around it: clear expectations, usable tools, ownership, manager follow-through, and whether the system can hold without me.
The goal isn't to build more. It's to make the work clearer, easier to repeat, and harder to break.
The work is grounded in how things function under pressure, not how they look on a slide.
See the Case Study →
"People shouldn't have to guess their way through their work."
They asked for a checklist. I delivered it. Then we built what made it work.
Enablement Strategy · Curriculum Architecture · Manager Capability · Performance Readiness
Organization: Multi-business-unit enterprise
Audience: Customer Success professionals and managers
Structure: 36 fully developed learning and certification modules across four business units
I led the end-to-end design and development, coaching two team members through initial product workstreams before expanding and integrating their contributions into the complete 36-module system.
I owned the overall strategy, architecture, core curriculum, field-application model, manager-readiness system, final content development, standardization, and integration.
All 36 modules were fully developed to an Articulate-ready level, including on-screen content, narration or facilitator scripts, learning objectives, build guidance, interactions, knowledge checks, assessment questions, answer feedback, and supporting resources.
The organization had Account Executives serving in a post-sale Customer Success Manager role with no formal enablement infrastructure in place. The initial request was a 30-minute training session to align on role expectations.
When I began discovery, it became clear that the performance standards, role expectations, and readiness criteria were still being developed. The challenge was not creating the content. It was defining the standards the content was supposed to teach.
Defined what the Customer Success Manager role required, what excellence looked like, and what was expected at each stage. Built the foundational learning experience that every other layer connected to.
Developed product-readiness pathways so Customer Success professionals could demonstrate working knowledge rather than just completing a module. Includes knowledge checks, scenario assessments, and certification-based validation.
Created field-shadowing resources and scenario-based tools to connect what was learned to what is actually required in a customer conversation. Designed for use at the point of performance, not just before it.
Built the layer that determines whether learning actually transfers. A four-level readiness framework, weekly manager check-ins, a universal readiness checklist, a 30-day review structure, and behavior-based manager sign-off.
“Course completion does not equal readiness. Readiness must be demonstrated through observable behavior and validated by the manager.”
Eight instructor-led sessions. Ninety minutes each. Approximately 200 Customer Success professionals and managers across four business units. I personally designed and facilitated each session.
Managers attended alongside their teams. I recognized that attendance alone would not create sustained reinforcement, so I built the manager-readiness system to carry expectations beyond the classroom.
Eight instructor-led sessions, ninety minutes each, approximately 200 professionals and managers across four business units
36 fully developed learning and certification modules
Core role curriculum
Product-readiness pathways
Field-application resources
Manager-readiness system
Knowledge checks and final assessments
Behavior-based readiness and manager sign-off tools
Complete, approved, Articulate-ready content transferred to the instructional designer for production
The broader curriculum is not yet live while the final delivery model, including eLearning, instructor-led, and blended options, is being confirmed
Full participation in end-of-session knowledge checks across all eight sessions
Active participation in engagement prompts
Substantial verbal feedback during the live sessions
Long-term performance impact and sustained field application
The curriculum was completed in a format another instructional designer could move directly into production and adapt once the final delivery approach was approved. The manager tools, readiness criteria, rollout structure, and production documentation were built so the program could move forward without the content being recreated from scratch.
This case study has been anonymized and generalized to protect confidential and proprietary information. Names, terminology, and selected details have been modified or aggregated while preserving the scope of the work, leadership approach, and design methodology.
A Competency-Based QA Governance Framework: Built and Rebuilt Through Three Distinct Iterations
Over the course of my work at Cox, I built and rebuilt the QA framework through three distinct iterations, refining the structure as the operation evolved.
Built from the ground up: scorecards, calibration cadence, coaching models, dispute workflows, and governance documentation. Consistently exceeded the 90% department goal across 65+ agents and 260+ monthly evaluations.
Three pieces on what I have learned about enablement, quality, and leadership after a decade of building things that actually work.
Nobody Asked for an Ecosystem.
Every project I have taken on starts the same way.
Someone needs a checklist.
Cool. I can do a checklist.
Except when I actually look at what is going on, it was never really about the checklist. That is just what you ask for when you do not have time to diagnose what is actually broken. And what is actually broken is always something nobody wrote down, nobody owns, and everyone has been quietly working around for longer than they want to admit.
I find it anyway.
Not because I am trying to create more work for myself. Because I genuinely cannot walk past a gap. It is a blessing and a curse and my calendar reflects both.
What starts as a simple ask becomes a curriculum. A framework becomes a governance model. “Can you just put together a quick training” becomes a nine-phase onboarding architecture that gets presented to the COO.
I do not overscope work. I scope it correctly the first time.
The difference is that I am actually looking at what is broken rather than just executing what was requested. If you have ever handed someone a simple ask and gotten back something that solved three problems you did not know you had. You already know what working with me looks like.
QA Is Not the Problem.
Bad QA scores do not mean you have a QA problem.
They mean you have a training problem. A coaching problem. A documentation problem. An expectations problem. A leadership visibility problem. Possibly all five at once and nobody has connected the dots yet.
I have seen QA used as a gotcha tool. A paper trail. A checkbox that gets filed and forgotten. Evaluations completed not because anyone intends to do anything with the data, but because someone somewhere decided the number needed to exist.
That is not quality assurance. That is compliance theater with a scorecard attached.
Here is what QA is actually supposed to do: tell you the truth. It tells you whether your training is landing. Whether your coaching is working. Whether your team has what they need to succeed. Whether the expectations you think you communicated were actually understood. Whether the gap is a skill issue, a knowledge issue, a process issue, or something leadership created and the frontline is absorbing.
When I built QA frameworks, the score was never the point. The score was the signal. What you do with it is the work.
If your QA program is producing data and nothing is changing, the program is not the problem. The culture around accountability is the problem. And that one goes all the way to the top.
Fix the system. Coach the person. Lead with the data. In that order.
QA done right does not feel punitive. It feels like someone finally gave the team a mirror and said: here is where you are, here is where we are going, and here is what support looks like on the way there.
That is the version worth building.
People Don’t Underperform. Systems Do.
I have inherited teams that were holding themselves together through sheer loyalty to each other.
Not to the company. Not to leadership. To each other. Because somewhere along the way, leadership had checked out. One-on-ones got cancelled. Meetings became optional. Real work quietly shifted to whoever would absorb it. And the team normalized it because they had no other choice.
When I stepped in, I never did anything extraordinary. I just did the job.
I kept the one-on-ones. I learned names. Kids names. Dogs names. The small details people share when they finally feel safe enough to share them. I looked at whoever had been carrying too much and coached them back to what their role was actually supposed to look like.
Every single time, someone on that team eventually said some version of the same thing: that I had done more for them in a short time than they had experienced in years.
That is not a compliment to me. That is an indictment of what happens when people are treated like a function instead of a priority.
Here is what I know after years of watching teams succeed and watching them quietly fall apart:
People do not underperform because they are lazy. They underperform because expectations were never clear. Because their questions went unanswered. Because they asked for help once, felt invisible, and stopped asking. Because the system around them was broken and they were absorbing the cost of it.
Cancelling the team huddle does not fix your metrics. It tells your team that their time together, their morale, and their connection to each other are expendable. And people remember that long after the quarter ends.
You cannot metric your way out of a culture problem. You cannot work people harder through a system failure. And you cannot lead from a distance and wonder why nobody is following.
My team spends 40+ hours a week with me. That is 40 hours they could have spent with their families. So if someone reports to me, I am going to make sure they do not feel like that time was wasted. That the time they sacrificed meant something.
Give me the room no one wanted.I'll show you what I do with it.
Nobody asked me to build an ecosystem. They asked for a checklist. Below is what happens when I dig in and find what is actually needed.
AE Enablement Infrastructure
Audited a client-facing role and found it was actually ten undocumented jobs running on tribal knowledge and informal shadowing. Built a complete enablement ecosystem from scratch: behavioral training, systems training, product-specific guides, and a 9-phase curriculum architecture across four business units. Being presented to C-suite leadership.
Hiring Manager Onboarding Toolkit
Brought in to build a simple onboarding checklist. Found no cross-functional ownership model, process contradictions, and content written for the wrong audience. Built a full toolkit: 9-phase checklist, complete FAQ, and ownership labels at every step so no handoff is ever ambiguous. Identified and flagged a live process contradiction before it reached hiring managers.