Need someone to lead product or development at your software company? I lead product and engineering teams and I'm looking for my next opportunity. Check out my resume and get in touch.

What Clients Want (part2)

Freshness Warning
This blog post is over 18 years old. It's possible that the information you read below isn't current and the links no longer work.

winterspeack.com’s Zimran Ahmed disagrees with Joel Spolsky’s article "The solution is not to pander to corporate myopia and produce software that helps neither the business nor its customers. Somebody’s business is going to rely on what you produce and I beleive it is unethical to knowingly create a product that doesn’t improve the life of the end customer."

That’s very true, but I think he’s missing the point of Spolsky’s article. If you show the client (or your internal customers) a series of pretty screenshots, they assume you are done with all the work and don’t understand what else there is to do. If you show them a fully working product that doesn’t have a pretty face they will assume that nothing has been done. So Joel is suggesting that you remember this and strike a balance with your demos.

The problem with this approach is that you are lying to your client. That is not a good idea. A profitable consulting business relies on repeat customers and referrals. Deceit is not the way to acheive this.

Ahmed is right about one thing though. "If you want to find the real iceberg in the technology world, it’s that the 1% of people who create technology are utterly clueless at figuring out what 99% of people actually want. The technology world is a wasteland of pointlessly hard to use products that don’t benefit anyone and were expensive to produce."

Recently Written

How to advance your Product Market Fit KPI (Oct 21)
Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.
Developer Experience Principle 5: Easy to Trust (Oct 9)
A developer building part of their business on your product needs to believe that you're going to do the right thing for them and their customers.
Developer Experience Principle 4: Easy to Get Help (Oct 8)
The faster you can unblock a stuck developer, the better their experience will be.
Developer Experience Principle 3: Easy to Build (Oct 5)
A product makes it Easy to Build by focusing on productivity for developers building real-world applications.
How to understand your product and your market (Sep 30)
A customer development question you can ask to find out who your product is best for and why they'll love it.
Developer Experience Principle 2: Easy to Use (Sep 28)
Making it Easy to Use means letting the developer do everything without involving you.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2020 Adam Kalsey.