Community Finland Product Development Technology 
Startup Lessons Learned
AUGUST 24, 2009
The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. There are too many products clamoring for attention. I’ve met a lot of gatekeepers in the past few months.
Startup Lessons Learned
JANUARY 19, 2009
I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. You are doing the startup community a great service by sharing your insights via your blog. Sounds a little abstract, though, doesnt it? Almost all of it is in one giant fixed-cost bucket: salaries.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
FEBRUARY 22, 2009
That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Its this second point I want to emphasize.
Startup Lessons Learned
SEPTEMBER 3, 2009
If you look at the typical startup, you will see the vast majority of their energy and time invested in building new technology. We act as if the biggest risk to startup success is that the technology won’t work. Take the example of the Hoverboard. Take a look and let me know what you think.
Startup Lessons Learned
SEPTEMBER 15, 2009
whorunsgov : Eric Ries: Startups fail not because the technology works, but because no one wants the tech. g2s The very abbreviated version of Customer Development (channeling Steve Blank ). Its natural at a gathering like this to focus on new technology and applications. once it launches. Startup=Experiment. link] Amen!
Startup Lessons Learned
AUGUST 8, 2009
Heres the pitch: a group of 10 companies would meet once a month for six months to develop their capacity to run lean. Each company would enroll two leaders in the series, one on the technology side, one on the business side. Each month, wed hold each other accountable for making changes to our product, process, and team.
Startup Lessons Learned
NOVEMBER 19, 2008
This wasnt an education product - it was a pretty surprising group to find using it. What all these teachers had in common were two things: they were technology early adopters that were willing to take a chance on a new software product, and they all had similar problems organizing their classes and students.
Expert insights. Personalized for you.
113 
Let's personalize your content