Project Management · WEREP PERSPECTIVE
Before the plan: five conversations that give a project direction
A schedule can organize activity. Shared understanding gives that activity a purpose. Start with the decisions that make delivery possible.
Start with the problem the business needs to solve
A project often arrives as a request for a system, a process, or a deadline. Those are useful starting points, but they do not fully describe the business need. Ask what is difficult today, who experiences the problem, and what should be different when the work is complete.
Translate the answers into a short outcome statement. If different stakeholders describe different outcomes, address the difference before turning the request into a detailed plan. Otherwise, the schedule may hide a disagreement that returns at the point of acceptance.
Agree what success and acceptance mean
Identify how the organization will recognize a useful result. Consider the deliverables, the operational conditions required to use them, and the evidence needed for acceptance. A technically complete release may still be difficult to adopt if responsibilities, data, or support arrangements are unresolved.
Keep the measures proportionate. A small initiative may need a short acceptance checklist; a larger program may need several business owners to confirm readiness. The important point is that the standard is visible before the team commits to delivery.
Name the decisions, constraints, and assumptions
Clarify who can approve scope, resolve cross-team priorities, and accept the result. Give escalation a practical route: what decision is needed, who owns it, and when a delay starts to affect the plan.
Then record the assumptions behind the first estimate. Availability of key people, access to information, supplier dependencies, and fixed business dates all influence the outlook. Treat these as conditions to review, rather than facts that disappear into a planning document.
Build the first plan around learning
Use the early plan to answer the largest uncertainties. Sequence discovery, validation, and stakeholder decisions alongside delivery activities. The plan becomes more credible as the team replaces assumptions with evidence.
A useful kickoff ends with a common understanding of the outcome, the immediate work, the accountable owners, and the next decision. That foundation gives later reporting something meaningful to measure against.
Include the people who will own the result
Bring the future operating owner into the early conversation. Ask what information, support, and acceptance evidence will be needed to use the result after the project team steps back. A useful handover is easier to prepare when ownership is discussed at the start.
Before approving the next stage, review whether the outcome, acceptance conditions, decision rights, assumptions, and operating ownership still describe the same piece of work. Resolve differences while the plan can still respond to them.
WEREP editorial perspective
Discuss your priorities