Skip to main content

Mindfulness, Resilience and Positive Intelligence (Book Review)

I got a copy of Positive Intelligence at the recommendation of a leadership coach. After having done the “Saboteur” quiz on the Positive Intelligence site, I wanted to learn more about the his approach. While the book gets at some of the concepts I've seen in other places, the approach is worth exploring.

The positive intelligence framework is that we have within us Saboteurs, which hold us back, and a Sage, which helps us explore possibilities. While the anthropomorphism initially made me feel a bit awkward, there is some power in ascribing non-productive reactions to a part of your thought process, and giving it a name. The book explains techniques to both be more attentive to, and thus able to suppress, your saboteurs, and also how to “strengthen” your Sage, so you can treat setbacks as opportunities more readily.

Some of the basic themes of Positive Intelligence may sound familiar if you’ve spent any time learning about team leadership, but Chamine’s way of modeling them adds an interesting and compelling twist. Saboteurs are reminiscent of the concept of “survival rules” that I first learned about while reading one of Jerry Weinberg’s Becoming a Technical Leader. Like survival rules, saboteurs are useful in certain circumstances, but have negative effects when you misapply them. Chamine describes how each Saboteur manifests themselves in terms of how you feel, act, and how others may perceive you. He then describes techniques to become more aware of them so that you can take a step back and act appropriately.

In short, this is a book about mindfulness and resilience, both very useful concepts that are very difficult to apply. Even if you feel like you have a basic appreciation of the how to be be more mindful and resilient, reading about them again, and considering a slightly different approach to achieving them can’t hurt.

While it has a business focus, you can apply what you learn to both personal and work situations. The author also explains how to apply the model and techniques in individual and team contexts. And while not about Agile, the book also left me with some ideas for activities to use in Sprint Retrospectives, which are after all, a practice teams use to be more mindful and resilient.

Positive Intelligence is a rather quick read (but you will want to take notes and mark pages), which mixes discussions, stories, and practices, so you can apply what you’ve learned. The book also makes frequent references to resource on the companion website. If you feel that negative reactions are holding you back, even subtly, this book is worth a read.


Comments

Popular posts from this blog

Continuous Integration of Python Code with Unit Tests and Maven

My main development language is Java, but I also some work in Python for deployment and related tools. Being a big fan of unit testing I write unit tests in Python using PyUnit. Being a big fan of Maven and Continuous Integration, I really want the  Python unit tests to run as part of the build. I wanted to have a solution that met the following criteria:
Used commonly available pluginsKeep the maven structure of test and src files in the appropriate directories.Have the tests run in the test phase and fail the build when the tests fail.
The simplest approach I came up with to do this was to use the Exec Maven Plugin by adding the following configuration to your (python) project's POM.

<plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <executions> <execution> <configuration> <executable>python</executable> <workingDirectory>src/test/python</workingDirect…

Displaying Build Numbers in Grails Apps

Being a fan of Continuous Delivery, identifiable builds, and Continuous Integration: I like to deploy web apps with a visible build number, or some other way of identifying the version. For example, having the build number on the login screen for example. In the Maven/Java world, this is straightforward. Or at least I know the idioms. I struggled with this a bit while working on a Grails app,  and wanted to share my solution. There may be other, better, solutions, but the ones I found approaches that didn't quite work they way that I'd hoped.

My requirements were:
To display a build number from my CI tool, where the number was passed in on the command line. In Bamboo, for example you might configure a grails build as
-Dbuild.number=${bamboo.buildNumber} warTo only change build artifacts and not any source files.To not misuse the app version, or change the names of any artifacts.To be simple and idiomatic.I realized that that Grails itself changes the application metadata (appl…

Motivation Visibility, and Unit Testing

I've always been interested in organizational patterns (such as those in Organizational Patterns of Agile Software Development). I've recently found myself thinking a lot about motivation. I'm now reading Drive: The Surprising Truth About What Motivates Us and just finished Rob Austin's book on performance measurement. Being the parent of a three year old, I'm finding more and more that "because I said so, and I'm right" isn't too effective at home. My interests in motivation are closely related to my interest in writing software effectively. Writing software is partially a technical problem about frameworks, coding, and the like, but the harder (and perhaps more interesting) problem is how to get a group of people working together towards a common goal. Agile practices, both technical and organizational, build a framework which makes having the right amount of collaboration and feedback possible. But there's a bootstrapping process: How do yo…