Drawing Boundaries


Esther and I are editing (the next-to-final pass, we think) the book this week, integrating comments from our reviewers. We are very fortunate; our reviewers provided wonderful feedback. And some of the feedback we're not going to use — at least, not in this book.

One of the hardest things to do, whether it's in a book or in a project (or many other undertakings), is to decide what you're not going to do. As we're walking through the comments, we've been asking ourselves, “Is that comment for this book?” We've been drawing the boundaries around what we decided to accomplish with this book, and we're not adding more.

This is frustrating, relieving, and freeing for me all at the same time. It's frustrating, because I would like to address many of these topics. But it's relieving , because our reviewers want us to address these topics, and many of them will be going into my project management book (which has been put aside for the moment), to finish this book. Our boundaries are freeing for me, because I don't have to consider things outside of the boundary for this book; I can consider them for future writing.

Esther and I decided on our boundaries for this book with something that looks like a project charter (but was our purpose for writing the book). If you haven't developed a project charter yet for your project, do so. It will help you draw — and keep — the boundaries on your project.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.