How do corporates and startups approach product? - Innovify

How do corporates and startups approach product?

I have worked with both corporates and startups as the product guy and there are a lot of difference in the way how it is done at each. I have tried to summarize it in the following table. Please note that there is no clear demarcation between the approaches highlighted but they are more inclinations.

ITEM
CORPORATES
STARTUPS
1.Identifying the need of a new productTypically, they would have the strategic team deciding to develop a new product. However, before they decide, they will conduct a large scale market research, strategic planning, user research, etc.Typically, the founders experience the need themselves and they perform a basic research before deciding to develop a new product.
2.InitiationHaving identified the need, they would then start planning for it before a full-fledged development. A product manager would be appointed and he would be tasked to create a business case for the new product.Entrepreneur either start doing it themselves with support from their network. No detailed business case is done, but a basic research and analysis is done to assess if it is worthwhile to pursue the opportunity.
3.ApprovalA strategic committee would either approve the development or not depending on business case and their business priorities.There is no committee. It’s the founder and his founding team, if there is one, makes the decision quickly.
4.MVPMany old style corporate don’t have the concept of MVP. Once approved, they just want to get the product done completely. Even their MVPs are more like finished products.MVP is very important for startup. They build the MVP, conduct the user research and then improve on it or pivot.
5.InnovationLow. Many corporate do produce a lot of innovative products. However, they do spend a lot of resources on it.High. Startups by definition needs to be highly innovative. It doesn’t need to be technical innovation, but could be service or business model. Unlike corporates they have less resources to spend and thus the innovation output has to be higher, much higher. If they are not innovative, they would not succeed.
6.PivotingNot often and not much.As, when and as much as is required until the product is accepted by the market.
7.ScrappingCorporate are more comfortable to scrap the product as they have a portfolio of products to select from.Startups typically have one or a very few products and hence scrapping the project is not really an option. Instead they pivot.
8.MethodologyMore waterfall, although there are highly agile org. They still have a lot of waterfall style governance and gates.Mostly agile with little governance and gates.
9.Risk AttitudeConservativeAggressive
10.MeasurementsMore data less intuition. A large number of metrics are captured to create a number of reports and dashboards as the measure of success or failure.More intuition than data. Only the required metrics are captured and measured.
11.User research and acceptanceTypically appoint agencies to do it for them. Product managers and developers don’t really engage with the end users.Founders engage directly with their users, bringing first-hand feedback to the development team.
12.Market LaunchGrand for new products, with high marketing plans.Slow and organic. A lot of word-of-mouth that aggressive marketing.
13.RolesSpecialised. Even the product managers are specialist within their domain.Masters of all. They are not just jack of all trades, but continuously mastering new skills, domains and technologies.
14.Integrations3rd party integrations are mostly with paid packages.3rd party integrations are mostly with free packages.
15.Programme ManagementCorporate typically have programmes within which the products are planned.What the hell is a programme?
16.ResponsivenessLow and slow. User feedback would go through a series of gates (customer service, 3rd level support, triage, planning, fixing, testing, release, communicate) before the addressed.High and fast. User feedback would be directly to the founders who prioritise them quickly with a faster build and release.
17.CommunicationEmails, documents, etc. Though they have scrum walls, they still rely a lot on documentation.Verbal and more face to face. Drawings all over the walls.

Related Posts