Lead Product Development Assistant

Role Purpose & Context

Role Summary

The Lead Product Development Assistant is here to bridge the gap between our R&D vision and the actual engineering work. You'll take those innovative concepts, break them down, and turn them into actionable plans, making sure our development teams know exactly what to build and why it's important. This role directly impacts our ability to deliver groundbreaking products to market on time and, crucially, to spec. You'll be the central point, making sure the technical details align with the overall business goals, and that we're always focused on what truly matters to our users and our bottom line. When you do this well, we launch products that genuinely solve problems, delight customers, and hit our strategic targets. Mess it up, and we're building the wrong thing, wasting precious R&D budget, and missing market opportunities. The tricky part is dealing with constant change and conflicting priorities – everyone thinks their idea is the most important. But the reward? Seeing your ideas go from a whiteboard sketch to a real product that makes a difference, knowing you were the one who guided it through the maze.

Reporting Structure

• Reports to: Product Development Manager
• Direct reports: Roughly 3-5 junior or mid-level Product Development Assistants, or perhaps a couple of dedicated analysts. It's about guiding, not just managing.
• Matrix relationships: Product Owner, Junior Product Manager (R&D), Product Lead (Innovation), Technical Product Analyst,

Key Stakeholders

Internal:

• Head of R&D
• Engineering Leads and Architects
• Senior Scientists and Researchers
• Marketing and Sales Leadership
• Customer Support Managers
• Legal and Compliance Teams

External:

• Key Research Partners (Universities, other R&D firms)
• Early Adopter Customers (for feedback and testing)
• Technology Vendors (for new tools or components)
• Industry Regulators (where applicable)

Organisational Impact

Scope: You'll directly shape the features and functionalities of our core R&D products, influencing everything from market adoption to our competitive advantage. Your decisions on what gets built, and how, will have a tangible impact on our R&D budget, project timelines, and ultimately, our ability to innovate and deliver value. You're the one who ensures our R&D efforts actually turn into something usable and valuable.

Performance Metrics

Quantitative Metrics

1. Metric: Feature Adoption Rate
2. Desc: The percentage of target users actively using new features you've launched.
3. Target: Achieve 20%+ adoption for major features within 3 months post-launch.
4. Freq: Monthly, reviewed quarterly.
5. Example: We launched 'Project X' with a new data visualisation module. You'd track if 25% of our target research users actually use it regularly, not just once.
6. Metric: Backlog Health Score
7. Desc: A weighted score based on backlog clarity (well-defined stories), readiness for development, and alignment to strategic objectives.
8. Target: Maintain a score of 85% or higher for your owned product area.
9. Freq: Weekly grooming sessions, reported monthly.
10. Example: Your backlog for the 'AI Experimentation Platform' has 90% of stories with clear acceptance criteria, 80% estimated, and all linked to Q3 OKRs, giving it a high health score.
11. Metric: Development Cycle Time Reduction
12. Desc: The average time it takes for a feature idea (from your backlog) to go from 'ready for development' to 'released to users'.
13. Target: Reduce cycle time by 10% year-on-year for your product stream.
14. Freq: Quarterly analysis.
15. Example: If it took 6 weeks on average last year to get a feature out, you're aiming for 5.4 weeks this year, by streamlining requirements and reducing re-work.
16. Metric: Team Velocity Stability
17. Desc: How consistent your development team's sprint velocity is, indicating predictable delivery and clear requirements.
18. Target: Maintain less than 15% variance in sprint velocity over 6 consecutive sprints.
19. Freq: Every sprint, reviewed monthly.
20. Example: If your team typically completes 30 story points per sprint, you'd want to see them consistently hitting between 26 and 34 points, not wildly fluctuating.
21. Metric: Bug Rate Reduction (Post-Launch)
22. Desc: The number of critical or major bugs reported by users within the first month after a feature you've led goes live.
23. Target: Reduce critical/major bug count by 15% compared to similar previous launches.
24. Freq: Monthly post-launch review.
25. Example: For the 'Advanced Simulation Engine' you launched, we saw 5 critical bugs in the first month. Your target for the next big feature would be 4 or fewer, showing better upfront definition.

Qualitative Metrics

