This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
I’ve been having discussions with several people recently about the role of the CTO (Chief Technology Officer) in very early stage companies. In December 2007, I described how I commonly take on an Acting CTO Role in a Start-up. I used an image from Roger Smith that describes the varying roles of a CTO as the company matures.
Once you build it, they will now ask you about the key metrics that they need proven in order to see if you really are a good investment. The real reason to build an MVP is to do early tests of key Startup Metrics for the business. " Once you have the metrics defined, it focuses your effort. To prove/disprove a hypothesis.
I'm going to be looking at aspects like: Things to consider before building your MVP Features often overlooked when documenting an MVP for developers Understanding important metrics you want to measure Risks and challenges in developing an MVP. Do you have a Technical Advisors: Every Web/Mobile Startup Must Have One ?
they need a developer more than they need a CTO. Ideally, you would have had a technical advisor, had better up-front definition, had more iteration, then you would not be in this situation. Provide the metrics you are trying to achieve. This is a classic sign and you need to do something about it.
I seem to encounter a lot of people who want to attach a CTO label to me as I'm the only programmer on the founding team of three. While I do fill that role at the moment, I'm a little hesitant to refer to myself as a CTO as we still haven't launched a product, acquired a single user, or turned or a penny in profit. Accounting?
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content