I usually start by getting everyone on the same page about the problem before we jump to solutions.
Create shared understanding before teams push toward solutions.
Turn ambiguity into a direction teams can execute.
Translate intent into buildable work with engineering and partners.
Use outcomes to strengthen the system over time.
Some of the highest-leverage leadership work in my career happened when I did not own the org chart. I had to make the problem, evidence, and tradeoffs clear enough that Product, Engineering, vendors, and leaders could move together.
That usually means:
The goal is not agreement for its own sake. It is alignment that survives implementation.
Example: A 100+ product audit at Hy-Vee exposed variation failures the existing ProdX model could not support. I used those edge cases to align internal teams with the vendor, and ProdX added two API attributes the new variation model required.
At ACT, the leadership challenge was bigger than adding headcount. UX needed enough capability, structure, and autonomy to support a fragmented enterprise portfolio without concentrating critical knowledge in a few people.
I stayed hands-on while doing this, leading cross-product strategy across 37+ systems and 5+ product lines. The goal was not to become the design bottleneck. It was to make the function more capable without lowering the quality bar.
At Grey Dog, the constraint was different: a small agency had to deliver consistent UX across multiple clients without scaling headcount every time complexity increased.
