[benjaminwootton]

Do we not have exactly the opposite problem within this community?

We know coding so we spend our time hacking away in dark rooms on product stuff such as frameworks, features, deployments, websites etc.

We leave considerations about marketing, distribution, customer research till later, and end up building something that we have no way to effectively market.

The order should probably be to develop the business model, then develop the product, and only add this kind of administravia in as absolutely necessary.

[drd]

Building the product is the easy part of the work. First we have to sell. Here is the summary of my experiences:

[http://www.drdacademy.com/?id=first-solve-the-selling-proble...]

[flyosity]

Figuring out what to do after you build a product is only hard if you don't plan to sell the product. For example, if you build a consumer-oriented service that you plan to offer for free, then, yes, developing the business model is hard. And by looking at lots of "pageview-successful" startups who are still trying to make their first dime of revenue, it may take years to graft a successful business model to a free service. Hell, I think Twitter is still working on this.

But if you build a product that you want because it fits a need that you have, then it'll probably fit other people's needs as well. And then you attach a price to it, and then people pay for it, just like any other types of goods that people purchase. Examples of products with simple business models? SaaS apps with monthly subscriptions. Build a good product, charge a fee to use it. Yes, you still have to figure out how to market it, but since the big hurdle is getting people to hand over money for the thing you built, you're well on your way.

(And, just one more clarification, talking to potential customers and integrating their feedback while you build the product and making sure that at each step you're building something people want is a good way to make your marketing/distribution problems a lot simpler.)

[jmathai]

I think that's a bit of an oversimplification. Scratching your own itch might not solve a need for a market big enough for a viable business. You end up "pivoting" till you figure that out.

If there's a way to find that out early then you save yourself valuable time. Time which could determine if you're able to stay alive long enough to succeed or not.

Not at all advocating spending a year on market research but don't go straight from idea to your basement to start coding. Not if you're trying to build a business out if it.

[saosebastiao]

I think the community is too diverse to be able to say that. I have a background in Supply Chain Management, and while I can code well enough to be an engineer, I have never been the same type of hacker that you imply.

My conversations with others in this community confirm that I am not alone. I have read many comments from Marketers/Product Managers, TPMs, SEOs, CEOs, Designers, Stock Traders, Financial Analysts, Ops Researchers, Executive Assistants, etc.

[dberube]

This is more geared towards the administrative stuff that adds no value and is an excuse to doing actual work.