I'm on the road, but by voting I mean with their wallets, i.e. Paying in advance for a viewing.

- -
Sent from a phone, so apologies for any spelling mistakes.

Lmao

- -
Sent from a phone, so apologies for any spelling mistakes.

Thanks for your comments, Penelope. Big fan! :-)

Thank you for your wonderful comment. I felt it would be more wonderful without your URL, because it seemed a little spammy.

Yeah, the blog post by Paul Miller refers to both as well.

Nice post! I like this quote: "The problem with digital tools : almost anything can be done in less than two minutes." The problem that knowledge workers face, is that their work can no longer be qualified as widget-work with predictable productivity levels. That also creates the problem of compensation, of how you quantify the work that a knowledge worker does. And as your post(s) implies, we are all increasingly becoming knowledge workers.

My own approach is to try to understand what processes contribute to what approximate portion of a businesses' bottom-line. Then it doesn't matter how much you work, but how much your work contributes to part, a whole, or multiple processes. And price appropriately for that. Widget-work is dead, so it the idea of a 9-5 job.

I mean search in the sense of searching your existing content. At this moment, I have over 100 pages saved in Instapaper, which makes for a long list. And it's hard to tell which article you came from when you leave it to check for something else (like what your friends liked). So sometimes I end up searching for the last article I was reading for several minutes…

Wow, the difference between the iusethis top-list and the app store one is quite stunning. Pretty clear divide between open source and Apple source, not a good thing!

I kind of dream about MS Visio and OneNote :)

RE: market testing. Having developed pretty complex hardware for over a year now, I can say that it's really tricky to do market testing prior to building a product. People want to feel something tangible and find it hard to imagine something that doesn't exist yet. Even we had that problem, but hoped for the best. I can't speak for Apple, though I imagine they had the same problem when they started, but the risk of market influence on the building of a product is that adjusting features is very, very, very tedious. We had to work with suppliers that just wanted a single specification at the start and if a mistake was made in terms of what we wanted, that was our problem. So you want to release a simple product early, have people use it, and then can innovate on top of that.

I think the culture of hardware building is probably to use a lot of engineering talent from the start, talent that knows how to visualise and build competently. Market testing comes at a later stage. For the iPad, however, much of the market testing happened on the iPhone!

I can't speak for software, though I'm hearing development is much simpler, more flexible, and collaborative, which (if true), I am very jealous of. Of course, there are different problems that come with that, such as the simplicity for the competition to do what you do.

This is a very contextual point of view. I've worked in a financial institution, where plenty of valuable information existed on the intranet. I've also worked in startups, where plenty of valuable information still had to be found—on Google or elsewhere (better results from experts or carrying out online surveys). Generally, for it to become usable, however, it had to be integrated into processes that generate value for the company. Related reading:
- The knowledge-creating company: http://www.techiteasy.org/2009/05/29/the-knowledg...
- Process-coding for entrepreneurs: http://www.techiteasy.org/2008/07/08/entrepreneur...

My critical comments aside, I like your blog posts a lot, keep it up!