We engage in a lot of project based work; the two-sided problem of considering information flow and information flow design for both our stakeholders and for the underlying data structures. Going into Info-Ops I was pleasantly surprised to see that it wasn't your standard business book - it was relevant, had actionable advice, and was written by someone who had experience doing the kind of work that I do. For someone who reads their fair share of business books, this was a breath of fresh air!

At first I thought you were a funny guy, but arrogant. After reading the beginning of this book, I realize you're not actually arrogant - just really fucking capable. This may be the best book about process analysis I've ever read. OK, this may be the only book about process analysis I've ever read, but damn. This stuff is truly fantastic. Very, very well-considered and thought-provoking. I find this roughly on par, in its level of thought-provocation, as Doug Hofstadter's work. Damned fine work

If you want to be more agile you need to read this book. Daniel uses example information from real world stories to build a case for how to think differently about how your work gets accomplished. The first part identifies the importance of communication, experience, and understanding where you are in the scope of a thing. Focus on the heart of what needs to be done, keeping it simple, with just enough detail to cut across the skills of the team. A few good notes can be all it takes to begin.

My job is to balance software development with regards to process, delivery and collaboration. This book gave me a concrete way of looking at, understanding and managing the information that flows through a software development effort. It helped me understand underlying problems, gave me new ideas on how to work more pragmatically with semantics in software development. It will help you create a shared mental model in your team and beyond, and become the grease between business and tech.

Parts of this book are stories, that, while being interesting on their own, help explain what information is, and how to extract and handle it. Other parts are about human interactions, doing the right thing and not just waving hammers. And about possums. And weasels. Very thought provoking. I read it once and it already is paying off. I'm using ideas Daniel put in easily digested form in my daily work with my team, and clients. Partially thanks to that book? I got a promotion at work!

Teams ‘create mental models’ and ‘make analytical leaps’ as if those are real and not some kind of black art. A few great writers have tried to explain it. They haven't done very well. Daniel has a remarkable gift. He’s funny and entertaining, yet without realizing what’s happening, he has you thinking in his terms. Whilst you’re enjoying the metaphor of directing a scene in an alien invasion movie, he’s got your mind sorting and organizing. His gift is explaining how to perform the black magic.

This book really helped me understand more deeply not only how people really communicate but also to learn HOW to ensure a company is building the right products and why that's important to survival. In listening to the wisdom of product development thought-leaders like Daniel Markham, it's easy to see how we can avoid career-and-company-destroying mistakes while enjoy the success that well-placed products in the right market can provide.