A Non-Techie Tries to Build a Tech Company
boss.blogs.nytimes.com
A Non-Techie Tries to Build a Tech Company
1–10 of 62 posts
Re: A Non-Techie Tries to Build a Tech Company
#2Founder makes mistake after mistake, blames other people, then finds a famous & rich engineer, suddenly stops making mistakes.
Re: A Non-Techie Tries to Build a Tech Company
#3Re: A Non-Techie Tries to Build a Tech Company
#4TL;DR: Founder makes mistake after mistake, blames other people, then finds a famous & rich engineer, suddenly stops making mistakes.
Re: A Non-Techie Tries to Build a Tech Company
#5Re: A Non-Techie Tries to Build a Tech Company
#6"I’ve also discovered that nothing is more motivating than a high profile, non-negotiable deadline." Sweet jesus no. If you don't understand what is required do NOT sign your team up for that. That's what causes death marches. Now if you had the team already analyze the opportunity and prototype "the hard parts" then by all means go for it :)
The one deadline she mentioned was implicitly a decision, "we will launch at X event". That eliminates the first general problem with these, they're usually artificial (vs. what I like to refer to as the "pesky" customer challenge). It also allows for the right sort of deadline bargaining, what shall we present then? Vs. the "I think I can do this in 4 weeks" which the worst managers take as a starting negotiating position.
Re: A Non-Techie Tries to Build a Tech Company
#7According to LinkedIn the CTO left the company
Re: A Non-Techie Tries to Build a Tech Company
#8TL;DR: Founder makes mistake after mistake, blames other people, then finds a famous & rich engineer, suddenly stops making mistakes.
Getting the UI stuff right is just as important as implementing it solidly.
Re: A Non-Techie Tries to Build a Tech Company
#9"I’ve also discovered that nothing is more motivating than a high profile, non-negotiable deadline." Sweet jesus no. If you don't understand what is required do NOT sign your team up for that. That's what causes death marches. Now if you had the team already analyze the opportunity and prototype "the hard parts" then by all means go for it :)
"Our team performed brilliantly in the month leading up to our launch at the South by Southwest festival; they worked day and night. Now I look for major events that we can all work toward every three months. It’s a great way to keep everyone pointing in the same direction and working fast."
Ugh, I'm really not sure this founder learned the right lesson here either. I'm hoping there's an unspoken here that deadlines are being set in a less-arbitrary method grounded with a technical reality check.
Re: A Non-Techie Tries to Build a Tech Company
#10"I’ve also discovered that nothing is more motivating than a high profile, non-negotiable deadline." Sweet jesus no. If you don't understand what is required do NOT sign your team up for that. That's what causes death marches. Now if you had the team already analyze the opportunity and prototype "the hard parts" then by all means go for it :)