Product Managers with UX & Design Thinking

A Systems Problem Nobody Was Naming
Skill Constellation
Primary
Supporting
Emerging
At John Deere, Product Managers are the connective tissue between users, engineering, and business strategy across a 250+ product portfolio. But observations revealed a critical gap: PMs were making decisions about user-facing features without a shared UX language. Research findings sat in slide decks, and usability results arrived too late to impact development.
Equip PMs with UX frameworks and collaborative workflows so they can confidently lead user-centred design, moving from ad-hoc practices to systematic execution.
Stakeholder Mapping
Mapped full ecosystem of PMs, UX, Engineering, and Leadership to understand information flow breakdowns and highest-leverage intervention points.
Evidence: Identified 3 macro-clusters of friction through cross-functional mapping.
Measurable Cultural Shift
Before diving into the methodology, here is the tangible impact of deploying the "PM-UX Playbook" pilot to a 50-person cohort over 4 weeks:
Participants reported greater confidence interpreting research deliverables.
Reduction in average time to complete feature specifications.
Started in month one. Peer learning happened organically.
Mentorship pairs voluntarily continued beyond the pilot.
Double Diamond Framework
We applied the Double Diamond framework augmented by contextual interviews and collaborative design thinking workshops.
Contextual Inquiry
Conducted 15 contextual interviews AND shadowed real planning meetings. Observation in context surfaced friction points interview questions alone miss.
Evidence: "Contextual research reveals what surveys cannot" became core learning.
What The Research Revealed
15 contextual interviews revealed structural gaps that showed up consistently across product lines, driving the need for a practical, low-friction solution.
Rajesh, Senior Product Manager
Research synthesised into "Rajesh," capturing the composite behaviours and frustrations of our target PMs. Identifying his true baseline was critical: they needed collaboration templates, not UX encyclopedias.
Persona Development
Synthesized interview data into 'Rajesh' persona with quantified baseline scores.
Evidence: Persona directly shaped solution design — templates over education.
Behaviors & Actions
- Willing to Learn/Upskill
- Workaholic
- Seeks advice from other PMs or GPMs
- Keen on leadership
Expectations / Gains
- Wants to understand career options for PM
- UX Support
- Set path and direction for new PMs in the role
- Gain better understanding on the technical side
Pain Points/Challenges
- Benchmarking/ repository of best practices
- No PM forums
- Don't know how to utilize P&C team
- Need help with research
- Do not know how to analyze data
- Do not know how to proceed in career/aim
- Technical challenges when not from tech background
- Right Courses for PM
Rajesh's Baseline Proficiency
Affinity Mapping
Clustered raw interview data into 3 macro-themes, enabling convergence on root causes rather than symptoms.
Evidence: 3 clusters directly mapped to 3 of the 4 solution concepts.
Four Solutions From Co-Creation
Co-creation sessions generated 40+ ideas, which we whittled down to four highly feasible, high-impact concepts designed to integrate into existing workflows.
Workshop Facilitation & Co-creation
Designed and facilitated 2 co-creation workshops generating 40+ ideas, then led convergence to 4 feasible solutions.
Evidence: 40+ ideas → 4 high-impact concepts in 2 sessions.
1. PM-UX Playbook
Template-driven heuristic guides.
2. Buddy-Up Programme
Quarterly UX/PM collaboration pairs.
3. Community Forum
Internal platform for sharing templates & wins.
4. Micro-Learning
5min UX concepts via Slack & Jira.


Testing in the Real World
Tested directly during actual monthly planning workshops. The key insight: Contextual timing is everything.
- Simplified Navigation: Merged "Learn" and "Templates" into a workflow-staged "Resources" hub.
- Contextual Prompts: Added "Use this when..." tips to all UX Playbooks.
Usability Testing & SUS Scoring
Tested during actual planning workshops, not lab settings. SUS 78 validated usability; qualitative feedback drove the 'contextual timing' iteration.
Evidence: SUS 78 + "Now I know WHEN to use this" insight → Resources restructure.
Now I know when to use this, not just that it exists.
— PM participant, Round 2 testing
Key Learnings & Next Steps
What Worked
- Embedded learning beats standalone training. PMs have time for a 5-minute module between meetings but not a 2-hour workshop.
- Community drives adoption faster than mandates. The forum took off because PMs shared real wins with peers who understood their context.
- Contextual research reveals what surveys cannot. Shadowing PMs in their actual meetings surfaced friction points interview questions alone would never have found.
What Happened Next
- Scale & Personalise: Role-based learning tracks for data-driven PMs versus platform PMs.
- Measure ROI: Connecting UX literacy to downstream business metrics like conversion lift and support tickets.
- Extend to Product Ops: Folding in analytics playbooks and A/B testing frameworks.
The community forum is still active. The Buddy-Up programme is in its third cohort. And the phrase "What does the research say?" is now heard in sprint planning meetings across the organisation.
