Product Manager Portfolio
Product-minded operator who turns ambiguous workflows into clear product decisions.
I am Ryan Humphrey, an operations and growth leader moving into product management with a track record of identifying user friction, validating problems through workflow data, defining tradeoffs, building tools, and shipping systems that teams can adopt.
DesignIntent
PriceConfidence
BuyCommit
ProduceHandoff
Discoveryfinding the highest-leverage customer and operator pain points
Strategychoosing scoped solutions with clear tradeoffs and success criteria
Executionturning workflows, data, and constraints into usable product systems
Iterationmonitoring adoption, feedback, and quality after launch
Selected Product Work
Case studies framed around problem selection, tradeoffs, and outcomes.
Commerce SystemsActive build
Blanq MFG self-serve print ordering
Blanq MFG had demand signals, but the customer path still moved from design to quote instead of design to buy. I reframed the opportunity around removing the wait, interpretation, and pricing uncertainty between a buyer's intent and a production-ready order. The first product bet is a focused self-serve flow with clearer pricing, a narrower catalog, and cleaner handoffs for the shop.
Transparent pricingStructured order dataProduction handoff
View decision path
Problem
The existing journey helped customers start a design conversation, but it did not give them a reliable path to purchase.
Users
Buyers needed price confidence and fewer handoffs; the shop needed complete, production-ready order data.
Signals
Delayed responses, abandoned inquiries, missed opportunities, and customer frustration pointed to a conversion problem.
Focus
I focused on repeatable order types where pricing and production rules could be clear enough for self-serve purchase.
Options
I considered better garment lookup, vendor data access, manual quote improvements, and self-serve ordering.
Decision
Self-serve ordering was the strongest path from design-to-quote to design-to-buy.
Outcome
The goal is to make online ordering a viable revenue channel while reducing quoting drag and improving production handoffs.
PM signal
Shows product judgment across the full funnel: demand capture, pricing clarity, buyer UX, and fulfillment readiness.
AI DiscoveryPrototype in validation
Ask the Sommelier recommendation engine
Ask the Sommelier packages expert wine guidance into an experience guests can use when staff expertise is not immediately available. The goal is not to replace hospitality, but to make the restaurant’s knowledge easier to access, apply, and trust. The product uses guided inputs and curated recommendation logic to improve confidence, pairing quality, and order value.
Guided inputsPairing logicGuest confidence
View decision path
Problem
Guests often need help translating preferences, food pairings, and occasion into a confident wine choice.
Users
The guest is the primary user; the restaurant benefits through better engagement, pairing quality, and wine attach rate.
Signals
The opportunity was the gap between what the restaurant knows and what guests can use at the moment of decision.
Focus
I prioritized recommendation quality and trust before expanding into a broader wine education tool.
Options
Options included a static pairing menu, staff guide, simple filters, or a guided recommendation flow.
Decision
A guided flow best matched the user need because guests needed interpretation, not just information.
Outcome
The goal is faster decisions, stronger pairing quality, and higher order value while preserving trust in the sommelier's expertise.
PM signal
Shows how domain expertise can become a guided product experience with clear user value and revenue upside.
Trust & FeedbackPilot in use
Closed-loop reputation management
The reputation system creates a private feedback path before customer sentiment turns into a missed recovery moment or unmanaged public review. It gives guests a simple way to be heard while giving management a structured queue for triage, follow-up, and learning. Positive feedback can become public-facing social proof, while negative feedback becomes an operating signal.
Private captureRating breakdownApproval workflow
View decision path
Problem
Feedback was reaching the restaurant too late or too publicly to support consistent service recovery.
Users
Guests needed a simple way to be heard; managers needed a structured queue for review and action.
Signals
The key insight was that feedback collection only matters if it becomes a recovery and learning loop.
Focus
I focused first on controlled routing and manual review before adding heavier automation.
Options
Options included public response management, private surveys, manual tracking, and closed-loop routing.
Decision
A closed loop gave management a way to recover poor moments and selectively amplify positive ones.
Outcome
The goal is faster recovery, clearer operational learning, and stronger public-facing proof from positive reviews.
PM signal
Shows closed-loop product thinking: capture feedback, route action, recover service, and turn wins into public trust.
Internal ToolsLive operations tool
Catering workflow and label automation
The catering platform turned an inconsistent manual process into a repeatable internal tool for quoting, invoicing, prep, and labeling. I treated recurring order issues as a product design problem: the workflow needed to make accuracy easier for every team involved. The shipped tool standardized the employee experience, which improved speed, reduced mistakes, and created a more consistent guest experience.
View decision path
Situation
Catering orders depended on inconsistent templates and manual coordination across managers, kitchen staff, and front-of-house teams.
Goal
The goal was to make quoting, invoicing, prep, and labeling easier to execute consistently.
Approach
I built an Excel/VBA tool around order history, tax rules, menu pricing, prep needs, and customer records.
Tradeoff
I kept payment capture outside the tool so the workflow could improve accuracy without disrupting existing revenue controls.
Result
The shipped workflow sped up invoicing, reduced order errors, cleaned up handoffs, and added visibility for high-value catering requests.
PM signal
Shows operational product thinking: improve the employee workflow first to create faster, more consistent customer outcomes.
PM Fit
How this background maps to product management work.
My work sits at the intersection of customer empathy, operational systems, data-informed prioritization, and hands-on execution. The throughline is PM judgment: choosing the right problem, defining why it matters now, and shipping a focused path to measurable impact.
Product discovery
Starts with workflow observation, customer friction, service gaps, and operational constraints before defining the product surface.
Prioritization under constraints
Uses team capacity, data availability, margin logic, adoption risk, and implementation cost to choose the next best version.
Cross-functional execution
Turns customer needs into usable systems by aligning business goals, operational workflows, technical constraints, and frontline realities.
Outcome orientation
Defines success around conversion, cycle time, service recovery, recommendation quality, adoption, and operational reliability.
How I Work
How I move from ambiguity to shipped decisions.
- Define the user problem.Identify where customers, operators, or teams are losing time, trust, money, or clarity.
- Validate with evidence.Use workflow observation, customer feedback, operational data, and constraints to confirm what matters.
- Choose a scoped solution.Compare options, name tradeoffs, define success criteria, and ship a focused first version.
- Ship for adoption and learning.Design around real users, monitor quality, and iterate based on behavior after launch.
Next Step
Ready to bring operator-grade product judgment to PM teams.
Based in Las Vegas and actively pursuing product management and operations leadership roles where customer insight, systems thinking, AI fluency, and cross-functional execution matter.