Skip to main content

Starting Over

Over the past 20 months I've been considering what to do next. For over 2 years I've been considering what my life's work is; that navel-gazing was triggered by an article on Chongo in the New York Times sports section. I finished the article and said out loud "man, that's his life's work".

And I couldn't stop talking about it. And only a few people seemed to get what I meant.

At the time I was frustrated with software. Burned out, blocked by internal politics that I had failed to manage, racing toward a brick wall instead of finding a way around it, I wondered what my life's work was. Software? Really?

Software is just a tool--a means to an end.

I think my life's work is about helping other people. When I'm not doing that, I'm a lot less happy. The farther removed I am from the delivery of the help, the less happy I am. But it also seems that the closer I am to the delivery of the help, the more diluted my efforts are.

So I ran for school board, wanting to help. And that's sometimes satisfying, though it's far enough removed from helping kids directly that I feel a bit detached from the results. And I've volunteered a bunch in other ways, mostly in an effort to learn more about the nature of poverty in Lancaster city, and what we can do to reverse it (I believe we can).

But I think my life's work is more than just helping, I think it's catalyzing. I've been able to spark some good things, and help others create their own sparks. So I want to put myself in a position where I can do that more--maybe even full time.

Consulting to startups has been fun, and sometimes frustrating, because I'm removed from the actual execution that it takes to make my advice meaningful. So if the advice isn't followed, they aren't successful on its basis (and maybe not at all), which means I wasn't successful.

Coding for the past 10 months has put me in direct control of execution. Getting that immediate feedback is very fulfilling--you code, discover bugs, fix them, see stuff work, and move on to the next thing. It feels great.

It feels 20 times better when someone uses it and says, this is ok, but what would really rock is...and then I have someone to help. I've given them the basis for something that scratches an itch, and they say no, you need more cowbell and less whatever.

That feedback is really important in the process of building software. I'm about to release an alpha to some friends of a new thing I've been working on, and it's the feedback I crave. I'm not yet sure why it's different or better, but I know it's useful to me. And through that, my guess is it will be useful to someone else.

I recently decided it's time to build a small team so I can move things along faster. So I'm going to raise a round of capital and take a swing for the fences again. I'm hoping that what we produce will fundamentally change the way people work and help them simplify.


So I think I found out what my life's work is. It's helping people to help themselves. How I get there, for now, is through software. Really.

Comments

Popular posts from this blog

Beta Signup

I've been working for quite a while on a new search concept, though the further in I get, the closer the rest of the world gets to what we're doing. So today I'm inviting you to sign up for the rather modest beta, which will be ready soon if we can nail down a few difficult  details. Jawaya is a way of navigating the web and getting better results. And that's as much as I can say right now, because we're not a funded startup, and things are moving really fast in this space--it's going to be very competitive. I predict there will be about 10 funded startups in the next 6 months doing something similar. One of them will be mine, and we aim to make it the best. We're raising a round of capital to fund the team, and are shooting for early sustainability. This is my fifth company; my fourth in the tech space, and my third software company. I think it will be the biggest and can possibly have a positive impact on the world by reducing the amount of time it takes

Where Innovation Happens

As I get closer to a go/no-go decision on a project, I've been thinking about the difference about my vision for the project and the supportive innovations to enable the core innovations The vision combines (in unequal parts) product, core innovation as I imagine it, the application of that core innovation, design, marketing,  developer ecosystem, and business development. The core innovation enables everything else, but it's the application of the innovation that makes it meaningful, useful, and in this case, fun. This week we're testing initial approaches to the implementation for our specific application, and that's where we'll develop the enabling innovations, which is basically where the rubber meets the road. The difference is that the enabling innovation happens at the source of real problems only encountered in the making of something, and in a project like this just getting the essence of it right isn't enough; it also has to be safe, the compone

Projects vs. Startups

Yesterday I spent some time thinking about the difference between my successful starts and my projects, which I'll call R&D that never makes it to market. The start is the most fun, and it can also be the hardest part, and it's certainly the most important: figure out the market, the opportunity, develop vision, design the product, figure out the sourcing if it's a physical product, figure out best methods and user interface if it's a software product (and both if it's both hardware and software), refine the product, find early customers, test, refine, improve, iterate all of that while you also develop the brand, the marketing language, figure out the best sales approach, sales system, sales language, customer support, etc. During that time you're setting up internal systems of communication, accounting, legal, HR, etc, but mostly you wing it until you have more than a few people. And, of course, you have to figure out how to pay the bills. You can