Skip to main content

Iterations

One of the biggest disconnects & questions between startup personalities and others working on a project is the idea of when a product is finished.

Answer: It's never finished during the startup phase.

This is tough for traditional developers to embrace and can be frustrating when there are constant changes coming from founders seeking the right balance of features to serve people.

The reality is we really don't know. We have a vision, which leads to concepts and a path forward, and along the way we learn new things and shape the product (i.e., new features or different approaches to the vision), test it out with our friends and family, absorb feedback and let it percolate, and come back with a new list of changes.

"But we just did that". It's frustrating.

Yes, we built this house, and the customer wants the ceilings 3 feet higher and contiguous windows all around the house, like a spaceship.

"But we just did that." Sigh.

That is actually not what we just did.

What we did was do a ton of work that moved the engine along, took a very good stab at the interface, got a lot of great, useful feedback, and learned some important things.

And with an evolved vision, we take another stab, we try again. Fail, recover, try again. Rinse, repeat.

Sometimes it feels like you're wandering in the desert for 40 years, seeking clarity, seeking the truth, seeking that amazing feeling of absolute confidence.

That's why tenacity is so important.

It takes time to evolve ideas, and more time to memorialize them in code. If you don't build it, you can't feel it. If you can't feel it, you can't know how to rebuild it so you really nail it. You can't cross that gap unless you have a lot of luck, where your execution meets the vision perfectly and your people (users) dig it enough to come back regularly (free app), or pay and stay.

So where are we?
  • On Monday we'll relaunch Jawaya (name change on the way). 
  • We're not addressing the full vision--we're simply making it an easy way of saving and organizing the links you value
  • ...privately, with optional sharing/following
If we can get that part right, the rest will follow. But I'm going to bet this: we'll have at least 2 more releases before we fully nail it so people want to use it and tell their friends about it. I admire the brilliant product people who are able to nail it the first time out. I'm not one of them, nor are most founders. 

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

Disqus Digests

This morning my phone dinged with a fresh notification--a new email! What oh what could it be?  I rush over to check while thinking "I need to unsubscribe to a lot of stuff so I get fewer non-urgent dinging notifications." Well shoot, that's disappointing. It's Disqus Digests, one of the biggest wastes of dopamine anticipation ever.  It simply sucks.  Disqus itself is great as a commenting system. I've been there since the beginning and have mostly enjoyed its evolution.  And then they did this interruptive, irrelevant email. Well why does it suck, you say.  Every one of these "Digests" sends a few comments from a blog conversation in which I've already participated. That means it's very, very likely that I've seen the comments before.  So I open the mail, see something I've already read, and curse Daniel and Company for enticing me into wasting my time, and cursing myself for falling for it.  So I unsub