Skip to main content

Don't Be a Feature Pig

I had conversations with 3 separate founders over the past 4 days, all of whom are brilliant and accomplished, and all of whom have more vision than capacity to serve it. I'm very familiar with this, because I am absolutely the same way: I want it all, I want it fast, I want it now, so let's get it done.

And that's not a great approach.

You're smart. Brilliant. Your mind races through the possibilities, almost constantly. Because these days the possibilities seem endless; I believe they are.

Everything is programmatically possible. And that's the problem.

As founders we bring a lot to the table--vision, energy, capabilities, desire to serve, desire to win, etc. Balancing that so you move forward is sometimes tough.

I'm a Feature Pig. Anyone who's worked with me knows I see the possibilities and want them all, if only to see how they work in real life; there's a big difference between a feature on paper and in practice.

But it's not the best approach, and can really interfere with a project.

The balancing act is this: you need enough features to round out the product--like Ries' Minimum Viable Product--but not so much that you 1)overwhelm the customer and 2) delay your project.

The brain interprets everything it sees and hears. Everything on a page is information--every line, every word, every space, color, images, shapes, etc.

And all of that goes into the user's understanding of the app and experience with it. The more features, the greater the learning curve. The more features, the more noise on the page, the more interpretation and the greater chances of problems along the way.

It's frustrating--I know this very well--it's frustrating to have a vision that will accelerate the product adoption and not be able to get that in, because your team is focused on the "core stuff". And sometimes you can redefine what's core.

But when you have ideas coming all the time, in real time, and you run them by everyone, all the time, in real time, it starts to wear on them.

Your team needs successes, concrete wins, and a sane working environment. If you're constantly innovating and expecting them to respond, you'll weaken their efforts and be perceived as, well, as Random Idea Guy. RIG. RIG the Features Pig. Nice.

So how do you handle that brain on fire?

Write it down. Run it by people when they aren't focused on production--like after work at dinner, or during lunch. If you have a technical hurdle to understand, you might pull someone in, but again, write it down. Then schedule it, realistically. Take time to socialize the idea with your team.

I write down everything these days using Evernote or on paper. Very simply--I mostly use bullet points. If I need to sketch something out, I use a simple image program and create quick mockups. If it makes sense to move forward with it, I wireframe it with light BDD specs.

Developing the discipline of knowing what features should go in, how they are represented visually, how it works, and when to let your team know is critical to your success.

Develop that balance and you'll be able to push your team faster, and you'll get your features (which you should definitely test with users before deploying fully).

Don't develop that balance and discipline, and you'll slow things down--it's self-defeating. Now go cut some features :)

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

The Real Jobs Problem

It's the economy, stupid.  Well, yes, it always has been, if you're in the distortion field of politics.  But whose economy? The pundits, the White House, the Republican candidates all miss the mark. They keep talking about debt, taxes, and monetary policy. None of those things tell the real story behind today's economy.  The Old Economy Keynes was right--in the old economy. Economy gets weak, pump some money into the economy through public works projects, which  1) puts people to work, which  2) boosts the economy and  3) generates new tax revenue, while  4) leaving us with another generation of reliable infrastructure to support  5) more growth (for growth's sake, which is another post).  The Beach Ball Imagine a beach ball, partially deflated to represent a recession. Got it? Now imagine the govt pumping that beach ball back up through sensible public investment (which we haven't seen for decades). The New Economy Same beach ball, same pum