Skip to content
Org-Wide Theme

Data-Driven Decision Culture Program, from the Dashboard to the Decision Meeting

An annual theme with four integrated pillars (data literacy, analytics instruments, data governance, decision rituals), a structured budget envelope, and a phased rollout from pilot to org-wide. Built for the CHRO, CDO/CIO, and CFO setting this year as the year critical meetings stop guessing.

  • 4.9/5 · 287 reviews
  • 300+ clients nationwide
  • 2,000+ trainers
  • 1 to hundreds of participants
  • Standard · Premium · Private 1-on-1
Program scale
Org-wide (CHRO + CDO/CIO sponsorship)Program scale
Typical duration
12 months (renewable)Typical duration
Program pillars
4: Literacy · Instruments · Governance · Decision RitualsProgram pillars
Budget level
Standard or PremiumBudget level

2,000+ trainers and experts

Our group's teaching network, matched to what your team needs.

See class documentation

You see your trainer first

The trainer's profile, track record and field come with the proposal, before you decide.

4.9 out of 5

287 participant reviews.

300+ clients nationwide and 180,000+ private training sessions completed. Among them: MPR RI, Akademi Militer Magelang, DPRD Provinsi Jawa Timur.

One person to hundreds

Private coaching for one participant, a class for one team, or several cohorts at once.

Three budget levels

  • Standard: core class, material fitted to the participants’ work
  • Premium: senior trainer, deeper material design
  • Private 1-on-1: one participant, one trainer, schedule set by the participant
Tell us your budget
Short answer

Neksus's data-driven decision culture program is an annual four-pillar theme: data literacy for every employee, analytics instruments (Power BI/Tableau) for BI teams and analysts, data governance aligned with DMBOK 2.0, and daily decision rituals that treat data as a mandatory input. Rollout phases from a 30-day pilot to a 90-day wave to org-wide over 12 months. One CHRO + CDO governance umbrella covers the program. The calculation starts from the number of BUs, the number of analysts trained on Power BI or Tableau, and the scope of data governance, then is checked against the budget the company proposes.

Annual Theme

Why a data-driven decision culture must be designed as a year-long theme

Many enterprises already own BI tools (Tableau, Power BI, Looker) and pay data scientists, yet critical meetings still get decided by senior opinion. McKinsey's The State of AI 2024 shows organizations at high analytics maturity (level 4–5 on the five-level scale) generate 1.5–2x EBITDA versus laggards, and the primary driver is decision culture, with dashboard count playing a much smaller role. Tom Davenport in Competing on Analytics maps five levels of organizational analytics maturity (analytically impaired, localized analytics, analytical aspirations, analytical companies, analytical competitors). DJ Patil in Building Data Science Teams emphasizes that data culture is built through daily rituals, with annual training playing only a supporting role. Gartner's Decision Intelligence framework adds that decision quality equals data quality × context quality × process quality. DMBOK 2.0 (DAMA International) supplies the discipline backbone: data quality, data architecture, master data management, and data security. The DataOps Manifesto keeps pipelines alive with CI/CD-grade cadence akin to software. This program weaves all four foundations together.

  • Analytics-mature organizations generate 1.5–2x EBITDA (McKinsey State of AI 2024)
  • Root cause: many dashboards, meeting rituals still driven by senior opinion
  • Four integrated pillars under one executive sponsor close the structural gap
  • Anchored on DMBOK 2.0, Davenport Analytics Maturity, Gartner Decision Intelligence, DataOps Manifesto — proven public frameworks
Dashboards without decision rituals = data theater

Organizations that buy BI tools without changing how meetings run end with hundreds of dashboards viewed once every 1–2 weeks and then ignored. Tens of billions of rupiah invested in tooling decay because there is no social contract: 'no numbers, no decision.' Pillar 4 (decision rituals) is the differentiator analytics vendors often skip.

Three mandatory sponsors for this theme

A data culture program needs three aligned sponsors: the CHRO (literacy and behavior change), the CDO/CIO (instruments and technical governance), and the CFO or COO (financial and operating decision rituals with data). Without the CFO/COO, decision rituals stall at middle management and never reach the board room.

