Served as the first UX Indeed University Lead, managing and mentoring four non-UX direct reports while building a 10+ person UX support network.
Design leadership
Indeed University UX Integration
Turning UX from late-stage support into a repeatable system for product learning, facilitation, and better decisions.
Company / context
Indeed
Role
UX leadership, people management, mentoring, facilitation systems
Timeframe
2019
Proof strategy
Leadership systems and repeatable UX capability
My role
Responsibility before artifacts.
Created facilitation and advisor structures that helped UX show up earlier in product-learning moments.
Turned workshops, guides, critique rituals, and mentoring into a more repeatable support system for product teams.
Problem beneath the brief
Design influence needed to move upstream.
UX influence was limited when designers entered the work too late, after the important product questions had already been framed. The opportunity was to make UX a partner in how teams learned, structured ambiguity, and made decisions.
Decision evidence
What the artifacts made discussable.
01 / Signal
The leadership problem was upstream influence.
The visible work may look like workshops, guides, and mentorship. The deeper product problem was timing: UX had more value to offer when it helped teams frame the question, not only refine the output.
That made this an organizational design case. The product of the work was not a screen; it was a repeatable way for design to improve how teams learn and decide.
Senior design leadership often shows up as better conditions for decision-making, not as a prettier final artifact.
UX advisor
Team ritual
Critique loop
Learning system
Indeed University UX integration
02 / System
Advisor roles made UX contribution legible and repeatable.
A vague request for “more UX involvement” is hard to scale. The advisor model clarified how design could enter the work: framing questions, facilitating critique, structuring evidence, and helping teams compare options.
Once the role was visible, it became easier for teams to ask for the right kind of design help earlier — and for designers to contribute without waiting for a production brief.
The role model turned influence from personality-driven effort into an operating pattern.
03 / Enablement
Facilitation artifacts helped other people practice better product thinking.
The facilitator guide and related materials are strongest when presented as enablement infrastructure. They made the invisible parts of design work explicit: framing, sequencing, synthesis, critique, and decision hygiene.
This is why the case belongs in a senior portfolio. It shows the move from making artifacts to making teams more capable of producing better artifacts themselves.
Design maturity scales when the method becomes teachable.
01Frame
What decision are we helping the team make?
02Facilitate
Turn product ambiguity into comparable options.
03Reflect
Make the next team ritual better.
Facilitator guide
04 / Outcome
The outcome was a stronger product-learning system.
The change was not only individual workshop quality. UX became a more strategic partner in how teams moved through ambiguity.
The strongest framing is not “I ran workshops.” It is “I helped build a repeatable system that supported product teams as they thought, learned, and decided.”
This is the leadership case: influence through systems, rituals, and capability building.
Decision journey
How the work unfolded.
01 / Diagnose
UX was arriving after the frame was set
When UX enters only at execution time, the biggest opportunity is already gone: shaping the problem, the evidence, and the decision path.
02 / Reposition
Make UX an advisor to product learning
The work defined clearer roles and rituals so UX could support teams upstream — helping them ask better questions before committing to solutions.
03 / Enable
Turn facilitation into a shared practice
Guides, workshop formats, and mentoring made the practice repeatable. The goal was not one great session; it was a system others could use.
04 / Scale
Support better decision quality across teams
The strongest outcome evidence is cultural and qualitative: teams had clearer structures for framing, critique, synthesis, and learning — even when a designer was not controlling every artifact.
Evidence boundary
Resume evidence for the first UX Lead role, four non-UX direct reports, a 10+ person UX support network, plus advisor models, facilitation systems, mentoring patterns, and product-learning rituals.
Portfolio status: Needs public-safety review. Claims remain bounded to what the reviewed source set can support.
What changed / what the evidence supports
The source evidence supports a more repeatable UX product-learning support system: clearer advisor roles, facilitation structures, mentoring infrastructure, and a network that helped participating teams frame and critique work earlier.
Reflection
This is the senior-leadership case. It shows design as an organizational capability: not only making screens, but improving how teams frame problems, use evidence, and make decisions.