What Don Woodlock's Leadership Means for Data Management: An Excel Perspective

When a senior leader like Don Woodlock takes the helm at a data-centric company such as InterSystems, the ripples are both strategic and operational. This deep-dive explains what that leadership change means for data management, supply chain data, and Excel governance — and shows practical Excel-first tactics UK businesses can adopt now to stay aligned with evolving enterprise priorities. For context on how acquisitions and leadership shape organisational insights, see our analysis of how Brex's acquisition influenced data security.

1. Why a leadership change at InterSystems matters for enterprise data strategy

Signal to the market and customers

A new leader is a signal. Boards appoint executives to shift priorities — often accelerating product integrations, opening new partner networks, or changing go-to-market approaches. InterSystems' renewed focus may mean increased investment in interoperability, real-time streaming, or cloud connectors. That affects how downstream teams collect and transform data. For parallels in infrastructure investment and scale, review lessons on building scalable AI infrastructure.

Resource allocation and roadmap changes

Expect a reallocation of engineering and product resources towards strategic bets. If leadership prioritises real-time clinical or supply-chain throughput, APIs and connectors get more attention — affecting how Excel-based reports ingest canonical datasets. Organisations that still rely on manual exports will need to prioritise automation or risk latency and integrity gaps.

Partnerships, integrations and vendor strategy

New leadership often reshapes partner strategies. Stronger partnerships with cloud providers, EHR platforms, or analytics firms create new integration points. Teams should map those changes to their Excel toolchain: which connectors will become available, what security approvals are needed, and which sheets will be replaced by live feeds.

2. Immediate implications for data management & governance

Policy and governance shifts that matter to spreadsheet owners

At an enterprise level, governance shifts can cascade to departmental workbooks. Expect updated access controls, stricter audit requirements, and formalised data dictionaries. Spreadsheet owners should prepare for enforced policies such as centralised data catalogues, single sources of truth, or mandatory retention rules.

Renewed emphasis on data integrity

When senior leaders champion data-driven decisions, the tolerance for poor data quality drops. That means more pre-publication checks, stronger validation rules in Excel, and expanded test coverage for macros and transformation steps. For best practice on protecting data in transit and at rest, review how secure sharing models have evolved in data ecosystems like modern data-sharing platforms.

Security, compliance and legal scrutiny

Leadership changes often bring legal and compliance reviews — especially in health and regulated industries. Expect external audits, data lineage demands, and stricter user provisioning. Cross-functional teams must show who accessed data, when, and what transformations were applied; spreadsheets become part of compliance evidence unless replaced by governed reporting tools.

3. Supply chain data under new strategic priorities

Visibility and analytics improvements

InterSystems’ leadership could prioritise real-time supply-chain visibility, increasing demand for analytics that combine telemetry, orders and inventory. For teams using Excel as a tactical analytics layer, this means building robust ETL patterns (Power Query or linked tables) and designing dashboards that surface delays and exceptions quickly. Our guide to harnessing data analytics for supply chain decisions shows practical KPI sets that translate well into Excel dashboards.

Real-time vs periodic reporting

Leadership often forces the question: should we move from daily exports to streaming and direct queries? Where live connections aren't possible, create near-real-time data ingestion using automated refreshes via Power Query or scheduled macro-driven imports. Consider also the trade-offs of freshness vs governance: more frequent updates require stronger validation and anomaly detection.

Vendor and partner integration

Expect increased integration with vendors for shared telemetry, invoicing, and logistics status. Teams must standardise fields, map identifiers, and agree on SLA-driven data formats. Excel templates can act as the transitional contract for data exchange until APIs or middleware fully replace them.

4. Excel's practical role in a post-leadership-shift world

Excel as the tactical, trusted layer

Even with enterprise platforms, Excel remains critical for ad-hoc analysis, what-if modelling, and stakeholder-ready reports. It’s a flexible surface for prototyping KPIs before investing in dashboards. The trick is to keep Excel files governed and auditable so they can serve both exploratory and operational needs.

Standardised templates as the bridge

Create company-wide templates for P&L, inventory, vendor performance and SLA tracking. Standard templates reduce ambiguity, accelerate auditing, and speed training. Consider implementing a template registry and include metadata headers to show data source, last refresh and author.

Migration path vs permanent solution

Not every Excel workbook should become a permanent fixture. Define clear migration criteria: when a report needs concurrent users, real-time data, or strict SLAs, schedule it for redevelopment on a governed platform. Use Excel templates that are structured to ease porting to BI tools or InterSystems connectors when available.

5. Excel governance: practical policies aligned to senior leadership goals

Version control and storage

Enforce SharePoint/OneDrive storage with controlled permissions and version history. Use naming conventions that include service, environment (prod/test), and date. For critical reports, require a release note and changelog tab within the workbook so reviewers see what changed between versions.

Validation, data integrity and lineage

Embed validation rules: dropdown lists, cross-sheet reconciliation checks, and checksum rows that surface mismatches. Keep a mapped lineage tab documenting the source table, transformation logic (Power Query steps), and who validated each transformation — this supports audit requests driven by leadership and legal teams.

Auditability and approval workflows

Integrate lightweight approvals: a sign-off tab with digital signatures or a simple approval column that includes approver, timestamp and comment. For higher assurance, link approvals to Microsoft Flow/Power Automate so approvals are preserved in enterprise logs accessible to compliance teams.

6. Automation: Power Query, VBA and low-code connectors

