"[Starting a Project] without a clear purpose is like setting sail without a destination—you might enjoy the journey, but you'll never know if you've arrived." — Anonymous
In our previous post, we gave some examples of identifying stakeholders when initiating a project. Now, let's continue looking at those same examples via the next crucial step: establishing the project's mission statement, which will answer the question of "Why are we doing this project?"
Understanding the "why" behind a project is fundamental to its success. It provides direction, motivation, and a benchmark against which all decisions can be measured. Let's revisit our examples to illustrate the importance of defining the "why,” including how this can shape the entire project:
Example A: Let's Bake a Cake
When baking a cake, the "why" goes beyond simply creating a dessert. Is it to celebrate a special occasion? To showcase your baking skills? To experiment with new flavors? Each purpose will lead to different decisions in the cake-making process.
For instance, if the cake is for a child's birthday party, the "why" (a/k/a the “mission”) might be "to create a fun, colorful, and delicious centerpiece that will delight the birthday child and impress the guests." This mission statement would clearly guide decisions about the cake's design, flavors, and decorations.
In contrast, if the cake is for a chic, high-end wedding celebration, the cake requirements will be quite different. The same is true if the cake is for someone retiring from their job, but they have severe food allergies that must be accounted for. And so forth. Regardless, all of these types of decisions will be driven by the “why” behind the cake project.
Example B: Let's Write a Book
The "why" behind writing a book can also vary. Is it to inform, educate, entertain, inspire, or perhaps something else? Maybe it's to establish yourself as an expert in your field; i.e., serve as a type of “business card on steroids” that you can point to. Or maybe it’s simply to fulfill a lifelong dream to say you’re an author. If you're writing a self-help book, your mission statement might be "to provide readers with practical, actionable advice that can significantly improve their lives."
Truly understanding the "why" behind a book can and should influence your writing style, the examples you choose, and even the book's structure and outline. Who is the book for—and why do they need it?
Example C: Let's Design a House
The mission of a house design project typically extends beyond simply creating a shelter. Are you designing for comfort, sustainability, luxury, or practicality? Is the goal to create a forever home for a growing family, or a minimalist retreat for a single retiree? For a sustainable home project, the mission statement might be "to design an energy-efficient, environmentally friendly house that minimizes carbon footprint while maximizing comfort and functionality."
Knowing who the house is for—and then why they want it—will drive the majority of decisions, ranging from location, to materials, to energy systems, and, of course, the overall size and layout of the house.
Example D: Let's Go Nuclear!
The "why" behind constructing a nuclear power plant is complex and multifaceted. Is it to meet the growing energy demands of a specific region of the country? To reduce the nation’s reliance on fossil fuels? To boost the local economy? Maybe all of these things. Perhaps it’s a research reactor, where medical isotopes will be created for experimental treatments.
A simplified power plant mission statement could be "to provide a reliable, long-term source of clean energy that will meet the region's growing power needs while contributing to national energy independence and environmental goals." This purpose would obviously guide decisions about the plant's capacity, location, and technology choices.
Bonus Example: Inertial Simulator
In my last post, I brought up a real world project management example in which I had no clue in what I was doing. And as I alluded to, I think this was deliberate by my boss; i.e., he wanted me to fail so that I could learn—and the first lesson I absorbed was the importance of identifying my stakeholders—which I initially ignored. The second hard lesson was this one: the importance of establishing a clear mission for the project.
In hindsight, I can clearly see how a definitive "why" could have prevented many of my initial missteps and wasted time. A mission statement might have been something like "to create a versatile, accurate testing platform that enables control systems engineers to safely validate satellite control algorithms across a range of simulated satellite sizes and behaviors." This clear purpose would have immediately highlighted the need to consult with the aforementioned control systems engineers, consider all design parameters, and address safety concerns from the outset. My failure to do this up front cost me weeks of wasted work—and more than a little embarrassment. Sigh.
The Bottom Line:
Establishing a clear and compelling "why" for your project is as crucial as identifying its key stakeholders. The mission provides a north star to guide key project decisions, helps align team efforts, and, most importantly, ensures that the final deliverable meets its intended purpose. Whether you're baking a cake or building a nuclear power plant, starting with a well-defined mission statement sets the foundation for project success. Keeping the "why" at the forefront ensures that your project remains relevant, valuable, and on track to deliver meaningful results.