tDS Project Brief

The one-page brief I use to scope every data engagement — purpose, deliverables, timelines, cost, and a RACI table. Copy it, fill it in, and align stakeholders before a line of SQL gets written.

Primary Outcome

A shared, agreed scope document that aligns stakeholders on deliverables, timelines, cost, and ownership before work begins.

Solution

A one-page brief that pins down purpose, deliverables, timeline, cost, and a RACI ownership table before work starts — and stays the reference point throughout.

Deliverables

  • A purpose section that states the business value of the project

  • A structured deliverables list (presentations, dashboards, data)

  • A timeline table with format, date range, work hours, and estimated cost

  • A RACI table mapping each deliverable to responsible, accountable, consulted, and informed parties

  • A notes section for resources and existing work

Strategic Context

Most data projects don't fail technically. They fail on alignment — unclear deliverables, fuzzy ownership, and a cost nobody agreed to. A brief forces those decisions to the front, where they're cheap to make, instead of the middle, where they're expensive.

Technical Architecture

Most data projects don't fail technically. They fail on alignment — unclear deliverables, fuzzy ownership, and a cost nobody agreed to. A brief forces those decisions to the front, where they're cheap to make, instead of the middle, where they're expensive.

Problem Statement

Data projects start without agreed scope, so deliverables drift, ownership is fuzzy, and cost balloons. By the time misalignment surfaces, it's expensive to fix.

Links

What's Included

A ready-to-copy Google Doc with an Overview (purpose, deliverables, timelines) and Notes (resources, existing work), including pre-built timeline and RACI tables you fill in.

FAQs

Is this only for consultants?

No. Internal data leaders use it to scope projects with stakeholders just as much as consultants use it with clients.

Can I change the deliverable types?

Yes — the timeline and RACI tables are templates. Swap in whatever your project actually produces.

Tech Stack

Tool 1

Tool 4

Tool 4

Tool 3

Tool 2

Tool 4

Primary Outcome

A shared, agreed scope document that aligns stakeholders on deliverables, timelines, cost, and ownership before work begins.

Problem Statement

Data projects start without agreed scope, so deliverables drift, ownership is fuzzy, and cost balloons. By the time misalignment surfaces, it's expensive to fix.

Solution

A one-page brief that pins down purpose, deliverables, timeline, cost, and a RACI ownership table before work starts — and stays the reference point throughout.

Links

Deliverables

  • A purpose section that states the business value of the project

  • A structured deliverables list (presentations, dashboards, data)

  • A timeline table with format, date range, work hours, and estimated cost

  • A RACI table mapping each deliverable to responsible, accountable, consulted, and informed parties

  • A notes section for resources and existing work

What's Included

A ready-to-copy Google Doc with an Overview (purpose, deliverables, timelines) and Notes (resources, existing work), including pre-built timeline and RACI tables you fill in.

Strategic Context

Most data projects don't fail technically. They fail on alignment — unclear deliverables, fuzzy ownership, and a cost nobody agreed to. A brief forces those decisions to the front, where they're cheap to make, instead of the middle, where they're expensive.

FAQs

Is this only for consultants?

No. Internal data leaders use it to scope projects with stakeholders just as much as consultants use it with clients.

Can I change the deliverable types?

Yes — the timeline and RACI tables are templates. Swap in whatever your project actually produces.

Technical Architecture

Most data projects don't fail technically. They fail on alignment — unclear deliverables, fuzzy ownership, and a cost nobody agreed to. A brief forces those decisions to the front, where they're cheap to make, instead of the middle, where they're expensive.

Tech Stack

Tool 1

Tool 4

Tool 4

Tool 3

Tool 2

Tool 4