935 karma · joined March 7, 2012
Was there sort of a pivotal moment where you felt OfficeSnapshots was going to be viable? Did it happen organically or did you have to push hard for it?
Justin Wilcox's 5 simple questions helped a lot but practice makes perfect: https://customerdevlabs.com/2013/11/05/how-i-interview-custo...
Here's a link to additional resources: https://medium.com/lean-startup-circle/all-the-resources-you...
In industry, you also need to balance the amount of time and effort it takes to build your model against the incremental benefit.
Selling the project immediately likely won't give you the greatest value for the effort you've put into it simply because there is a lack of evidence on whether you're able to sell anything to the audience.
However, there is still some value in the audience, credibility and web properties and you can approach classical music promotion companies, etc. to see if they would be interested in taking it over.
If you collect data and have an insight into user preferences, this could add additional value but as what some have said, you'll likely get more money if you show that you can also sell to this audience.
For startups, things move much faster but there might be less of a defined process on what to do. You'll be learning how to deal with ambiguity but also have the opportunity to establish leadership and set the direction.
For large companies, there have vast amounts of interesting datasets to explore to but depending on where they are at with their data journey, it might require significant amount of time for cleaning. Everything you propose might require approvals, consensus depending on the structure of the organization. They also have vast financial resources to spend on new technology so if you are thinking about the tech giants and if you can develop expertise in them, it might be a path there.
Based on your aim to get into a tech company in the future, I would lean slightly towards the large retail company given a stronger brand name.
> I think that this might not be considering the inherent politics of work and the power dynamics present in every business. To be clear, I don't think the comment is coming from a bad place, I just think that it points to a common fallacy that any sort of "meritocracy" is possible in business as usual. When you have a small group of people holding power there are few incentives for them to share that power. And In my experience it is the person who is able to sell themselves the best that gets the highest reward, not the most productive.
You're absolutely right and I see it with my experience as well. The highest rewards don't usually tend to fall naturally and equally to everyone whom we deem to be the most productive. And while there may be few incentives to share the power in small groups, one would hope that the goodness of an individual's heart would lead them to do so.
The assumption that marketing, administration and sales work of business as non-productive is an arrogant view. While as engineers, we tend to think that doing the actual work counts more than the rest, clients actually value the other stuff and would be willing to pay much more for it as well. You can easily see this with enterprise contracts that value $25k to $1m or more, where they usually have account executives, project managers, training programs, etc. in addition to the product.
Assuming the management team cares most about the finances and risk, outline what the costs and the risk factors of their approach vs the lean startup methodology. Present it to them as an option. But let them decide while positioning the lean startup as the less risky option.
I've always presented lean methodologies over long periods of development by highlighting the amount of engineering and project management resources it involves. Not to mention 6-9 months down the line, you might have wasted your time building something that your customers didn't want/need.
When I started to prioritize, delegate and only focus on key details, it was a big shift in mindset but also a big boost in my effectiveness as a VP.
Know when to say things and when not to say things. Let go and think big picture. You're in the business of delivering through your team and your role is about giving direction to your team so their work is meaningful to them and to the organization.
Not everything will need your attention - you mostly only need to know when the project will be completed, help your team unblock roadblocks (in terms of tech, process, people) and align all projects to the overall strategy.
I've also found that some VCs don't get what we're doing (because they're not part of the industry) and some do. At least here in the UK anyway. So I've shifted my strategy somewhat to try and leverage corporate VCs while also getting them to bring us into the enterprise market.