About this dashboard

The Revenue Dashboard is a Tableau workbook serving DocuSign Revenue Accounting and FP&A leadership as the single source of truth for revenue performance, recognition, and contract-level research. Phase 1 is a four-tab, two-tier architecture - aggregated extract for executive views (Tabs 1-2), parameter-injected live SQL for research views (Tabs 3-4) - replacing the prior one-size-fits-all flat extract that struggles at 50M-217M rows.

Wireframe status: Phase 1A. The HTML in this folder is a stakeholder-review mockup, not a functional Tableau workbook. Phase 1B builds the workbook against RevPro + SFDC in Snowflake.

Audience & usage

Out of scope for Phase 1: RevPro Reconciliation team (Phase 2, revisit ~2 weeks after Phase 1 progress). VP Rev Rec specific use cases to be solicited via the Primary Stakeholder, with the Project Sponsor as escalation path (OQ-14).

Data sources

Refresh cadence

• Default: Daily, aligned with Snowflake refresh.
• The "Data as of" timestamp shown in every tab header reflects the most recent extract refresh, not query time.
• Source-system-to-Snowflake timing gaps may produce small source-vs-warehouse discrepancies. Surface these to users via this Read Me when they appear.
• Refresh failures are surfaced via Tableau Server alerts to the FBT team; users see a stale "Data as of" timestamp.

Measure definitions

Pivots / dimensions

Pivots are exposed on Tab 3 (Research). Tab 1 exposes one primary segmentation with toggle (default Business Source). Tab 2 features the top 4 higher-priority dimensions in the small multiples grid; the remainder is selectable via the long-tail dropdown. Owner Segment and Territory Segment are tagged Low priority across all surfaces pending the GDA segment-mapping conversation (OQ-13).

Performance contracts

The current production dashboard's performance is the project's primary risk. Each tab has a published target load time and a clearly stated strategy.

Design rationale (what changed vs the prior mock)

The earlier dark-theme prototype was rejected for the following reasons. Each is fixed in this Phase 1 design:

• Dark theme & purple-to-pink gradient header. Replaced with light theme on white / Ecru, flat header. Aligns with ARR Dashboard convention and Brand Identity Guidelines v2.0.
• Rejected KPI strip (Revenue Contract count, Debit Amount, Reporting Debit USD, Credit Amount, Reporting Credit USD). The Primary Stakeholder stripped this down to Revenue only because the non-Revenue tiles were accounting mechanics, not stakeholder questions. Replaced with five KPIs that each map 1:1 to Section 3.1 questions (Q1.1 Revenue, Q1.2 TCV, Q1.3 ACV, Q1.4 # Opps, Q1.5 # RCs). See OQ-3 in ASSUMPTIONS.md for risk + mitigation.
• Redundant donut + horizontal bar showing the same Business Source breakdown. Cole Knaflic principle: if two charts answer the same question, kill one. Tab 1 segmentation is now a single bar chart with a dimension toggle.
• Oversized right-side filter rail with stacked "Summary Pivot / Period Pivot / Period Filter / Measurement" controls. Tab 1 is now scannable with minimal controls; the dense filter rail moves to Tab 3 where it belongs (research surface).
• 14-pivot exposure on the summary tab. Pivots are research tools, not summary tools. Tab 1 has one primary segmentation with toggle; Tab 3 exposes everything.
• Ambiguous YoY delta (full-year vs partial-year). Every KPI tile now states YTD vs prior YTD explicitly to address the Project Lead's stated concern (OQ-7).

Cole Knaflic / Tufte / Few applied by audience tier: Tab 1 leans Knaflic (minimal, scannable, opinionated for FP&A leadership); Tabs 3 & 4 lean Few (dense, configurable, research-grade for revenue accounting); Tab 2 sits in between.

Reference dashboards

Existing FBT dashboards used as patterns or anti-patterns for this build:

Wireframe assumptions

Every open question that touches the wireframe has a documented assumption in ASSUMPTIONS.md. Summary as of req doc v1.1 (post 4/27/26 PM review):

• OQ-1 (architecture): RESOLVED 4/27/26 PM Dual-tier approved. Physical workbook split deferred to Phase 1B.
• OQ-2 (default segmentation): RESOLVED 4/27/26 PM Business Source default. Owner / Territory Segment deferred (OQ-13).
• OQ-3 (KPI strip): PARTIALLY RESOLVED Built with 6 KPIs (Revenue, TCV, ACV, # SFDC Accounts, # RCs, # Opps). # Opps is the explicit cut-line if the Primary Stakeholder pushes back on density.
• OQ-4 (look-back window): OPEN Wireframe uses 3 fiscal years.
• OQ-6 (future schedule): OPEN Built with placeholder + caveat; removable if data unavailable. Tab 4 deprioritization in v1.1 partly driven by this.
• OQ-7 (YoY convention): OPEN YTD vs prior YTD explicitly labeled per tile. Recompute behavior under period filter changes still TBD.
• OQ-8 (top-4 dimensions for Tab 2): RESOLVED 4/27/26 PM Business Source, Product Line, Account Region, Currency.
• OQ-9 (mandatory pre-filters on Tab 3): OPEN Period only confirmed mandatory. Additional pre-filters pending user testing.
• OQ-12 (typography): OPEN Arial as Tableau-safe default for Docusign Indigo.
• OQ-13 (GDA segment-mapping): NEW - OPEN Surfaced 4/27/26 PM by the Project Sponsor. Blocks Owner / Territory Segment promotion. Same conversation needed for ARR build.
• OQ-14 (VP Rev Rec / Rev Rec team use cases): NEW - OPEN Solicit via the Primary Stakeholder; Project Sponsor as fallback escalation.
• OQ-15 (Phase 2 RevPro recon scope): NEW - OPEN RevPro Recon team. Revisit ~2 weeks post Phase 1.

OQ-5 (Tableau parameter SQL feasibility), OQ-10 (build-new vs reuse extract), and OQ-11 (access provisioning) are build-phase technical questions, not wireframe-relevant.

Known gaps

FBT contacts

Change log