VALUEWORKSInsights to Results
Sign in
Help center

Products, organisation, systems

Set up the three structures a driver tree can be read against.

A tree of formulas means nothing until you can say whose product, whose team and whose system each number belongs to.

Product Hierarchy groups products under parents, nested to any depth — a top-level product such as ValueWorks Analytics Platform holding categories like Data Integration and Analytics & Reporting, each of those holding named products such as ETL Engine or Dashboard Builder. Every row shows its sub-product count. + Add Product adds one; Generate via AI drafts the whole structure.

Organisation is a fuller hierarchy: departments hold a role title (e.g. Vice President), a headcount count, and a sub-team count where they have children. A row labelled Unassigned Departments holds anything not yet placed under a parent — a working area for a structure that isn't finished, not an error state. Two separate buttons build it: Add Entity and Add Department. An entity is a legal or organisational unit in its own right; a department sits inside one. Confusing the two is the easiest mistake to make here, and it's worth getting right before headcount and cost planning start referencing the structure.

Systems is a table of the software the company runs on: System Type, Vendor and Data Ingestion are plain free-text fields — each shows placeholder text ("e.g. CRM, ERP…", "e.g. HubSpot…", "e.g. Live API…") rather than a fixed list, so "Live API" and "Manual Entry" are a convention people type consistently, not an enforced choice. Deployment is the one genuine picklist here: Cloud, On-Premise or Hybrid. Prefill Standard Systems populates common rows to start from; + Add System adds one by hand.

Product Hierarchy for ValueWorks Analytics Platform, expanded to show categories like Data Integration and Analytics and Reporting, each holding named products such as ETL Engine and Dashboard Builder, with a sub-product count per row.
  1. 1Top-level product, with its total sub-product count
  2. 2A category nested beneath it, with its own sub-product count
  3. 3Named products at the bottom of the branch

ValueWorks 2026.08

Organisation showing an Unassigned Departments section, Executive Leadership with a Chief Executive Officer role and headcount of 1, and Product and Engineering expanded to Product Management, Software Development and Data Infrastructure and DevOps, each with a role title and headcount.
  1. 1Add Entity and Add Department, as two separate buttons
  2. 2Unassigned Departments — a holding area, not an error
  3. 3Role title and headcount per department
  4. 4Sub-team count on a department with children

ValueWorks 2026.08

Systems listing CRM, ERP, Accounting, HRIS, BI, Project Management and Marketing Automation with their vendors Salesforce, SAP, DATEV, Workday, Power BI, Jira and HubSpot, and an unset Data Ingestion column showing placeholder text.
  1. 1System Type and Vendor, filled in
  2. 2Deployment — the only picklist here: Cloud, On-Premise, Hybrid
  3. 3Data Ingestion, still showing its placeholder — nothing has been set yet
  4. 4Prefill Standard Systems and + Add System

ValueWorks 2026.08

Takeaways

  • Product Hierarchy nests to any depth, with a sub-product count at every level.

  • Organisation distinguishes Add Entity (a standalone unit) from Add Department (sits inside one) — Unassigned Departments is a normal holding area, not an error.

  • Systems records System Type, Vendor and Data Ingestion as free text; only Deployment (Cloud/On-Premise/Hybrid) is an enforced picklist.

Surfaces covered

  • Product Hierarchy
  • Organisation (Add Entity vs Add Department)
  • Systems (type, vendor, deployment, ingestion, Prefill Standard Systems)

Also taught in the Academy

Module 7 · Digital Twin: the Driver Tree

Take it as lesson 7.2 in Business Analyst & FP&A