What I actually do
Eight ways to work together, depending on what you need. Some are fractional and ongoing. Some are scoped sprints with a clear deliverable. All of them start from the same place: you have a gap, I know how to close it.
Not sure which fits? Tell me what's going on and we'll figure it out together.
01
Fractional UX leadership
Senior UX leadership embedded in your product org, without the full-time headcount, onboarding runway, or eighteen-month performance review cycle.
This is the right fit if you're scaling faster than your design practice can keep up, if you have designers but no one setting the strategic direction, or if you're between design leaders and can't afford to let things drift for six months while you recruit.
I work alongside your team, not above it. I can own the design strategy, mentor your designers, run cross-functional alignment, or fill whatever specific gap is creating the most friction, depending on what the org actually needs.
⇒ Series A–C teams with designers but no design leadership
⇒ Orgs that need senior UX direction without a full-time hire
⇒ Teams mid-hiring-search who need continuity while they recruit
⇒ Companies scaling fast and discovering their design process hasn't kept up
WHAT THIS LOOKS LIKE
Defined engagement scope — hours per week, duration, specific outcomes
Design strategy, principles, and team operating model
Cross-functional alignment and stakeholder facilitation
Designer mentorship and craft development
Optional: hiring support, job ladder frameworks, critique structure
02
Product ops consulting
Fast product teams don't slow down because people aren't working hard enough. They slow down because the operating model hasn't kept up with the size of the org.
I design and operationalize the infrastructure that makes product teams work: discovery rituals, release rhythms, planning cadences, cross-functional alignment, and the feedback loops that tell you whether anything is actually landing. I've owned operating models for up to 100 product managers, designers, and engineers — and built the systems to run them sustainably.
I'm a Certified Scrum Product Owner (CSPO) and a Continuous Discovery Habits practitioner. If your product teams are shipping but not learning — or learning but not acting on it — that's a solvable problem, and I've solved it.
⇒ Multi-team orgs where coordination is becoming the bottleneck
⇒ Product orgs that are shipping but not improving
⇒ Teams that have adopted discovery rhetoric but no actual discovery rituals
⇒ Leadership that wants earlier, quantified signal on value and usability
WHAT THIS LOOKS LIKE
Operating model audit: what's working, what's creating drag
Discovery ritual design and implementation
Release rhythm and planning cadence redesign
Voice of Customer program buildout
Cross-functional alignment frameworks and facilitation
03
AI-powered operations
Most product teams have AI on the roadmap. Fewer have figured out how to actually embed it into how they work — the discovery rituals, the release rhythms, the cross-functional handoffs that determine whether AI features ship or stall.
This is not AI strategy at 30,000 feet. This is the ground-level work: figuring out where AI creates real leverage in your product development process, building the rituals and infrastructure to support it, and making sure it sticks after the engagement ends.
At CompanyCam, I drove AI feature acceleration from 1 beta release to 4+ launches per month in six months, not by adding headcount or buying new tools, but by fixing how the team discovered, prioritized, and shipped.
⇒ Product teams with AI on the roadmap but no operational model to support it
⇒ Orgs where AI features keep stalling before they ship
⇒ Teams that have adopted AI tools but haven't changed how they work around them
⇒ Leaders who want to move faster but aren't sure where the actual bottleneck is
WHAT THIS LOOKS LIKE
Current-state audit of your discovery and release process
AI integration opportunities mapped to your specific workflow gaps
Ritual and infrastructure design — the stuff that makes it repeatable
Implementation support: tooling setup, team onboarding, documentation
Optional: ongoing advisory retainer
04
Research program buildout
"We talk to users sometimes" is not a research program. It's a start, but it's not a system, it doesn't scale, and when the person doing the talking leaves, the knowledge leaves with them.
I build the infrastructure that turns ad-hoc user conversations into organizational knowledge: the methods, the rituals, the templates, the repositories, and the culture that makes research a decision-making tool instead of a compliance checkbox.
I've built research programs from scratch at multiple organizations, including standing up structured usability testing, information architecture frameworks, heuristic evaluation processes, and Voice of Customer programs that actually fed the roadmap.
⇒ Teams that are shipping without consistent user insight
⇒ Orgs that have a researcher but no program around them
⇒ Companies where research happens but doesn't influence decisions
⇒ Product orgs preparing to hire their first researcher and needing the foundation first
WHAT THIS LOOKS LIKE
Research method selection and protocol templates
Participant recruitment and screener frameworks
Repository structure and synthesis processes
Stakeholder integration — how research gets into the room
Team training and documentation for ongoing use
05
Design sprint facilitation
A well-run design sprint collapses months of back-and-forth into five days and leaves your team aligned on something worth building. A poorly-run one is just a very expensive meeting.
I facilitate design sprints for teams that are stuck on a hard problem, launching something new, or trying to break a cycle of alignment meetings that produce more alignment meetings.
I've run sprints inside organizations at every stage — from early-stage startups figuring out product direction to established orgs trying to move faster on a specific problem. I bring structure, I keep things moving, and I know when to go off-script.
WHAT THIS LOOKS LIKE
Pre-sprint scoping and problem framing
Full facilitation — remote or in-person
Prototype and test planning
Post-sprint synthesis and next steps documentation
06
Internal tool cleanup
Somewhere in your company, there's an internal tool that everyone uses, nobody loves, and no one has touched in eighteen months.
It worked when you built it. Then priorities shifted, the team moved on, and now it's held together with workarounds and tribal knowledge. The UX debt is real. The accessibility gaps are piling up. Every new employee asks the same question: "Wait, why does it work like this?"
I come in, audit it, prioritize the work, and fix it, on a scoped timeline, with clear deliverables, and documentation so your team can maintain it going forward. You don't need a full-time hire for this. You need a cleanup sprint.
At Hudl, this kind of work saved over 1,000 billing support hours. At WP Engine, it brought a design system back into WCAG compliance. Both started with someone saying "it's been on the backlog forever."
WHAT THIS LOOKS LIKE
Audit and prioritization — usability, accessibility, workflow gaps
Design and remediation — implementation-ready Figma assets
Documentation and handoff — so the debt doesn't creep back
Optional: ongoing advisory retainer
07
WordPress + web services
Your website should work as hard as you do. If it's slow, outdated, hard to update, or just not representing you accurately anymore — that's fixable.
I build and maintain WordPress sites using Elementor, manage hosting through WP Engine, and handle the ongoing webmaster work that nobody wants to do but everyone needs: plugin updates, content edits, analytics, accessibility fixes, and "can you just move that button" requests.
I also work with Squarespace for clients where that's the better fit. The tool choice follows the client's needs, not my preference.
⇒ Nonprofits and small businesses that need a professional web presence without agency pricing
⇒ Orgs with a WordPress site that hasn't been touched in two years
⇒ Teams that need someone to own the site on retainer so they don't have to think about it
⇒ Anyone who wants their site built right the first time and maintained properly going forward
WHAT THIS LOOKS LIKE
WordPress site builds from scratch using Elementor
WP Engine hosting setup and management
Squarespace site builds and updates
Ongoing maintenance retainers — updates, edits, analytics reporting
Accessibility audits and remediation
08
Coaching for designers + researchers
For the designer who's in over their head in the best possible way, or the one doing excellent work inside a system that isn't set up to support them.
Three situations I see most often:
You've been asked to build something you've never built before. Leadership wants a research program. Or a design system. Or a team. You're the most senior person in the room, which means you're the one expected to figure it out — and you could use someone who's actually done it to think alongside.
Your management situation isn't working. Maybe your manager doesn't have a design background and the feedback is vague or missing. Maybe they're a strong individual contributor who got promoted into management and isn't equipped to help you grow. Either way, you're doing good work and not getting the support, credit, or direction you need to move forward. That's a solvable problem. It just requires a different kind of support than your org is set up to give you.
You're trying to figure out where you actually want to go. IC or manager? Senior designer or design lead? You're at a fork in the road and you'd like to think it through with someone who's navigated both sides — not a career coach with a framework, but a practitioner who can help you think clearly about goal setting, what the paths actually look like, and what you'd be trading in either direction.
I work with designers and researchers at the mid-to-senior level. I'm not here to hype you up. I'm here to give you honest perspective, help you build the thing or navigate the situation, and make sure you leave the engagement with more clarity than you came in with.
⇒ Mid-to-senior designers or researchers operating above their current support system
⇒ Designers building their first design system, research program, or team
⇒ Anyone navigating a management situation that isn't working
⇒ Designers at a career crossroads: IC vs. manager, next level, what's next
⇒ Anyone who needs a thought partner with real UX leadership experience, not just coaching credentials
WHAT THIS LOOKS LIKE
Research method selection and protocol templates
Participant recruitment and screener frameworks
Repository structure and synthesis processes
Stakeholder integration — how research gets into the room
Team training and documentation for ongoing use