Product Management: Big Tech vs Startups

Image taken from AppFutura

Roles and Responsibility

Rakuten

  • I am part of a 15 member product team, the entire team size is 100+!
  • We are working on a new service for the Rakuten Travel platform, which is one of the 70+ services integrated into the Rakuten ecosystem
  • As a PM, I handle the end-to-end experience of some features of our consumer app (like translation, guest reviews, coupons, notifications), I also do any other task that might be needed to release our products or manage our processes.

mymizu

  • At the time of joining, I was the only product person in a tech team of 3~4
  • mymizu’s tech offering includes a mobile app, internal tools as well as a B2B product, all integrated around the mymizu API
  • As a PM, I do everything from defining the mission, managing the backlog, hiring new members, alongside also doing all the usual work of a PM

Team and Mentorship

Big Tech

  • Usually, in big tech, your team would have many experienced Product Managers as well as domain experts. It’s easy to reach out to someone to ask for help and get advice or knowledge on different situations.
  • You will have dedicated Product people as your managers who will work on helping you improve your Product skills along with generally skilling up as a member of the team
  • There are many other Product people you could speak to laterally in the company to widen your perspectives, get advice or just for the purpose of networking and friendship.

Startup

  • Basically, you're mostly on your own. A lot of things you will learn will be based on experimentation and trial and error.
  • Since your managers would be either in the executive team or equally busy as you, most of your learning and development will come by yourself. A lot more reflection needs to be done since maybe no one can tell you exactly what you should work on to improve yourself.
  • However, the kind of learning and motivation you may get from your founders, external mentors, and team members is unparalleled in a startup!

Processes

Big Tech

  • Many processes have already been established for all types of activities.
  • There is lots of documentation outlining processes and its easy to go down a rabbit hole of information, which could lead to answers to many of your questions
  • Sometimes the processes and documentation could be outdated, unnecessary, and slow down the output

Startup

  • Usually, a startup doesn't have the time and bandwidth to create processes, many times this can be chaotic for stakeholder sync.
  • However, it also means that you have the freedom to build your own processes and switch quickly as you please
  • This could mean a lot of learning, forgetting, re-learning. (example, the whole team decided to shift to Notion from Google Drive)

Risk

Big Tech

  • Big tech companies have a reputation to maintain. so their tolerance for risk is relatively low
  • In many cases, they would prefer to delay launching rather than compromise on the quality, they may also have to plan for internal audits and checks as part of the release criteria
  • This space to delay also provides a safety net and the large organization is able to absorb mistakes or misfires very easily, without any consequences
  • Timelines for projects are well defined and scope is usually fixed

Startup

  • The idealogy in a startup is to always release first, and then fix later as needed
  • Speed is prioritized since getting core user feedback is extremely important as the product is new
  • Mistakes are usually made in public and need to be handled in public as well
  • Timelines are usually very tight, and scope could change very often based on external factors

Resources

Big Tech

  • Big tech usually has relatively higher budgets and resources to spend on product development
  • There is also usually a lot of specialized human resource as well, across different functions
  • A job in big tech is relatively stable, and usually, employees would stick around for a longer time, making it easier to work on longer-term projects
  • If there is any loss of revenue, it can be absorbed by other profitable services within the same company.

Startup

  • It's highly possible that there is an irregular flow of revenue in a startup
  • Human resource is also hard to find and retain, startups are still considered risky for many people to forego their job and work full time for
  • It's important to optimize the output and outcome with the limited resources that are present, which means lots of creative thinking and prioritization

Idea buy-in

Big Tech

  • To have your idea pushed, you may have to go through multiple levels of hierarchies and approvals
  • Ideas may get lost or altered in the chain of command

Startup

  • If you have trust and a good relationship with the founders, idea buy-in can be instant

--

--

--

I like to write about Product, Tech, Culture, and anything else I can think about

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Skills for a new Product Manager

How to structure the backlog to make it work

All You Need to Know About Product Management in Ten Videos

Product Management… What exactly is that?

Mindset of PM and Developer

How Scrum Accelerates Collaborative Learning in Teams

Product Management for Startups: Zero to One

Aaron Airmet — Product Advice For My Younger Self

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Tanmay Goel

Tanmay Goel

I like to write about Product, Tech, Culture, and anything else I can think about

More from Medium

3 Reasons Why Product Managers FAIL (every CEO should know that)

Why being a Product Manager is the hardest role I played in my career

Product Management Resources

10 killer questions to ask in your next Product Manager interview at a startup