en en en tr es id en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en en ca es es ne en en kn en en en en en en en en en en en en en en en en en en en en en en en en en en en pt it it en pt en en en en en en en en en en pms en en en en en en en pt fa it en it pt it fr en it en en en en en en en it en en en it pt en en en en en ceb en en it it en en en en en en en en en en en en ia it en en de en en en en en en en en it it en pt en en en en en en en en en en en en en en en it de en en en en en en en en en en pt en en it it en az en en en en uk en en en en en en en en en en en en en en en en en en en en pt en en en en en en en en en en en en en en en en en en
Shankar Kumarasamy Application Development, Enterprises, Startups April 12, 2019April 12, 2019 4 Minutes
Unlike old days, big enterprises need to be disruptive in their products. Technology is one of the biggest pillars supporting this disruption. We call it as ‘Digital Transformation’. But truly digital transformation is nothing but bringing your products at the earliest to the customers using latest and greatest tools and technologies. Startups excel in adapting to the new trends and also are quick in adapting to the changes.
But, why do enterprises with deep pockets hesitate to adapt to these changes?
This is one of the most common questions that many ask me. Being in the information and technology industry for the past 10 years, I do not see this as hesitation but caution. The advancement in technology and the rate of change of technology comes with its own constraints.
Many a times when we talk about startups we think about the successful startups. In reality, as per recent analysis, 9 out of 10 startups fail. Big enterprises can’t put their company at risk for every single change.
What do enterprises learn from startup failures?
Trying to adapt to startup culture is not just to look at the success factors but also to learn from their failures. Now let’s see some of the most common failure reasons and what enterprises can learn from it, even before we talk about tools and technologies.
Failure reason 1 – No clearly defined use case
This is the most common startup failures. No or very little market analysis and research on the idea. Do not try to decorate your ideas with too many good to have solutions.
Learnings -Remember, your product is trying to solve the most common problem for others. Great ideas and nice to have features are good. But check whether you got a buyer for the idea. Understand whether there are other solutions similar to yours, out in the market. In that case, analyze why your solution is better or worse than theirs.
Failure reason 2 – Less focus on audience
We focus more towards building the solution technically correct but do not focus on the end user. We go beyond what actually may be needed.
Learnings – Put a boundary to your solution design. Covering all the scenarios are fine, however focus on the most common scenarios that your customer may fall into.
Failure reason 3 – Wrong product launch in the wrong market
Lack of clear understanding on the geography will lead to this situation.
Learnings – One good example is internationalization. We always think launching an web or mobile app in multiple language will reach larger audience group. It is true, but we forget about accessibility. Improving accessibility with i18n give more inclusive approach.
Failure reason 4 – Assuming that the product would live longer in the market
The product can not exist in the same form as it was launched in the market for a long time. It will have to undergo changes, however we focus on getting the perfect product during the initial launch itself without analyzing the life time of the product.
Learnings – Focus on releasing the product and get feedback from the investors, partners, customers and be ready to add or modify design based on the criticism or constructive feedback from the users.
Failure reason 5 – More focus on long term rather than short term
Lack of short term strategy and poor execution will lead to problems with products not being launched within the launch window and the product development gets dragged.
Learnings – Having a vision is definitely needed, but a vision without immediate, short-term, mid-term and long-term goals will not move the needle.
Failure reason 6 – Investing too much of yourself in every stages of the product development
Too much involvement in one activity means lack of attention in other activities of the product development.
Learnings – Whenever possible, try to crowdsource and build a prototype of your product. This saves lot of your time which can be utilized in some other areas of product development.
Failure reason 7 – Too early or Too Late to the market problem
There are chances of losing customers if we launch the product too early and we get negative reviews. Similarly, there is problem of onboarding customers if it’s too late to launch the product in the market
Learnings – Find the right balance of time and do a little market research to fix the launch window of the product.
Enterprise learnings from startup failures
Now let us analyze the common tech stack problem that we face while developing the product –
Programming language – Choosing the right programming language for your solution is crucial. When it comes to front end, it depends on the types of form factors that we are going to deliver the product. For instance, responsive web vs react native vs PWA. And with backend, it depends on the problem domain and the characteristics of the language. For instance, .NET may be well suitable for UI based web apps but we will use Python for big data analysis.
Choice of cloud service – Cloud is a preferred choice to run your backend for variety of reasons. There are multiple cloud vendors available in the market. However, based on our solution we determine the type of the service we want to utilize from the providers. For example, IaaS vs PaaS vs SaaS.
Entry and exit criteria for the cloud – As the product grows, understanding the breakeven point of running on prem vs running on cloud will help us save money. So a clear criteria on when we get into cloud and when we think have to move away from cloud is a good to have feature.
Choice of tools and technologies
Overall, enterprises should go agile as startups do. At the same time, choosing the right tools and technology helps them quickly launch the product in the market.
Share your thoughts in the comments!
Published by Shankar Kumarasamy
Digital leader and technology enthusiast with experience in varied functional areas specializing in mobility and cloud backend. Areas of specialization include: 1) Solutions architecture - Enterprise-scale solution consulting to determine major IT investments, 2) Technical architecture - End-to-end system and integration architecture including hardware and software, 3) Applications architecture - Multi-cloud native server-less application architecture, 4) Data architecture - Canonical data architecture and design including support to multi-tenancy data models, 5) Identity architecture - Different LoB identity management solutions involving SSO for customer 360 experience, 6) Security architecture - Eliminate digital risk by designing the flow of data between people, systems, and things with granular and only the needed access View all posts by Shankar Kumarasamy
Published April 12, 2019April 12, 2019
Previous Post Major announcements from CES and MWC, 2019 – Developer insights
Next Post Major themes and products announcement @ IO 2019
Leave a Reply Cancel reply
Enter your comment here...
Fill in your details below or click an icon to log in:
Email (required) (Address never made public)
You are commenting using your WordPress.com account. ( Log Out /  Change )
You are commenting using your Twitter account. ( Log Out /  Change )
You are commenting using your Facebook account. ( Log Out /  Change )
Notify me of new comments via email.
Notify me of new posts via email.
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Android App Bundle (1)
Android Flash Tools (1)
Application Integration Strategy (2)
Best Mobile Apps – 2018 (1)
Cloud Next 2018 (1)
Contact Center AI (1)
EV Charging Station (1)
Google AI Solutions (1)
Google IO 2019 (1)
Google IO 2021 (1)
Google Play Store (1)
Hybrid ML for Mobility (1)
Intelligent Behavior Detection (1)
Intelligent Mobile Solutions (3)
Mobile Application Development Strategies (7)
Mobile World Congress (1)
Mobility In 2019 (1)
Modern Tech Tools (4)
Multi Cloud Strategy (4)
Self driving cars (3)
Self Sovereign Identity (SSI) (1)
Zero Trust Model (1)
AI Amazon Android AndroidP API APIOrchestration ApplicationDevelopment AWS Azure BigDataAnalytics Blockchain Cloud CloudComputing CodingCulture ConnectedDevices DataFirst DigitalTransformation Edge EdgeComputing ElectricVehicle Firebase FutureCode FuturisticSolutions GCP GigEconomy Google GoogleHome GoogleIO2017 GooglePlayStore IdentityManagement IntelligentMobileApplications iOS IoT Learn MachineLearning Microsoft ML MobileAppsDevelopment MobileDevelopers MobileTechnology Mobility MobilitySolutions ModernTechTools MultiCloudStrategy On-DeviceLearning ServerlessComputing Strategy UbiquitousComputing VoiceAssistants VR
© [Shankar Kumarasamy] and [shankarkumarasamy.blog], [2017-2020].
Unauthorized use and/or duplication of this material without express and written permission from this site’s author and/or owner is strictly prohibited.
Excerpts and links may be used, provided that full and clear credit is given to [Shankar Kumarasamy] and [shankarkumarasamy.blog] with appropriate and specific direction to the original content.
Archives Select Month September 2022  (1) August 2022  (1) July 2022  (1) June 2022  (1) May 2022  (1) April 2022  (1) February 2022  (1) January 2022  (1) December 2021  (1) November 2021  (1) October 2021  (1) September 2021  (1) August 2021  (1) July 2021  (1) June 2021  (1) May 2021  (1) April 2021  (1) March 2021  (1) February 2021  (1) January 2021  (1) December 2020  (1) November 2020  (1) October 2020  (1) September 2020  (1) August 2020  (1) July 2020  (1) June 2020  (1) May 2020  (1) April 2020  (1) March 2020  (1) February 2020  (1) January 2020  (1) December 2019  (1) November 2019  (1) October 2019  (1) September 2019  (1) August 2019  (1) July 2019  (1) June 2019  (1) May 2019  (2) April 2019  (1) March 2019  (1) February 2019  (2) January 2019  (1) December 2018  (2) November 2018  (2) October 2018  (2) September 2018  (1) August 2018  (1) July 2018  (1) June 2018  (1) May 2018  (2) April 2018  (1) March 2018  (2) February 2018  (1) January 2018  (2) December 2017  (2) November 2017  (2) October 2017  (3) September 2017  (2) August 2017  (3) July 2017  (4) June 2017  (4) May 2017  (5) April 2017  (4) March 2017  (2)
Follow Blog via Email
Enter your email address to follow this blog and receive notifications of new posts by email.
Join 47 other followers
Start a Blog at WordPress.com.
Join 47 other followers
Already have a WordPress.com account? Log in now.
View post in Reader
Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.