Gina Doyle
@gdoyle
📞 You've reached my README!
I created this to help you get to know me, how I work, why I enjoy working with others, and hopefully somewhere along the way, help build some comfort in wanting to connect.
@gdoyle
This README was inspired by Austin Regnery's.
Hi, I'm Gina 👋 👩🏻
Some personal things...
- I use she/her pronouns.
- I currently live in Uxbridge, MA with my partner. No dog yet, but hopefully one day
🐶 ! - I've been in
🇺🇸 Massachusetts my whole life, as I grew up in Hopkinton, and then studied Human Factors Engineering (also called Engineering Psychology) at Tufts University. I also played on the Women's basketball team at Tufts🏀 .👉 Fun fact: I played against one of Randy Moss's daughters at the 2016 NCAA championship🍾 . - I enjoy staying active still, usually doing some form of high intensity interval training, like CrossFit
🏋🏻 , or anything outdoor if it's warm.
Now onto work...
- I'm a Product Design Manager for the Create team
🧑🏻💻 . I transitioned to this position after being a Senior Product Designer with the Fleet Visibility team in the Runner Group. I started at GitLab in July of 2021. -
Collaboration
🤝 has always been a priority for me at work. It's something I learned from playing sports with a team all my life. You'll see that in a lot of the work I do, such as sharing designs early and often, leading the Tufts University capstone project for the UX department, and consistently asking for feedback and making time to give others feedback if they ask. - I'm familiar with designing for developers with technical use cases because of my previous work at Red Hat where I worked on OpenShift. If you have questions about Runner, reach out!
🛑 Beware: I'm certainly not an expert, I may not know the answer, but I can point you to those who are😊 . - I really enjoy mentoring students who are interested in UX, no matter the age. I've had experience running UX programs with high school students as well as college students.
Personal principles
- The outcome should always result in helping someone.
- Other ideas to solve problems are not just welcomed, they're seeked. Same with feedback!
- Set goals that are realistic, but be relentless to succeed.
- Quality over quantity.
- When it comes to pitching an idea, bring the data.
- Accept failures and mistakes, learn from them, and use them to be better.
My working style
- I prefer to work async-first always, unless there is a topic to brainstorm on, where I'll typically reach out to team members and see if they'd be comfortable with a sync session.
- I take pride in my organization skills, and therefore am almost always editing issue descriptions, organizing epics, and updating my priorities list. I'm impatient when it comes to cleaning up issues, but I will make sure to loop DRIs in when I do.
📝 Please help me with organizational efforts! - When a new problem appears, I always start with data. Even if one customer meeting talks about an issue, I want to make sure that problem is validated before moving it through the product development flow.
- A big reason why I joined GitLab was because of the opensource handbook, documented processes, and collaboration and contribution practices. Because of that, I am a stickler for process. The work I take on will always have a documented process at it's core. With that said, if something isn't working, tell me! I am open to change if there's enough data to back it up (are you seeing the trend yet?
📈 ).
Personal projects
View all- Loading