Data literacy and analytics capability are different investments

Data literacy for every employee (reading charts and interpreting numbers) takes 6–10 hours per person per year. Deep analytics capability (SQL, modeling, dashboarding) takes 60–120 hours per person per year for 8–15% selected employees. Budget must reflect both as separate lines.

Program Architecture

Four-pillar integrated architecture

Each pillar carries its own audience, modules, and metrics. The program governance aligns all four under a single annual roadmap.

Pillar 1
Pillar 1 — Data Literacy for All Employees

Give every employee the foundations of reading data: chart literacy, basic statistics, internal data sources, healthy interpretation. 6–10 hours per person per year (async + division sessions).

  • 100% of employees can read line/bar/scatter charts and spot misleading visuals
  • Awareness of the corporate metric definitions (single source of truth)
  • A common vocabulary for cross-functional data discussion
Pillar 2
Pillar 2 — Analytics Capability (Power BI / Tableau / SQL)

Build real analysts and power users — SQL, dashboard authoring, data exploration, statistical thinking. 60–120 hours per person per year for 8–15% of selected employees across BUs.

  • BU analysts can build dashboards end-to-end (data extract → publish)
  • Teams manage a consistent semantic layer / data model
  • Internal career track Data Analyst Level 1–3 agreed with HR
Pillar 3
Pillar 3 — Data Governance (DMBOK 2.0 + DataOps)

Stand up the corporate data dictionary, data quality framework, master data management, data classification, and DataOps Manifesto-style CI/CD pipelines. Data contracts as the single source of truth backbone.

  • Live corporate data dictionary for 50–150 key metrics
  • Published and monitored data quality SLAs
  • Quarterly Data Council with documented decisions
Pillar 4
Pillar 4 — Data-Driven Decision Rituals

Change how meetings run. Data-first QBR templates, a decision log, pre-mortems with explicit data assumptions, structured monthly business reviews. Without this pillar, the other three remain theater.

  • QBR + MBR across all BUs use the data-first template
  • Live corporate decision log for decisions ≥ Rp 500M
  • Quarterly decision retros (what was guessed right / wrong)
Annual Budget Envelope

Annual budget envelope by organization size

The level in the rows below follows organization size and the number of BUs. The design is recalculated from analyst numbers and the proposed budget. BI tool licences (Power BI Pro/Premium, Tableau, Looker) sit outside this program.

ScopeParticipantsBudget LevelNotes
Mid-size enterprise (200–500 employees, one dominant BU)100% literacy + 25 analysts + 8 championsStandardSuitable as a first-year pilot before scaling to org-wide.
Large enterprise (500–2000 employees, 2–4 BUs)100% literacy + 70 analysts + 20 champions + cross-BU Data CouncilStandard or Premium, 2 to 4 BUsStandard 12-month rollout with three waves across BUs.
Enterprise (2000+ employees, 5+ BUs, multi-site)100% literacy + 180+ analysts + 45+ champions + cross-BU Data CouncilPremium, many BUs and sitesMulti-year contract with optimization based on first-year outcomes.
SOE with a national data / Satu Data mandateEnterprise-tier scheme + Satu Data Indonesia alignmentPremium, aligned with Satu DataProcurement via SPSE LKPP. Envelope follows PMK 39/2024 and SBM K/L. Aligned with Perpres 39/2019 Satu Data Indonesia.
Multinational subsidiaryEnterprise-tier scheme + bilingual (ID/EN) + global data policy alignmentStandard or PremiumFinal contract approved by regional HQ. Bilingual reporting.
Rollout Phases

Rollout phases — 30-day pilot → 90-day wave → 12-month org-wide

Phased rollout lowers risk, calibrates messaging, and accumulates success stories that fuel the next wave.

1
Pilot — 30 days
Month 1

Validate modules, decision-ritual templates, and data dictionary with one pilot BU (20–50 employees).

  • Data dictionary v0.1 for 15–25 pilot BU metrics
  • 6-hour data literacy delivered to the full pilot BU
  • Analyst Level 1 cohort kicked off (5–8 people)
  • First pilot QBR run on the new template
2
Wave 1 — 90 days
Months 2–4