1. Metric: Stakeholder Trust & Influence
2. Desc: Are you seen as the go-to person for your product area? Do people actively seek your input and trust your judgment?
3. Evidence: You're proactively invited to early strategic discussions, not just informed later. Engineering leads come to you with problems before they become crises. Senior scientists trust your ability to translate their research into practical features. People actually listen when you say 'no' to a feature request, understanding the 'why'.
4. Metric: Clarity of Requirements
5. Desc: How well do your user stories and specifications prevent rework and misunderstandings?
6. Evidence: Engineering rarely needs to ask for clarification on your acceptance criteria. QA finds very few 'misunderstanding' bugs (where the feature works as specified, but not as intended). New team members can pick up your documentation and understand the feature without constant hand-holding.
7. Metric: Mentorship & Team Development
8. Desc: How effectively do you guide and develop the junior members of the product development team?
9. Evidence: Your direct reports show clear growth in their ability to write user stories, analyse feedback, and manage small features independently. They actively seek your advice and feel supported. You're regularly providing constructive feedback and helping them navigate tricky situations. Their confidence and competence visibly improve under your guidance.
10. Metric: Strategic Alignment of Deliverables
11. Desc: How well does the work your team delivers align with our broader R&D and business strategy?
12. Evidence: Every major feature you oversee can be directly mapped back to a company OKR or strategic initiative. You can articulate the 'why' behind each priority to anyone who asks. Leadership consistently sees your product area contributing meaningfully to the company's overall direction, not just building 'cool stuff'.
13. Metric: Proactive Problem Solving
14. Desc: Do you anticipate issues and address them before they escalate, rather than just reacting?
15. Evidence: You're flagging potential technical debt, user experience pitfalls, or stakeholder conflicts early on. You're proposing solutions before problems become blockers. You're not waiting for someone to tell you there's a problem; you're finding it and working to fix it.

Primary Traits

• Trait: The Unflappable Navigator
• Manifestation: You're the calm in the storm when priorities shift, which they will. You can take a sudden, urgent request from the Head of R&D, assess its real impact, and figure out how to slot it in (or push back) without panicking. When an engineer tells you 'that's impossible', you don't throw your hands up; you ask 'what if we tried this?' or 'what's the *real* blocker here?' You're good at seeing the path through the weeds, even when it's not clear to others.
• Benefit: Our R&D environment is complex and, frankly, a bit chaotic at times. New research breakthroughs, unexpected technical hurdles, or a competitor's move can completely change our direction. If you get rattled easily, you'll struggle to keep your team focused and productive. We need someone who can keep their head, make sensible trade-offs, and guide the ship through choppy waters.
• Trait: The Relentless Clarifier
• Manifestation: You don't just write user stories; you make them bulletproof. You'll ask 'what if' questions until you've uncovered every edge case. You can take a researcher's brilliant, but vague, concept and turn it into a crystal-clear set of requirements that an engineer can build without guessing. You're the person who spots the ambiguity in a design mock-up or the missing step in a user journey. You're almost obsessive about making sure everyone understands exactly what 'done' looks like.
• Benefit: Ambiguity is the enemy of efficient R&D. Every minute an engineer spends guessing, or every feature that needs re-work because the requirements were fuzzy, costs us time and money. Your ability to make things clear and unambiguous directly translates to faster development cycles, fewer bugs, and products that actually meet the intended need. It's about preventing problems before they even start.
• Trait: The Diplomatic Influencer
• Manifestation: You often don't have direct authority over the engineers, designers, or even the senior scientists you work with, but you can get them all marching in the same direction. You're a master of persuasion, using data, logic, and a bit of charm to get people to agree on a path forward. When two teams have conflicting priorities, you're the one who can bring them together, find common ground, and get them to shake hands. You listen intently, understand different perspectives, and then build consensus. You can tell a senior stakeholder 'no' in a way that makes them understand and respect your decision.
• Benefit: Product development is a team sport, but it's full of strong opinions and competing interests. If you can't influence without authority, you'll become a bottleneck, and projects will stall. We need someone who can build bridges, mediate disagreements, and inspire confidence across different functions, ensuring that everyone's pulling in the same direction towards a shared product vision. It's about getting things done through people, not just processes.

Supporting Traits

• Trait: Curious Investigator
• Desc: You're not content with surface-level answers. You'll dig deep into user feedback, market trends, and technical possibilities to truly understand the problem we're trying to solve and the best way to solve it. You're always asking 'why' and 'what if?'
• Trait: Pragmatic Problem-Solver
• Desc: You're not just identifying problems; you're finding practical, achievable solutions. You can balance the ideal solution with what's actually feasible given our resources and timelines. You're good at finding the 'least worst' option when trade-offs are necessary.
• Trait: Constructive Challenger
• Desc: You're not afraid to question assumptions or push back on ideas, even from senior leadership, but you do it respectfully and with data to back up your points. You're focused on making the product better, not just being agreeable.
• Trait: Organised Orchestrator
• Desc: You can keep multiple plates spinning at once, managing complex backlogs, coordinating across teams, and ensuring nothing falls through the cracks. Your projects usually run smoothly because you've thought several steps ahead.

