Data is a Team Sport with Paul Grobler

Key Takeaways

• Rugby Forward Pack as a Framework: Position Business Architecture as the cornerstone of enterprise strategy, akin to a rugby front row, ensuring contests are strong and ROI is demonstrable. Application Architecture, represented by Locks, serves as the operational powerhouse, while Data Architecture, the Eighth Man, strategically controls and disseminates information. Technology Architecture, the Flankers, provides agility and foundational infrastructure support.
• Prioritise Business Strategy: Avoid the common “application-first” approach that emphasises rapid automation over thoughtful, long-term data and enterprise architectures. A clearly defined business strategy should guide technical implementation for sustainable success.
• Emphasise Pragmatic Solutions: In complex transformations, such as the demerger and EHR replacement at Medi Clinic, the most effective architecture is one that aligns with the organization’s cultural readiness, budget constraints, and operational appetite, rather than theoretical ideals.
• Clarity in Communication: Adopt standardised terminology to eliminate confusion. Replace vague terms like “data platform” with precise definitions that enhance understanding and facilitate effective communication among all stakeholders.
• Effective Visual Modelling: Use consistent visual modelling techniques, like ArchiMate’s “Roman camp” layout, to maintain clarity across diagrams. This approach positions stakeholders and key components in recognisable locations, adhering to the (7 \pm 2) principle to ensure engagement and comprehension.
• AI as a Supportive Tool: Use AI to enhance qualitative discoveries, such as analysing interview transcripts, but maintain human oversight to identify potential gaps. Clearly define AI roles, whether it’s as a coach, teammate, extra capacity, or managing routine tasks, ensuring it complements human efforts rather than replacing them.
• Agile Architectural Delivery: Shift away from lengthy, monolithic architectural models by adopting an Agile approach. Focus on delivering value through short, two-week cycles that address immediate business challenges across all layers (business, application, data, and technology), ensuring rapid results and adaptability.

Webinar Details

Title: Data is a Team Sport with Paul Grobler
Date: 2026-10-21
Presenter: Paul Grobler
Meetup Group: DAMA SA Big Data
Write-up Author: Howard Diesel

How Can Enterprise Architecture Be a Team Sport?

Enterprise architecture functions best when viewed as an interconnected team sport rather than an isolated technical discipline.

Paul Grobler of Data Gambit establishes that data architecture cannot succeed in a silo. By drawing on enterprise architecture consulting engagements, specifically large-scale healthcare initiatives with Medi Clinic, the session makes the case for aligning strategic business design with foundational systems.

Using the cultural touchstone of South African rugby, technical architecture concepts are translated into relatable, collaborative roles.

Key Takeaways

• Collaborative Context: Data architecture is inextricably linked to surrounding enterprise architecture layers.
• Real-World Grounding: Architectural principles must directly address complex client challenges, such as healthcare system transitions.
• Shared Metaphors: Sports analogies offer non-technical stakeholders an accessible framework for evaluating technical capabilities.

Frequently Asked Questions

• What is the primary theme of the presentation? It explores enterprise architecture and how data architecture interacts with business, application, and technology layers using a rugby forward pack analogy.

Figure 1 Data Architecture’s Teammates

Figure 2 About the Speaker

Figure 3 Introducing the Team

How Does Rugby Illustrate Enterprise Architecture Layers?

A rugby forward pack illustrates the structural interdependencies across the four classic layers of enterprise architecture.

The front row (props and hooker) represents business architecture. If the front row is weak or absent, the scrum becomes non-contestable, destroying competitive advantage and preventing strategic alignment. The locks directly behind them represent application architecture, providing the core driving power that anchors operations and delivers data.

The eighth man represents data architecture, positioned at the base to control the ball cleanly and feed it to the backline runners. Flankers symbolise technology infrastructure, remaining mobile and responsive to exploit tactical opportunities.

Key Takeaways

• Front-Row Business Alignment: A missing or weak business architecture creates “non-contestable scrums” where strategic ROI cannot be achieved.
• Applications Produce Data: The eighth man (data) cannot distribute the ball if the locks (applications) fail to channel it cleanly.
• Infrastructure Agility: Technology architecture functions as the flankers, providing speed and operational flexibility.

Frequently Asked Questions

• What happens if an organisation lacks business architecture? Much like playing without certified props forces a non-contestable scrum, lacking business architecture diminishes organisational strength, leaving teams unable to prove ROI or align technical projects with strategic value.

Figure 4 The Front Row – Business Architecture

How Is Application Architecture Prioritised in Enterprises Today?

Enterprises frequently prioritise application features over data architecture because operational processes demand immediate automation.

While frameworks like TOGAF group application and data domains within the same phase, operational leaders historically focus on processes, ERPs, and CRMs first. This application-centric mindset often neglects broader analytical reporting and decision-making requirements. Business architecture defines the overarching strategy, value streams, and capabilities.