Scale to three priority BUs (200–400 employees total) using calibrated modules.

  • Data dictionary v1.0 ratified by Data Council
  • Org-wide literacy completed across the three BUs
  • Cross-functional Data Council convened, first meeting held
  • Per-BU data champions selected and trained
3
Wave 2–3 — 180 days
Months 5–10

Roll out to the rest of the organization with continuous retrospectives.

  • 100% of employees complete data literacy
  • Live corporate decision log for decisions ≥ Rp 500M
  • Analyst Level 2 cohort complete (live capstone dashboards)
  • Quarterly calibration with governing body + decision retros
4
Sustaining — next 60 days + renewal
Months 11–12 + renewal

Formalize the data culture operating model as a permanent part of the organization.

  • Quarterly Data Council established as a standing forum
  • Capstone presentation to the board: decisions with documented impact
  • Year-two theme design (next analytics maturity level)
  • Internal Data Analyst Level 1–3 certification named and slotted into career tracks
Success Measures Across the Organization

Organization-level success metrics — beyond training satisfaction

Pick 4–6 metrics from this list before the program starts so impact is measured against agreed thresholds.

% of data-literate employees
≥ 95% within 12 months
LMS completion + assessment pass rate
Corporate metrics in the data dictionary
50–150 within the first year (all Data Council approved)
Data dictionary register
% of strategic decision meetings using the data-first template
≥ 80% of QBR + MBR adopt the template
Quarterly spot-check by Program Office (one working day per quarter)
Certified Level 2 internal analysts
5–8% of target staff within 12 months
Internal certification + live capstone dashboard
Corporate decision log — documented decisions
≥ 80% of decisions ≥ Rp 500M recorded with explicit data assumptions
Quarterly decision-log audit by Data Council
Business output from data-driven decisions
At least 5 decisions with documented ≥ Rp 100M/year impact
Post-decision review 6–12 months after the decision
Active Data Champions per BU
1 champion per 30–50 employees, 12-month retention ≥ 80%
Champions network dashboard
Decision Aid

Integrated annual theme vs Ad-hoc BI training vs BI licenses alone

Three approaches enterprises commonly take — with very different outcome profiles.

CriterionAd-hoc BI trainingIntegrated annual theme
★
BI licenses alone
How the budget is builtCost per standalone classStandard or Premium per BULicence per user per year
Meeting ritual changeNoneYes — QBR/MBR templates, decision logNone — dashboards without social contract
Single source of truth for metricsNo — definitions differ per BUYes — live corporate data dictionaryNo — semantic layer interpreted ad-hoc per team
ROI justification to the boardDifficultStrong — decision log + post-decision reviewDifficult — license cost without decision quality
Dashboard sprawl risk (hundreds of unused dashboards)HighLow — governance + clear ownershipVery high
Engagement Path

Neksus engagement flow for an annual theme

  1. 1

    Kickoff & analytics maturity diagnostic (4 weeks)

    Weeks 1–4

    Two-day workshop with CHRO/CDO/CFO/BU Head, 15 key stakeholder interviews, and an analytics maturity assessment (Davenport 5-level) across BUs. Output: program charter, per-BU maturity map, and rollout design.

  2. 2

    30-day BU pilot

    Month 2

    Four-pillar rollout to one pilot BU (20–50 employees). Data dictionary v0.1, new QBR template, Analyst Level 1 cohort stress-tested with weekly retros. The Neksus team and pilot-BU champions work side by side.

  3. 3

    Pilot retro & calibration (2 weeks)

    Early Month 3

    Retrospective workshop with the pilot team and stakeholders. Data dictionary revised to v1.0. Modules adjusted to feedback. Wave 1 plan agreed.

  4. 4

    Wave 1 — three priority BUs (90 days)

    Months 3–5

    Org-wide literacy across the three BUs, Analyst Level 1+2 cohorts, Data Council convened, per-BU data champions trained. Weekly calibration with the Neksus and client steering committee.

  5. 5

    Wave 2–3 — remaining BUs + sustaining (180 days)

    Months 6–11

    Rollout to the rest of the organization. Analyst cohorts 2 and 3. Corporate decision log starts filling. Quarterly governing body calibration + decision retros.

  6. 6

    Capstone & year-two design

    Month 12

    Capstone presentation to the board: live data dictionary, documented decision log, analyst capstone dashboards. Year-two design workshop (leveling up maturity) with CHRO + CDO + CFO.