Power Query as the default ETL in Excel

Power Query offers repeatable, auditable transformations that are preferable to opaque macro code. Keep applied steps readable and document key transformations in a query documentation tab. When InterSystems or partners expose connectors, Power Query often supports OData/REST sources, making integration manageable.

Govern VBA and macros

Where Excel macros remain necessary, govern them. Use code repositories, code reviews and signed macros. Store macro-enabled templates in a controlled library and apply digital certificates. Unchecked VBA is a common vector for errors and compliance breaches.

Low-code connectors and API integration

Leadership prioritising platform openness will produce more APIs. Use Power Automate, Power Query native connectors, or lightweight middleware to surface those APIs into Excel. For secure transaction flows, consider patterns from B2B payments evolution to reduce manual reconciliation burden; see our discussion on B2B payment innovations.

7. Dashboards and KPIs that senior leadership will care about

Choosing the right KPIs

Senior leaders prefer a mix of outcome KPIs (revenue, fill rate, system uptime) and leading indicators (inventory days, latency, exception counts). Map KPIs to strategy pillars and avoid vanity metrics. If new leadership emphasises interoperability, add metrics like API success rate and data delivery latency.

Designing executive-ready Excel dashboards

Executive dashboards should be uncluttered, with clear visuals, annotated variance explanations and an assumptions tab. Use sparklines, conditional formats and small multiples to compress information into one screen. Ensure the dashboard links to validated source tabs and include refresh instructions for non-technical execs.

Storytelling and narrative controls

Attach a commentary tab that explains variances, root causes and recommended actions. Leadership expects not just numbers but insight. Train report owners to present three action items per dashboard refresh: what changed, why it matters, and what to do next.

8. Case study: Converting InterSystems supply chain signals into Excel-driven decisions

Problem statement

A UK regional distribution team relied on daily CSV exports from a legacy system. Data was inconsistent and late, causing stock-outs and urgent airfreight. New leadership at InterSystems announced an initiative to accelerate data sharing with partners — a perfect time to upgrade analytics workflows.

Step-by-step Excel template and automation

We designed a three-tier solution: (1) A Power Query master workbook that automatically refreshes source files and performs cleanses; (2) A governed template with validation rules, named ranges and a lineage tab; (3) A KPI dashboard with automated variance commentary. For inspiration on improving operational visibility and yard management, see technologies for real-time yard visibility.

Outcome and lessons

Within eight weeks the team reduced manual reconciling time by 60%, improved fill rate by 4 percentage points, and established a migration plan to a governed reporting service. The core lesson: using disciplined Excel patterns accelerates impact while new integrations mature.

Pro Tip: Treat your Excel template as a software artifact. Use version tags, release notes, and a small test suite of validation checks. That makes it auditable and easier to migrate when enterprise connectors arrive.

9. Roadmap: how UK organisations should adapt

Pilot, then scale

Start with a pilot for critical reporting (e.g., supply chain SLA dashboard). Solidify templates, governance and training during the pilot. Use measurable KPIs to decide when a report should migrate from Excel to an enterprise platform.

Training and upskilling

Invest in short, role-based Excel courses covering Power Query, structured tables, and governance workflows. Upskilling reduces dependency on individuals and increases report maintainability. Consider pairing training with templates and cheat sheets.

Long-term architecture and integration

Plan for an architecture that uses Excel at the tactical edge, a mid-tier for governed datasets (a data lakehouse or an InterSystems-backed store), and enterprise BI for consolidated KPIs. Monitor new leadership signals for investments in APIs or real-time layers and build migration triggers into your roadmap.

10. Comparing governance approaches: Excel vs specialised platforms vs hybrid

Choose a governance model that fits your risk appetite and timeline. The table below compares practical attributes and when to choose each approach.

11. Strategic signals to watch from Don Woodlock's leadership

Open integration partnerships

If the leadership emphasises open APIs and partners, your Excel roadmap should prioritise API-based ingestion, standardised schemas, and automated refresh. Track announcements, technical preview programs, and partner roadmaps closely.

Investment in analytics and AI

Leadership interest in analytics or agentic AI implies an emphasis on scale and model governance. Prepare Excel workbooks to surface model outputs while keeping model lineage, inputs and versioning documented; investigate enterprise AI infrastructure trends similar to those described in agentic AI planning and scalable AI infrastructure.

Commercial shifts and pricing impacts

If product pricing or commercial models shift, Excel-based scenario models become invaluable. Build scenario tabs with sensitised drivers and centralised assumptions to quickly stress-test business models. For background on preparing for price volatility, see our consumer guide on navigating price changes which shares general approaches for sensitivity analysis.

Related Reading

• Using Modern Tech to Enhance Your Camping Experience - A creative look at practical tech adoption that parallels rapid prototyping in analytics.
• Lessons from Ancient Art - Timeless design lessons for structuring complex spreadsheets and interfaces.
• Networking in a Shifting Landscape - How personal networks and partnerships matter during leadership transitions.
• Personalized Keto - An example of tailoring solutions to users, useful when designing stakeholder-specific dashboards.
• The Future of Content Acquisition - Strategic thinking about investments and acquisitions that influence data priorities.

Leadership changes at an enterprise like InterSystems present risk and opportunity. For UK teams relying on Excel, the practical path is clear: tighten governance, adopt repeatable automation (Power Query first), prepare migration triggers, and keep templates auditable. That way, your organisation remains nimble now and ready for the platform-driven future the new leadership will define.