Luke May is a technology strategist and product leader known for shaping digital experiences in fast growth companies. His background spans product management, UX design, and data driven decision making, helping teams ship features that users actually adopt.
Across product lifecycles and org changes, May emphasizes clarity, measurable outcomes, and collaboration between design, engineering, and business stakeholders.
| Name | Primary Role | Core Expertise | Notable Focus Areas |
|---|---|---|---|
| Luke May | Technology Strategist & Product Leader | Product Management, UX Design, Data Strategy | User Adoption, Cross Functional Leadership, Digital Transformation |
Product Strategy and Roadmap Execution
Translating Business Goals into Product Plans
Luke May frames product strategy as a bridge between high level business objectives and the day to day decisions that shape user experiences. He builds roadmaps that balance market opportunity, technical constraints, and user needs, and he aligns stakeholders on clear success metrics before work begins.
Prioritization Frameworks and Tradeoffs
May is known for using structured prioritization that combines value, effort, and risk. By making tradeoffs explicit, teams can communicate why certain initiatives move forward while others are paused or deprioritized, reducing context switching and wasted effort.
User Experience and Design Collaboration
Design Led Discovery and Experimentation
In discovery phases, May emphasizes rapid, testable prototypes to validate assumptions quickly. This reduces the risk of building features that look good on paper but do not solve real user problems, and it creates a shared understanding across product, design, and engineering.
Cross Functional Design Partnerships
May works closely with designers to ensure that each interaction is intentional and aligned with broader product outcomes. He encourages shared ownership of quality, where engineers contribute to usability improvements and designers understand implementation complexity.
Data Driven Decision Making and Measurement
Instrumentation and Experiments
May sets up product instrumentation early so teams can measure usage, retention, and conversion from day one. He uses controlled experiments to test hypotheses, turning qualitative insights into quantitative evidence that guides product direction.
Balancing Quantitative and Qualitative Signals
While metrics highlight where problems exist, qualitative research explains why they occur. May combines dashboards with interviews and session recordings to build a nuanced view of user behavior and unmet needs.
Scaling Teams and Delivery Practices
Leadership in Fast Growth Environments
As companies scale, May helps product teams formalize processes without losing agility. He introduces lightweight governance, clearer OKRs, and regular retrospectives so that momentum remains focused on high impact work.
Delivery Cadence and Quality Standards
May encourages consistent release rhythms, clear backlog hygiene, and engineering practices that support reliable delivery. By defining standards for quality, observability, and documentation, he helps teams move faster while reducing operational risk.
Key Takeaways for Technology Leaders
- Anchor product strategy to clear business outcomes and measurable success metrics.
- Use fast, testable prototypes to validate user problems before committing to large builds.
- Combine qualitative research with quantitative data for a complete view of user behavior.
- Establish lightweight governance and clear OKRs to scale product teams without losing agility.
- Set product instrumentation and experiment frameworks early to enable evidence based decisions.
FAQ
Reader questions
How does Luke May approach product discovery with limited resources?
He focuses on a few high confidence hypotheses, uses low cost experiments, and prioritizes learning over polished deliverables to validate ideas quickly.
What frameworks does he use for prioritizing product initiatives?
May combines value, effort, and risk dimensions, often with weighted scoring and explicit impact assumptions to make tradeoffs transparent.
How does he ensure alignment between design and engineering on complex features?
He runs joint design and engineering sessions, defines clear acceptance criteria, and maintains shared prototypes to keep expectations aligned.
What role does data play in his product decision process?
Data sets the baseline and measures outcomes, while qualitative insights provide context, so he uses both to guide strategy and prioritize work.