Program Governance

Program governance — who, what role, what cadence

Clear governance prevents the program from losing momentum. Three core layers with distinct cadences.

Steering Committee (CHRO + CDO/CIO + CFO + 1 BU Head)
Quarterly

Executive sponsorship. Ratify the corporate data dictionary, allocate budget, prioritize the next wave, and resolve cross-BU metric conflicts. Accountable to the board.

Data Council (Data Owner per BU + Data Steward + Legal/Compliance)
Monthly

Review new metric definitions, data quality SLAs, data classification, and corporate-level dashboard approvals. Develop the governance playbook.

Program Office (L&D Lead + PMO + Champions Lead)
Weekly

Operational execution. Scheduling, LMS, communications, champions coordination, and reporting up to the steering committee.

Data Champions Network (1 per 30–50 employees)
Weekly check-ins, monthly all-champions

Adoption influencers within each BU. Mentor peers on decision-ritual templates, escalate blockers to the Program Office, and run quarterly retros.

Neksus Engagement Team (Account Director + Lead Facilitator + Curriculum Architect)
Weekly steering call + onsite per wave

Co-design the program, facilitate core sessions, calibrate modules, and escalate methodology issues (analytics maturity, decision intelligence, DMBOK).

Target Participants

Who joins from your organization — an integrated multi-cohort design

The program is a portfolio of parallel cohorts with different curricula.

All-employee data literacy
100% of employees

Every employee (6–10 hours async + 2 hours in person).

Internal Analyst Level 1–3
8–15% of target staff

BU analysts, BI developers, finance analysts, ops analysts. 60–120 hours of structured learning plus a capstone dashboard.

Data Champions per BU
1 per 30–50 employees

Mid-level employees with peer influence and operational credibility on their team.

Data Council members
8–15 people

Per-BU data owner, data steward, legal/compliance, IT/data engineering lead.

Steering committee
4–5 people

CHRO, CDO/CIO, CFO, and one BU Head with the highest-priority data agenda.

Board briefing
Full board

Quarterly 90-minute session covering program summary + sample decision log entries.

How We Reduce Program Risk

Common failure modes — and effective mitigations

Different metric definitions across BUs (multi-source-of-truth)

BU A reports revenue Rp 12B; BU B reports Rp 11.4B for the same period. The board loses trust in the numbers.

How we reduce it: Pillar 3 corporate data dictionary with explicit ownership + Data Council as the conflict-resolution forum + quarterly audits.

Dashboard sprawl — hundreds of unused dashboards

Tableau/Power BI workspaces hold 300+ dashboards with 70% untouched in the last 30 days.

How we reduce it: Dashboard governance with classification (corporate / BU / personal) + 90-day sunset policy + mandatory ownership + usage KPI tracked by Data Council.

Executive sponsors out of alignment

CHRO pushes forward, CDO holds back; or CFO pulls budget six months in.

How we reduce it: Program charter with three mandatory sponsors + a one-day initial retreat to agree shared outcomes + quarterly reporting to the full board.

Training without ritual change

Employees complete modules yet meetings still get decided by senior opinion; knowledge evaporates in 90 days.

How we reduce it: Pillar 4 is mandatory — new QBR/MBR templates + decision log + ritual audits by Program Office. Without Pillar 4, the charter is rejected.

Poor data quality drives decisions in the wrong direction

Decision log records data-driven decisions; six months later it surfaces that data was biased or pipelines were broken.

How we reduce it: Per-pipeline data quality SLA (timeliness, completeness, accuracy, consistency) + automated monitoring + quarterly post-decision review to clear problematic data.

Champions burn out within 6 months

Champions who started energized stop showing up because their regular workload stayed full.

How we reduce it: Formal allocation of 10–15% work time to the champion role as a job duty + recognition + an internal Data Analyst Level 1–3 career track.

Procurement Info

