Working Together

Working With DDPW

A good engagement should be understandable before the work gets complicated. This page explains how DDPW approaches scope, communication, review, changes and project handoff.

Before work begins

Start with a visible definition of the project.

Objective

Define the result

Identify what the project is meant to improve, create, clarify or decide. The objective should be specific enough to guide tradeoffs.

Scope

Name the deliverables

List the pages, documents, systems, research outputs or other assets expected from the engagement.

Inputs

Identify dependencies

Clarify which files, access, approvals, source materials, account credentials or decisions are needed before work can move efficiently.

Timing

Set realistic sequencing

Separate true deadlines from preferences, and identify which steps depend on earlier approvals or materials.

Review

Define feedback points

Decide where review is useful so feedback arrives before large downstream changes become expensive.

Definition of Done

Make completion visible

Agree on what successful completion means rather than relying on a vague sense that the project feels finished.

During the project

Keep communication proportional to the work.

Small assignments should not require enterprise-level ceremony. Larger projects do benefit from milestones, decision logs, documented approvals and visible next steps. The amount of process should match the amount of risk, complexity and coordination involved.

When something changes, DDPW’s preference is to identify whether the change affects scope, timing, dependencies or the definition of done. That keeps new requests from quietly turning into a different project.

At completion

Leave behind something usable.

Final Assets

Deliver the current working version

Final files, pages, reports or project materials should be distinguishable from drafts and abandoned directions.

Handoff

Explain what matters next

Where useful, provide practical notes about maintenance, ownership, future updates or unresolved items.

Reference

Preserve important decisions

Keep the key source material, project logic and major decisions easy to locate after the active work ends.

Start a Project

Project controls

Keep change and completion visible.

Scroll to Top