Hey Buffer,
I want to be your next Senior Product Designer
Hey Buffer,
I want to be your next Senior Product Designer
Hey Buffer,
I want to be your next Senior Product Designer

I'm Ryan Shumway
Designing web and mobile apps for startups and small businesses since 2017. I'm an async Figma wizard that's built 3 design systems and thousands of prototypes.

I'm Ryan Shumway
Designing web and mobile apps for startups and small businesses since 2017. I'm an async Figma wizard that's built 3 design systems and thousands of prototypes.

I'm Ryan Shumway
Designing web and mobile apps for startups and small businesses since 2017. I'm an async Figma wizard that's built 3 design systems and thousands of prototypes.



Why I'm a good fit for you:
Why I'm a good fit for you:

General: I have over 5 years of experience as a product designer going from 0 to 1 on a number of products, mobile apps, and web apps.
Process: I've been doing a number of UX processes from start to finish like wireframing, fat marker sketching on paper and in FigJam, qualitative interviews, return and report presentations, user journey mapping, heuristic testing, prototyping, …. you get the point.
Problem Solving: I heavily lean on feedback and data to make my decisions—without input I feel stuck and don't want to waste my time or company money.

General: I have over 5 years of experience as a product designer going from 0 to 1 on a number of products, mobile apps, and web apps.
Process: I've been doing a number of UX processes from start to finish like wireframing, fat marker sketching on paper and in FigJam, qualitative interviews, return and report presentations, user journey mapping, heuristic testing, prototyping, …. you get the point.
Problem Solving: I heavily lean on feedback and data to make my decisions—without input I feel stuck and don't want to waste my time or company money.

General: I have over 5 years of experience as a product designer going from 0 to 1 on a number of products, mobile apps, and web apps.
Process: I've been doing a number of UX processes from start to finish like wireframing, fat marker sketching on paper and in FigJam, qualitative interviews, return and report presentations, user journey mapping, heuristic testing, prototyping, …. you get the point.
Problem Solving: I heavily lean on feedback and data to make my decisions—without input I feel stuck and don't want to waste my time or company money.
Interaction Design: I lean on Design System components in Figma to help me build quick and consistent, effective flows every time.
Visual Design: Relying on a beautiful design system means I can build visually engaging and delightful interfaces!
Technical: Since I have gone above to learn to code, I'm aware of web constraints, and these influence my designs.
Collaboration: I have worked remote for almost 4 years, where collaboration daily was the expectation. Daily slack huddles for a few hours weren't surprising to me.
Drag and Drop component video I built for Graphite
Let's schedule a call:
Let's schedule a call:
Let's schedule a call:

Communication: I've been presenting my work to stakeholders at all levels for 5+ years. Also, I occasionally publish my tech experience to a blog: Tech Trailblazer.
Business: I've been involved in product strategy with executive stakeholders since the early days—plus I'm an entrepreneur at heart. I get that there are business objectives, and my design work needs to move the needle on revenue.
Work Standards: I'm always trying to learn and improve—I regularly buy books and courses to improve my mental health, my professional skills, etc.
Other: See a few of my case studies (below) showcasing my process from start to finish, how I problem solve, and what metrics I focused on for each problem.
Fun Fact: I use Figma and FigJam all the time for personal and professional work.
Funner Fact: I'm hoping you've read to this point, so if you have, your'e a real winner.

Communication: I've been presenting my work to stakeholders at all levels for 5+ years. Also, I occasionally publish my tech experience to a blog: Tech Trailblazer.
Business: I've been involved in product strategy with executive stakeholders since the early days—plus I'm an entrepreneur at heart. I get that there are business objectives, and my design work needs to move the needle on revenue.
Work Standards: I'm always trying to learn and improve—I regularly buy books and courses to improve my mental health, my professional skills, etc.
Other: See a few of my case studies (below) showcasing my process from start to finish, how I problem solve, and what metrics I focused on for each problem.
Fun Fact: I use Figma and FigJam all the time for personal and professional work.
Funner Fact: I'm hoping you've read to this point, so if you have, your'e a real winner.

