News for hackers. Stuff that matters.
Re:Ask HN: How do you handle a co-founder that misses all go... by tptacek on Sunday January 12, 2014 @02:09PM (#7047030)
1. You're probably not going to be successful without colocated founders.

2. What makes you think the milestones you've set up are reasonable? Most estimation in software development is fantastical.

3. If you're done with your component and your partner is in the weeds, it's not up for discussion whether you're going to pitch in on their component. The company can't have you idling.

4. People get demoralized easily. Your "cofounder" fits the description. Maybe he bit off more than he can chew; maybe his milestones were much harder to perform than yours. Maybe he just stumbled. Either way, it's not a problem that goes away by itself; the company has to fix it. You should have been able to spot it happening 3-4 months ago and fixed it then, but you weren't skilled enough to do that.

What can you do? First, learn from the experience. Here you are, done with your component, partner in the weeds, and, guess what? Moral superiority (not that you necessarily have it) gets you nowhere. Problems happen. The more problems you can foresee, the more you can discuss ahead of time how you'll handle them. But discussed or not, you need to get out of your own head, stop thinking about what you did get done versus what your partner didn't get done, and figure out how the company can move forward.

Moving forward here, I think you have two choices: you can give up on this particular partnership, or you can reassure your partner that everyone gets lost in the weeds sometimes and then renegotiate who's doing what pieces for the next month or so, and put things back together. Then, before your next sprint or whatever, have a long conversation that accepts the fact that one or the other of you aren't going to be successful at your personal piece of the project, and figure out how you'll handle that.

There are no comments on this comment yet.