Application architecture maps the software portfolio carrying those capabilities. Data architecture governs information models, subject area maps, quality, and semantic definitions. Technology architecture manages the underlying cloud or on-premise infrastructure.

Key Takeaways

• Automation Bias: Organisations typically adopt software to automate manual processes quickly rather than designing data models upfront.
• Data Architecture Scope: Encompasses conceptual and physical modelling, information glossaries, data flows, and governance constraints.
• Closing the Divide: Information architecture links business goals directly to technical schemas.

Frequently Asked Questions

• Why do C-level leaders often overlook a data-first approach? Traditional CIOs and IT leadership often originate from application development or infrastructure backgrounds, instinctively focusing on software features and immediate process automation over long-term data design.

Figure 5 The Locks – Application Architecture

Figure 6 The Eighth Man – Data Architecture

Figure 7 The Flanker – Technology Architecture

What Challenges Do Multinational Demergers Face?

Demerging multinational enterprises face extreme architectural friction when disentangling legacy systems, multi-country operations, and conflicting stakeholder agendas.

Healthcare provider Medi Clinic initiated an international demerger across its divisions in South Africa, Switzerland (operating as Hirslanden), and the Middle East. Decades of shared platforms, including master data management (MDM) solutions, required systematic untangling. Simultaneously, the organisation undertook replacements of core patient administration, revenue management, and electronic health record (EHR) systems.

The enterprise architecture team was tasked with clarifying 13 high-level, ambiguous problem statements by engaging nine business divisions, competing internal factions, and over 40 stakeholders.

Key Takeaways

• Demerger Challenges: Unwinding shared enterprise systems requires unravelling historical dependencies across global divisions.
• Stakeholder Factions: Large-scale transformations must work through divergent opinions where individual factions strongly advocate for or oppose specific platforms.
• Legacy System Modernisation: Concurrent replacement of EHR and administrative engines raises implementation risks.

Frequently Asked Questions

• What made the Medi Clinic architectural environment uniquely challenging? The organisation was managing an international demerger while concurrently replacing its core patient administration, revenue management, and electronic health record platforms on aging infrastructure.

Figure 8 Bridging Strategy to Execution

Figure 9 Mediclinic – a Worked Example

Figure 10 Mediclinic Demerge – Core System Replacements

How Do We Align Architecture with Organisational Priorities?

Effective architectural consulting requires reconciling formal statements of work with operational realities and real organisational appetite.

Consultants were commissioned to document the baseline “as-is” landscape, establish a target “to-be” architecture, and map tactical transitional options across a five-year horizon. Engaging executives revealed distinct operational priorities: hospital leadership sought real-time operational visibility into bed occupancy, theatre schedules, and patient flow.

When evaluating three tactical architectural transitions, client appetite took precedence over textbook purity. Delivering actionable recommendations meant selecting the path the organisation possessed the energy, resources, and cultural willingness to execute.

Key Takeaways

• Operational Grounding: Executive needs often centre on practical operational metrics, such as bed allocation and surgical turnaround.
• Pragmatic Recommendations: The optimal architectural path is the one the organisation actually has the operational appetite to implement.
• Five-Year Horizon: Transition architectures must account for multi-year rollout schedules across distributed facilities.

Frequently Asked Questions

• Why did the consultants recommend the client’s preferred transition option over their own theoretical ideal? Even if an option appears superior on paper, successful execution hinges on the client’s internal appetite, available energy, and cultural commitment to change.

Figure 11 The Brief, and the Work

How Do AI Notebooks Enhance Architectural Discovery?

Specialised AI notebooks accelerate architectural discovery by transforming sprawling stakeholder interview transcripts into searchable, traceable corpora.

Managing 40+ extensive stakeholder interviews and complex vendor documentation (such as InterSystems IRIS) created an overwhelming volume of qualitative data. The consulting team deployed AI notebooks to rapidly query transcript evidence and trace specific architectural claims directly back to original interview recordings.

This speed proved invaluable during client playback sessions when defending architectural findings. Human oversight was still needed to correct phonetic transcription errors, such as audio software rendering the Swiss hospital group “Hirslanden” as “his London”.

Key Takeaways

• Traceable Evidence: AI notebooks enable consultants to link findings directly back to specific stakeholder statements in seconds.
• Rapid Vendor Onboarding: Ingesting technical manuals allows teams to quickly uncover system capabilities missed by internal teams.
• Human Verification: Domain experts must review AI outputs to spot transcription slips and contextual misunderstandings.

Frequently Asked Questions

• How did AI notebooks assist during client feedback sessions? They allowed consultants to locate verbatim quotes, identify who made specific statements, and pinpoint exact timestamps across dozens of meeting transcripts instantaneously.