Procurement information

  • Contract format
    Structured annual theme (renewable). Multi-year engagement with an SOW agreed per year.
  • Location
    Onsite at the client office, regional onsite, or hybrid (onsite kickoff + bi-weekly online sessions).
  • Delivery language
    Bahasa Indonesia (default) or bilingual ID/EN for multinational enterprises and SOEs with global reporting.
  • Materials & participant certificates
    Structured modules, bilingual workbook, data dictionary + QBR/MBR + decision log templates, 12-month alumni resource hub access, internal Data Analyst Level 1–3 certification.
  • Tax & e-procurement documentation
    PPN tax invoice, official receipt, BAST. SOE/government e-procurement (SPSE LKPP) supported. SBM K/L envelope for ministries and agencies.
  • Payment terms
    A deposit on contract, a milestone payment per wave (3x), the balance after year-one capstone. The size of each payment is agreed in the contract under the client's procurement rules.
  • Optional add-ons
    Personal coaching for CHRO/CDO (separate package), quarterly executive briefing for the board (90 minutes), and annual dashboard sprawl audit (manday basis).

Frequently Asked Questions

Ritual change happens in stages. Wave 1 (months 3–5) introduces the new QBR/MBR template for the three priority BUs. By months 9–12 the ritual becomes the default for 80% of strategic meetings. Full stabilization usually settles in year two after two full QBR cycles run on the new template.

No. We work with existing data conditions (legacy DW, structured spreadsheets, or modern lakehouse). Pillar 3 (governance) maps the data condition and identifies 3–5 cleanup priorities for year one. Many enterprises start from a messy data state — that is the norm and a key reason this theme exists.

IT vendors focus on technology (installation, semantic layer, infrastructure). Neksus focuses on culture — four pillars including the decision ritual that makes tools used with discipline. Many clients run both as complements: an IT vendor for tooling, Neksus for the capability and culture that determine whether tools produce impact.

Yes. We have supplied through SPSE LKPP with full documentation (RKS, HPS, BAST). Envelope follows PMK 39/2024 / SBM K/L. For SOEs under the Satu Data Indonesia mandate (Perpres 39/2019), contracts are typically multi-year through RKAP with commissioner approval.

Many mid-size enterprises have no CDO; this theme often becomes the catalyst for forming a CDO role or Head of Data Office in year one or two. If you already have a CDO, that role becomes the lead sponsor for Pillars 2 and 3. If not, the sponsor function is temporarily held by the CIO + Head of BI, with a transition plan discussed by the Steering Committee.

The 30-day pilot is an independent contractual commitment. If your organization decides to stop, data dictionary v0.1, ritual templates, and pilot materials remain your property. We do not offer retroactive discounts; the pilot experience becomes a foundation for any future vendor.

Every theme is led by an Account Director plus a Lead Facilitator with 10+ years in enterprise data analytics and production data engineering, plus a Curriculum Architect for module design. Team bios are sent before contract signing.

Mutual NDA signed before the diagnostic. Decision log entries and client capstone dashboards are used as marketing case studies only with explicit written consent. Neksus team access to client data is limited to anonymized samples or read-only on a need-to-know basis with full audit logs.

Quarterly steering committee at 90 minutes (4x/year) + a one-day initial retreat + quarterly board briefing at 90 minutes. Roughly 20 hours per year per sponsor. A realistic time commitment for C-suite executives; without it, an annual theme typically loses momentum at months 6–9.

Discuss your organization's data-driven decision culture design

Share your organization size, priority BUs, and the decision-ritual challenge you face. The Neksus team studies your context and returns an annual theme design.

  • Four integrated pillars (literacy · instruments · governance · decision rituals) under one executive sponsor
  • 30-day pilot → 90-day wave → 12-month org-wide
  • Data dictionary + decision log + QBR/MBR templates aligned with DMBOK 2.0 and Davenport Analytics Maturity
  • Data champions network in every BU with recognition and a Data Analyst Level 1–3 career track
  • Steering committee + Data Council + Program Office with clearly defined cadence

Six fields to get started. Our corporate team reads and answers it.

Additional details (optional)

Add these if you already know them. Every field in this section can be left empty, and our team will cover them during the needs-analysis call.