So much knowledge not being applied Most organisations have a lot of documents and data floating around that hardly ever gets revisited or used. They all have research, reading, and relevant information collecting dust. Stuff that should be informing the decisions and strategies of the company. Some of it sits unread in a knowledge base or a wiki. Some of it lies in the drives of individual employees who don’t have a way to share it productively. So much knowledge not being applied! Except that’s not how we work as human beings. If you haven’t read it, experienced it, and contextualised it, then it isn’t knowledge to you. Knowledge is a quality that people possess, not documents, and the only way to transfer it from one place to another is for people at both ends to apply themselves and make it their own. Baldur Bjarnason, On online collaboration and our obligations as makers of software knowledgedocumentationwork
Dependence is more profitable than education A customer who pays—in advance—for service contracts is a more stable income source than a customer who has fully mastered a product's use. Customer dependence is more profitable than customer education. What I find truly baffling are manuals—hundreds of pages long—that accompany software applications, programming languages, and operating systems. Unmistakably, they signal both a contorted design that lacks clear concepts and an intent to hook customers. Niklaus Wirth, A Plea for Lean Software The design concept documentation
On Greatness What’s important to you in the development of a product? One of the things that really hurt Apple was that after I left John Sculley got a very serious disease. And that disease — I’ve seen other people get it too — it’s the disease of thinking that a really great idea is 90% of the work, and if you just tell all these other people “here’s this great idea,” then of course they can just go off and make it happen. The problem with that is that there’s just a tremendous amount of craftsmanship in between a great idea and a great product. And as you evolve that great idea it changes and grows. It never comes out like it starts, because you learn a lot more as you get into the subtleties of it, and you also find there are tremendous tradeoffs you have to make, there are just certain things you can’t make electrons do, there are certain things you can’t make plastic, or glass, or factories, or robots do. And as you get into all these things, you find that designing a product is keeping 5,000 things in your brain, these concepts, and just fitting them all together and continuing to push to fit them together in new and different ways to get what you want. And every day you discover a new problem or a new opportunity to do it a little differently. And it’s that process that is the magic. Steve Jobs, Steve Jobs: The Lost Interview The idea grows as they workThe Design SquiggleThe Nature of Product ideascraft