Primary Motivators

1. Motivator: Seeing Your Ideas Come to Life
2. Daily: You'll be directly responsible for taking abstract R&D concepts and turning them into tangible features. You'll get a real buzz from seeing a user story you wrote go from Jira ticket to deployed product, knowing you guided its journey.
3. Motivator: Solving Complex Puzzles
4. Daily: Every day presents new challenges, from untangling ambiguous research requirements to figuring out how to integrate a tricky new technology. You'll spend a lot of time breaking down big problems into smaller, solvable pieces.
5. Motivator: Leading and Guiding Others
6. Daily: You'll be mentoring junior team members, helping them grow their product development skills. You'll also be leading discussions, driving consensus, and influencing various teams to align on product direction.

Potential Demotivators

Honestly, this role isn't for everyone. You'll spend a fair bit of time herding cats, translating between highly technical engineers and business-focused stakeholders. You'll define brilliant features that get deprioritised because the market shifted or a technical blocker proved too big. You'll also have to say 'no' to a lot of good ideas, which can be tough when people are passionate. If you need constant, immediate gratification from seeing every single piece of your work shipped, you'll struggle here. Sometimes, the best product decision is to *not* build something, or to delay it indefinitely.

Common Frustrations

1. Dealing with scope creep from well-meaning but unfocused stakeholders.
2. The constant tension between technical feasibility and ambitious R&D goals.
3. Spending hours refining requirements, only for them to change at the last minute.
4. Being the 'bad cop' who has to say 'no' to feature requests that don't align with strategy.
5. The sheer volume of meetings and the effort required to make them productive.

What Role Doesn't Offer

1. A purely technical coding role – you're defining, not building the code.
2. A 'set it and forget it' environment – things change, often.
3. A role where you always have direct authority over everyone involved.
4. A quiet, solitary job – you'll be talking to people constantly.

ADHD Positives

1. The fast-paced, varied nature of product development can be highly stimulating, offering constant new challenges and problems to solve.
2. The need to quickly pivot between different tasks and topics (e.g., user research, technical discussions, strategic planning) can suit those who thrive on novelty.
3. The focus on breaking down complex problems into smaller, manageable user stories can be a strength, as it requires intense, focused bursts of activity.

ADHD Challenges and Accommodations

1. The high volume of meetings and the need for sustained attention can be challenging. We can help by ensuring clear agendas, regular breaks, and allowing for movement or fidget tools.
2. Managing a complex backlog with shifting priorities requires strong organisational skills. We use tools like Jira and Confluence extensively, and can offer coaching on prioritisation frameworks and time management techniques.
3. Documentation is crucial here, and it can be a significant hurdle. We encourage the use of templates, AI-assisted drafting, and pairing with colleagues for review to ease this burden.

Dyslexia Positives

1. The role's emphasis on conceptual thinking, problem-solving, and understanding complex systems can be a strong suit.
2. Visual tools like Figma and Miro are heavily used for communicating ideas, user flows, and product designs, which can be very effective for visual thinkers.
3. The ability to see the 'big picture' and make connections between disparate pieces of information is highly valued.

Dyslexia Challenges and Accommodations

1. A lot of communication happens in writing (user stories, PRDs, emails). We encourage the use of proofreading tools, AI writing assistants, and can offer templates and support for written communication.
2. Reading detailed technical specifications can be demanding. We promote verbal summaries, visual aids, and recorded explanations where possible.
3. We can provide access to assistive technologies like text-to-speech software and screen readers to help with documentation review.

Autism Positives

1. The logical, structured nature of breaking down problems into user stories and defining clear acceptance criteria can be very appealing.
2. A deep focus on understanding systems, processes, and technical details is highly valued in this role.
3. The need for precise, unambiguous communication in technical specifications is a core requirement, which can align well with a preference for directness.

Autism Challenges and Accommodations

