I combine analytical product thinking with hands-on delivery: understand the problem, choose a direction and learn from what ships.
01
Understand
Combine user needs, product signals and business context to define the problem.
OutputProblem brief
02
Prioritize
Choose a testable hypothesis using evidence, expected value and delivery constraints.
OutputA testable priority
03
Deliver
Align stakeholders and work with the team to ship a focused change.
OutputFocused improvement
04
Learn
Measure the result, check the assumptions and decide what to do next.
OutputNext decision
Learning feeds the next priority
Working process: understand, prioritize, deliver and learn. Feed the learning back into prioritization.
Product Metrics
Funnel Analysis
User Research
Competitor Research
Hypothesis Validation
A/B Testing
Roadmapping
02 /Selected growth impact
What changed. Where it mattered.
Selected results from my Product Manager role at NDA / iGaming, 2024–2026.
Product growth
Conversion & transactions
+12%
Conversion uplift
Identified a high-performing product section and initiated its prioritization and visibility.
~50
Additional successful transactions / month
Identified and resolved a hidden, critical issue in the transaction funnel.
Operational efficiency
Time & processing
~40
FTE hours saved / month
Reduced operational workload by driving resolution of a high-impact business issue.
18%
Faster request processing
Aligned business requirements, KPIs and priorities for an internal CRM workflow.
Discovery & delivery
Work volume · not business outcomes
110+
Product ideas generated & validated
Built a strong backlog of opportunities for future product improvements.
73+
Tasks in the 2026 roadmap
Translated research and analysis into a structured roadmap aligned with business goals.
Reported career results. Approximate figures retain their original qualifiers; they are separate from the independent studies below.
03 /Independent product research
The thinking behind the proposal.
Three studies showing how I frame a problem, choose a first move and define what to learn.
Danske Bank
Banking · Self-service
Make everyday banking clearer
Independent research. No internal data. Recommendations not implemented.
Problem
Customers can struggle to obtain the right statement or understand a payment status, creating avoidable support work.
Read product reasoning
Evidence
Public documentation and user-reported friction. Exports, PIN viewing and spending categories already exist; discoverability and clarity are the questions.
Proposed solution
Improve statement selection, PIN recovery guidance and transaction timelines so customers can finish tasks with less uncertainty.
First / later
First: audit support reasons and test these three service flows. Defer PIN-change infrastructure, dynamic CVV and P2P extensions until feasibility and costs are validated.
How I would test it
Proposed checks: task completion and avoidable contacts per completed task. Validate incremental value, security and actual cost reductions before treating freed capacity as savings.
Source: proposal and evidence appendix, PDF pages 3–13 and 16–19.
Limitations
No authenticated app walkthrough. Financial figures in the PDF are illustrative scenarios; feature variants, costs and demand need validation.
Independent research. No internal data. Recommendations not implemented.
Problem
Buyers, sellers and service customers share a generic B2B enquiry path, leaving needs unclear and adding sales follow-up.
Read product reasoning
Evidence
The research identifies one generic B2B page and form. Its journey review flags unclear routing, phone-field friction and gaps in buyer reassurance—not measured drop-off.
Proposed solution
Offer four intent paths: buy, sell, repair and IT lifecycle / ESG. Use email-first contact, an optional phone field and relevant, verifiable trust information.
First / later
First: segment intent, simplify the form, add verified trust signals and instrument the funnel. Next: bulk valuation and routing. Validate demand before building a buyback calculator.
How I would test it
Proposed checks: form completion by intent, qualified-lead rate, time to quote and sales follow-up effort. Compare against a measured baseline, not the mockup figures.
Source: journey proposals and prioritisation, PDF pages 2–8.
Limitations
No funnel baseline or buyer interviews in the supplied study. Mockup prices, customer examples and compliance claims require verification.
Independent research. No internal data. Recommendations not implemented.
Problem
Deskless employees may miss schedule changes; managers then spend time reminding people and coordinating across channels.
Read product reasoning
Evidence
The presentation reviews scheduling, shift bids, company information and email screens. It frames adoption and coordination problems as hypotheses, without usage or incident data.
Proposed solution
Make shift changes explicit through notifications and a “what changed” view; reduce access friction and bring schedules into employees’ calendars.
First / later
First: validate change visibility, biometric login and calendar sync. Next: contextual shift chat and role-based onboarding. Defer payroll validation, an integration marketplace and recognition features.
How I would test it
Proposed checks: time to notice a change, successful shift coordination and manager follow-up effort. Monitor notification fatigue, login failures and retention in a pilot.
Source: workflow concepts and prioritisation, PDF pages 2–8.
Limitations
Feature availability, role permissions and platform constraints need checking. The study provides no baseline proving missed shifts or a retention effect.