POV
Cross-functional work usually breaks for a simple reason: smart people are optimizing for different versions of “right.” Product is chasing time-to-value, Engineering is protecting scalability, QE is protecting risk, GTM is protecting what we can promise, and Design is protecting clarity and trust. I actually enjoy this part of the job. It’s where good leadership makes work feel calmer.
I lead by making trade-offs explicit early, so teams can commit without resentment and execute without churn. I care a lot about teams leaving meetings with clarity, not fatigue. I have done this year-round across HR Service Delivery, Legal Service Delivery, Contract Lifecycle Management, Agentic + GenAI initiatives and NowX by partnering closely with PM, Dev, QE, Research, Solution Consulting, Visual and Content Design, and outbound teams. I am hands-on with teams day-to-day, and I have also worked very closely with senior leaders when direction and sequencing need clarity.
What this approach enables
Faster alignment: we agree on what “good” means before debating solutions
Less thrash: fewer reopened debates, fewer late surprises
Quality that holds up at scale: clarity, error-risk reduction, and extensibility built in
How I work in practice
Alignment briefs that travel: I capture who’s optimizing for what, what is constrained, what is still unknown, who would own the answers and next checkpoints in Miro/Figma or workshop follow-up email notes.
Evidence over opinion: We agree on what we’re optimizing for, then evaluate options against it, including what we can validate quickly.
Constraints pulled forward: I pull in QE, Solution Consulting, and outbound voices sooner than feels necessary, because late constraints are the most expensive ones.
Shared ownership over handoffs: I keep partners engaged end-to-end through working sessions and milestone checkpoints, so we don’t treat build as a surprise reveal.
Decision hygiene: When decisions get slippery, I lean on my decision canvas to keep trade offs explicit (see “Decision systems I built”).
Where this showed up
Decision reset (Agentic AI, metadata + obligation extraction)
We got stuck in a real debate: one PM was pushing hard for “fewer clicks” while our UX bet was “a few more steps, but far less cognitive load” for a heavy, high-volume flow where mistakes matter. Instead of letting it turn into a two-week tug-of-war, I reset the room around shared criteria: clarity under load, error risk, scalability, and what we could validate quickly. Once we had shared criteria, it stopped being about preferences. We compared options, made the call, and moved into execution with a rationale everyone could defend.
Usability guardrail (CLM Word setup, contract admin)
There was pressure to dump everything into one mega-form to save effort. My pushback was simple: that version feels fast once, then becomes confusing forever, especially as requirements grow. Categorization meant extra engineering work, so it needed a real trade-off conversation, not a “design opinion” fight. We aligned early on the downstream costs of the shortcut (errors, support burden, extensibility), chose the structured path, and shipped something that stayed usable as complexity grew.
Org compass (CBWF mission and vision)
I led the global leadership initiative to define mission and vision for my design org, then focused on what most teams skip: making it real. We published it, propagated it through routines, and used it as a shared compass for prioritization and decisions. The impact was not a statement on a slide. It reduced second-guessing and made trade-offs easier to land across teams.
When alignment breaks
When alignment breaks, I bring the room back to three things: who decides, what “good” means, and when we’ll decide. Then we move.
