Loading...
Answers
MenuWhat are some of the common dilemmas and paradoxes in innovation a startup, as opposed to a large firm, will face?
What are your experiences?
Answers
The short answer (with respects to problems) is everything that comes along with capital. The good news is that there is significantly less red tape to cut through for innovation!
In my journey from working at a Fortune 100 firm to starting my own company, I had a "transition" working with a medium sized company.
As I moved from the large firm to the medium company, I noticed the number of resources drop off significantly and really gained an appreciation for how much information is free when you know how to look for it. In this setting, I found that I was actually able to be more innovative as I still had access to capital for innovation experiments and there were fewer barriers as far as corporate policies.
Moving from the medium company to my own startup, the resources obviously dropped off even further, this time with respect to capital. Of course, there is no problem as far as making the go/no-go decision on pursuing an innovative effort, but I also have to be clever with what type of front end studies are performed.
Innovation as a startup is essential and it's great fun when you figure out how cheaply evaluate efforts to determine if making a larger investment is viable. Feel free to reach out to me to discuss further!
The dilemmas that I faced during my startups are, even though culture was casual, no judgement and easy-to-talk-with-everyone environment, we simply did not have time to spend on creativity and innovation often due to tight cash-flow and overwhelming work load from hyper growth. Creativity and innovation require a lot of incubation time and with often tight cash-flow, it’s challenging to balance where to focus on.
Jeremy is absolutely right about resources in a firm. Capital is a huge issue.
One of the biggest issues a startup will face is the Built It/Buy It question. You need a new piece of technology or software to do business. Maybe you need a CRM, or a time tracking app for employees, or a document filing and stamping system. Should you buy a product already on the market or make your own? There's a lot of factors here that come into play such as speed to market and cost of development vs licensure.
Another issue that startups can run into is a lack of bandwidth. When you engage contract developers for work, make sure you discuss timelines and what their workload looks like. Is your team going to be dedicated to your project or are they working on other efforts. Hiring 1 developer to build something might seem like a great idea, but if they are working on 10 other projects, you might never get your product.
I hope this helps! If you have any other questions, please feel free to reach out!
Going against the stream you will find several oppositions related to creation of a start-up. Common dilemmas and paradoxes you will face will be in terms of plan, legal issues, founder readiness, business structure, company name, website creation and there would be many more. To be frank, if you will be opposed to a large firm it is going to be difficult.
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
Any advice on starting up small businesses in two countries at the same time?
Please realize that my suggestion would be slightly different if I knew which two countries. However, without knowing that here's what I'd suggestion: 1. Since you're just getting started figure out which country provides the best legal benefits for starting a company. This should include tax benefits, legal protection, and ease when it comes to filing paperwork (incorporating, managing payroll, taxes, etc.). This will undoubtedly save you time and money moving forward, and staying lean. 2. Once you've established your home base country, you'll still need to hire people in the other country as you scale. You may want to think about using a service like oDesk or Elance, not necessarily to recruit people but to manage ALL the paperwork associated with hiring international people. They will of course be given contract status. If you are going to be providing employees equity then I'd suggest consulting a lawyer for how people in the non-home base country will be treated. 3. Reporting revenue. You need to be very careful about whether you are providing goods and services. If it's goods keep in mind that you might be subject to tariffs. If you're providing services then I think you might be in the clear, but please double check. Finally, some countries might have an issue with where the revenue was actually made i.e. are you sitting in your office in your home based country while servicing clients in the non-home base country, or are you actually in the non-home base country. 4. No matter what you'll need to setup a remote working environment for yourself. Invest in the best technology you can, and find clients who are willing to utilize your services on a remote basis. Here are a few additional posts on running a remote team that I've written: http://femgineer.com/2013/09/running-remote-and-making-progress/ http://femgineer.com/2013/03/how-to-transition-to-a-remote-team/PV
-
I'm having problems with ideation for a startup, I'm a web developer, what needs of yours aren't being met? Or how can I find a big problem to solve?
It's really ill-advised to solicit your vision from anyone. In my 20 years of building, investing and supporting tech companies, I don't know of a single success story that has it's origins in someone with your approach. Running a tech startup is incredibly hard. It demands sacrifices few are truly able to make and come with it tremendous risks that most people are unwilling to take. It sounds to me as if you want the startup life because you have an impression of what it's about but haven't yet experienced it first-hand. I'd encourage you to first join an early-stage startup. Developers are incredibly in-demand. Find an entrepreneur who has some experience, funding and a compelling vision that you believe in and get to know what the journey is really like.TW
-
How can I smoothly transition from full time worker to self-employment?
The ways I've done this in the past are 1) Find some customers that are willing to hire you (or your product) but know that you'll only be free nights & weekends to support/work with them. 2) Find a "partner" (co-founder or other) that's got a flexible schedule that can help build the business while you're at work. 3) Block out nights, mornings and weekends to build the business till you have enough orders to cover 50% of your salary. This might mean 7pm-11pm most nights, and 4 hours each day Sat & Sun. Make progress (sales $$$) and momentum. All that being said, it's risk reward. Sounds like you want to avoid taken the risk, and I get that .. but the upside is always smaller. Unless you put yourself in a position to have to succeed (ex: quitting your job) then you may never make the scary decisions that are required to build a company (like cold calling, going in debt, making a presentation, etc). I'm on company #5 with many other side projects started nights & weekends .. so I get it - but don't be afraid to bet on yourself and go all in.DM
-
What are some important milestones for a bootstrapped startup?
If you haven't fully tested your app with the 100 individual accounts Apple allows you to test via TestFlight or Hockey, then I'd suggest you should test thoroughly with your email list before launching to the app store. Things to look for at this early-stage: Activation and Breakage Points: From app download to user onboarding, where are people getting lost? Your goal is not only to have them download the app, but complete whatever steps for them to become your user. Optimizing the flow to ensure maximum conversion is a key first step. Engagement: How often are they completing the tasks you deem most important based on your business model? How can you increase this number? User Understanding: How clear is the app's UI and messaging? Where are they getting lost? Virality: While true virality is hard to measure at this stage (given the constraints of pre-launch testing), you can evaluate the potential effectiveness of any distribution tactics you might employ (contacts, OAuth's etc) in terms of user opt-in and conversion issues. Real analytical data is easier to interpret than user interviews but there is a such a treasure trove of good customer development intel from customer interviews. Those first 100 people who download the app should be personally interviewed about their experience, what they like, how much it solves their problem, how much of a problem that is for them in the first place and so on. Before you go live in the app store, I highly recommend you max out your installs in a private testing environment. I'm happy to talk this through with you in more detail in a call.TW
-
What are ways to find and engage B2B beta users for a brand new application?
Find apps that are B2B and go to the review sections. Specifically going to Google's play or Chrome store and look at reviews and follow them to Google+ to engage. I took that same angle for B2C app I was building last year. Check it out. http://blendah.com/post/37331434653/lean-startup-hackTM
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.