Blog
/
Current post

Motherboard Memoirs: Mfon's Internship Review

From her enthusiastic application to the successful execution of various project, Mfon Etok shares her experiences as a Product Management Analyst in Motherboard's Internship Program.

Join us in exploring her motivations, hurdles, and achievement during her time with Motherboard.

Why did you decide to apply to Motherboard?

I applied to Motherboard to use my creative mind, problem-solving skills, and passion for learning to help solve people's problems. 

What was the application and interview process like for you?

The application and interview process was quite smooth for me! I filled out the application online and then had a couple of interviews. In one of the interviews, I was given a task to write and pitch an organic-focused strategy where I got to showcase my writing and problem-solving skills and also talk about my experience. It was a great opportunity to show them why I'd be a great fit.

How did it feel to get accepted?

It was a moment of excitement and accomplishment! I was beyond thrilled and grateful for the opportunity. It felt like all my hard work and preparation had paid off. I couldn't wait to dive in.
Internship Offer Letter

What was the onboarding process like? What were your first impressions of Motherboard and the team?

The onboarding process at Motherboard was smooth and welcoming. They provided me with all the necessary information and resources to get started. My first impressions of Motherboard and the team were good! Everyone was friendly, supportive, and passionate about their work. It was such a positive environment to be in, and it made me even more excited to contribute to the company's goals. 

How did it feel to have ownership of a project?

Having ownership of a project felt both exhilarating and a little nerve-wracking at first. On one hand, it was exciting to have the opportunity to lead and make decisions. But on the other hand, I had some initial fears and worries. I was concerned about whether I would be able to meet the expectations and deliver results. However, I quickly realized that these fears were natural and part of the learning process. With proper planning and support from my colleagues, I gained confidence and overcame those worries. It was a valuable experience that helped me grow both personally and professionally.

How did it feel to work on a vision document for your project? Was it your first time doing that? Did you face any challenges along the way? 

When I worked on my first vision document, I felt excited but also unsure. It was a great opportunity to shape the direction of the project and get everyone aligned. The challenge there was ensuring that the vision document captured all the necessary details while still being concise and clear. However, I found that breaking it down into smaller sections and collaborating with others helped a lot. 
Vision document for merchant profile improvement and merchant acquisition.

If you had to work with other people in the course of your project, how was that? Any struggles or lessons learned?

I got the opportunity to work with some amazing individuals at Motherboard, and it taught me valuable lessons along the way. One of the struggles I faced was ensuring effective communication. I learned that having regular stand-up meetings helped keep everyone on the same page. 

What were the outcomes of your project?

I worked on three projects: Merchant acquisition, merchant profile improvement, and FAQ repository and knowledge base.
The Merchant acquisition project aimed to increase the number of vendors in existing and new benefit categories by 20% within a tight timeframe of 10 weeks. One unforeseen challenge was the onboarding process. Despite successfully attracting vendors interested in partnering with Motherboard, the onboarding process proved more complex than expected. This bottleneck affected the visibility and accessibility of vendors, hindering the project's impact. But, thanks to our transparent communication with the vendors, we were able to manage expectations. 
The project not only increased the number of vendors but also highlighted the need for a comprehensive onboarding strategy.
For the merchant profile improvement project, while the outcome may not have fully realized the initial goal of significantly enhancing content and profiles, the creation of robust product descriptions represents a significant step forward. These descriptions lay the foundation for future expansions and improvements, serving as a valuable resource for employees making informed decisions about the benefits offered on the platform.
Vendor product description for scoop’d (a vendor on motherboard)
Finally, for the FAQ and knowledge base repository project, the goal was to create a comprehensive and user-friendly FAQ repository and knowledge base for Motherboard, fostering a more informed and confident user community. The revamped knowledge base and targeted "how-to" articles improved the overall user experience by providing clear and accessible information. The analysis of support tickets not only addressed immediate concerns but also informed ongoing improvements, ensuring the FAQ repository remains a dynamic and responsive resource.
Knowledge base refined for easy navigation

Did you learn anything new in the course of planning and executing your project? 

I learned how to gather user feedback and use that information to shape the product's direction. I also learned to effectively communicate, prioritize tasks, and align everyone towards a common goal. I also learned how to apply agile principles, like sprints, stand-up meetings, and iterative development, to ensure the project stayed on track and responded to changing needs. 
I gained hands-on experience in different stages of the product life cycle, from ideation and planning to development, testing, and launch. I learned to adapt to unexpected changes, pivot when necessary, and embrace feedback as an opportunity for growth.

Anything else you want to share?

In reflection, the challenges I encountered as a Product Manager Associate were not roadblocks but growth opportunities. The dynamic nature of the role, coupled with the satisfaction of seeing a product evolve, made every step in this journey a rewarding experience. Thank you, Motherboard!
Subscribe to our newsletter
Get the latest HR and people management insights delivered straight to your inbox
Thank you for subscribing to our newsletter.
Oops! Something went wrong while submitting the form.