Contents
Purpose
Report Data
Process Flow
Create Summary Pivot Tables
Update the Master TTV Report
TTV Review
Purpose
Time to Value (TTV) is a measurement of the duration of a project from project start to when the customer is “live” or using the product to run their business. It is a critical measurement that helps forecast when the revenue for the project should be recognized.
It also helps identify projects by product and project type throughput changes. Fluctuations in TTV value can be reviewed to determine reasons for increase and areas of focus for the business to drive improvement.
TTV should not be confused with when customers are billed for their monthly fees. Monthly fees begin at start of UAT (install for license projects). TTV is when the customer is using it to run their business.
On the first workday of each month, a report is run to pull current project data to build data graphs for in flight and completed projects by Product and Project Type.
Note: You can also subscribe to the TTV From Project Create Date report and have it delivered to your email each month to ensure the report is ran timely.
Report Data
Fields within the project will determine TTV. The Project Manager (PM) must have accurate data within the project fields to prevent skewing the data.
The report used to pull the project data from Salesforce is TTV From Project Create Date.
The following fields are used to generate the data:
- Product - The product the project is for
- Source: Row formula field that pulls the first two letters of the Project name to determine the product the project is for
- Formula: LEFT(CUST_NAME, 2)
- Use: Assist with breakout of data TTV values by product
- Total On-Hold Duration days - Number of days the project has been on hold
- Source: Project Field: Total On-Hold Duration Days
- Use:
- Shows the total number of days a project has been on hold and unable to move forward. These days are removed to show TTV as the actual number of days the product was able to be worked vs stalled.
- Track the number and days projects are stalled
- Opportunity Close Date
- Source: Opportunity field: Opportunity Close Date
- Use: Starting date to calculate the Opportunity TTV (OPP TTV)
- TaskRay Project Created Date
- Source: TaskRay Project field: TaskRay Project Created Date
- Use: Starting date to calculate the Project TTV
- Go-Live Date
- Source: TaskRay Project field: Go-Live Date showing the date the customer was able to use the product to drive their business
- Use: This is the target TTV end date. Calculates the end date for the project for TTV if populated
- Estimated Go-Live Date
- Source: TaskRay Project field: Estimated Go-Live Date showing the date the project should go live
- Use: Calculates the end date for the project for TTV if populated and project has not gone live yet
- Actual Completion Date
- Source: TaskRay Project field: Actual Completion Date showing the date the project closed
- Use: Calculates the end date for the project for TTV if populated and project has no Go-Live Date
- Project Stage
- Source: TaskRay Project field: Project Stage which shows the stage the project is in
- Initiating
- Planning
- Executing
- Closing
- Complete - All project deliverables in scope have been completed
- Expired - Hours sold for the project have expired. Project scope may or may not have been delivered in full
- Terminated By Customer - Projects under old MSA that did not include hours that expire but customer is unresponsive
- Contract Cancelation - Customer requested project be canceled. Project scope may or may not have been delivered in full
- Use: Calculates Determines if project is in flight or completed
- In flight = all open project
- Closed = all projects in Complete/Expired status
- Source: TaskRay Project field: Project Stage which shows the stage the project is in
- Status Reason
- Source: TaskRay Project field: Status Reason showing the reason a project is in the current stage
- Use: Reference field to help ensure accuracy of other field data (Project Stage)
- Project Type
- Source: TaskRay Project field: Project Type:
- Add-On
- Migration
- New Implementation
- Rework
- Use: Used to break out TTV data into like project types to help narrow down long TTV by project type
- Source: TaskRay Project field: Project Type:
- Project State
- Source: Report Bucket Formula field
- Formula: Groups projects by Project State into buckets to determine which projects are live vs closed:
- Live or Closed = Project Stage: Closing (has gone live)/Completed/Expired
- In Flight = Project Stage: Initiating/Planning/Executing
- Canceled/Terminated = Project Stage: Contract Cancelation/Terminated by Customer
- Other = Project Stage: other than the above
- Use: Breaks out TTV for graphs for In Flight vs Closed projects
- TaskRay Project:Project Name
- Source: TaskRay Project field: Project Name
- Use: Reference field to help look up project data to fix or ensure accuracy in reporting
- TaskRay Project:Owner Name
- Source: TaskRay Project field: Owner Name
- Use: Reference field to report data errors
- Expiration Date
- Source: TaskRay Project field: Expiration Date
- Use: Reference field to review project data accuracy for Expired projects
- Start Date
- Source: TaskRay Project field: Start Date
- Use: Reference field to assist with audit of report data errors
The following filters are used on the report and should not require updating:
- All TaskRay projects
- Actual Completion Date = All Time
- Template = False
- Start Date = greater or equal Jan 1, 2023
- Project Type <> Internal, Rework
- Project Stage <> Contract Cancelation/Terminated by customer
- These projects will have long stall timeframes and will never complete. Therefore should not be included in TTV averages
Process Flow
The following steps are required to review and create the TTV data:
- Open the Salesforce report: TTV From Project Create Date
- Run the report and export the details only to Excel
- Rename the tab Month/Year Data
- Save the report to the Monthly Data folder under the appropriate folder
- See the example in the 2025/January 31 2025 folder
- Add a column at the end for Data Error
- This field will track the errors in the data for future analysis
- Add Two columns at the start of the report for TTV values:
- Column A header = Project TTV
- Enter formula for all rows in column A: =IF(AND(G2="",I2=""),H2-F2, G2-F2)-D2
- Column B header = Opp TTV
- Enter formula for all rows in column A:=IF(AND(G2="",I2=""),H2-E2, G2-E2)-D2
- Drag the formulas to all rows
- Filter Column A
- Negative number - the Go live date field has a bad date that requires correction in both the report AND the database:
- Go Live date cannot be earlier than project start date - set to project start date
- Go live date is in wrong year due to typo - fix year
- Highlight the row yellow, the Go Live date orange and add Bad Go Live Date in Data Error column
- Large number (Example: 4xxxx or 2xxxx)
- A closed project is missing the Go Live date - copy the Actual Completion date to the Go Live Date
- Highlight the row yellow, the Go Live date orange and add Bad Go Live Date in Data Error column
- An open project is stalled with No Go live or Actual Completion date. The Estimated Go Live = 12/31/2099
- These records will be filtered out via the Pivot Tables and require no action
- A closed project is missing the Go Live date - copy the Actual Completion date to the Go Live Date
- Negative number - the Go live date field has a bad date that requires correction in both the report AND the database:
- Column A header = Project TTV
- Sort the data by Created date Oldest
- Remove Incorrect Data Record Rows
- Filter by Created Date = the new month
- Example Report run Jan 31: locate records where project was created on Feb 1 of same year or later
- Delete these records, they will be counted in Feb numbers
- Filter by Project State = Other
- If Status Reason = Contract Cancelation or Terminated by Customer, these projects are pending closure and the records should be deleted
- If the project has not been assigned to a PM yet, confirm with the project creator that the project should be deleted:
- If the project is linked to an opportunity , open the opportunity and confirm with Sales Ops the project can be deleted and unlinked to the opportunity. If so:
- Delete the project from the opportunity
- Delete the template name from the Implementation Project Template field
- This will place the opportunity back on the list of closed opportunities awaiting payment/approval to start
- If the project is linked to an opportunity , open the opportunity and confirm with Sales Ops the project can be deleted and unlinked to the opportunity. If so:
- Filter by Created Date = the new month
- Audit the report data for errors. NOTE: For any record that is incorrect, highlight the row yellow and data field that is incorrect in Orange. Include the data error type in the Data Error Colum
- Review all rows where the Actual Completion Date, Estimated Go Live, AND Go Live dates are all blank. These records will skew the TTV results and the Estimated Go Live date will need to be updated before continuing
- Use the Expiration Date on the project as the Estimated Go Live date if one cannot be determined by the project task dates or other information on the project
- For Completed projects with Estimated Go Live of 12/31/2099 - remove the date
- Highlight the row yellow, the Estimated Go Live field orange and populated it with the Expiration Date
- Data Error Field Entry = Missing Estimated Go Live Date
- Filter by Project State = Live or Closed and Estimated Go Live date = 12/31/2099
- The Estimated Go Live date was not updated at time of project close to remove the 2099 data, which skews the TTV data
- Highlight the row yellow, the Estimated Go Live field orange and remove the Expiration Date on the report and database project
- Data Error Field Entry = Bad Estimated Go Live Date
- Filter by Project Stage = Expired
- Review project expired in most recent month. Confirm project hours actually expired vs delivered. If delivered, change project closure type on the project to Complete
- Highlight the row yellow, the Project Stage field orange, and populated it with Complete
- Data Error Field Entry = Wrong Project Closure Type
- Review Project Types
- Update the Project Type field to the correct type:
- Ab to Managely projects should be classified as Migration, not New Implementation
- Managely changes from one level to another are Add On Upgrades
- SIMS to Manitou are Migrations
- Highlight the row yellow, the Project Type field orange, and populated the report field with the correct type
- Data Error Field Entry = Wrong Project Type
- Update the Project Type field to the correct type:
- Review all rows where the Actual Completion Date, Estimated Go Live, AND Go Live dates are all blank. These records will skew the TTV results and the Estimated Go Live date will need to be updated before continuing
Create Summary Pivot Tables
The following pivot tables are created on monthly report to summarize the data:
- Create a pivot table for TTV by Product/Project Type from the data with the following criteria:
- Rows
- Project State
- Project Type
- Product
- Values
- Count of TaskRay Project Name
- Average of Project TTV
- Average of Opp TTV
- Filter records to exclude Estimated Go Live Date in 2099
- Change the format of the amounts in the pivot to Number with no decimals
- Collapse Pipeline Category and Project Type Fields
- Rows
- Create a second Pivot for just in flight projects based on:
- Rows
- Project Type
- Product
- TaskRay Project: Project Name
- Values
- Count of TaskRay Project Name
- Average of Project TTV
- Average of Opp TTV
- Filters
- Project State = In Flight
- Filter records to exclude Estimated Go Live Date in 2099
- Change the format of the amounts in the pivot to Number with no decimals
- Collapse Pipeline Category and Project Type Fields
- Rows
- Create a third pivot to summarize Data Errors:
- Rows
- Data Error
- TaskRay Project: Project Name
- Columns
- TaskRay Project: Owner
- Values
- Count of TaskRay Project: Project Name
- Filters
- Data Error <> Blank
- Rows
- Add a 4th pivot to summarize the average On-Hold time for projects on hold by product
- Rows
- Product
- Project Type
- TaskRay Project: Project Name
- Values
- Count of TaskRay Project: Project Name
- Average of Total On-Hand Duration Days
- Filters
- Total On Hand Duration <> 0
- Project Stage <> Complete, Completed, Expired, Contract Cancellation, Termianted by Customer
- Rows
- Rename the tab created for the pivots to Month Year Summary
- Example Jan 2025 Summary
Update the Master TTV Report
The master report is located in the TTV folder and labeled with the current year. Follow the steps below to update the master report:
- Open the TTV report for the current year
- Currently: TTV Report 2025.xls
- Populate the appropriate sections in the Data Summary tab with the values from:
- Average TTV and Average TTV by Product values source = Monthly TTV report pivot tables
- Days On Hold =
- Project Counts - use the information from the reports linked below to populate:
- Start - drag formula from pervious month's field (Uses ending count from previous month)
- New = Project Counts Created report
- Completed, Expired, Contract Cancelation, and Terminated by Customer columns - Project Counts - Complete Date
- Pending Contract Cancel/Terminate by customer = TTV Report 2025.xls filtered by Project state = Other and Status Reason = Contract Cancelation or Terminated by customer
- The next month starting count should now match the values in Project Count - Open
- Update the Graphs on the Graphs tab to include the new month
- Use a rolling 13 months
- Copy both tabs from the Monthly TTV report to the master TTV Report placing them to the right of the Data Summary tab
- Notify the Director of Professional Services the report is complete and available for their review
TTV Review
The Director of Professional Services will review the monthly report to monitor progress towards reducing the TTV and determine if any areas require focus efforts to reduce project TTV.
Return to Contents