Figure 12 How We Worked – Working a Dog Out of a Bush

How Can We Standardise Business Terminology Effectively?

Clear enterprise architecture requires standardising overloaded business terminology and visualising systemic complexity through structured modelling languages.

Channelling grandmotherly wisdom to “say what you mean and mean what you say,” the team banned ambiguous phrases like “data platform,” which caused friction due to conflicting stakeholder interpretations. To eliminate ambiguity, the team used ArchiMate to model 13 core business problem statements.

Adopting a standardised “Roman camp” layout ensured every diagram presented stakeholders, root causes, affected capabilities, and symptoms in identical positions. Healthcare operations were structured across four core value streams (patient logistics, clinical care pathways, revenue management, and continuum of care) while adhering to the \(7 \pm 2\) modelling rule to avoid cognitive overload.

Key Takeaways

• Banish Ambiguous Terms: Overloaded words like “platform” or “data backbone” create confusion and should be replaced with precise definitions.
• The “Roman Camp” Pattern: Structuring architecture diagrams with consistent visual templates allows non-technical readers to follow complex models easily.
• \(7 \pm 2\) Rule of Modelling: Limiting visual compartments to between 5 and 9 containers prevents stakeholder disengagement.

Frequently Asked Questions

• What are the four primary operational value chains in a healthcare system? Patient logistics, clinical care and medical pathways, revenue management, and continuum of care.

Figure 13 The Other Consultant – Grandma Kate

Figure 14 “Say What You Mean, and Mean What You Say”

Figure 15 A Formal Modelling Language is Not a Nice-to-have

Figure 16 ArchiMate – Our Language of Choice

Figure 17 Unpacking the Problem Statements

Figure 18 Turning Technical Drawings into a Decision

Figure 19 Business Architecture

Figure 20 As-is Application Architecture

Figure 21 To-be Application Architecture

Figure 22 Simplify for Clarity (Still Detailed!)

Figure 23 Quote by Steve Hoberman

Figure 24 Simplify More

How Should AI Roles be Assigned in Business?

Artificial intelligence functions as an exceptional assistant but must never be allowed to dictate enterprise strategy without rigorous governance.

Applying the Afrikaans adage “don’t be led by the reins,” practitioners must consciously assign AI specific roles: coach, teammate, bomb squad (specialist reserve energy), or waterboy (routine task automation). AI lacks contextual awareness, ignores room dynamics, and exhibits subtle blind spots that can distort sensitive business processes.

In parallel, enterprise systems are experiencing a pendulum swing away from brittle low-code/no-code platforms back toward disciplined, purpose-built bespoke software. Across every shift, balance across all four architectural layers remains non-negotiable.

Key Takeaways

• Assigned AI Roles: Treat AI as a coach, teammate, on-demand bomb squad, or slide waterboy, never as the manager.
• Subtle Blind Spots: AI models cannot grasp political dynamics, room tone, or hyper-specific domain nuances.
• Return to Purpose-Built Code: Enterprises are moving away from restrictive low-code apps in favour of customized, well-governed software.

Frequently Asked Questions

• What is the “bomb squad” role of AI in enterprise consulting? Inspired by South African rugby reserves, the bomb squad represents deploying AI as a fresh burst of analytical power to unblock stalled workflows and process demanding tasks rapidly.

Figure 25 “Don’t Let Someone Hold You a Hand-horse”

Figure 26 Your AI Needs You!

Figure 27 “Quiet Waters, Deep Soil – the Devil is Lurking Underneath It All”

Figure 28 Where Does This Leave Us?

Figure 29 Closing Slides

How Can We Overcome Monolithic Delivery Hurdles Effectively?

Enterprise architecture must be delivered through thin, vertical slices across all four architectural layers to deliver rapid business value.

In the concluding panel, participants discussed overcoming monolithic delivery hurdles. Rather than attempting enterprise-wide semantic models or multi-year broad architectures upfront, teams should execute iterative two-week “slivers” spanning business, application, data, and technology tiers.

The discussion also explored modern healthcare data sharing, including the governance of longitudinal patient records and the legal complexities (GDPR/POPIA) of sharing clinical trial data with academic research universities. The ultimate trap for architects remains falling in love with models rather than solving business problems.

Key Takeaways

• Vertical Architecture Slicers: Address focused business questions by modelling thin, end-to-end slices across all four layers iteratively.
• Longitudinal Record Governance: Sharing patient data across disparate healthcare networks requires strong consent models and integration standards.
• Outcome Over Output: Architectural models must serve as dynamic communication tools that enable decisions rather than remaining static documentation.

Frequently Asked Questions

• Can enterprise architecture be delivered in an agile or iterative fashion? Yes; by avoiding exhaustive upfront documentation and instead delivering focused, two-week vertical slices that link an immediate business KPI through application, data, and technology requirements.