Communication: I've been presenting my work to stakeholders at all levels for 5+ years. Also, I occasionally publish my tech experience to a blog: Tech Trailblazer.
Business: I've been involved in product strategy with executive stakeholders since the early days—plus I'm an entrepreneur at heart. I get that there are business objectives, and my design work needs to move the needle on revenue.
Work Standards: I'm always trying to learn and improve—I regularly buy books and courses to improve my mental health, my professional skills, etc.
Other: See a few of my case studies (below) showcasing my process from start to finish, how I problem solve, and what metrics I focused on for each problem.
Fun Fact: I use Figma and FigJam all the time for personal and professional work.
Funner Fact: I'm hoping you've read to this point, so if you have, your'e a real winner.
I sound like a good fit huh? See for yourself
I sound like a good fit huh? See for yourself
I sound like a good fit huh? See for yourself
Share a time when you were wrong about something:
Oh boy, where to do I begin? Two (of many) experiences come to mind:
Qualitative interviews: In the beginning of my career, I really sucked at doing these interviews, because I struggled to listen to what the customer / user was actually saying—I had my prepared list of questions because I thought I knew what feature we were going to build. I didn't actually listen.
The outcome? Missed opportunities to build the right thing at the right time—if I were listening, I would have discovered products users wanted instead of what my team and I thought they wanted.
What did I learn? Listening is key; be flexible enough to let the conversation go a different way than you anticipated—it pays dividends (sometimes literally) to be curious.
Product Market Fit: In my current position at Nerd United, my team and I have a solution, and we've been trying to apply it to a problem. I made the assumption that we had validated that this product was what users wanted. (I was wrong). My team hadn't done any user interviews, or smoke screen tests, or thrown a website together.. nothing.
The Outcome? Our team has had to downsize (laying off staff) because we're still not at product market fit. I should have begun validating and researching right away instead of assuming my team had already done the work before hiring me.
What did I learn? Always ask to see the research, the proof, the testimonials from future buyers.
Share a time when you were wrong about something:
Oh boy, where to do I begin? Two (of many) experiences come to mind:
Qualitative interviews: In the beginning of my career, I really sucked at doing these interviews, because I struggled to listen to what the customer / user was actually saying—I had my prepared list of questions because I thought I knew what feature we were going to build. I didn't actually listen.
The outcome? Missed opportunities to build the right thing at the right time—if I were listening, I would have discovered products users wanted instead of what my team and I thought they wanted.
What did I learn? Listening is key; be flexible enough to let the conversation go a different way than you anticipated—it pays dividends (sometimes literally) to be curious.
Product Market Fit: In my current position at Nerd United, my team and I have a solution, and we've been trying to apply it to a problem. I made the assumption that we had validated that this product was what users wanted. (I was wrong). My team hadn't done any user interviews, or smoke screen tests, or thrown a website together.. nothing.
The Outcome? Our team has had to downsize (laying off staff) because we're still not at product market fit. I should have begun validating and researching right away instead of assuming my team had already done the work before hiring me.
What did I learn? Always ask to see the research, the proof, the testimonials from future buyers.
Share a time when you were wrong about something:
Oh boy, where to do I begin? Two (of many) experiences come to mind:
Qualitative interviews: In the beginning of my career, I really sucked at doing these interviews, because I struggled to listen to what the customer / user was actually saying—I had my prepared list of questions because I thought I knew what feature we were going to build. I didn't actually listen.
The outcome? Missed opportunities to build the right thing at the right time—if I were listening, I would have discovered products users wanted instead of what my team and I thought they wanted.
What did I learn? Listening is key; be flexible enough to let the conversation go a different way than you anticipated—it pays dividends (sometimes literally) to be curious.
Product Market Fit: In my current position at Nerd United, my team and I have a solution, and we've been trying to apply it to a problem. I made the assumption that we had validated that this product was what users wanted. (I was wrong). My team hadn't done any user interviews, or smoke screen tests, or thrown a website together.. nothing.
The Outcome? Our team has had to downsize (laying off staff) because we're still not at product market fit. I should have begun validating and researching right away instead of assuming my team had already done the work before hiring me.
What did I learn? Always ask to see the research, the proof, the testimonials from future buyers.
Drag and Drop component video I built for Graphite


Gif Example I included when handing off components to developers


I led the redesign of Mango's brand, which impacted the web and mobile app.