<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article xml:lang="EN" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Sports Act. Living</journal-id>
<journal-title>Frontiers in Sports and Active Living</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Sports Act. Living</abbrev-journal-title>
<issn pub-type="epub">2624-9367</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.3389/fspor.2022.850885</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Sports and Active Living</subject>
<subj-group>
<subject>Original Research</subject>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>Digitally Optimizing the Information Flows Necessary to Manage Professional Athletes: A Case Study in Rugby Union</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<name><surname>Ranaweera</surname> <given-names>Jayamini</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<xref ref-type="corresp" rid="c001"><sup>&#x0002A;</sup></xref>
<uri xlink:href="http://loop.frontiersin.org/people/1627795/overview"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Weaving</surname> <given-names>Dan</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff3"><sup>3</sup></xref>
<uri xlink:href="http://loop.frontiersin.org/people/436418/overview"/>
</contrib>
<contrib contrib-type="author">
<name><surname>Zanin</surname> <given-names>Marco</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Pickard</surname> <given-names>Matthew C.</given-names></name>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
</contrib>
<contrib contrib-type="author">
<name><surname>Roe</surname> <given-names>Gregory</given-names></name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<uri xlink:href="http://loop.frontiersin.org/people/1129808/overview"/>
</contrib>
</contrib-group>
<aff id="aff1"><sup>1</sup><institution>Carnegie Applied Rugby Research (CARR) Centre, Carnegie School of Sport, Leeds Beckett University</institution>, <addr-line>Leeds</addr-line>, <country>United Kingdom</country></aff>
<aff id="aff2"><sup>2</sup><institution>Bath Rugby Football Club</institution>, <addr-line>Bath</addr-line>, <country>United Kingdom</country></aff>
<aff id="aff3"><sup>3</sup><institution>Leeds Rhinos Rugby League Club</institution>, <addr-line>Leeds</addr-line>, <country>United Kingdom</country></aff>
<author-notes>
<fn fn-type="edited-by"><p>Edited by: Valentina Agostini, Politecnico di Torino, Italy</p></fn>
<fn fn-type="edited-by"><p>Reviewed by: Laurie Lovett Novak, Vanderbilt University Medical Center, United States; Lorenzo Rossi, University of Camerino, Italy; Jon Bartlett, Victoria University, Australia</p></fn>
<corresp id="c001">&#x0002A;Correspondence: Jayamini Ranaweera <email>j.ranaweera&#x00040;leedsbeckett.ac.uk</email></corresp>
<fn fn-type="other" id="fn001"><p>This article was submitted to Sports Science, Technology and Engineering, a section of the journal Frontiers in Sports and Active Living</p></fn></author-notes>
<pub-date pub-type="epub">
<day>09</day>
<month>06</month>
<year>2022</year>
</pub-date>
<pub-date pub-type="collection">
<year>2022</year>
</pub-date>
<volume>4</volume>
<elocation-id>850885</elocation-id>
<history>
<date date-type="received">
<day>08</day>
<month>01</month>
<year>2022</year>
</date>
<date date-type="accepted">
<day>06</day>
<month>05</month>
<year>2022</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#x000A9; 2022 Ranaweera, Weaving, Zanin, Pickard and Roe.</copyright-statement>
<copyright-year>2022</copyright-year>
<copyright-holder>Ranaweera, Weaving, Zanin, Pickard and Roe</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</p></license>
</permissions>
<abstract>
<p>Practical case studies elaborating end-to-end attempts to improve the quality of information flows associated with athlete management processes are scarce in the current sport literature. Therefore, guided by a Business Process Management (BPM) approach, the current study presents the outcomes from a case study to optimize the quality of strength and conditioning (S&#x00026;C) information flow in the performance department of a professional rugby union club. Initially, the S&#x00026;C information flow was redesigned using integral technology, activity elimination and activity automation redesign heuristics. Utilizing the Lean Startup framework, the redesigned information flow was digitally transformed by designing data collection, management and visualization systems. Statistical tests used to assess the usability of the data collection systems against industry benchmarks using the System Usability Scale (SUS) administered to 55 players highlighted that its usability (mean SUS score of 87.6 &#x000B1; 10.76) was well above average industry benchmarks of similar systems (Grade A from SUS scale). In the data visualization system, 14 minor usability problems were identified from 9 cognitive walkthroughs conducted with the High-Performance Unit (HPU) staff. Pre-post optimization information quality was subjectively assessed by administering a standardized questionnaire to the HPU members. The results indicated positive improvements in all of the information quality dimensions (with major improvements to the accessibility) relating to the S&#x00026;C information flow. Additionally, the methods utilized in the study would be especially beneficial for sporting environments requiring cost effective and easily adoptable information flow digitization initiatives which need to be implemented by its internal staff members.</p></abstract>
<kwd-group>
<kwd>sports informatics</kwd>
<kwd>digitization in sport</kwd>
<kwd>system usability assessment</kwd>
<kwd>sport process optimization</kwd>
<kwd>Business Process Management</kwd>
</kwd-group>
<counts>
<fig-count count="9"/>
<table-count count="6"/>
<equation-count count="0"/>
<ref-count count="46"/>
<page-count count="17"/>
<word-count count="10441"/>
</counts>
</article-meta>
</front>
<body>
<sec sec-type="intro" id="s1">
<title>Introduction</title>
<p>Sport practitioners in the modern era rely heavily on evidence generated from data and information sources to manage professional athletes (West et al., <xref ref-type="bibr" rid="B43">2019</xref>). Based on initial information and knowledge management frameworks such as the <italic>wisdom hierarchy</italic> (Rowley, <xref ref-type="bibr" rid="B36">2007</xref>), researchers like Dammann (<xref ref-type="bibr" rid="B9">2018</xref>) have illustrated the process of generating knowledge from data as a four-layer hierarchical model (<xref ref-type="fig" rid="F1">Figure 1</xref>). Experts have defined data, information and knowledge through different viewpoints (Zins, <xref ref-type="bibr" rid="B46">2007</xref>) and it is therefore challenging to provide a single valid definition for data. However, it is assumed that data on its own has no meaning which has led to defining information as <italic>data with meaning</italic> (Hey, <xref ref-type="bibr" rid="B15">2004</xref>). Researchers have further illustrated that information is a flow that leads to the creation of knowledge as a stock (Scharmer, <xref ref-type="bibr" rid="B39">1996</xref>). Therefore, an information flow might initiate from data and extend until knowledge creation. This demonstrates that data and information act as the principal foundation for generating evidence and knowledge. Hence, in sporting environments, where information plays a significant role in generating the evidence and knowledge necessary to manage athletes (refer to <xref ref-type="fig" rid="F1">Figure 1</xref> for an example from rugby union), it is vital that sport practitioners have access to high quality data and information sources to support decision making. Additionally, a suboptimal information flow at a micro-level can lead practitioners to generate incorrect or incomplete decisions pertaining to player management (e.g., practitioners making incorrect judgments on player training load due to inaccessible information). This in turn, could deviate the player management outcomes from the overall organizational goals (e.g., enhanced injury risks to the athlete or suboptimal training adaptations).</p>
<fig id="F1" position="float">
<label>Figure 1</label>
<caption><p>Data-Information-Evidence-Knowledge (DIEK) hierarchy introduced by Dammann (<xref ref-type="bibr" rid="B9">2018</xref>) in the Online Journal of Public Health Informatics (OJPHI) with a professional rugby union illustration.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fspor-04-850885-g0001.tif"/>
</fig>
<p>Therefore, minimizing noise and enhancing the quality of information flows linking to player management processes through optimization would enable the creation of rigorous decision support systems in professional sporting environments (Schelling and Robertson, <xref ref-type="bibr" rid="B40">2020</xref>) and enhance the overall effectiveness of decision making associated with player management. Extending this line of thinking further, there has been a growing interest to embed modern strategies such as digital transformation into sporting environments (Str&#x000F6;bel et al., <xref ref-type="bibr" rid="B41">2021</xref>). While information system architectures for sports specific environments have been discussed on the macro-level (Blobel and Lames, <xref ref-type="bibr" rid="B5">2020</xref>), limited practical case studies exist to highlight how such digitization attempts can be implemented by sport practitioners in professional sporting environments at the micro-level (Mullane et al., <xref ref-type="bibr" rid="B25">2011</xref>). Furthermore, in current contexts, implementing data visualization systems to illustrate sport specific information appears to be the favorable method to optimize the information flows in sporting environments (Perin et al., <xref ref-type="bibr" rid="B29">2018</xref>; Du and Yuan, <xref ref-type="bibr" rid="B11">2021</xref>).</p>
<p>However, developing a data visualization system would only act as a part of a complete digital optimization project. For instance, for digitization projects, sport literature does not currently provide sufficient practical case studies to elaborate how requirements for such data visualization systems were generated in sporting environments, how the usability of those systems (e.g., data visualizations) were evaluated and how assessments were conducted to determine if such systems truly enhanced the performance of a given sporting environment (relating to a performance dimension of time, cost, quality or flexibility). Hence, based on digitization techniques, this article aimed to bridge this gap in sport literature by presenting the results from an attempt to improve the quality of an information flow associated with player management processes in a professional rugby union environment. Specifically, based on a practically implemented case study, the current article aimed at; (1) redesigning a player management information flow to overcome an existing issue in a professional sporting environment (2) implementing the redesigned information flow using digitization techniques (3) evaluating the usability of the implemented digital systems (4) assessing the change in information quality due to the optimization.</p>
</sec>
<sec sec-type="methods" id="s2">
<title>Methods</title>
<sec>
<title>Case Study</title>
<p>The present study concentrated on optimizing the information flow of player management processes at a rugby union club competing in the Gallagher Premiership in England. During the 2019/2020 season, an organizational objective was set at the club to enhance the use of information for decision making within the performance department, referred to as the High-Performance Unit (HPU). At the time frame of the study, the HPU consisted of physiotherapists (5), strength and conditioning (S&#x00026;C) coaches (3), sports scientist (1), doctor (1), medical administrator (1) and a data scientist (1). Additionally, Head of Medical, Head of Strength and Conditioning and Head of Applied Sciences and Research were providing leadership to the HPU and will be referred to as the <italic>HPU management team</italic> throughout the article. Furthermore, the study was approved by the ethics committee of the affiliated university.</p>
<p>As the first step of this project, specific issues existing in the HPU player management information flow were identified. Among them, the inaccessibility of strength and conditioning data (includes resistance training data for each training day and progressive baseline testing data) of the players was one of the key issues in the current state information flow. For illustration, using an activity diagram in Unified Modeling Language (UML), <xref ref-type="fig" rid="F2">Figure 2</xref> demonstrates how resistance training data was collected prior to the optimization. The model shows that only one data point for a 6-week period was available online to be accessed by the HPU staff. But if access to daily player resistance training data was required for decision making, then the practitioners could only obtain that data by observing the whiteboard inside the gym. Therefore, the rest of the article will present the outcomes from the attempts that were undertaken to optimize the strength and conditioning information flow (resistance training and baseline testing) of the players within the HPU (results will be mainly provided for improvements relating to the resistance training information flow and where appropriate, progressive baseline testing information flow optimization outcomes will also be presented). During the change management initiative, special attention was given to improve the accessibility of the S&#x00026;C information flow to HPU staff during decision making.</p>
<fig id="F2" position="float">
<label>Figure 2</label>
<caption><p>Activity diagram of resistance training data collection prior to the optimisation (will be referred to as As-Is state).</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fspor-04-850885-g0002.tif"/>
</fig>
</sec>
<sec>
<title>Business Process Management (BPM) Approach</title>
<p>We have adopted Business Process Management (BPM) as the change management framework to optimize the considered information flow in the HPU. The applicability of BPM to sporting contexts has been discussed previously (Ranaweera et al., <xref ref-type="bibr" rid="B31">2021</xref>) and as specified below, we have adopted the six phase BPM lifecycle presented by Dumas et al. (<xref ref-type="bibr" rid="B12">2013</xref>). Within the latter lifecycle, the first three phases (process identification, discovery and analysis) were previously implemented to determine the issues existing in the HPU player management information flow (Ranaweera et al., <xref ref-type="bibr" rid="B32">2022</xref>). Hence, in the current article, as presented in <xref ref-type="fig" rid="F3">Figure 3</xref>, the last three stages (process redesign, implementation, and monitoring) of the BPM lifecycle were used to improve the S&#x00026;C information flow in the HPU. However, the current study was initiated by assessing the quality of the considered information flow prior to optimization. This latter step is a constituent of the process analysis stage.</p>
<list list-type="bullet">
<list-item><p>Process identification&#x02014;Generates the organizational process architecture, performance measures, relationships and systematically identifies which of those processes require a BPM intervention to assist in meeting organizational goals.</p></list-item>
<list-item><p>Process discovery&#x02014;For the identified processes, information on the current state (As-Is) is collected and documented through process modeling techniques.</p></list-item>
<list-item><p>Process analysis&#x02014;Issues within the documented As-Is state of the processes are identified for optimization, potentially generating a list of prevailing issues.</p></list-item>
<list-item><p>Process redesign&#x02014;The process is redesigned (optimized) to overcome the issues identified in the process analysis stage to define the best future state (To-Be).</p></list-item>
<list-item><p>Process implementation&#x02014;Necessary changes to move the process from the As-Is to the To-Be state are performed by managing organizational change.</p></list-item>
<list-item><p>Process monitoring&#x02014;The implemented process is monitored to determine the effectiveness of the changes. The cycle is repeated to discovery stage if further issues are present or further continuous improvements are necessary.</p></list-item>
</list>
<fig id="F3" position="float">
<label>Figure 3</label>
<caption><p>The methods adopted to optimize the strength and conditioning information flow in the HPU.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fspor-04-850885-g0003.tif"/>
</fig>
</sec>
<sec>
<title>Process Analysis</title>
<sec>
<title>Pre-optimization Information Quality Assessment</title>
<p>Research has discussed data quality as an outcome from decision support systems proposed for high-performance sporting environments by considering the effects to different dimensions (e.g., reliability, accessibility, timeliness) of data quality (Schelling and Robertson, <xref ref-type="bibr" rid="B40">2020</xref>). Wider computing research illustrates different frameworks to assess data quality (Batini et al., <xref ref-type="bibr" rid="B3">2009</xref>; Cichy and Rass, <xref ref-type="bibr" rid="B8">2019</xref>) including combined subjective and objective methods (Pipino et al., <xref ref-type="bibr" rid="B30">2003</xref>). However, we opted to refer to the assessment of information quality rather than data quality as theoretically (from the DIEK hierarchy in <xref ref-type="fig" rid="F1">Figure 1</xref>) practitioners are more inclined to create evidence and knowledge from information sources rather than direct data sources (Dammann, <xref ref-type="bibr" rid="B9">2018</xref>).</p>
<p>Hence, we used the product and service performance model for information quality (<italic>PSP/IQ model)</italic> (Kahn et al., <xref ref-type="bibr" rid="B17">2002</xref>) to assess the quality of the S&#x00026;C information flow in the HPU. This focuses on assessing the information quality from 16 dimensions that are mapped to four quadrants: sound, useful, dependable and usable information. Within the PSP/IQ framework, the view of information as a product (data generation to storage, typically in a database) or service (transforming data to information) is closely related to the DIEK hierarchy and its illustration in sport. For example, the collection, storage and maintenance of daily S&#x00026;C data can be viewed from <italic>information as a product</italic> lens. The process of accessing the stored S&#x00026;C data and visualizing it as an information source to staff for player management can be analyzed from <italic>information as a service</italic> viewpoint. We utilized the standard <italic>IQA instrument</italic> (questionnaire with 11-point scale), introduced through the <italic>AIMQ</italic> information quality assessment method (Lee et al., <xref ref-type="bibr" rid="B20">2002</xref>) (built on the foundations of the PSP/IQ model) to subjectively determine the information quality of the information flow considered for optimization. Therefore, at the initiation of the study, the IQA questionnaire was administered to all the members of the HPU (refer to <xref ref-type="table" rid="T1">Table 1</xref> for the participant characteristics) who required access to daily S&#x00026;C data of the players in the first team and senior academy. The feedback to the questionnaires were used to determine the pre-optimization information quality level of the S&#x00026;C information flow.</p>
<table-wrap position="float" id="T1">
<label>Table 1</label>
<caption><p>Information quality assessment and cognitive walkthrough participant characteristics.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th valign="top" align="left"><bold>User</bold><break/> <bold>ID</bold></th>
<th valign="top" align="left"><bold>Age</bold></th>
<th valign="top" align="center"><bold>Years of experience in professional sport</bold></th>
<th valign="top" align="left"><bold>Pre-optimization</bold></th>
<th valign="top" align="left"><bold>Post-optimization</bold></th>
<th valign="top" align="left"><bold>Cognitive walkthrough</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">U<sub>1</sub></td>
<td valign="top" align="left">35</td>
<td valign="top" align="center">8</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
</tr>
<tr>
<td valign="top" align="left">U<sub>2</sub></td>
<td valign="top" align="left">39</td>
<td valign="top" align="center">14</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
</tr>
<tr>
<td valign="top" align="left">U<sub>3</sub></td>
<td valign="top" align="left">37</td>
<td valign="top" align="center">11</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
</tr>
<tr>
<td valign="top" align="left">U<sub>4</sub></td>
<td valign="top" align="left">27</td>
<td valign="top" align="center">5</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
</tr>
<tr>
<td valign="top" align="left">U<sub>5</sub></td>
<td valign="top" align="left">31</td>
<td valign="top" align="center">6</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
</tr>
<tr>
<td valign="top" align="left">U<sub>6</sub></td>
<td valign="top" align="left">46</td>
<td valign="top" align="center">12</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
</tr>
<tr>
<td valign="top" align="left">U<sub>7</sub></td>
<td valign="top" align="left">29</td>
<td valign="top" align="center">8</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
</tr>
<tr>
<td valign="top" align="left">U<sub>8</sub></td>
<td valign="top" align="left">31</td>
<td valign="top" align="center">4</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
</tr>
<tr>
<td valign="top" align="left">U<sub>9</sub></td>
<td valign="top" align="left">27</td>
<td valign="top" align="center">4</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">Y</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec>
<title>Process Redesign</title>
<p>For the current study, we used <italic>Heuristic Redesign</italic> (Reijers and Mansar, <xref ref-type="bibr" rid="B33">2005</xref>; Dumas et al., <xref ref-type="bibr" rid="B12">2013</xref>) to transform the S&#x00026;C information flow into an improved future state. Heuristic redesign was suitable for redesigning player management processes since it focuses on changing the current (As-Is) state incrementally (transactional) whilst operating within the context of the As-Is process (inward-looking) by using a defined set of redesign heuristics (analytical). Readers can refer to the redesign orbit presented by Dumas et al. (<xref ref-type="bibr" rid="B12">2013</xref>) to understand other process redesign techniques. Furthermore, most outward-looking redesign strategies (e.g., redesigning from best practices on similar processes by other alike sporting organizations) were not practical as sport organizations tend to operate within closed boundaries and do not often consider strategies such as open innovation. On a specific level, we selected relevant redesign heuristics from the 29 presented by Dumas et al. (<xref ref-type="bibr" rid="B12">2013</xref>) to transform the considered information flow to an optimized future state (To-Be). The resulting processes after redesign and the systems necessary to transform the processes were modeled using UML.</p>
</sec>
<sec>
<title>Process Implementation</title>
<p>Once the S&#x00026;C information flow was redesigned, it was implemented using digitization techniques. Within the literature, the common mode of process implementation in a BPM lifecycle is to automate tasks by using a Business Process Management System (BPMS) (De Ram&#x000F3;n Fern&#x000E1;ndez et al., <xref ref-type="bibr" rid="B10">2019</xref>). Whilst there might be possibilities to integrate a BPMS with an Athlete Management System (AMS) in sporting contexts, for the current study, instead of experimenting with a BPMS, we implemented the redesigned information flow by developing digital systems to collect, manage and visualize daily resistance training and progressive baseline testing data of the players. This was because firstly, the implemented system automation had to address unique user requirements aligning to the business goals of the considered organization. Secondly and most importantly, unlike certain other professional sports (e.g., football), sporting organizations like the one considered in the current study did not possess the financial strength that was needed to automate the redesigned process using an existing BPM technology like a BPMS.</p>
<p>Due to the dynamic nature of the HPU (e.g., constantly changing requirements), system developments needed to be flexible and agile in nature. Therefore, as highlighted by other sport researchers (Lacome, <xref ref-type="bibr" rid="B18">2020</xref>), a method like <italic>Lean Startup</italic> (Reis, <xref ref-type="bibr" rid="B34">2011</xref>), which focuses on a more adaptable process to changes, consisting of shorter design durations with early prototyping during the product development lifecycle, was more suitable for developing the proposed data collection, management and visualization systems. Specifically, guided by a design thinking approach for collecting the user requirements (Blessing and Chakrabarti, <xref ref-type="bibr" rid="B4">2009</xref>), as illustrated in <xref ref-type="fig" rid="F4">Figure 4</xref>, we utilized the iterative <italic>build-measure-learn</italic> cycle proposed in Lean Startup to digitize the S&#x00026;C information flow.</p>
<fig id="F4" position="float">
<label>Figure 4</label>
<caption><p>Build-Measure-Learn cycle in Lean Startup framework (Reis, <xref ref-type="bibr" rid="B34">2011</xref>).</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fspor-04-850885-g0004.tif"/>
</fig>
<sec>
<title>Plan</title>
<p>Although the build-measure-learn cycle appears to initiate with the build stage, it practically begins in the plan step, occurring in reverse to the development flow. Basically, a hypothesis about the system (e.g., if staff use the system for certain number of times, then it can be deemed appropriate to be implemented) is defined first through the plan step. Subsequently, the resulting build-measure-learn cycle is executed to understand if the hypothesis set in the plan step is proven, if not, the cycle is repeated. For the current study, as illustrated in <xref ref-type="fig" rid="F4">Figure 4</xref>, we used two build-measure-learn loops for the system development. An internal loop (executed entirely within the Build phase of the outer loop) was used to design a <italic>Minimum Viable Product</italic> (MVP) to meet the functionality requirement and the outer loop was used to validate its usability.</p>
<p>For the internal loop, we defined the exact user requirements (functional) from the proposed data collection, management and visualization systems in the plan stage. At the onset of the system development, we embedded three users into the design cycle to guide the design process. Specifically, two S&#x00026;C coaches (each from the first and academy teams) and one physiotherapist were selected for this purpose. Therefore, the initial functional requirements from the systems were collected from unstructured interviews with those three HPU members. The outer loop was targeted at assessing the system usability. For such usability assessments, the following criteria were defined in the plan stage.</p>
<list list-type="bullet">
<list-item><p>Data collection systems were acceptable if the usability of them were above the industry defined average system usability thresholds for such similar systems.</p></list-item>
<list-item><p>Data visualization systems were acceptable if no major usability problems were existing in them during operation.</p></list-item>
</list>
</sec>
<sec>
<title>Build</title>
<p>The principal outcome from the build phase was to create a Minimum Viable Product (MVP) (Lacome, <xref ref-type="bibr" rid="B18">2020</xref>), which was used to validate the usability criteria defined in the plan stage. An MVP is a version of the system providing just enough features to be usable by the customers for evaluating the prior set standard in the plan stage. Readers can refer to the original work by Reis (<xref ref-type="bibr" rid="B34">2011</xref>) to understand the different available options for developing MVPs. For the current study, we followed the internal build-measure-learn loop to design an MVP to meet the basic functional requirements set by the users. Specifically, for the S&#x00026;C information flow, we first developed web based interfaces coupled with Internet of Things (IoT) (Ikram et al., <xref ref-type="bibr" rid="B16">2015</xref>) based gateways to collect daily player data and then implemented a Database Management System (DBMS) (Vincent et al., <xref ref-type="bibr" rid="B42">2009</xref>) to manage it. We designed web-based interfaces to process and visualize the data as meaningful information to staff. Therefore, each build iteration in the internal loop produced a design version of the MVP. Next, we collected feedback (functionality) regarding each design version from the three users in the design loop (measure). Finally, the comments were validated against the functionality requirements (learn) to understand if another design iteration within the internal loop was necessary or if the development could progress to the next phase (measure) of the outer build-measure-learn loop. Once the system functionality requirements were met through the internal build-measure-learn loop, that final version of the system was defined as an MVP of the outer loop.</p>
</sec>
<sec>
<title>Measure</title>
<p>After building an adequately functioning MVP, measurements relating to the usability of the MVP were necessary to evaluate it against the criteria set in the plan stage (system usability requirements). Therefore, this step was associated with collecting data about the usability of the MVP. There were two distinctive MVP systems relating to the digitized resistance training information flow; (1) data collection systems (2) data visualization system. Therefore, aligning to the plan phase, as specified below, two different approaches were undertaken to collect data on the usability of the two systems.</p>
<list list-type="bullet">
<list-item><p><italic>Data collection system:</italic> In relation to the plan step, the goal was to assess the usability of the system in reference to industry benchmarks (summative). Hence, for this purpose, we chose the System Usability Scale (SUS) (Brooke, <xref ref-type="bibr" rid="B6">1995</xref>) from the different standard usability assessment questionnaires defined in literature (Sauro and Lewis, <xref ref-type="bibr" rid="B38">2016</xref>) to collect data on the usability of the system. Therefore, the goal was to collect the necessary SUS scores for the interface to be assessed against the industry benchmarks of similar interfaces defined in literature (Bangor et al., <xref ref-type="bibr" rid="B2">2008</xref>). To achieve this, first, a priori sample size calculation [&#x003B1; &#x0003D; 0.01, 80% power, <italic>SD</italic> &#x0003D; 8.54 from a similar study (Yuliawan et al., <xref ref-type="bibr" rid="B45">2020</xref>)] was conducted to determine the minimum number of individuals that were required to obtain a statistically significant assessment on the usability of the system to be at least 1 score above the SUS average industry benchmark score of 68 (Sauro and Lewis, <xref ref-type="bibr" rid="B38">2016</xref>). This resulted in a sample size of 852 (<xref ref-type="supplementary-material" rid="SM3">Supplementary Data Sheet 1</xref>), which is not practically viable in any sporting environment. In the considered rugby club, the squad at the time frame had only 65 players. Therefore, after the players had used the data collection interface to enter their daily resistance training data following a session, author JR administered the SUS questionnaire to 55 players (<italic>mean age</italic> &#x0003D; 24.11&#x000B1;4.26) in the squad (all the available players) and requested them to rate the usability of the system using the scale. The unavailable athletes for data collection (<italic>n</italic> &#x0003D; 10) were either injured or on loan at another club.</p></list-item>
<list-item><p><italic>Data visualization system:</italic> According to the criteria set in the Plan phase, the goal was to collect data to unravel potential usability issues in the system (formative). Hence, we conducted cognitive walkthroughs (Mahatody et al., <xref ref-type="bibr" rid="B22">2010</xref>) with think aloud techniques (users discussing their thoughts when interacting with a system during testing) (Nielsen, <xref ref-type="bibr" rid="B27">2012</xref>; Alomari et al., <xref ref-type="bibr" rid="B1">2020</xref>) with 9 HPU staff members (refer to <xref ref-type="table" rid="T1">Table 1</xref> for the participant characteristics) to identify usability problems in the data visualization interface. To achieve this, in the HPU, we set up a lab-based environment where a participant would attempt a set of tasks using the interface under the presence of a moderator (<xref ref-type="supplementary-material" rid="SM4">Supplementary Figure 1</xref>). Specifically, the five tasks (covering each core aspect of the interface) mentioned in <xref ref-type="table" rid="T2">Table 2</xref> were developed for the cognitive walkthrough sessions. Author JR conducted those sessions (each &#x0003C;30 min) by acting as the moderator. During the sessions, users were requested to attempt those tasks (order of tasks were randomized for each user) using the data visualization interface and they recorded the results from each task on an online task sheet. Additionally, after completing each task, users were requested to answer the Single Ease Question (SEQ) (Sauro and Lewis, <xref ref-type="bibr" rid="B38">2016</xref>; Laubheimer, <xref ref-type="bibr" rid="B19">2018</xref>) to help determine the difficulty of the task. And screen recording was used to collect audio (users think aloud data) and video (screen) data when the users attempted the tasks.</p></list-item>
</list>
<table-wrap position="float" id="T2">
<label>Table 2</label>
<caption><p>Description of tasks designed for the cognitive walkthrough sessions.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th valign="top" align="left"><bold>Task</bold></th>
<th valign="top" align="left"><bold>Task description</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">T<sub>1</sub></td>
<td valign="top" align="left">Record the All-Time best Squat one-repetition maximum (1RM) value of player A.</td>
</tr>
<tr>
<td valign="top" align="left">T<sub>2</sub></td>
<td valign="top" align="left">Record Current (42 day rolling) best Bench Press 1RM rating of player B.</td>
</tr>
<tr>
<td valign="top" align="left">T<sub>3</sub></td>
<td valign="top" align="left">State the recorded Dumbbell Press weight, reps and lift type by player C on 3/3/2021</td>
</tr>
<tr>
<td valign="top" align="left">T<sub>4</sub></td>
<td valign="top" align="left">Determine (Yes/No) if player D had done his Calf ISO&#x00027;s during week number 7 of year 2021.</td>
</tr>
<tr>
<td valign="top" align="left">T<sub>5</sub></td>
<td valign="top" align="left">For player D, during the period of 1/12/2020 to 31/03/2021, please determine the lowest SL CMJ Jump Height Left, Right values and record if it is Good/Poor.</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec>
<title>Learn</title>
<p>The final phase of the cycle was used to analyze the collected data from the measure step to determine if the MVP met the usability criteria set in the plan step. In line with the measure step, two distinctive approaches were considered for the two systems.</p>
<list list-type="bullet">
<list-item><p><italic>Data collection system:</italic> To validate the usability, first, a random sample of 50 SUS scores were selected from the data collected from all the active players. Next, as per the arguments justifying the use of parametric tests to group ordinal data like SUS scores (Harpe, <xref ref-type="bibr" rid="B14">2015</xref>; Sauro and Lewis, <xref ref-type="bibr" rid="B38">2016</xref>), a one-sample <italic>Z</italic>-test (by setting &#x003B1; = 0.01) was used to determine if the mean SUS scores of the sample (<overline>x</overline>) were statistically different (above) from the average industry SUS score of 68 (&#x003BC;) (Bangor et al., <xref ref-type="bibr" rid="B2">2008</xref>; Sauro and Lewis, <xref ref-type="bibr" rid="B38">2016</xref>). Additionally, the mean SUS score was also compared against a SUS grading scale defined in literature (Sauro and Lewis, <xref ref-type="bibr" rid="B38">2016</xref>) to determine an overall grading (comparative) for the usability of the data collection interface in relation to similar interfaces defined in literature. Finally, if the usability of the system was above industry average, it was decided to <italic>Persevere</italic> with the system by implementing any minor improvement. On the contrary, if the usability was below average, the cycle was repeated by using another internal build-measure-learn loop, a new MVP was created by <italic>Pivoting</italic> to the build step of the outer loop.</p></list-item>
<list-item><p><italic>Data visualization system:</italic> For identifying any usability issues in the system using the cognitive walkthroughs, first, the action sequences of each task (series of steps required to successfully execute the given task) were defined. Next, as specified below, author JR used the four-question approach by Wharton et al. (<xref ref-type="bibr" rid="B44">1994</xref>) to walk through the action sequences of each task performed by all the users (using the screen recordings). In this context, for each action in the task, a Yes/No was marked against the four questions and a rating of No for any question illustrated a usability problem in that action.
<list list-type="simple">
<list-item><p>&#x025CB; Will the user try to conduct the right action (Q1)?</p></list-item>
<list-item><p>&#x025CB; Will the user recognize that the correct action is available (Q2)?</p></list-item>
<list-item><p>&#x025CB; Will the user know that the correct action will achieve the expected outcome (Q3)?</p></list-item>
<list-item><p>&#x025CB; If the correct action is performed, will the user notice that progress is being made toward achieving the final outcome of the task (Q4)?</p></list-item></list>
</p></list-item>
</list>
<p>Finally, the validity and severity (minor vs. major) of the unraveled usability problems were evaluated with the authors DW and GR. In relation to the plan step, if no major usability problems were present, it was decided to <italic>Persevere</italic> with the existing design by conducting any minor amendments. Otherwise, a new MVP was developed by <italic>Pivoting</italic> to the build step and the build-measure-learn loop were repeated.</p>
</sec>
</sec>
<sec>
<title>Process Monitoring</title>
<sec>
<title>Post-optimization Information Quality Assessment</title>
<p>Once the S&#x00026;C information flow was digitally optimized, the same IQA instrument in the AIMQ information quality assessment method was administered to the HPU staff to determine the post-optimization information quality level. <xref ref-type="table" rid="T1">Table 1</xref> illustrates the characteristics of the HPU practitioners (pre-post) who responded to the questionnaire. The resultant pre-post optimization information quality change for all the dimensions and the corresponding impact to each quadrant of the PSP/IQ model were analyzed. However, due to the low sample sizes, statistical tests were not conducted to statistically determine the pre-post impact to the information quality of the considered information flows.</p>
</sec>
</sec>
</sec>
<sec sec-type="results" id="s3">
<title>Results</title>
<p>As specified previously, for illustration, the main results relating to the S&#x00026;C information flow optimization will be presented. Specifically, results will be mainly provided for improvements relating to the resistance training information flow and where appropriate, progressive baseline testing data optimizations outcomes will also be presented.</p>
<sec>
<title>Process Redesign</title>
<p>As specified below, three key redesign heuristics were used to transform the S&#x00026;C information flow to an optimized future state (To-Be).</p>
<list list-type="bullet">
<list-item><p>Integral technology (to introduce new technology for process execution): For the resistance training information flow, instead of recording data on a whiteboard, as presented by the <italic>use case diagram</italic> in <xref ref-type="fig" rid="F5">Figure 5A</xref>, a new digital interface was proposed to allow the players to enter their daily resistance training data after each session, and the collected data was planned to be stored and managed within a database. A similar interface was also proposed to enter the progressive baseline testing data of the players. However, data entry to the latter system was to be done by HPU staff and not the players. Next, a data visualization interface would access the daily S&#x00026;C data in the database and visualize the necessary information to the HPU staff.</p></list-item>
<list-item><p>Activity elimination (to remove unwanted activities from the process): All the activities performed by the S&#x00026;C coach in the previous resistance training data collection process (<xref ref-type="fig" rid="F2">Figure 2</xref>) would be eliminated to create an optimized future state (<xref ref-type="fig" rid="F5">Figure 5B</xref>).</p></list-item>
<list-item><p>Activity automation (considers automation of tasks in the considered process): The proposed data visualization interface automated tasks (e.g., estimated 1RM calculation, graphical representation of data) currently executed in the As-Is state when accessing S&#x00026;C information by HPU staff.</p></list-item>
</list>
<fig id="F5" position="float">
<label>Figure 5</label>
<caption><p>Redesigned resistance training information flow <bold>(A)</bold> use case diagram from UML depicting the proposed system <bold>(B)</bold> resistance training data collection future state (To-Be) process model. Notice how all the activities of the S&#x00026;C Coach have been eliminated (refer to <xref ref-type="fig" rid="F2">Figure 2</xref> for As-Is state).</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fspor-04-850885-g0005.tif"/>
</fig>
</sec>
<sec>
<title>Process Implementation</title>
<p>For illustration, the results from the attempts to implement the high-level system described in <xref ref-type="fig" rid="F5">Figure 5</xref> for optimizing the resistance training information flow will be presented. In such regard, as per the methods, the digital system was implemented using the two (internal and external) build-measure-learn loops.</p>
<sec>
<title>Plan</title>
<p>For the Plan step, <xref ref-type="table" rid="T3">Table 3</xref> presents the functionality requirements of the resistance training data collection system, discovered from the unstructured interviews with three users connected to the design cycle. Similar requirements were defined for the baseline testing data collection and the overall data visualization interface as well (<xref ref-type="supplementary-material" rid="SM1">Supplementary Table 1</xref>).</p>
<table-wrap position="float" id="T3">
<label>Table 3</label>
<caption><p>User defined functionality requirements of the resistance training data collection system.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th valign="top" align="left"><bold>Requirement</bold></th>
<th valign="top" align="left"><bold>Detail</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Data entry features</td>
<td valign="top" align="left">The data entry user must be selected by the player.</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">For each of the defined lifts, users must be able to enter the weight and repetitions corresponding to their top lift for the session.</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">Users must be able to select the lift type (e.g., heavy or dynamic) for lower body lifts.</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">Classes of lift types (e.g., upper body, lower body, prophylactics) must be grouped.</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">Separate data entry inputs are necessary for player body weight and Rated Perceived Exertion (RPE).</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">Prophylactic data requires a &#x00027;Yes/No&#x00027; input.</td>
</tr>
<tr>
<td valign="top" align="left">Real-time feedback</td>
<td valign="top" align="left">Automatically calculate and show the 1RM value corresponding to the entered weight and reps to the player.</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">Notify users of the data entry status, including any specific data entry errors.</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">Notify users the success/failure of data submission.</td>
</tr>
<tr>
<td valign="top" align="left">Data entry controls</td>
<td valign="top" align="left">Restrict users from submitting incorrect data. The interface must be capable of detecting defined data entry error conditions.</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">Restrict users from submitting data if mandatory data inputs are not entered (e.g., player body weight data is mandatory to calculate relative strength scores).</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">Users must enter data to at least a single lift to submit the data for storage.</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">Prevent players from entering multiple data entries for a specific date.</td>
</tr>
<tr>
<td valign="top" align="left">Data storage</td>
<td valign="top" align="left">The entered data must be stored in a secure database.</td>
</tr>
<tr>
<td valign="top" align="left">User friendliness</td>
<td valign="top" align="left">The interface must be simple and easy to use. The number of operations performed by the user must be minimized.</td>
</tr>
<tr>
<td valign="top" align="left">Accessibility</td>
<td valign="top" align="left">The interface must be easily accessible to the players after completing their resistance training sessions.</td>
</tr>
<tr>
<td/>
<td valign="top" align="left">The RPE scale must be accessible to the player during data entry.</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec>
<title>Build (External Loop)</title>
<p>From a technical point of view, to implement the redesigned resistance training information flow, as shown by the system network model in <xref ref-type="fig" rid="F6">Figure 6A</xref>, we developed a web-based interface using R Shiny (application hosted in shinyapps.io server) for collecting the daily resistance training data of the players. The data collection interface was launched inside the gym using Raspberry Pi 4 devices (<xref ref-type="fig" rid="F6">Figure 6B</xref>), acting as IoT gateways using Wi-Fi and the collected data were stored in a MySQL database. Finally, data visualization interfaces were also designed using R Shiny (hosted in shinyapps.io server) to allow HPU staff, players and coaches to automatically access the data in the database when necessary and transform it to meaningful information to support decision making relating to player management.</p>
<fig id="F6" position="float">
<label>Figure 6</label>
<caption><p>Implemented system overview <bold>(A)</bold> network model <bold>(B)</bold> data collection interfaces inside the gym.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fspor-04-850885-g0006.tif"/>
</fig>
<p>Utilizing the technologies discussed previously, the internal build-measure-learn loop within the Build step of the external loop was used to develop an MVP to achieve the functionality requirements defined in the Plan step (e.g., the requirements for the data collection interface defined in <xref ref-type="table" rid="T4">Table 4</xref>). <xref ref-type="fig" rid="F7">Figure 7</xref> illustrates each iteration of the internal build-measure-learn loop used to design the resistance training data collection system MVP, including each version, the corresponding feedback by the three users in the design loop and the required design changes for the next iteration. Readers can refer to <xref ref-type="supplementary-material" rid="SM5">Supplementary Figure 2</xref> for the algorithm flow of the data collection system. <xref ref-type="fig" rid="F8">Figure 8</xref> shows the data visualization system MVP and specifically, as described below, the four tabs illustrate how S&#x00026;C data were converted to the different information sources which were necessary to manage the athletes.</p>
<list list-type="simple">
<list-item><p>(A) S&#x00026;C Charts (for each player)
<list list-type="roman-upper">
<list-item><p>Illustrates the best scores, per each resistance training exercise, during a selected date range.</p></list-item>
<list-item><p>Presents the longitudinal data (each day of the selected date range) of each exercise.</p></list-item>
<list-item><p>Based on a color coding, indicates (Yes/No) if each prophylactic exercise has been conducted at least once during a week.</p></list-item>
</list></p></list-item>
<list-item><p>(B) S&#x00026;C All Time (whole squad)
<list list-type="roman-upper">
<list-item><p>A table illustrating the best scores of all players in the squad for each resistance training exercise (calculated from all data in the database until the current date).</p></list-item>
<list-item><p>Within the performance department, according to the positional groups in rugby union (e.g., prop, scrum half), the expected standards for each resistance training exercise have been defined. Therefore, aligning to the methods defined in sport literature (Robertson et al., <xref ref-type="bibr" rid="B35">2016</xref>), each data cell in the table was color coded in relation to the set standards.</p></list-item>
</list></p></list-item>
<list-item><p>(C) S&#x00026;C Current (whole squad)
<list list-type="roman-upper">
<list-item><p>A table illustrating the best scores of all players in the squad for each resistance training exercise performed during the last 6 weeks (rolling). Notice how the missing data (in all columns) for players illustrate that they were either injured, on loan or training with the national team.</p></list-item>
<list-item><p>The same color coding described previously was used to highlight each cell.</p></list-item>
</list></p></list-item>
<list-item><p>(D) Baseline Tests (for each player)
<list list-type="roman-upper">
<list-item><p>Illustrates the best scores, per each baseline test, during a selected date range.</p></list-item>
<list-item><p>At a given instance, four different tests can be compared on the screen.</p></list-item>
<list-item><p>Similar to the above, standards have been defined for each baseline test and they were incorporated into the graphs by translating into a color coding.</p></list-item>
</list>
</p></list-item>
</list>
<table-wrap position="float" id="T4">
<label>Table 4</label>
<caption><p>Task completion rates (including SEQ results) for the usability evaluation data collection.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th valign="top" align="left"><bold>Task</bold><break/> <bold>number</bold></th>
<th valign="top" align="center" colspan="18" style="border-bottom: thin solid #000000;"><bold>User</bold></th>
<th valign="top" align="center"><bold>Task completion rate <italic>(%)</italic></bold></th>
<th valign="top" align="center"><bold>SEQ (Geometric mean)</bold></th>
</tr>
<tr>
<th/>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>1</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>2</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>3</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>4</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>5</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>6</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>7</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>8</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>9</sub></bold></th>
<th/>
<th/>
</tr>
<tr>
<th/>
<th valign="top" align="center"><bold>Completion</bold></th>
<th valign="top" align="center"><bold>SEQ</bold></th>
<th valign="top" align="center"><bold>Completion</bold></th>
<th valign="top" align="center"><bold>SEQ</bold></th>
<th valign="top" align="center"><bold>Completion</bold></th>
<th valign="top" align="center"><bold>SEQ</bold></th>
<th valign="top" align="center"><bold>Completion</bold></th>
<th valign="top" align="center"><bold>SEQ</bold></th>
<th valign="top" align="center"><bold>Completion</bold></th>
<th valign="top" align="center"><bold>SEQ</bold></th>
<th valign="top" align="center"><bold>Completion</bold></th>
<th valign="top" align="center"><bold>SEQ</bold></th>
<th valign="top" align="center"><bold>Completion</bold></th>
<th valign="top" align="center"><bold>SEQ</bold></th>
<th valign="top" align="center"><bold>Completion</bold></th>
<th valign="top" align="center"><bold>SEQ</bold></th>
<th valign="top" align="center"><bold>Completion</bold></th>
<th valign="top" align="center"><bold>SEQ</bold></th>
<th/>
<th/>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">T<sub>1</sub></td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">100</td>
<td valign="top" align="center">6.46</td>
</tr>
<tr>
<td valign="top" align="left">T<sub>2</sub></td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">33.33</td>
<td valign="top" align="center">5.06</td>
</tr>
<tr>
<td valign="top" align="left">T<sub>3</sub></td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">55.56</td>
<td valign="top" align="center">5.13</td>
</tr>
<tr>
<td valign="top" align="left">T<sub>4</sub></td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">N</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">77.78</td>
<td valign="top" align="center">5.41</td>
</tr>
<tr>
<td valign="top" align="left">T<sub>5</sub></td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">Y</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">100</td>
<td valign="top" align="center">4.40</td>
</tr>
</tbody>
</table>
</table-wrap>
<fig id="F7" position="float">
<label>Figure 7</label>
<caption><p>Internal build-measure-learn loop used to develop the digital interface for daily resistance training data collection MVP.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fspor-04-850885-g0007.tif"/>
</fig>
<fig id="F8" position="float">
<label>Figure 8</label>
<caption><p>Strength and conditioning data visualization system (interface) MVP <bold>(A)</bold> S&#x00026;C Charts <bold>(B)</bold> S&#x00026;C All Time <bold>(C)</bold> S&#x00026;C Current <bold>(D)</bold> Baseline Tests.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fspor-04-850885-g0008.tif"/>
</fig>
</sec>
<sec>
<title>Measure (External Loop)</title>
<p>The data collected to evaluate the usability of the two MVP&#x00027;s described previously; (1) data collection (<xref ref-type="fig" rid="F7">Figure 7</xref>) and (2) data visualization (<xref ref-type="fig" rid="F8">Figure 8</xref>) is specified below.</p>
<p><italic>Data collection system:</italic> The mean (<overline>x</overline>) System Usability Scale (SUS) score of the random sample (<italic>n</italic> &#x0003D; 50) was 87.6 (<italic>SD</italic> &#x0003D; 10.76), where the 99% confidence interval (CI) ranged from 83.68 to 91.59 (<xref ref-type="supplementary-material" rid="SM3">Supplementary Data Sheet 1</xref>).</p>
<p><italic>Data visualization system:</italic> For data collection relating to the cognitive walkthrough (usability evaluation of the data visualization system), the completion rates of the 5 tasks performed by the HPU staff and the responses to the Single Ease Question (SEQ) question are specified in <xref ref-type="table" rid="T4">Table 4</xref>. Although users had found Task 5 to be the most difficult, everyone had successfully competed it along with Task 1. On the contrary, Task 2 had the worst completion rate among the five tasks, illustrating the possibility for usability problems associated with it. Additionally, in reference to the geometric mean of the SEQ rating, the users had encountered Task 1 to be the easiest to complete.</p>
</sec>
<sec>
<title>Learn (External Loop)</title>
<p>From the data collected in the previous step, in relation to the resistance training information flow, the following results were generated relating to the usability assessment and evaluation of the two systems (data collection and visualization).</p>
<list list-type="bullet">
<list-item><p><italic>Data collection system:</italic> Initially, aligning to the guidelines suggested for using parametric tests for grouped ordinal data like the Likert-scale in SUS (Harpe, <xref ref-type="bibr" rid="B14">2015</xref>), a computation using R was conducted to evaluate if the central limit theorem (CLT) held true for the sampling considered in the current study. The results demonstrated that the sample means were normally distributed (refer to <xref ref-type="supplementary-material" rid="SM3">Supplementary Data Sheet 1</xref>). Therefore, the planned Z-tests were conducted for the random sample specified in the Measure step. The core outcomes of the two-sided Z-tests have been provided below; readers can refer to <xref ref-type="supplementary-material" rid="SM3">Supplementary Data Sheet 1</xref> in the supporting information for all the calculations.
<list list-type="simple">
<list-item><p>&#x025CB; An initial one-sample <italic>Z</italic>-test was conducted to evaluate the sample SUS score mean (<overline>x</overline> = 87.6) against the average SUS industry benchmark (&#x003BC; &#x0003D; 68), with the significance level set to &#x003B1; &#x0003D; 0.01. The resultant test yielded a two-tailed <italic>p value</italic> &#x0003D; 5.93 <italic>x</italic> 10<sup>&#x02212;38</sup>. Therefore, sufficient statistical evidence was available to reject the null hypothesis (<overline>x</overline> = 68).</p></list-item>
<list-item><p>&#x025CB; Next, a second, one-sample Z-test was conducted to evaluate the sample mean (<overline>x</overline> = 87.6) against the lower industry SUS score benchmark for a Grade A interface (&#x003BC; &#x0003D; 80.8) according to the SUS grading scale (Sauro, <xref ref-type="bibr" rid="B37">2011</xref>; Sauro and Lewis, <xref ref-type="bibr" rid="B38">2016</xref>). To compensate for the two tests, a <italic>Bonferroni correction</italic> was used by setting &#x003B1; &#x0003D; 0.005. The resultant test generated a two-tailed <italic>p value</italic> &#x0003D; 7.8897 <italic>x</italic> 10<sup>&#x02212;6</sup>. Hence, it was possible to reject the null hypothesis <overline>x</overline> = 80.8) for this test as well.</p></list-item>
<list-item><p>&#x025CB; Finally, a post study power calculation was conducted in relation to the second Z-test performed against the lower Grade A SUS score (<overline>x</overline> = 87.6, <italic>&#x003BC;</italic> = 80.8, <italic>&#x003B1;</italic> = 0.05, <italic>n</italic> = 50, <italic>d</italic> = 0.632). The results illustrated that the test had 95% power.</p></list-item>
</list></p></list-item></list>
<p>Therefore, based on the prior results from the statistical tests, there was less than 1% chance that a mean SUS score of 87.6 &#x000B1; 10.76 for a sample of size 50 would be generated from a population (professional rugby union players using the interface in the considered club) with a mean score equal to 68 or 80.8. With additional justification from the sample 99% CI of 83.68 to 91.59, there was sufficient evidence to suggest that the usability of the data collection system was potentially above industry average and could be minimally rated as a Grade A system according to the SUS grading scale. This meant that the latter system had higher perceived usability than 90% of the systems tested within the SUS grading scale (Sauro, <xref ref-type="bibr" rid="B37">2011</xref>; Lewis, <xref ref-type="bibr" rid="B21">2018</xref>). Therefore, it was decided to <italic>Persevere</italic> with this version of the resistance training data collection system MVP by conducting any further minor modifications.</p>
<list list-type="bullet">
<list-item><p><italic>Data visualization system:</italic> According to the plan step, the data visualization system was acceptable if there were no major usability issues within the system. Therefore, for illustration, the results from the cognitive walkthrough evaluations of three users conducted from the four-question approach (Wharton et al., <xref ref-type="bibr" rid="B44">1994</xref>) for the action sequence relating to Task 2 has been provided in <xref ref-type="table" rid="T5">Table 5</xref>. Similar analysis was conducted for all users and tasks in the assessment.</p></list-item>
</list>
<table-wrap position="float" id="T5">
<label>Table 5</label>
<caption><p>Four-question cognitive walkthrough corresponding to the second task (T<sub>2</sub>) used to evaluate the usability of the data visualization system.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th valign="top" align="center" colspan="3" style="border-bottom: thin solid #000000;"><bold>Action sequence</bold></th>
<th valign="top" align="center" colspan="12" style="border-bottom: thin solid #000000;"><bold>User</bold></th>
</tr>
<tr>
<th/>
<th/>
<th/>
<th valign="top" align="center" colspan="4" style="border-bottom: thin solid #000000;"><bold>U<sub>1</sub></bold></th>
<th valign="top" align="center" colspan="4" style="border-bottom: thin solid #000000;"><bold>U<sub>2</sub></bold></th>
<th valign="top" align="center" colspan="4" style="border-bottom: thin solid #000000;"><bold>U<sub>3</sub></bold></th>
</tr>
<tr>
<th valign="top" align="left"><bold>No</bold>.</th>
<th valign="top" align="left"><bold>Action</bold></th>
<th valign="top" align="left"><bold>Type</bold></th>
<th valign="top" align="left"><bold>Q1</bold></th>
<th valign="top" align="left"><bold>Q2</bold></th>
<th valign="top" align="left"><bold>Q3</bold></th>
<th valign="top" align="left"><bold>Q4</bold></th>
<th valign="top" align="left"><bold>Q1</bold></th>
<th valign="top" align="left"><bold>Q2</bold></th>
<th valign="top" align="left"><bold>Q3</bold></th>
<th valign="top" align="left"><bold>Q4</bold></th>
<th valign="top" align="left"><bold>Q1</bold></th>
<th valign="top" align="left"><bold>Q2</bold></th>
<th valign="top" align="left"><bold>Q3</bold></th>
<th valign="top" align="left"><bold>Q4</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">1</td>
<td valign="top" align="left">Click &#x0201C;S&#x00026;C Current&#x0201D; tab</td>
<td valign="top" align="left">User</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
</tr>
<tr>
<td valign="top" align="left">2</td>
<td valign="top" align="left">Data appears</td>
<td valign="top" align="left">System</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">N</td>
</tr>
<tr>
<td valign="top" align="left">3</td>
<td valign="top" align="left">Type player name in &#x0201C;Search&#x0201D;</td>
<td valign="top" align="left">User</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
</tr>
<tr>
<td valign="top" align="left">4</td>
<td valign="top" align="left">Filtered data appears</td>
<td valign="top" align="left">System</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
</tr>
<tr>
<td valign="top" align="left">5</td>
<td valign="top" align="left">Scroll down to player name</td>
<td valign="top" align="left">User</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">NA</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
</tr>
<tr>
<td valign="top" align="left">6</td>
<td valign="top" align="left">Read Bench Press fill color</td>
<td valign="top" align="left">User</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
</tr>
<tr>
<td valign="top" align="left">7</td>
<td valign="top" align="left">Read the color rating from the legend</td>
<td valign="top" align="left">User</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">Y</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
<td valign="top" align="left">N</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<p><italic>A &#x0201C;No&#x0201D; answer to any question depicted an instance of a potential usability problem</italic>.</p>
</table-wrap-foot>
</table-wrap>
<p>From the usability evaluation, 14 usability issues and 4 further functionality improvement requirements (which were not captured in the initial user requirements) were unraveled (<xref ref-type="supplementary-material" rid="SM2">Supplementary Table 2</xref>). Consensus was reached between the three authors on the severity of the usability problems. Specifically, based on a practical viewpoint, it was agreed that the 14 usability issues were minor problems. Among the functionality improvements, two required major changes to be implemented in the system. However, after a discussion with the HPU management team, it was agreed that the two functionality improvements requiring major changes were of low priority. Therefore, it was decided to <italic>Persevere</italic> with this version of the S&#x00026;C data visualization system MVP by improving the system to overcome the minor usability problems.</p>
</sec>
</sec>
<sec>
<title>Process Monitoring</title>
<sec>
<title>Pre-post Optimization Information Quality</title>
<p>The main results pertaining to this stage focused on assessing the change in information quality of the S&#x00026;C information flow due to the optimization. <xref ref-type="table" rid="T6">Table 6</xref> shows the responses provided by each HPU staff member to the IQA questionnaire to assess the pre-post information quality of the S&#x00026;C information flow.</p>
<table-wrap position="float" id="T6">
<label>Table 6</label>
<caption><p>Individual responses to the IQA questionnaire and the resulting overall scores for the pre- post-optimization information quality assessment of the S&#x00026;C information flow.</p></caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th valign="top" align="left"><bold>Information quality dimension</bold></th>
<th valign="top" align="center" colspan="16" style="border-bottom: thin solid #000000;"><bold>Individual scores</bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>Overall score</bold></th>
</tr>
<tr>
<th/>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>1</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>2</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>3</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>4</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>5</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>6</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>7</sub></bold></th>
<th valign="top" align="center" colspan="2" style="border-bottom: thin solid #000000;"><bold>U<sub>8</sub></bold></th>
<th/>
</tr>
<tr>
<th/>
<th valign="top" align="center"><bold>Pre</bold></th>
<th valign="top" align="center"><bold>Post</bold></th>
<th valign="top" align="center"><bold>Pre</bold></th>
<th valign="top" align="center"><bold>Post</bold></th>
<th valign="top" align="center"><bold>Pre</bold></th>
<th valign="top" align="center"><bold>Post</bold></th>
<th valign="top" align="center"><bold>Pre</bold></th>
<th valign="top" align="center"><bold>Post</bold></th>
<th valign="top" align="center"><bold>Pre</bold></th>
<th valign="top" align="center"><bold>Post</bold></th>
<th valign="top" align="center"><bold>Pre</bold></th>
<th valign="top" align="center"><bold>Post</bold></th>
<th valign="top" align="left"><bold>Pre</bold></th>
<th valign="top" align="center"><bold>Post</bold></th>
<th valign="top" align="left"><bold>Pre</bold></th>
<th valign="top" align="center"><bold>Post</bold></th>
<th valign="top" align="center"><bold>Pre</bold></th>
<th valign="top" align="center"><bold>Post</bold></th>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Accessibility</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">9.5</td>
<td valign="top" align="center">5.5</td>
<td valign="top" align="center">7.8</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">8.8</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">4.3</td>
<td valign="top" align="center">8.5</td>
<td/>
<td valign="top" align="center">7.5</td>
<td/>
<td valign="top" align="center">9.3</td>
<td valign="top" align="center">4.3</td>
<td valign="top" align="center">8.9</td>
</tr>
<tr>
<td/>
<td/>
<td/>
<td/>
<td/>
<td/>
<td/>
<td/>
<td/>
<td/>
<td/>
<td/>
<td/>
<td valign="top" align="left">Data unavailable</td>
<td/>
<td valign="top" align="left">Data unavailable</td>
<td/>
<td/>
<td/>
</tr>
<tr>
<td valign="top" align="left">Appropriate amount</td>
<td valign="top" align="center">4.8</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">0.5</td>
<td valign="top" align="center">5.5</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">4.8</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">5.3</td>
<td valign="top" align="center">5</td>
<td/>
<td valign="top" align="center">3.8</td>
<td/>
<td valign="top" align="center">2.5</td>
<td valign="top" align="center">4.4</td>
<td valign="top" align="center">5.2</td>
</tr>
<tr>
<td valign="top" align="left">Believability</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">3.5</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">6.3</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">6.8</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">6.5</td>
<td/>
<td valign="top" align="center">6.3</td>
<td/>
<td valign="top" align="center">5</td>
<td valign="top" align="center">5.7</td>
<td valign="top" align="center">6.5</td>
</tr>
<tr>
<td valign="top" align="left">Completeness</td>
<td valign="top" align="center">3.7</td>
<td valign="top" align="center">6.8</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">7.2</td>
<td valign="top" align="center">5.5</td>
<td valign="top" align="center">6.3</td>
<td valign="top" align="center">6.2</td>
<td valign="top" align="center">7.2</td>
<td valign="top" align="center">4.3</td>
<td valign="top" align="center">8.3</td>
<td valign="top" align="center">4.2</td>
<td valign="top" align="center">7.2</td>
<td/>
<td valign="top" align="center">5.7</td>
<td/>
<td valign="top" align="center">6.8</td>
<td valign="top" align="center">4.8</td>
<td valign="top" align="center">6.9</td>
</tr>
<tr>
<td valign="top" align="left">Concise representation</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">3.3</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">6.3</td>
<td valign="top" align="center">6.5</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">8.3</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">4.5</td>
<td valign="top" align="center">9</td>
<td/>
<td valign="top" align="center">9</td>
<td/>
<td valign="top" align="center">7.3</td>
<td valign="top" align="center">4.5</td>
<td valign="top" align="center">8.8</td>
</tr>
<tr>
<td valign="top" align="left">Consistent Representation</td>
<td valign="top" align="center">6.3</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">4.3</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">4.3</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">6.5</td>
<td valign="top" align="center">6.5</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">7</td>
<td/>
<td valign="top" align="center">7</td>
<td/>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">5.2</td>
<td valign="top" align="center">7.0</td>
</tr>
<tr>
<td valign="top" align="left">Ease of operation</td>
<td valign="top" align="center">4.2</td>
<td valign="top" align="center">5.6</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">5.4</td>
<td valign="top" align="center">4.6</td>
<td valign="top" align="center">4.2</td>
<td valign="top" align="center">5.4</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">5.4</td>
<td valign="top" align="center">5.4</td>
<td/>
<td valign="top" align="center">5</td>
<td/>
<td valign="top" align="center">5.2</td>
<td valign="top" align="center">4.9</td>
<td valign="top" align="center">5.4</td>
</tr>
<tr>
<td valign="top" align="left">Free of error</td>
<td valign="top" align="center">6.3</td>
<td valign="top" align="center">6.8</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">6.3</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">6.8</td>
<td valign="top" align="center">3.3</td>
<td valign="top" align="center">6.8</td>
<td valign="top" align="center">4.3</td>
<td valign="top" align="center">6.8</td>
<td/>
<td valign="top" align="center">6.5</td>
<td/>
<td valign="top" align="center">6.3</td>
<td valign="top" align="center">5.1</td>
<td valign="top" align="center">6.7</td>
</tr>
<tr>
<td valign="top" align="left">Interpretability</td>
<td valign="top" align="center">5.3</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">6.6</td>
<td valign="top" align="center">5.5</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">4.8</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">5.6</td>
<td/>
<td valign="top" align="center">5.6</td>
<td/>
<td valign="top" align="center">6.8</td>
<td valign="top" align="center">5.0</td>
<td valign="top" align="center">6.0</td>
</tr>
<tr>
<td valign="top" align="left">Objectivity</td>
<td valign="top" align="center">8</td>
<td valign="top" align="center">8.5</td>
<td valign="top" align="center">9</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">8.3</td>
<td valign="top" align="center">8.3</td>
<td valign="top" align="center">4.8</td>
<td valign="top" align="center">7.3</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">7.8</td>
<td valign="top" align="center">4.8</td>
<td valign="top" align="center">9</td>
<td/>
<td valign="top" align="center">8</td>
<td/>
<td valign="top" align="center">8</td>
<td valign="top" align="center">6.8</td>
<td valign="top" align="center">8.3</td>
</tr>
<tr>
<td valign="top" align="left">Relevancy</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">9</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">8.5</td>
<td valign="top" align="center">8</td>
<td valign="top" align="center">9</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">9</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">9</td>
<td/>
<td valign="top" align="center">8</td>
<td/>
<td valign="top" align="center">10</td>
<td valign="top" align="center">8.3</td>
<td valign="top" align="center">9.4</td>
</tr>
<tr>
<td valign="top" align="left">Reputation</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">6.5</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">5.5</td>
<td valign="top" align="center">7.3</td>
<td/>
<td valign="top" align="center">6.5</td>
<td/>
<td valign="top" align="center">6.8</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">6.4</td>
</tr>
<tr>
<td valign="top" align="left">Security</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">6.5</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">8.5</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">3.8</td>
<td valign="top" align="center">5.3</td>
<td/>
<td valign="top" align="center">7.5</td>
<td/>
<td valign="top" align="center">6.8</td>
<td valign="top" align="center">5.0</td>
<td valign="top" align="center">7.1</td>
</tr>
<tr>
<td valign="top" align="left">Timeliness</td>
<td valign="top" align="center">5.6</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">4.4</td>
<td valign="top" align="center">5.2</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">5.2</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">4.6</td>
<td valign="top" align="center">5.8</td>
<td/>
<td valign="top" align="center">5.6</td>
<td/>
<td valign="top" align="center">6</td>
<td valign="top" align="center">5.3</td>
<td valign="top" align="center">5.9</td>
</tr>
<tr>
<td valign="top" align="left">Understandability</td>
<td valign="top" align="center">5.5</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">5.8</td>
<td valign="top" align="center">6.5</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">9.5</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">7.5</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">7</td>
<td/>
<td valign="top" align="center">6.5</td>
<td/>
<td valign="top" align="center">7</td>
<td valign="top" align="center">6.0</td>
<td valign="top" align="center">7.2</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>For further illustration, the overall impact to each information quality dimension has been visualized by the radar chart in <xref ref-type="fig" rid="F9">Figure 9A</xref> and the corresponding effects to the quality of the S&#x00026;C information flow analyzed from the PSP/IQ model (information as a product and service) has been illustrated by <xref ref-type="fig" rid="F9">Figure 9B</xref>. The results indicate that there has been an increase in the quality of S&#x00026;C information flow as a product and service.</p>
<fig id="F9" position="float">
<label>Figure 9</label>
<caption><p>Change in pre- post-optimization information quality <bold>(A)</bold> impact to each information quality dimension relating to the S&#x00026;C information flow <bold>(B)</bold> effect analyzed from the PSP/IQ model.</p></caption>
<graphic mimetype="image" mime-subtype="tiff" xlink:href="fspor-04-850885-g0009.tif"/>
</fig>
</sec>
</sec>
</sec>
<sec sec-type="discussion" id="s4">
<title>Discussion</title>
<p>This study presented results from an attempt to digitally optimize the strength and conditioning (S&#x00026;C) information flow in the performance department of a professional rugby union environment. Specifically, the S&#x00026;C information flow was redesigned using integral technology, activity elimination and activity automation redesign heuristics. The redesigned information flow was implemented using digital technologies (web-based applications, IoT and database management systems) by utilizing two build-measure-lean loops specified in the Lean Startup method. The internal loop was used to create minimum viable products of S&#x00026;C data collection and visualization systems to meet the system functionality requirements set by their potential users. The outer loop evaluated the usability of the designed systems. For the data collection systems, usability data collected from a random sample of 50 players using the System Usability Scale (SUS) produced a mean score of 87.6 &#x000B1; 10.76. And the results from statistical tests conducted for the sample against the average industry usability SUS benchmark score (68) and minimum score for a Grade A rating (80.8) for similar interfaces illustrated sufficient evidence to suggest that the data collection system could be above industry average and can be rated minimally as Grade A system. For the data visualization system, 9 cognitive walkthroughs were conducted to evaluate potential usability problems. The results helped to unravel 14 minor usability issues and 4 functionality problems. Hence, it was decided to persevere with the designed digital systems. A pre-post optimization information quality assessment of the S&#x00026;C information flow conducted using the IQA questionnaire highlighted potential positive improvements in all the information quality dimensions with a distinctive enhancement to the accessibility of the S&#x00026;C information flow. Similar positive improvements in the information quality were observed through the PSP/IQ model as well.</p>
<p>But most importantly, the case study successfully presented a practical example of how sports practitioners operating within a professional environment could effectively use existing digital technologies to optimize the information flows needed to manage professional athletes. This is critical to the current sporting landscape where the importance of managing time and cost have significantly increased due to the complexities created by the COVID-19 pandemic. Therefore, we feel that the overall outcomes from the study would be especially beneficial to practitioners requiring guidelines for implementing cost effective and easily adoptable information flow digitization solutions in sporting environments.</p>
<sec>
<title>Design Thinking</title>
<p>Previous design research clearly illustrates how technology developments fail due to poorly defined user requirements (El-Ansary, <xref ref-type="bibr" rid="B13">2002</xref>; Mirza, <xref ref-type="bibr" rid="B24">2010</xref>). However, for the presented study, embedding users early into the design loop when developing the digital systems allowed us to capture the expected user requirement properly and create solutions from the viewpoints of the actual end users. We believe that this was a major reason for experiencing limited challenges when deploying the designed systems into the considered professional sporting environment.</p>
<p>The Lean Startup framework used to design the digital systems in the current study suited the flexibility requirements of a system design expected in a dynamic environment like sports. This statement is justified since it was possible to embed changing user requirements within the internal build-measure-learn loop when developing the system MVP&#x00027;s (<xref ref-type="fig" rid="F7">Figures 7</xref>, <xref ref-type="fig" rid="F8">8</xref>). Furthermore, the availability of high-level programming languages like R with packages like Shiny has made it easy and less time consuming to design interactive web applications like the ones developed in this study. Author JR developed all the applications by working within the considered sporting environment, this greatly assisted to bring the potential users into the design loop and allow them to be the most important member of the design team. Following a design thinking approach by modeling a system and its corresponding algorithms from standards like UML (use case, activity and sequence diagrams) helped to properly plan a system design rather than leaping straight into its implementation. Finally, we have not provided information on the data management model in the current article due to intellectual property concerns associated with sharing the relevant data architecture.</p>
</sec>
<sec>
<title>System Usability</title>
<p>Evaluating the usability of a system interacting with players with time consuming methods like lab-based experiments was not practical in the considered sporting context due to the time constraints existing within the training schedule. Therefore, assessing the overall usability of a system using a quick and easy method like the System Usability Scale (SUS) was more viable in the considered environment, mainly, because it took only few minutes for a player to respond to the 10 SUS questions. Furthermore, in the current study, the use of parametric tests on Likert-scale data (like the SUS) is justified since the study adhered to the guidelines provided in literature when considering such approaches (Harpe, <xref ref-type="bibr" rid="B14">2015</xref>; Mircioiu and Atkinson, <xref ref-type="bibr" rid="B23">2017</xref>).</p>
<p>For the data visualization system, the results highlighted that most (12/14) of the usability issues identified through the cognitive walkthroughs were caused due to the poor usage of labels on the interfaces. Overall, we feel the latter usability evaluation was an important step since although sports informatics related research discusses the growing importance of data visualization in sport, less emphasis has been given to presenting results from assessments conducted to evaluate the usability of such visualization systems. Although still debated in literature, research illustrates that testing with at least 5 users could help to obtain about 80% of usability problems in a system (Nielsen et al., <xref ref-type="bibr" rid="B28">1993</xref>; Nielsen, <xref ref-type="bibr" rid="B26">2000</xref>). Therefore, there is a requirement to embed usability assessment of data visualization systems in professional sporting environments. In most cases, cognitive walkthroughs are normally used as a usability evaluation method without using actual users, where the design team would contextualize the interaction of the user. However, there are examples of cognitive walkthroughs conducted with actual users in research (Mahatody et al., <xref ref-type="bibr" rid="B22">2010</xref>; Carvalho et al., <xref ref-type="bibr" rid="B7">2014</xref>). Therefore, for the given study, since the system developments and implementation occurred within the performance department itself, it was possible to allow the actual users to perform the required tasks for the cognitive walkthroughs. But above all, by utilizing the actual users, we were able to understand the exact problems which existed in the system and improve them during deployment. So far, the deployed systems have been used for a full rugby season without the occurrence of breakdowns.</p>
</sec>
<sec>
<title>Information Quality</title>
<p>The results suggested that there were improvements to all the information quality dimensions due to the optimization. However, we were unable to strictly verify the latter statement using statistical tests since the sample sizes associated with the pre-post optimization information quality assessments were low; <italic>n</italic> &#x0003D; 6 (pre) and <italic>n</italic> &#x0003D; 8 (post). Such limitations in sample size were dictated by the smaller number of HPU staff members associated with the S&#x00026;C information flow. Yet, there appears to be a distinctive change in the accessibility dimension (4.3 to 8.9), suggesting a probable improvement in accessibility of player S&#x00026;C data in the considered environment. The latter statement was justified by the positive feedback from the HPU staff relating to the implemented systems. Additionally, the dashboards used to monitor the implemented systems (e.g., number of connections, network usage) illustrated that the practitioners continuously used those digital systems. However, in future, there is a definite need to conduct sport informatics research for developing more objective methods for assessing information quality in sporting environments. Researchers could refer to information sciences research on objective assessments of data quality to guide such developments (Pipino et al., <xref ref-type="bibr" rid="B30">2003</xref>). Finally, especially due to the optimization of the resistance information flow (<xref ref-type="fig" rid="F5">Figure 5B</xref>), there were reductions in the workloads of the HPU staff (e.g., S&#x00026;C Coaches).</p>
</sec>
</sec>
<sec sec-type="conclusions" id="s5">
<title>Conclusion</title>
<p>We presented the complete results from our attempts to optimize the strength and conditioning (S&#x00026;C) information flow existing within the performance department of a professional rugby union environment. One of the key requirements for the optimization project considered in the study was to improve the accessibility of S&#x00026;C information. Therefore, from the outcomes of the pre-post information quality assessment, we can conclude that the implemented digital systems have enhanced the S&#x00026;C information flow quality with improvements to its accessibility to the HPU staff. Additionally, the build-measure-learn cycle in the Lean Startup method was a suitable framework for designing and implementing digital systems in the considered case study environment. This was due its flexibility in execution, early prototyping and short design lead times associated with the framework. In relation to the usability assessments of the systems, we can conclude that the SUS scale was a quick and efficient tool to conduct summative usability assessments of digital systems interacting with athletes in the examined professional rugby union club. Based on the findings, we can emphasize the importance of conducting evaluations for unraveling usability issues even within data visualization systems implemented to support player management. Moreover, while the IQA instrument helps to obtain a subjective assessment of information quality in a sporting environment like the one considered in this article, more objective or combined (objective and subjective) methods with less complexity and burden on the practitioners may be necessary to be developed in future due to the large increase in the implementation of digital technologies in professional sporting environments. Finally, we invite other sport researchers to utilize the methods adopted within this case study to optimize information flows within their respective environments and report the relevant findings to synthesize the outcomes that may be generalizable across different professional sporting organizations.</p>
</sec>
<sec sec-type="data-availability" id="s6">
<title>Data Availability Statement</title>
<p>The original contributions presented in the study are included in the article/<xref ref-type="sec" rid="s10">Supplementary Material</xref>, further inquiries can be directed to the corresponding author.</p>
</sec>
<sec id="s7">
<title>Ethics Statement</title>
<p>The studies involving human participants were reviewed and approved by Local Research Ethics Co-ordinator, Carnegie School of Sport, Leeds Beckett University, UK. The patients/participants provided their written informed consent to participate in this study.</p>
</sec>
<sec id="s8">
<title>Author Contributions</title>
<p>JR, GR, and DW contributed to conception and design of the study, read, provided revisions, and approved the submitted version. JR, MP, and MZ contributed to requirement gathering phase. JR designed all systems discussed in the study, conducted the pre- post-information quality assessment, and wrote the initial draft of the manuscript. All authors were engaged during the implementation of usability tests and evaluations.</p>
</sec>
<sec sec-type="COI-statement" id="conf1">
<title>Conflict of Interest</title>
<p>JR, MZ, MP, and GR were employed by Bath Rugby Football Club. DW was employed by Leeds Rhinos Rugby League Club.</p>
</sec>
<sec sec-type="disclaimer" id="s9">
<title>Publisher&#x00027;s Note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
</body>
<back>
<sec sec-type="supplementary-material" id="s10">
<title>Supplementary Material</title>
<p>The Supplementary Material for this article can be found online at: <ext-link ext-link-type="uri" xlink:href="https://www.frontiersin.org/articles/10.3389/fspor.2022.850885/full#supplementary-material">https://www.frontiersin.org/articles/10.3389/fspor.2022.850885/full#supplementary-material</ext-link></p>
<supplementary-material xlink:href="Table_1.docx" id="SM1" mimetype="application/vnd.openxmlformats-officedocument.wordprocessingml.document" xmlns:xlink="http://www.w3.org/1999/xlink"/>
<supplementary-material xlink:href="Table_2.docx" id="SM2" mimetype="application/vnd.openxmlformats-officedocument.wordprocessingml.document" xmlns:xlink="http://www.w3.org/1999/xlink"/>
<supplementary-material xlink:href="Data_Sheet_1.docx" id="SM3" mimetype="application/vnd.openxmlformats-officedocument.wordprocessingml.document" xmlns:xlink="http://www.w3.org/1999/xlink"/>
<supplementary-material xlink:href="Image_1.TIF" id="SM4" mimetype="image/tif" xmlns:xlink="http://www.w3.org/1999/xlink"/>
<supplementary-material xlink:href="Image_2.TIF" id="SM5" mimetype="image/tif" xmlns:xlink="http://www.w3.org/1999/xlink"/>
</sec>
<ref-list>
<title>References</title>
<ref id="B1">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Alomari</surname> <given-names>H.</given-names></name> <name><surname>Ramasamy</surname> <given-names>V.</given-names></name> <name><surname>Kiper</surname> <given-names>J.</given-names></name> <name><surname>Potvin</surname> <given-names>G.</given-names></name></person-group> (<year>2020</year>). <article-title>A User Interface (UI) and User eXperience (UX) evaluation framework for cyberlearning environments in computer science and software engineering education</article-title>. <source>Heliyon</source> <volume>6</volume>, <fpage>e03917</fpage>. <pub-id pub-id-type="doi">10.1016/j.heliyon.2020.e03917</pub-id><pub-id pub-id-type="pmid">32426541</pub-id></citation></ref>
<ref id="B2">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Bangor</surname> <given-names>A.</given-names></name> <name><surname>Kortum</surname> <given-names>P. T.</given-names></name> <name><surname>Miller</surname> <given-names>J. T.</given-names></name></person-group> (<year>2008</year>). <article-title>An empirical evaluation of the system usability scale</article-title>. <source>Int. J. Hum. Comput. Interact</source>. <volume>24</volume>, <fpage>574</fpage>&#x02013;<lpage>594</lpage>. <pub-id pub-id-type="doi">10.1080/10447310802205776</pub-id></citation>
</ref>
<ref id="B3">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Batini</surname> <given-names>C.</given-names></name> <name><surname>Cappiello</surname> <given-names>C.</given-names></name> <name><surname>Francalanci</surname> <given-names>C.</given-names></name> <name><surname>Maurino</surname> <given-names>A.</given-names></name></person-group> (<year>2009</year>). <article-title>Methodologies for data quality assessment and improvement</article-title>. <source>ACM Comput. Surv</source>. <volume>41</volume>, <fpage>1</fpage>&#x02013;<lpage>52</lpage>. <pub-id pub-id-type="doi">10.1145/1541880.1541883</pub-id></citation>
</ref>
<ref id="B4">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Blessing</surname> <given-names>L. T.</given-names></name> <name><surname>Chakrabarti</surname> <given-names>A.</given-names></name></person-group> (<year>2009</year>). <source>DRM: A Design Reseach Methodology</source>. <publisher-name>Springer</publisher-name>. <pub-id pub-id-type="doi">10.1007/978-1-84882-587-1</pub-id></citation>
</ref>
<ref id="B5">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Blobel</surname> <given-names>T.</given-names></name> <name><surname>Lames</surname> <given-names>M.</given-names></name></person-group> (<year>2020</year>). <article-title>A Concept for Club Information Systems (CIS)An Example for Applied Sports Informatics</article-title>. <source>Int. J. Comput. Sci. Sport</source> <volume>19</volume>, <fpage>102</fpage>&#x02013;<lpage>122</lpage>. <pub-id pub-id-type="doi">10.2478/ijcss-2020-0006</pub-id></citation>
</ref>
<ref id="B6">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Brooke</surname> <given-names>J.</given-names></name></person-group> (<year>1995</year>). <article-title>SUS: a quick and dirty usability scale</article-title>. <source>Usability Eval Ind</source>. <fpage>189</fpage>&#x02013;<lpage>194</lpage>.</citation>
</ref>
<ref id="B7">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Carvalho</surname> <given-names>S.</given-names></name> <name><surname>Lira</surname> <given-names>W.</given-names></name> <name><surname>Souza</surname> <given-names>C.</given-names></name> <name><surname>Ferreira</surname> <given-names>R.</given-names></name></person-group> (<year>2014</year>). <article-title>Experimenting on the cognitive walkthrough with users,</article-title> in <source>MobileHCI &#x00027;14: Proceedings of the 16th International Conference on Human-Computer Interaction with Mobile Devices &#x00026; Services</source> (<publisher-loc>Toronto, ON</publisher-loc>).</citation>
</ref>
<ref id="B8">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Cichy</surname> <given-names>C.</given-names></name> <name><surname>Rass</surname> <given-names>S.</given-names></name></person-group> (<year>2019</year>). <article-title>An overview of data quality frameworks</article-title>. <source>IEEE Access</source>. <volume>7</volume>, <fpage>24634</fpage>&#x02013;<lpage>24648</lpage>. <pub-id pub-id-type="doi">10.1109/ACCESS.2019.2899751</pub-id></citation>
</ref>
<ref id="B9">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Dammann</surname> <given-names>O.</given-names></name></person-group> (<year>2018</year>). <article-title>Data, information, evidence, and knowledge: a proposal for health informatics and data science</article-title>. <source>Online J. Public Health Inform</source>. <volume>10</volume>, <fpage>e224</fpage>. <pub-id pub-id-type="doi">10.5210/ojphi.v10i3.9631</pub-id><pub-id pub-id-type="pmid">30931086</pub-id></citation></ref>
<ref id="B10">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>De Ram&#x000F3;n Fern&#x000E1;ndez</surname> <given-names>A.</given-names></name> <name><surname>Ruiz Fern&#x000E1;ndez</surname> <given-names>D.</given-names></name> <name><surname>Sabuco Garc&#x000ED;a</surname> <given-names>Y.</given-names></name></person-group> (<year>2019</year>). <article-title>Business process management for optimizing clinical processes: a systematic literature review</article-title>. <source>Health Inform. J</source>. <volume>26</volume>, <fpage>1305</fpage>&#x02013;<lpage>1320</lpage>. <pub-id pub-id-type="doi">10.1177/1460458219877092</pub-id><pub-id pub-id-type="pmid">31581880</pub-id></citation></ref>
<ref id="B11">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Du</surname> <given-names>M.</given-names></name> <name><surname>Yuan</surname> <given-names>X.</given-names></name></person-group> (<year>2021</year>). <article-title>A survey of competitive sports data visualization and visual analysis</article-title>. <source>J. Visualiz</source>. <volume>24</volume>, <fpage>47</fpage>&#x02013;<lpage>67</lpage>. <pub-id pub-id-type="doi">10.1007/s12650-020-00687-2</pub-id></citation>
</ref>
<ref id="B12">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Dumas</surname> <given-names>M.</given-names></name> <name><surname>La Rosa</surname> <given-names>M.</given-names></name> <name><surname>Mendling</surname> <given-names>J.</given-names></name> <name><surname>Reijers</surname> <given-names>H. A.</given-names></name></person-group> (<year>2013</year>). <source>Fundamentals of Business Process Management</source>. <publisher-name>Springer</publisher-name>. <pub-id pub-id-type="doi">10.1007/978-3-642-33143-5</pub-id></citation>
</ref>
<ref id="B13">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>El-Ansary</surname> <given-names>A.</given-names></name></person-group> (<year>2002</year>). <article-title>Behavioral pattern analysis: towards a new representation of systems requirements based on actions and events,</article-title> in <source>SAC &#x00027;02: Proceedings of the 2002 ACM Symposium on Applied Computing</source> (<publisher-loc>New York, NY</publisher-loc>), p. <fpage>984</fpage>&#x02013;<lpage>991</lpage>. <pub-id pub-id-type="doi">10.1145/508791.508983</pub-id></citation>
</ref>
<ref id="B14">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Harpe</surname> <given-names>S.</given-names></name></person-group> (<year>2015</year>). <article-title>How to analyze Likert and other rating scale data</article-title>. <source>Curr. Pharm. Teach. Learn.</source> <volume>7</volume>, <fpage>836</fpage>&#x02013;<lpage>850</lpage>. <pub-id pub-id-type="doi">10.1016/j.cptl.2015.08.001</pub-id></citation>
</ref>
<ref id="B15">
<citation citation-type="web"><person-group person-group-type="author"><name><surname>Hey</surname> <given-names>J.</given-names></name></person-group> (<year>2004</year>). <source>The Data, Information, Knowledge, Wisdom Chain: The Metaphorical Link</source>. Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.jonohey.com/files/DIKW-chain-Hey-2004.pdf">https://www.jonohey.com/files/DIKW-chain-Hey-2004.pdf</ext-link> (accessed September 11, 2021).</citation>
</ref>
<ref id="B16">
<citation citation-type="book"><person-group person-group-type="editor"><name><surname>Ikram</surname> <given-names>M. A.</given-names></name> <name><surname>Alshehri</surname> <given-names>M. D.</given-names></name> <name><surname>Hussain</surname> <given-names>F. K.</given-names></name></person-group> editors. (<year>2015</year>). <article-title>Architecture of an IoT-based system for football supervision (IoT Football),</article-title> in <source>2015 IEEE 2nd World Forum on Internet of Things (WF-IoT)</source> (<publisher-loc>Milan</publisher-loc>: <publisher-name>IEEE</publisher-name>). <pub-id pub-id-type="doi">10.1109/WF-IoT.2015.7389029</pub-id></citation>
</ref>
<ref id="B17">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Kahn</surname> <given-names>B.</given-names></name> <name><surname>Strong</surname> <given-names>D.</given-names></name> <name><surname>Wang</surname> <given-names>R.</given-names></name></person-group> (<year>2002</year>). <article-title>Information quality benchmarks: product and service performance</article-title>. <source>Commun. ACM</source> <volume>45</volume>, <fpage>184</fpage>&#x02013;<lpage>192</lpage>. <pub-id pub-id-type="doi">10.1145/505248.506007</pub-id></citation>
</ref>
<ref id="B18">
<citation citation-type="web"><person-group person-group-type="author"><name><surname>Lacome</surname> <given-names>M.</given-names></name></person-group> (<year>2020</year>). <article-title>LEAN science &#x02013; When Innovation concepts help practitioners to get closer <italic>to the Graal?</italic></article-title> Available online at: <ext-link ext-link-type="uri" xlink:href="http://mathlacome.com/leansportssci/">http://mathlacome.com/leansportssci/</ext-link> (accessed May 12, 2021).</citation>
</ref>
<ref id="B19">
<citation citation-type="web"><person-group person-group-type="author"><name><surname>Laubheimer</surname> <given-names>P.</given-names></name></person-group> (<year>2018</year>). <source>Beyond the NPS: Measuring Perceived Usability with the SUS, NASA-TLX, and the Single Ease Question After Tasks and Usability Tests</source>. Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/measuring-perceived-usability/">https://www.nngroup.com/articles/measuring-perceived-usability/</ext-link> (accessed January 2, 2021).</citation>
</ref>
<ref id="B20">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Lee</surname> <given-names>Y.</given-names></name> <name><surname>Strong</surname> <given-names>D.</given-names></name> <name><surname>Kahn</surname> <given-names>B.</given-names></name> <name><surname>Wang</surname> <given-names>R.</given-names></name></person-group> (<year>2002</year>). <article-title>AIMQ: a methodology for information quality assessment</article-title>. <source>Inform. Manag</source>. <volume>40</volume>, <fpage>133</fpage>&#x02013;<lpage>146</lpage>. <pub-id pub-id-type="doi">10.1016/S0378-7206(02)00043-5</pub-id></citation>
</ref>
<ref id="B21">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Lewis</surname> <given-names>J. R.</given-names></name></person-group> (<year>2018</year>). <article-title>The system usability scale: past, present, and future</article-title>. <source>Int. J. Hum. Comput. Interact</source>. <volume>34</volume>, <fpage>577</fpage>&#x02013;<lpage>590</lpage>. <pub-id pub-id-type="doi">10.1080/10447318.2018.1455307</pub-id></citation>
</ref>
<ref id="B22">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Mahatody</surname> <given-names>T.</given-names></name> <name><surname>Sagar</surname> <given-names>M.</given-names></name> <name><surname>Kolski</surname> <given-names>C.</given-names></name></person-group> (<year>2010</year>). <article-title>State of the art on the cognitive walkthrough method, its variants and evolutions</article-title>. <source>Int. J. Hum. Comput. Interact</source>. <volume>26</volume>, <fpage>741</fpage>&#x02013;<lpage>785</lpage>. <pub-id pub-id-type="doi">10.1080/10447311003781409</pub-id></citation>
</ref>
<ref id="B23">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Mircioiu</surname> <given-names>C.</given-names></name> <name><surname>Atkinson</surname> <given-names>J. A.</given-names></name></person-group> (<year>2017</year>). <article-title>Comparison of parametric and non-parametric methods applied to a likert scale</article-title>. <source>Pharmacy</source> <volume>5</volume>, <fpage>26</fpage>. <pub-id pub-id-type="doi">10.3390/pharmacy5020026</pub-id><pub-id pub-id-type="pmid">28970438</pub-id></citation></ref>
<ref id="B24">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Mirza</surname> <given-names>A.</given-names></name></person-group> (<year>2010</year>). <article-title>Failure and success factors of an information system development in a charitable organization</article-title>. <source>Glob. J. Manag. Business Res</source>. <volume>10</volume>, <fpage>79</fpage>&#x02013;<lpage>83</lpage>.</citation>
</ref>
<ref id="B25">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Mullane</surname> <given-names>S.</given-names></name> <name><surname>Chakravorti</surname> <given-names>N.</given-names></name> <name><surname>Conway</surname> <given-names>P.</given-names></name> <name><surname>West</surname> <given-names>A.</given-names></name></person-group> (<year>2011</year>). <article-title>Design and implementation of a user-centric swimming performance monitoring tool</article-title>. <source>Proc. Inst. Mech. Eng. Part P J. Sports Eng. Technol</source>. <volume>225</volume>, <fpage>213</fpage>&#x02013;<lpage>229</lpage>. <pub-id pub-id-type="doi">10.1177/1754337111405271</pub-id></citation>
</ref>
<ref id="B26">
<citation citation-type="web"><person-group person-group-type="author"><name><surname>Nielsen</surname> <given-names>J.</given-names></name></person-group> (<year>2000</year>). <source>Why You Only Need to Test with 5 Users: Nielsen Norman Group</source>. Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/">https://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/</ext-link> (accessed December 17, 2020).</citation>
</ref>
<ref id="B27">
<citation citation-type="web"><person-group person-group-type="author"><name><surname>Nielsen</surname> <given-names>J.</given-names></name></person-group> (<year>2012</year>). <source>Thinking Aloud: The &#x00023;1 Usability Tool</source>. Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.nngroup.com/articles/thinking-aloud-the-1-usability-tool/">https://www.nngroup.com/articles/thinking-aloud-the-1-usability-tool/</ext-link> (accessed December 17, 2020).</citation>
</ref>
<ref id="B28">
<citation citation-type="book"><person-group person-group-type="editor"><name><surname>Nielsen</surname> <given-names>J.</given-names></name> <name><surname>Landauer</surname> <given-names>T. K.</given-names></name></person-group> editors. (<year>1993</year>). <article-title>A mathematical model of the finding of usability problems,</article-title> in <source>Proceedings of ACM INTERCHI&#x00027;93 Conference</source> (<publisher-loc>Amsterdam</publisher-loc>). <pub-id pub-id-type="doi">10.1145/169059.169166</pub-id></citation>
</ref>
<ref id="B29">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Perin</surname> <given-names>C.</given-names></name> <name><surname>Vuillemot</surname> <given-names>R.</given-names></name> <name><surname>Stolper</surname> <given-names>C.</given-names></name> <name><surname>Stasko</surname> <given-names>J.</given-names></name> <name><surname>Wood</surname> <given-names>J.</given-names></name> <name><surname>Carpendale</surname> <given-names>S.</given-names></name></person-group> (<year>2018</year>). <article-title>State of the art of sports data visualization</article-title>. <source>Comput. Graphics Forum</source> <volume>37</volume>, <fpage>663</fpage>&#x02013;<lpage>686</lpage>. <pub-id pub-id-type="doi">10.1111/cgf.13447</pub-id></citation>
</ref>
<ref id="B30">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Pipino</surname> <given-names>L.</given-names></name> <name><surname>Lee</surname> <given-names>Y.</given-names></name> <name><surname>Wang</surname> <given-names>R.</given-names></name></person-group> (<year>2003</year>). <article-title>Data quality assessment</article-title>. <source>Commun. ACM</source> <volume>45</volume>, <fpage>211</fpage>&#x02013;<lpage>218</lpage>. <pub-id pub-id-type="doi">10.1145/505999.506010</pub-id></citation>
</ref>
<ref id="B31">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ranaweera</surname> <given-names>J.</given-names></name> <name><surname>Zanin</surname> <given-names>M.</given-names></name> <name><surname>Weaving</surname> <given-names>D.</given-names></name> <name><surname>Withanage</surname> <given-names>C.</given-names></name> <name><surname>Roe</surname> <given-names>G.</given-names></name></person-group> (<year>2021</year>). <article-title>Optimizing player management processes in sports: translating lessons from healthcare process improvements to sports</article-title>. <source>Int. J. Comput. Sci. Sport</source> <volume>20</volume>, <fpage>119</fpage>&#x02013;<lpage>146</lpage>. <pub-id pub-id-type="doi">10.2478/ijcss-2021-0008</pub-id></citation>
</ref>
<ref id="B32">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ranaweera</surname> <given-names>J. S.</given-names></name> <name><surname>Weaving</surname> <given-names>D.</given-names></name> <name><surname>Zanin</surname> <given-names>M.</given-names></name> <name><surname>Roe</surname> <given-names>G.</given-names></name></person-group> (<year>2022</year>). <article-title>Identifying the current state and improvement opportunities in the information flows necessary to manage professional athletes: a case study in rugby union</article-title>. <source>Front Sport Act Liv.</source> <pub-id pub-id-type="doi">10.3389/fspor.2022.882516</pub-id></citation>
</ref>
<ref id="B33">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Reijers</surname> <given-names>H.</given-names></name> <name><surname>Mansar</surname> <given-names>S.</given-names></name></person-group> (<year>2005</year>). <article-title>Best practices in business process redesign: AN overview and qualitative evaluation of successful redesign heuristics</article-title>. <source>Omega</source> <volume>33</volume>, <fpage>283</fpage>&#x02013;<lpage>306</lpage>. <pub-id pub-id-type="doi">10.1016/j.omega.2004.04.012</pub-id></citation>
</ref>
<ref id="B34">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Reis</surname> <given-names>E.</given-names></name></person-group> (<year>2011</year>). <source>The Lean Startup.</source> <publisher-loc>New York, NY</publisher-loc>: <publisher-name>Crown Business</publisher-name>. p. <fpage>27</fpage>.</citation>
</ref>
<ref id="B35">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Robertson</surname> <given-names>S.</given-names></name> <name><surname>Bartlett</surname> <given-names>J.</given-names></name> <name><surname>Gastin</surname> <given-names>P.</given-names></name></person-group> (<year>2016</year>). <article-title>Red, Amber or Green? Athlete monitoring in team sport: the need for decision support systems</article-title>. <source>Int. J. Sports Physiol. Perform</source>. <volume>12</volume>, <fpage>S273</fpage>&#x02013;<lpage>S279</lpage>. <pub-id pub-id-type="doi">10.1123/ijspp.2016-0541</pub-id><pub-id pub-id-type="pmid">27967289</pub-id></citation></ref>
<ref id="B36">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Rowley</surname> <given-names>J.</given-names></name></person-group> (<year>2007</year>). <article-title>The wisdom hierarchy: representations of the DIKW hierarchy</article-title>. <source>J. Inform. Sci</source>. <volume>33</volume>, <fpage>163</fpage>&#x02013;<lpage>180</lpage>. <pub-id pub-id-type="doi">10.1177/0165551506070706</pub-id></citation>
</ref>
<ref id="B37">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Sauro</surname> <given-names>J.</given-names></name></person-group> (<year>2011</year>). <source>A Practical Guide to the System Usability Scale: Background, Benchmarks and Best Practices: Measuring Usability LLC</source>. <publisher-name>CreateSpace Independent Publishing Platform</publisher-name>.</citation>
</ref>
<ref id="B38">
<citation citation-type="book"><person-group person-group-type="author"><name><surname>Sauro</surname> <given-names>J.</given-names></name> <name><surname>Lewis</surname> <given-names>J. R.</given-names></name></person-group> (<year>2016</year>). <source>Quantifying the User Experience: Practical Statistics for User Research</source>. <publisher-name>Morgan Kaufmann</publisher-name>. <pub-id pub-id-type="doi">10.1016/B978-0-12-802308-2.00002-3</pub-id></citation>
</ref>
<ref id="B39">
<citation citation-type="web"><person-group person-group-type="author"><name><surname>Scharmer</surname> <given-names>C. O.</given-names></name></person-group> (<year>1996</year>). <source>Knowledge Has to Do with Truth, Goodness, and Beauty. Conversation with Professor Ikujiro Nonaka in Tokyo, Japan</source>. Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.presencing.org/aboutus/theory-u/leadership-interview&#x00023;eight">https://www.presencing.org/aboutus/theory-u/leadership-interview&#x00023;eight</ext-link> (accessed April 30, 2020).</citation>
</ref>
<ref id="B40">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Schelling</surname> <given-names>X.</given-names></name> <name><surname>Robertson</surname> <given-names>S.</given-names></name></person-group> (<year>2020</year>). <article-title>A development framework for decision support systems in high-performance sport</article-title>. <source>Int. J. Comput. Sci. Sport</source> <volume>19</volume>, <fpage>1</fpage>&#x02013;<lpage>23</lpage>. <pub-id pub-id-type="doi">10.2478/ijcss-2020-0001</pub-id></citation>
</ref>
<ref id="B41">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Str&#x000F6;bel</surname> <given-names>T.</given-names></name> <name><surname>Stieler</surname> <given-names>M.</given-names></name> <name><surname>Stegmann</surname> <given-names>P.</given-names></name></person-group> (<year>2021</year>). <article-title>Guest editorial</article-title>. <source>Sport Business Manag. Int. Jo</source>. <volume>11</volume>, <fpage>1</fpage>&#x02013;<lpage>9</lpage>. <pub-id pub-id-type="doi">10.1108/SBM-03-2021-124</pub-id></citation>
</ref>
<ref id="B42">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Vincent</surname> <given-names>J.</given-names></name> <name><surname>Stergiou</surname> <given-names>P.</given-names></name> <name><surname>Katz</surname> <given-names>L.</given-names></name></person-group> (<year>2009</year>). <article-title>The role of databases in sport science: current practice and future potential</article-title>. <source>Int. J. Comput. Sci. Sport</source>. <volume>8</volume>, <fpage>50</fpage>&#x02013;<lpage>66</lpage>.<pub-id pub-id-type="pmid">31530614</pub-id></citation></ref>
<ref id="B43">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>West</surname> <given-names>S. W.</given-names></name> <name><surname>Williams</surname> <given-names>S.</given-names></name> <name><surname>Kemp</surname> <given-names>S. P. T.</given-names></name> <name><surname>Cross</surname> <given-names>M. J.</given-names></name> <name><surname>Stokes</surname> <given-names>K. A.</given-names></name></person-group> (<year>2019</year>). <article-title>Athlete monitoring in rugby union: is heterogeneity in data capture holding us back?</article-title> <source>Sports</source> <volume>7</volume>, <fpage>98</fpage>. <pub-id pub-id-type="doi">10.3390/sports7050098</pub-id><pub-id pub-id-type="pmid">31035621</pub-id></citation></ref>
<ref id="B44">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Wharton</surname> <given-names>C.</given-names></name> <name><surname>Rieman</surname> <given-names>J.</given-names></name> <name><surname>Lewis</surname> <given-names>C.</given-names></name> <name><surname>Polson</surname> <given-names>P.</given-names></name></person-group> (<year>1994</year>). <article-title>The cognitive walkthrough method: a practitioner&#x00027;s guide</article-title>. <source>Usability Inspection Methods</source> <fpage>105</fpage>&#x02013;<lpage>40</lpage>.</citation>
</ref>
<ref id="B45">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Yuliawan</surname> <given-names>D.</given-names></name> <name><surname>Widyandana</surname> <given-names>D.</given-names></name> <name><surname>Nur Hidayah</surname> <given-names>R.</given-names></name></person-group> (<year>2020</year>). <article-title>Utilization of Nursing Education Progressive Web Application (NEPWA) media in an education and health promotion course using Gagne&#x00027;s model of instructional design on nursing students: quantitative research and development study</article-title>. <source>JMIR Nursing</source> <volume>3</volume>, <fpage>e19780</fpage>. <pub-id pub-id-type="doi">10.2196/19780</pub-id><pub-id pub-id-type="pmid">34345790</pub-id></citation></ref>
<ref id="B46">
<citation citation-type="journal"><person-group person-group-type="author"><name><surname>Zins</surname> <given-names>C.</given-names></name></person-group> (<year>2007</year>). <article-title>Conceptual approaches for defining data, information, and knowledge</article-title>. <source>JASIST</source> <volume>58</volume>, <fpage>479</fpage>&#x02013;<lpage>493</lpage>. <pub-id pub-id-type="doi">10.1002/asi.20508</pub-id></citation>
</ref>
</ref-list>
</back>
</article>