1. The role involves extensive social interaction and navigating unspoken social cues in meetings. We can support by ensuring clear meeting structures, explicit agendas, and encouraging direct, unambiguous communication.
2. Unexpected changes and shifting priorities can be unsettling. We aim to provide as much advance notice as possible for changes and clearly explain the 'why' behind them.
3. Sensory overload from open-plan offices or intense meeting environments can be an issue. We offer quiet zones, noise-cancelling headphones, and flexibility for remote work or specific office setups.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Lead Product Development Assistant (L4)
2. Responsibilities: Define the product backlog and roadmap for a specific R&D product or a significant feature area. This means deciding what gets built, when, and why—and being ready to defend those decisions to senior leadership. (You'll probably spend a good chunk of time on this.)
3. Accountable for the successful delivery of features and enhancements within your product domain. If it goes wrong, the buck stops with you. If it goes right, you get to celebrate with the team.
4. Build and mentor a small team of junior or mid-level Product Development Assistants. This isn't just delegating; it's about coaching them, reviewing their work, and helping them grow their skills. Expect to spend a couple of hours a week on this, minimum.
5. Influence senior stakeholders (like the Head of R&D, Engineering VPs, and even external research partners) to align on product strategy and priorities. This often involves presenting your rationale, negotiating trade-offs, and building consensus across different, sometimes conflicting, viewpoints.
6. Architect detailed user stories, acceptance criteria, and technical specifications for complex R&D features. This is where your 'relentless clarifier' trait really shines. You'll work closely with engineers and scientists to ensure everything is crystal clear.
7. Lead competitive and market analysis for your product area, identifying opportunities and threats. This isn't just a quick Google search; it's about deep dives, understanding competitor roadmaps, and translating that into actionable insights for our own strategy.
8. Own the end-to-end user research process for your product, from designing surveys and interviews to analysing the data and presenting actionable insights. This means getting out there and talking to actual users, not just relying on second-hand information.
9. Supervision: You'll typically have monthly strategic alignment meetings with your Product Development Manager. For day-to-day execution, you're largely autonomous. We trust you to get on with it, but you're expected to flag major roadblocks or strategic shifts early.
10. Decision: You'll have full technical decision-making authority within your product domain (e.g., tool selection for a specific feature, methodology for user research). You can approve budget expenditure up to roughly £50K for specific project needs (e.g., software licences, external research). You'll also have input into hiring decisions for your direct reports, and you're expected to define their objectives. Any strategic shifts or budget requests above £50K will need sign-off from your manager or the Head of R&D.
11. Success: You'll know you're succeeding when your product area consistently delivers high-quality features that meet user needs and business goals, your direct reports are growing in their roles, and you're seen as a trusted, influential voice across R&D and beyond. Basically, you're making a tangible difference to our product and our people.

Decision-Making Authority

• Type: Product Backlog Prioritisation
• Entry: Suggests priorities for individual tasks, reviewed by senior team.
• Mid: Prioritises tasks within a small feature, with manager review.
• Senior: Prioritises entire feature sets within a workstream, consulting Product Manager.
• Type: Technical Specification & Design
• Entry: Documents existing technical details following templates.
• Mid: Drafts specifications for simple features, reviewed by senior.
• Senior: Designs and implements technical specifications for complex features, with peer review.
• Type: User Research Methodology
• Entry: Assists with data collection (e.g., transcribing interviews).
• Mid: Conducts pre-defined user interviews, analyses basic survey data.
• Senior: Designs and executes user research studies, presents findings.
• Type: Budget Allocation (Project Specific)
• Entry: No authority; flags potential cost overruns.
• Mid: Proposes small purchases (<£1K) for approval.
• Senior: Recommends budget for specific tools or small projects (up to £5K), approved by manager.
• Type: Hiring & Team Development
• Entry: No involvement.
• Mid: Provides feedback on junior candidates during interviews.
• Senior: Actively participates in interviewing and onboarding junior team members.

Competency Requirements

Foundation Skills (Transferable)

These are the bedrock skills that underpin everything you'll do. They're not just 'nice-to-haves'; they're essential for navigating the complexities of a Lead Product Development Assistant role. Think of them as your core toolkit for getting things done with people.

• Category: Communication & Influence
• Skills: Active Listening: You'll need to truly hear what stakeholders, users, and engineers are saying, not just waiting for your turn to speak. This means asking clarifying questions and reflecting back what you've heard to ensure understanding.
• Concise Written Communication: Crafting clear, unambiguous user stories, PRDs, and emails that leave no room for misinterpretation. You'll need to get your point across quickly and effectively.
• Compelling Presentation Skills: Presenting product roadmaps, research findings, and strategic recommendations to diverse audiences, from technical teams to senior leadership. You'll need to tailor your message and tell a story.
• Negotiation & Consensus Building: Guiding diverse groups (often with conflicting priorities) towards a shared understanding and agreement on product direction and trade-offs. This is about finding win-win solutions.
• Category: Problem Solving & Critical Thinking
• Skills: Structured Problem Decomposition: Taking a huge, fuzzy problem and systematically breaking it down into smaller, manageable, and logical components. This is essential for turning vision into execution.
• Root Cause Analysis: Not just fixing symptoms, but digging deep to understand the underlying 'why' of a problem, whether it's a user pain point or a technical blocker.
• Strategic Trade-off Analysis: Evaluating different options, understanding their pros and cons (technical debt, user impact, business value), and making informed decisions under uncertainty.
• Data-Driven Decision Making: Using quantitative and qualitative data to inform your product choices, validate hypotheses, and measure success. You'll need to challenge assumptions with evidence.
• Category: Adaptability & Resilience
• Skills: Navigating Ambiguity: Thriving in situations where the path isn't clear, and being comfortable with evolving requirements and priorities. You're the one who brings clarity to the chaos.
• Managing Change: Effectively responding to shifts in market conditions, research findings, or technical capabilities, and guiding your team through these changes without losing momentum.
• Handling Constructive Criticism: Being open to feedback on your product ideas and decisions, and using it to iterate and improve, rather than getting defensive.
• Pressure Management: Keeping calm and focused when deadlines are tight, stakeholders are demanding, or unexpected issues arise. This role often feels like a pressure cooker.
• Category: Leadership & Mentorship
• Skills: Team Guidance & Coaching: Providing clear direction, constructive feedback, and support to junior team members, helping them develop their skills and navigate challenges.
• Delegation & Empowerment: Effectively assigning tasks to your team, trusting them to deliver, and giving them the autonomy to learn and grow.
• Conflict Resolution: Mediating disagreements between team members or stakeholders, finding common ground, and facilitating productive outcomes.
• Vision Articulation: Clearly communicating the 'why' behind product decisions and inspiring your team and stakeholders to rally around a shared product vision.

Functional Skills (Role-Specific Technical)

These are the specific skills and tools you'll use day-in, day-out to do the actual job. They're the practical application of your foundation skills, tailored for a Lead Product Development Assistant in R&D. You'll be expected to be pretty handy with these.

Technical Competencies

• Skill: Agile & Scrum Methodologies
• Desc: You don't just attend the meetings; you live the principles. This means understanding the 'why' behind stand-ups, sprint planning, retrospectives, and backlog refinement. You'll be leading these ceremonies, not just participating.
• Level: Advanced
• Skill: User Story Writing & Acceptance Criteria Definition
• Desc: The art of translating vague user needs into unambiguous, testable instructions for engineers. You'll be writing these for complex features and coaching others to do the same. Think Gherkin syntax (Given/When/Then) as a standard.
• Level: Expert
• Skill: Competitive & Market Analysis
• Desc: Systematically identifying competitors, deconstructing their products feature-by-feature, and analysing their market positioning to inform our own strategy. This goes beyond a simple SWOT analysis; you'll be building frameworks for this.
• Level: Advanced
• Skill: Minimum Viable Product (MVP) Scoping & Iteration
• Desc: The discipline of ruthlessly prioritising, asking 'What is the absolute smallest thing we can build to start learning from real users?' and defending those decisions against pressure to add 'just one more thing'. You'll be defining and iterating on MVPs.
• Level: Advanced
• Skill: User Persona & Journey Mapping
• Desc: Building and internalising detailed representations of our target users (not just demographics, but their goals, pains, and context) and mapping their end-to-end experience with our product to identify friction points and opportunities. You'll be leading these efforts.
• Level: Advanced
• Skill: Product Lifecycle Management (PLM)
• Desc: Understanding that products have distinct phases (introduction, growth, maturity, decline) and that your activities—from feature development to marketing support—must adapt to the current phase. You'll be making strategic decisions based on PLM.
• Level: Advanced

Digital Tools

• Tool: Jira
• Level: Advanced
• Usage: Configuring custom workflows, setting up complex dashboards and filters (JQL), leading backlog grooming sessions, and training new team members on best practices. You're the Jira guru for your team.
• Tool: Confluence / Notion
• Level: Expert
• Usage: Designing and architecting entire Confluence spaces or Notion databases for your product area. Creating dynamic templates, embedding reports, and establishing the single source of truth for product knowledge. You're building the knowledge base.
• Tool: Figma / Miro
• Level: Advanced
• Usage: Creating low-to-mid fidelity wireframes and user flow diagrams to communicate complex ideas. Facilitating collaborative workshops in Miro, using advanced features like templates and voting to drive consensus and ideation. You're guiding the visual communication.
• Tool: Productboard / Aha!
• Level: Advanced
• Usage: Managing the feedback repository for your product, triaging and prioritising incoming ideas, and helping the Product Manager build and update the roadmap. You're the one making sure feedback turns into action.
• Tool: SurveyMonkey / Typeform
• Level: Expert
• Usage: Designing surveys to minimise bias, using advanced logic and branching, and analysing results to extract actionable insights. You'll present these findings to stakeholders to inform product decisions. You're shaping how we gather user insights.
• Tool: Google Analytics / Mixpanel
• Level: Advanced
• Usage: Setting up funnels and cohorts to analyse user behaviour for your product. Identifying drop-off points, formulating hypotheses for A/B testing, and answering ad-hoc data questions from stakeholders. You're turning data into understanding.

Industry Knowledge

• Area: R&D Project Methodologies
• Desc: Understanding the specific phases and challenges of R&D projects, from basic research to applied development and commercialisation. This isn't just generic project management; it's about the unique lifecycle of innovation.
• Area: Scientific Data Management & Visualisation
• Desc: Familiarity with how scientific data is typically collected, stored, processed, and visualised in a research context. Understanding the needs of scientists for robust data integrity and clear presentation of complex results.
• Area: Intellectual Property (IP) Basics
• Desc: A foundational understanding of patents, copyrights, and trade secrets, particularly how they relate to product features and R&D outputs. You'll need to know when to flag potential IP issues.
• Area: Ethical Considerations in Research
• Desc: Awareness of ethical guidelines and best practices in scientific research, especially concerning data privacy, experimental design, and responsible innovation. This is crucial for our reputation and compliance.

Regulatory Compliance Regulations

• Reg: GDPR (General Data Protection Regulation)
• Usage: Ensuring that any product features involving user data collection, storage, or processing are compliant with GDPR principles. You'll need to work with legal to ensure our R&D products are not creating compliance risks.
• Reg: Industry-Specific Research Ethics Guidelines
• Usage: Applying relevant ethical guidelines (e.g., for clinical trials, AI ethics, data privacy in scientific research) to product design and feature development. You'll be a key voice in ensuring our products are developed responsibly.
• Reg: Data Security Standards (e.g., ISO 27001)
• Usage: Understanding the implications of data security standards for product architecture and feature design, ensuring that security is baked in from the start, especially for sensitive research data.

Essential Prerequisites

• Demonstrable experience leading product development for a specific feature or small product, from concept to launch.
• Proven ability to mentor and guide junior team members, with examples of their growth under your guidance.
• Strong track record of influencing cross-functional teams without direct authority, achieving consensus on complex issues.
• Experience defining and managing a product backlog for a development team, including prioritisation and trade-off decisions.
• A solid understanding of the R&D lifecycle and the unique challenges of developing products in a research-heavy environment, or equivalent experience in a highly technical domain.

Career Pathway Context

To step into this Lead role, you won't just have been 'doing' product development; you'll have been 'leading' it, even if informally. We're looking for someone who has already taken ownership, made tough calls, and helped others grow. This isn't your first rodeo when it comes to shipping features.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: AI-Powered Product Discovery & Ideation
• Why: AI is getting incredibly good at synthesising vast amounts of data—user feedback, market trends, scientific papers—to identify unmet needs and even suggest novel product ideas. Product teams that use this will be faster and more innovative.
• Concepts: [{'concept_name': 'Generative AI for Idea Generation', 'description': 'Using LLMs to brainstorm features, user stories, and even entire product concepts based on prompts and data inputs.'}, {'concept_name': 'Predictive Analytics for Market Trends', 'description': 'Employing AI to forecast market shifts and user needs before they become obvious, informing proactive product development.'}, {'concept_name': 'AI-Driven User Feedback Clustering', 'description': 'Automatically grouping and prioritising user feedback themes at scale, beyond simple keyword searches.'}, {'concept_name': 'Ethical AI in Product Design', 'description': 'Understanding and mitigating biases in AI-generated insights and ensuring responsible use of AI in product features.'}]
• Prepare: This month: Experiment with ChatGPT/Claude to brainstorm product ideas for a current challenge. See what it comes up with.
• Next quarter: Identify a dataset of user feedback or market research. Try using an AI tool to summarise and find patterns.
• Month 3-6: Take an online course on prompt engineering for product management or AI ethics in product development.
• Month 6-12: Lead a small internal project to pilot an AI tool for competitive analysis or feature ideation.
• QuickWin: Start using AI to draft initial user stories or summarise long research papers today. It's a low-risk way to get comfortable.
• Skill: Advanced Data Storytelling & Visualisation
• Why: As data becomes more complex, the ability to translate intricate R&D insights into clear, compelling narratives for non-technical audiences is paramount. A great model is useless if no one understands its implications.
• Concepts: [{'concept_name': 'Narrative Structure for Data', 'description': 'Crafting a clear beginning, middle, and end for data presentations, leading the audience to a specific conclusion or action.'}, {'concept_name': 'Visualisation Best Practices for R&D', 'description': 'Choosing the right chart types for scientific data, avoiding misleading visuals, and optimising for clarity and impact.'}, {'concept_name': 'Audience-Centric Communication', 'description': 'Tailoring data presentations to the specific needs and understanding of different stakeholders (e.g., engineers vs. sales vs. board).'}, {'concept_name': 'Interactive Dashboards & Tools', 'description': 'Designing and using tools like Tableau or Power BI to allow stakeholders to explore data themselves, fostering deeper understanding.'}]
• Prepare: This month: Critically review your last two presentations. Could the data story be clearer? Ask a colleague for honest feedback.
• Next quarter: Find an online course on data storytelling or advanced data visualisation (e.g., Edward Tufte's principles).
• Month 3-6: Volunteer to present a complex R&D finding to a non-technical team, focusing purely on the story and actionable insights.
• Month 6-12: Lead the creation of an interactive dashboard for a key product metric, ensuring it's intuitive and tells a clear story.
• QuickWin: Before your next meeting, sketch out the 'story' you want your data to tell. What's the headline? What's the call to action?

Advancing Technical Skills

• Skill: Advanced Product Analytics & Experimentation
• Why: Simply looking at dashboards isn't enough. As products become more complex, you'll need to design sophisticated experiments, interpret nuanced results, and make data-driven decisions that truly optimise product performance and user experience.
• Concepts: [{'concept_name': 'A/B Testing Design & Interpretation', 'description': 'Setting up robust experiments, understanding statistical significance, and avoiding common pitfalls in interpreting results.'}, {'concept_name': 'Cohort Analysis & Segmentation', 'description': "Tracking user behaviour over time for specific groups, identifying trends, and understanding different user segments' needs."}, {'concept_name': 'Funnel Optimisation', 'description': 'Identifying drop-off points in user journeys and designing interventions to improve conversion and engagement.'}, {'concept_name': 'North Star Metric Definition', 'description': 'Defining the single, most important metric that drives long-term product success and aligning all efforts towards it.'}]
• Prepare: This month: Deep dive into our current analytics platform. Can you set up a new custom event or a complex funnel?
• Next quarter: Read 'Trustworthy Online Controlled Experiments' by Kohavi, Tang, and Xu. It's the bible for A/B testing.
• Month 3-6: Propose and lead an A/B test for a feature in your product area, from hypothesis to analysis and recommendation.
• Month 6-12: Take an advanced course on product analytics or experimentation, focusing on practical application.
• QuickWin: Identify one key user journey in your product. Map out its current conversion rate and brainstorm 2-3 ways to improve it, even if you don't implement them yet.
• Skill: Technical Depth in R&D Domains
• Why: As a Lead, you'll need to speak the language of our scientists and engineers more fluently. A deeper understanding of the underlying scientific principles or engineering constraints will make you a much more effective product leader.
• Concepts: [{'concept_name': 'Core Scientific Principles', 'description': 'A deeper understanding of the scientific fields relevant to our R&D (e.g., biology, chemistry, physics, data science methodologies).'}, {'concept_name': 'Software Architecture Patterns', 'description': 'Familiarity with common architectural choices and their implications for scalability, maintainability, and feature development.'}, {'concept_name': 'Data Modelling & Database Concepts', 'description': 'Understanding how data is structured and stored, and the impact of these choices on product functionality and performance.'}, {'concept_name': 'API Design & Integration', 'description': 'Knowledge of how different systems communicate and the principles of designing robust and usable APIs for product features.'}]
• Prepare: This month: Spend an hour each week talking to an engineer or scientist about their current challenges and technical decisions.
• Next quarter: Pick one core technical component of our product and try to understand its architecture and limitations in detail.
• Month 3-6: Read a foundational book or take an online course on a specific scientific domain or software engineering concept relevant to our R&D.
• Month 6-12: Actively participate in architectural discussions, offering product insights and challenging technical assumptions where appropriate.
• QuickWin: Ask an engineer to walk you through a recent technical design document. Don't be afraid to ask 'stupid' questions – that's how you learn.

Education Requirements

• Level: Minimum
• Req: A Bachelor's degree (or equivalent OFQUAL Level 6 qualification) in a scientific, engineering, computer science, or a related technical field.
• Alts: We're pragmatic. If you've got 10+ years of demonstrable, hands-on experience in product development within a highly technical or R&D-focused environment, with a portfolio of successful product launches, we're happy to consider that in lieu of a degree. Proven results speak louder than certificates.
• Level: Preferred
• Req: A Master's degree (OFQUAL Level 7) in a relevant scientific discipline, Product Management, or a related technical field. This shows a deeper theoretical grounding.
• Alts: Relevant industry certifications (e.g., Certified Scrum Product Owner, SAFe Product Owner/Product Manager) combined with extensive practical experience can also be a strong plus.

Experience Requirements

You'll need roughly 8-12 years of progressive experience in product development, with at least 3-5 years specifically in a senior or lead capacity. This should include demonstrable experience owning a product backlog, driving feature development from concept to launch, and ideally, some experience mentoring junior team members. Experience in a Research & Development or highly technical product environment is pretty essential here; we're not looking for someone who's only built consumer apps.

Preferred Certifications

• Cert: Certified Scrum Product Owner (CSPO)
• Prod: Scrum Alliance
• Usage: Demonstrates a solid understanding of Agile principles and the Product Owner role, which is crucial for managing our development teams effectively.
• Cert: SAFe Product Owner/Product Manager
• Prod: Scaled Agile, Inc.
• Usage: Useful if you've worked in larger, scaled Agile environments, showing you can navigate complex organisational structures.
• Cert: Professional Scrum Product Owner (PSPO)
• Prod: Scrum.org
• Usage: Another strong certification for validating your Scrum Product Owner knowledge, often seen as more rigorous by some.
• Cert: Product Management in AI/ML
• Prod: Various (e.g., Coursera, Udacity)
• Usage: Given the increasing role of AI in R&D, specific training in product managing AI/ML features would be a significant advantage.

Recommended Activities

• Regularly attend industry conferences (e.g., Product-Led Summit, Mind the Product) to stay current on best practices and network with peers.
• Participate in online communities or forums dedicated to product management or R&D innovation, sharing your insights and learning from others.
• Read key product management books and publications (e.g., 'Inspired' by Marty Cagan, 'Continuous Discovery Habits' by Teresa Torres).
• Seek out opportunities to mentor junior product professionals, as teaching often deepens your own understanding.
• Actively contribute to internal knowledge sharing sessions, perhaps by presenting on a new tool or methodology you've explored.

Career Progression Pathways

Entry Paths to This Role

• Path: Senior Product Development Assistant (L3)
• Time: 3-5 years
• Path: Technical Lead (Engineering background)
• Time: 5-7 years
• Path: Research Scientist / Analyst (Product-focused)
• Time: 6-9 years

Career Progression From This Role

• Pathway: Product Development Manager (L5)
• Time: 3-5 years

Long Term Vision Potential Roles

• Title: Director of Product Development (L6)
• Time: 5-8 years from Lead
• Title: Chief Product Officer (CPO) (L7)
• Time: 10-15 years from Lead
• Title: Head of Innovation / R&D Strategy
• Time: 8-12 years from Lead

How Zavmo Delivers This Role's Development

DISCOVER Phase: Skills Gap Analysis

Zavmo maps your current competencies against all requirements in this job description through conversational assessment. We evaluate your foundation skills (communication, strategic thinking), functional skills (CRM expertise, negotiation), and readiness for career progression.

Output: Personalised skills gap heat map showing strengths and priorities, estimated time to competency, neurodiversity accommodations.

DISCUSS Phase: Personalised Learning Pathway

Based on your DISCOVER results, Zavmo creates a personalised learning plan prioritised by impact: foundation skills first, then functional skills. We adapt to your learning style, pace, and neurodiversity needs (ADHD, dyslexia, autism).

Output: Week-by-week schedule, each module linked to specific job responsibilities, checkpoints and milestones.

DELIVER Phase: Conversational Learning

Learn through conversation, not boring modules. Zavmo uses 10 conversation types (Socratic dialogue, role-play, coaching, case studies) to build competence. Practice difficult QBR presentations, negotiate tough renewals, and handle churn conversations in a safe AI environment before facing real clients.

Example: "For 'Stakeholder Mapping', Zavmo will guide you through analysing a complex enterprise account, identifying key decision-makers, and building an engagement strategy."

DEMONSTRATE Phase: Competency Assessment

Zavmo automatically builds your evidence portfolio as you learn. Every conversation, practice scenario, and application example is captured and mapped to NOS performance criteria. When ready, your portfolio supports OFQUAL qualification claims and demonstrates competence to employers.

Output: Competency matrix, evidence portfolio (downloadable), qualification readiness, career progression score.