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 four tabs:

Overview, Evidence, and Success Metrics are rich-text document sections that autosave while you edit. Feedback is a structured validation view (not a document section): linked widget sources, response health, a filterable response feed, and an optional project-level summary.

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.

Use Success Metrics before and after release to define what should change, then compare new customer feedback against the Project's evidence over time.

Feedback Tab

Use Feedback when you want a continuous validation loop for product surfaces that collect in-product widget responses — without mixing that signal into discovery Evidence.

What you will see

• A Feedback tab badge with the total response count across linked widgets
• Each linked widget with response count, last response time, and a deep link to Manage → Widgets
• A multi-widget source filter when more than one widget is linked
• Health metrics such as total responses, written comments, rating-only responses, and sentiment mix
• A feed of individual submissions
• Summarize feedback to generate or refresh a project-level aggregate summary of written comments

Linking widgets

Link a widget to a Project from Manage → Widgets (or during widget setup). That membership routes submissions to this Project’s Feedback tab only. Deck does not automatically add widget responses as Project Evidence or Related Insights.

If no widgets are linked, the Feedback tab shows an empty state with guidance to connect widgets.

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.

Automatic Insight Matching

After new feedback is processed, Deck can automatically relate high-confidence insights to relevant Projects. This works across feedback sources such as Slack, support conversations, surveys, NPS, interviews, Gong calls, and CSV imports.

Automatic matching is useful after a Project ships. For example, if a completed dashboard redesign starts receiving customer comments two days after launch, Deck can attach those new outcome insights back to the dashboard redesign Project so the evidence stays current.

Deck only attaches relationships above its confidence threshold. Manual evidence links remain editable from Related Insights.

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. When you link an existing Deck Project to a Linear Project or Jira Epic, Deck can fill missing execution fields from the provider: status when the Project is still Not started, plus empty start and target dates when the provider supplies them. Deck does not replace your Project title, owner, description, segments, or document sections during this linking step.

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:

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.