Q&A: Abstract Deliverables
How do we handle projects that start with abstract outcomes?
Many projects in mission-driven organizations begin with a spark of an idea, a desired change, or a complex problem to solve. These starting points often have abstract outcomes, requiring a period of exploration and research before we can even define the concrete deliverables that will ultimately achieve that outcome.
In these situations, clearly defining a project scope is critical, as it provides purpose and direction during the exploratory phase. Our scope should answer the questions: "What is the problem we are trying to solve?” and “What is the ultimate outcome we are trying to achieve?”.
To avoid the project getting bogged down in endless exploration, it's essential to set concrete deliverables or outcomes and a firm deadline for this initial phase. This creates a sense of urgency and keeps the project moving forward. These initial deliverables might take the form of a research report summarizing findings, a feasibility study outlining potential approaches, or a documented analysis of the problem.
One of the key deliverables of this initial phase should be a clear definition of the project's ultimate outcomes and deliverables. In other words, the exploration phase shouldn't just be about understanding the problem; it should also produce a concrete plan for how to solve it. This plan will provide the foundation upon which the subsequent phases of the project will be built.
Our project scope and initial deliverables act as a bridge, translating the abstract starting point into a tangible roadmap for the rest of the project.
Need more support leading successful projects?
Learn about our Project Services, schedule an introductory call with Jami Yazdani, or add a 1-hr Project Coaching Session to our calendar!
