Here’s a pasted version of our Account Trends Module V1 requirements that I pulled out from our Product Brief.
Version 1
| Abbrev | Focus Area | Description |
|---|---|---|
| B | Builder | The module builder where a user can build their trend visualization chart |
| I | Interactivity | Chart user interactivity that enables users to drive collaboration and action |
| E | Extensions | Extensions of trending data used outside of this Account object module |
<aside> 🎯 We want to provide a new Account-layout module where users can trend any Account field and its historical data values over time.
For the CS Ops and Managers, we want to deliver an intuitive and intelligent module building experience.
The resulting visualization needs to help prompt action from CSMs with their customers.
</aside>
| Abbrev | Phase | Priority | Requirement | Additional notes/questions |
|---|---|---|---|---|
| B1.1 | V1 | P1 | As an end user, I can select and create a new Trend-related module (name: ‘Historical Trends’) on an Account layout | |
| B2.1 | V1 | P1 | As an end user, I can select any Account field I want to chart | All Account fields are trend-able, including Health score changes and Calculated Fields (if possible, Product Usage CFs). Note: these values will be daily snapshots |
| B3.1 | V1 | P1 | As an end user, I can select a Table visualization type for all Account field types and additionally, a Line visualization for numeric field types | |
| B4.1 | V1 | P1 | As an end user, I am given a preview of the visualization I am building that changes dynamically based on my configurations | Callout from Engineering: This data can be placeholder, non-real data due to complications and latencies in calculating real data quickly for previews especially for CFs. Callout from Product/Design: be wary that we’re introducing a different experience than what is offered in other areas of the product today for module building |
| B5.1 | V1 | P1 | As an end user, I can set a custom numeric input and toggle between days (default), weeks, months, quarters time periods that follow our calendar | Does not include today or any form of “current time” option. We need to ensure including “yesterday’s” (full day) data will work without data syncing delays |
| B6.1 | V1 | P1 | As an end user, I can toggle a ‘time interval’ input to read by: Day (default), Week, Month, or Quarter which will subsequently adjust the x-axis label and measurement. | This will not attempt to roll up, sum, or smooth any non-numeric or Calculated Field chart. See next two sub requirements. |
| B6.2 | V1 | P1 | For numeric field selections, an end user can also toggle an aggregation type for the x-axis interval when selecting anything off of ‘Day’: SUM, MAX, MIN, AVG, Last Value in Period | |
| B6.3 | V1 | P1 | For all non-numeric field selections (and subsequently “table” visualizations), when the end user toggles a ‘time interval’ other than ‘Day’, we show the data value as of the “Last Value in Period” of that time interval. | E.g. a user selects the “sentiment” field and toggles the ‘time interval’ to show by “month”. The resulting Table visualization will show the month on the left-hand column and on the right, the “sentiment” value as of the last date per each month (i.e. July 31, Aug 31, Sept 30, Oct 31 etc.) |
| B7.1 | V1 | P2 | As an end user, if I have a numeric data type and “line” visualization, I can select a second field (of similar data type) to overlay and compare in my chart | (Fast follow enhancement) |
| B8.1 | V1 | P2 | As an end user, if I have a numeric data type and “line” visualization, I can set a dotted ‘Goal line’ across my chart after setting a Y-Axis value | (Fast follow enhancement) |
| I1.1 | V1 | P2 | As an end user, when I hover along any data point in my chart, I will see a tooltip of what that field value is, the date (or timeframe), and the % change from the last data point is (or timeframe) | |
| I2.1 | V1 | P1 | As an end user, I expect my Account trend module to load and render within 2 seconds in my Account permalink | Discuss: should we set the bar of sub 2-seconds for basic Account Fields but be more generous when it comes to CFs powered by Product Usage data (or more complex CFs)? |
| I3.1 | V1 | P1 | As an end user, I can see a null value for non-numeric data types in my “Table” visualization |
Future versions (V2 onward)
<aside> 🗣️ Our initial V1 (purposely) set forth ambitious requirements to satisfy the best solution we thought possible and throughout Product <> Engineering negotiation, we’ve naturally scoped requirements into a post-release or future iteration bucket, see below.
</aside>
| Abbrev | Phase | Requirement | Additional notes/questions |
|---|---|---|---|
| B3.2 | V2 | As an end user, I can select a Bar or Pie chart visualization for numeric field types | |
| B9.1 | V2 | As an end user, I can GROUP BY with N number of Account fields | |
| B10.1 | V2 | As an end user, I can select a specific timeframe or start date for my Trend module | E.g. “start since Jun 15 until current date” or specifically “Oct 1 - Jan 31” |
| B11.1 | V2 | As an end user, I can set the field % change or threshold (higher, lower, or exactly X value) that will highlight in my chart more boldly | |
| B12.1 | V2 | As an end user, I can boolean toggle if I want null values to appear or not | Design: If we count null as 0, would this affect aggregation calculations? |
| I3.1 | V2 | As an end user, I can hover over a data point and I will see the date(s) of drastic field % changes | This is a call out for a Health specific module to help users pinpoint the specific date(s) that an account’s health shifted dramatically. |
| I4.1 | V2 | As an end user, I can click and drill-down along any data point in my chart which will reveal a mini-form showing all of its relevant raw data | Product: This may be in practice difficult and need some decisions. Is the drill down the ability to click on a single time period and see the data that makes up that time period? If it’s anything beyond a day, will it be aggregated for that time period? |
| I5.1 | V2 | As an end user, I can toggle my chart to show me what the rolling average timeframe looks like for line charts that have numeric data type | Product: we should not include this in the module builder but offer it as something a user can toggle on a line chart temporarily as they interact with it. |
| I6.1 | V2 | As an end user, I can toggle a different timeframe of this module that’s already built without changing anyone else’s view or the module itself (i.e. temporary view change on the spot). | |
| I7.1 | V2 | As an end user, I can click any data point in my chart and annotate by leaving a comment and at mentioning a user | |
| I8.1 | V2 | As an end user, when I hover over any data point, I can automatically see a list of any Playbooks that may have been triggered by that change in field value (if applicable) | |
| E1.1 | Unknown | Replace the existing “Product Adoption” line visualization with the same module visualization that is created as a result | This is an important future step that will also be key in determining the future migration off of Success Metrics - this is a DNA Team decision. |
| E2.1 | Unknown | Replace or enhance existing ‘Trends’ module offered in our Home layouts with our V1 module build | We need to be ready and confident that Aggregate modules have the functionality that’s missing (such as GROUP BY, user reference fields) before this - this is a DNA Team decision. |
| E3.1 | V2 | As a user, I can set the parameters of which months belong to which quarters (i.e. mapping my Fiscal Year) via Settings tab (?) | It’s an important feature request for users given that JAN 1 may not always be the start of Q1 for customers (often, it is FEB 1). |