Deck Docs
Features

Projects

Track delivery work from customer evidence through execution links.

Projects

Projects live in the Build section and help you turn customer evidence into delivery-ready work. Use Projects when you want a focused artifact for a feature, fix, or product bet that can stay connected to initiatives, customer insights, and execution tools.

Open Projects

Go to Build -> Projects to see every Project in your organization. The list supports:

  • status tabs for active and completed work
  • search by Project title or linked context
  • segment and date filtering when those fields are available
  • quick creation from Deck
  • import from connected Linear or Jira accounts

You can also search for Projects from the command palette.

Create a Project

  1. Open Build -> Projects.
  2. Click New Project.
  3. Add a title and optional description.
  4. Optionally link the Project to an initiative.
  5. If your organization uses segments, choose the segment this Project is for.

Deck creates the Project immediately so you can fill in the document, status, owner, and dates.

You can also create a Project from an opportunity in Build -> Opportunity Backlog:

  1. Open an opportunity detail page.
  2. Open the action menu.
  3. Select Create Project.
  4. Add a Project title and optional description.
  5. Choose whether Deck should generate AI evidence for the new Project.

Deck links the new Project back to the opportunity and seeds it with the opportunity's direct insight evidence. If AI evidence generation is enabled, Deck drafts the Project overview and Evidence story from those seeded insights plus broader matching feedback.

Project Documents

Each Project has three document sections:

SectionUse it for
OverviewThe problem, scope, customer context, and intended solution
EvidenceLinked insights, quotes, and generated evidence stories
Success MetricsHow you will evaluate whether the Project worked

Project documents autosave while you edit. You can update the Project title, lifecycle status, start date, and target date from the Project header.

When a Project has linked insights or generated Evidence citations, click Related Insights to open a side sheet with the supporting insight cards. Selecting an insight keeps you in the Project and opens the source detail in the same sheet.

Work From an Initiative

Projects can be linked to initiatives. When you open an initiative, the Projects view shows the related Projects in the same document layout as the standalone Project page.

Use this when an initiative has multiple execution threads, such as separate onboarding, reporting, or integration Projects.

Generate With Customer Evidence

Projects can store an active evidence set, and Deck's AI can also search broader organization feedback when generating Project documents. Use generation when you want Deck to draft or refresh Overview, Evidence, or Success Metrics from the Project title, existing sections, initiative context, optional instructions, opportunity-seeded evidence, and discovered customer evidence.

Active linked insights and opportunity-seeded insights are treated as supplemental context. Generated Evidence cites the customer insights it uses, and Deck saves those citations back to the Project's evidence references.

Connect Linear or Jira

If Linear or Jira is connected in Settings -> Integrations, Projects can be connected to execution artifacts:

  • import an existing Linear Project into Deck
  • import an existing Jira Epic into Deck
  • link an existing Deck Project to a Linear Project or Jira Epic
  • create a new Linear Project or Jira Epic from a Deck Project

Deck stores the external link and copied metadata on the Project. Unlinking removes only the Deck-side connection; it does not delete the Linear Project or Jira Epic.

After import or linking, Deck refreshes provider-owned top-level metadata daily for connected Linear Projects and Jira Epics. Project documents, Evidence, Success Metrics, and generated sections stay Deck-owned and are not overwritten by provider sync.

Statuses

Projects use these lifecycle statuses:

StatusMeaning
Not startedThe Project is defined but not actively being built
In progressWork is underway
CompletedThe Project has shipped or is otherwise done
ArchivedThe Project is no longer active

To archive a Project, open the Project action menu and select Archive Project. Archived Projects are hidden from active Project views but preserved for history. Existing Jira or Linear links remain attached to the archived Project record.