1) POV
Over the years, I have learned that “executive communication” is not one format.
Sometimes it’s a high-stakes roadmap forum with the COO and SVPs. Sometimes it’s a design-only review where showing unfinished work is the point. Sometimes it’s a quarterly business review where the job is clarity and confidence. Sometimes it’s a smaller leadership room where you shape direction before it becomes a plan.
My role across these spaces has not been to perform polish. It has been to make the work legible in the room it’s in, so the team leaves with clearer direction, fewer misreads, and better momentum.
Clarity is kindness, especially when teams are moving fast.
[ARTIFACT: Hero visual]
“The same work, different rooms”
A simple map of forums by altitude: messy exploration → direction setting → commitments
2) The kinds of rooms I’ve operated in
I have participated in multiple leadership forums at ServiceNow, each with a different purpose, cadence, and expectation of “what good looks like.”
Roadmap Reviews (semi-annual)
Senior business leadership (COO staff and workflow leaders) reviewing selected topics to align on what ships in the next major release.
In these rooms, the story needs to be crisp and business-aware. The product leader typically drives, and my job is to represent UX clearly when the narrative turns to experience, workflow integrity, adoption risk, or tradeoffs that affect trust.
What I learned to do well here:
Speak to experience impact without going deep into design mechanics
Connect UX choices to adoption, risk, and workflow outcomes
Hold the experience line while staying aligned to the broader product storyline
[ARTIFACT: Roadmap review slice]
One slide + one mockup: “what we are proposing” + “how it shows up in the workflow”
Design executive reviews (ongoing)
Design-only reviews with executive design leadership and partner discipline leaders (research, content, and experience operations).
These are not about perfect answers. They are about bringing messy work into visibility, inviting senior direction, and sometimes re-routing the work early with design stakes involved.
What I learned to do well here:
Show unfinished work without losing the plot
Frame what feedback we need, not just “here’s a demo”
Turn senior feedback into usable direction the team can act on
[ARTIFACT: Design exec review frame]
A “messy work” slide pattern: What we are solving → what’s real today → what’s open → what feedback would help
Quarterly business reviews
Quarterly alignment with business and product leadership (often including marketing and experience leadership) to take stock of progress, upcoming release priorities, and cross-team dependencies.
These rooms are about confidence, progress, and coherence. Less about debate, more about whether the story holds and what needs escalation.
What I learned to do well here:
Translate design progress into business-relevant signals
Highlight risks early without sounding alarmist
Keep the work coherent across teams and release pillars
[ARTIFACT: QBR snapshot]
A single “now, next, watch-outs” card that includes experience risks and mitigations
Cross-functional leadership reviews (directors and senior directors)
Smaller leadership rooms across product, design, and engineering where work gets shaped before it becomes a formal narrative. Strategy, sequencing, guardrails, and tactical directioning.
This is where I’ve often had the most impact because the conversation is raw, alignment is faster, and clarity here prevents churn later.
What I learned to do well here:
Surface the real tension and name it cleanly
Clarify ownership and next steps without making it bureaucratic
Keep experience integrity across seams and handoffs
[ARTIFACT: Alignment recap]
A short “alignment recap” format you can paste into Slack or email: what we aligned on, what’s open, what happens next
Ad hoc leadership check-ins
Everything else that matters: quick check-ins with design leadership, forum-specific leadership reviews, and fast-moving syncs where direction is set in 10 minutes.
These are often the highest-leverage moments. You do not get time for a full story. You get time for clarity.
What I learned to do well here:
Start with what changed and why it matters
Share the few truths, not all context
Leave the room with one clean next move
[ARTIFACT: One-minute framing card]
“What changed / why it matters / what I recommend / what I need from you”
3) How I adjust my narrative based on the room
This is less about templates and more about instincts.
I match the level of mess the room expects
Design exec reviews can handle mess if the intent is clear
Roadmap reviews need the story tight, risks explicit, and the outcome repeatable
Smaller cross-functional rooms need honesty and traction
I choose the right “proof”
Exec forums often need implications and confidence
Design exec forums need craft stakes and cohesion
Cross-functional forums need tradeoffs plus delivery reality
I protect coherence across the whole experience
In enterprise work, the product is rarely one surface. It is workflows, handoffs, and the seams between teams. My narrative consistently brings the room back to workflow integrity, trust, and adoption.
4) What my contribution looks like in practice
I’m not claiming I drove every forum. In many, I was the design representative while product leadership drove the storyline. What I consistently owned was the experience narrative and how the work showed up with credibility.
Across workflow-native experiences in my space, my contribution often looked like:
helping the team sharpen the experience narrative before the forum
driving UX direction in the weeks leading into reviews
representing UX in-room during questions and debate
translating leadership feedback into clear direction for the team after
[ARTIFACT: Before / In / After panel]
A 3-panel visual showing your real role: pre-work shaping, in-room representation, post-room follow-through
5) What I have learned
Earlier in my career, I thought executive craft was about polish.
Now I think it’s about two things:
Can the room understand the work clearly, even when it’s unfinished
Can the team move faster after the room, because direction is clearer
That’s the bar I hold.
What we deprioritized (placeholders, replace later)
To
9) External validation
Listen
