Skip to main content

The Pumpkin Plan

From time to time I'll read a book about how to start or grow a business and I realize that there are lessons that apply not only to entrepreneurs, but also to anyone trying to manage their projects. The Pumpkin Plan: A Simple Strategy to Grow a Remarkable Business in Any Field is one of those books. It describes how to transition from an unsustainable situation where the people who start a company are over committed and doing all the work, to a sustainable organization where you can have a reasonable work/life balance, and create systems that allow your company to scale.While the details of the stories and techniques in the book are focused on business owners, there are lessons anyone whose work involves juggling priorities. I was glad to have had the chance to get a review copy of this book.

The Pumpkin Plan is addressed to entrepreneurs who have businesses that may have customers, but which aren't growing. The author delivers on his promise of providing guidance for helping your business grow. Once you read the advice, you may think that some of it is obvious, but the author helps you bridge the gap between knowing what to do and convincing your self you do it. For example, one core bit of advice is to focus on your best customers and spend less (or no) energy on the others. The book provides detailed guidance for how to decide who "the best" customers are and walks you through your reservations about letting (bad) customers slip away. This is a great example of what makes this a great business book: it acknowledges the human side of the decisions an entrepreneur needs to make.

Many of the lessons in the book will be familiar to those familiar with agile and lean methods, or who have read books like The Secrets of Consulting. Michalowicz frames these lessons and provides practical advice to entrepreneurs, with guidelines, examples and real stories.

The book is written in way that allows to to start applying the advice before you finish the book. (After reading the first few chapters I recommended the book to a family member who had been discussing how she was looking for ways to help her small business grow.). As to the title: not only is the metaphor between growing pumpkins and growing a business apt, the author applies it consistently throughout the book, in a way that makes sense.

Reading The Pumpkin Plan will serve you well if you have a business. If you're not a business person, reading book could help inspire you to apply an entrepreneurial approach to the way you work, regardless of your role.

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…