Competencies
4177.1.2 : Proposes Integrating Technology
The learner proposes integrating new technology to solve a business need using research and data-supported storytelling.
Introduction
Organizations increasingly rely on data to evaluate and improve the efficiency of their operational processes. As business environments grow more complex, legacy workflows can limit scalability, introduce errors, and delay decision-making. Data storytelling enables leaders to translate operational data into insights that support informed technology and process decisions.
In this task, you will assume the role of a digital-transformation consultant responsible for analyzing workflow-efficiency data in an enterprise organization (Mercurion Supply Co.). You will complete a data analysis, develop a stakeholder presentation using data storytelling, and provide an executive summary that integrates your key insights from the data and a recommended technology-enabled solution.
Scenario
Refer to the attached "Data Storytelling Scenario" and the attached "Mercurion Workflow Data" spreadsheet.
Requirements
Your submission must represent your original work and understanding of the course material. Most performance assessment submissions are automatically scanned through the WGU similarity checker. Students are strongly encouraged to wait for the similarity report to generate after uploading their work and then review it to ensure Academic Authenticity guidelines are met before submitting the file for evaluation. See Understanding Similarity Reports for more information.
Grammarly Note:
Professional Communication will be automatically assessed through Grammarly for Education in most performance assessments before a student submits work for evaluation. Students are strongly encouraged to review the Grammarly for Education feedback prior to submitting work for evaluation, as the overall submission will not pass without this aspect passing. See Use Grammarly for Education Effectively for more information.
Microsoft Files Note:
Write your paper in Microsoft Word (.doc or .docx) unless another Microsoft product, or pdf, is specified in the task directions. Tasks may not be submitted as cloud links, such as links to Google Docs, Google Slides, OneDrive, etc. All supporting documentation, such as screenshots and proof of experience, should be collected in a pdf file and submitted separately from the main file. For more information, please see Computer System and Technology Requirements.
Note: Length guidelines are provided to help you gauge appropriate depth. Submissions are evaluated on quality and alignment to requirements, not exact page count.
Part I: Data Analysis
Note: Part I should be submitted as a separate Word document from Parts II and III.
The Data Analysis document should be approximately 1–2 pages in length (double-spaced equivalent), excluding references.
A. Analyze the data in the attached "Data Storytelling Scenario" and do the following:
1. Explain the cause of the decline in organizational performance, including support from the scenario.
2. Predict two operational trends that are likely to occur in the future if the current workflows remain unchanged, based on the Workflow Context and Performance Indicators data sections.
3. Identify a technology-enabled course of action to improve workflow performance.
Part II: Storytelling Presentation
Note: Part II should be submitted as a separate multimedia presentation (e.g., Microsoft PowerPoint, Apple Keynote) from Parts I and III.
The multimedia presentation should include approximately 8–12 content slides (excluding title and reference slides).
B. Create a multimedia storytelling presentation that communicates a compelling narrative and explains the operational problem and proposed solution to stakeholders. Your presentation should do the following:
1. Introduce the operational situation facing the organization as it relates to workflow performance.
2. Describe the cause of the decline in workflow performance in a way that clearly communicates to stakeholders the need for action.
a. Create a data visualization (e.g., bar chart, line graph, heat map, pie chart) that represents workflow-performance metrics from the scenario and enhances stakeholders' understanding of the workflow performance data.
3. Propose a technology-enabled solution, supported by data from the scenario, that addresses the cause of the decline described in part B2 and modernizes the organization's workflows.
a. Describe two operational key performance indicators (KPI) that stakeholders could use to measure whether the proposed solution is successful.
b. Create a conclusion that explains the five steps stakeholders should take to implement the proposed solution through technology adoption and process change.
Part III: Executive Summary
Note: Part III should be submitted as a separate Word document from Parts I and II.
The Executive Summary should be approximately 1 page in length (double-spaced equivalent).
C. Provide an executive summary of the presentation in part B by doing the following:
1. Explain the operational problem the organization is facing.
2. Explain why the current workflows are causing performance issues and why changes are needed.
3. Explain the proposed technology-enabled solution.
4. Explain the impact of the proposed solution on the organization.
D. Acknowledge sources, using in-text citations and references, for content that is quoted, paraphrased, or summarized.
Note: The task scenario provided and attached documents are considered part of the assessment materials and do not require citation. Only external sources that are quoted, paraphrased, or summarized must be cited.
If you quote, paraphrase, or summarize external sources in your submission, you must include appropriate in-text citations and a reference list. If no external sources are used, citations and references are not evaluated.
E. Demonstrate professional communication in the content and presentation of your submission.
File Restrictions
File name may contain only letters, numbers, spaces, and these symbols: ! - _ . * ' ( ) File size limit: 200 MB File types allowed: doc, docx, rtf, xls, xlsx, ppt, pptx, odt, pdf, csv, txt, qt, mov, mpg, avi, mp3, wav, mp4, wma, flv, asf, mpeg, wmv, m4v, svg, tif, tiff, jpeg, jpg, gif, png, zip, rar, tar, 7z
Rubric
A1:DECLINE IN PERFORMANCE
Not Evident An explanation of the cause of the decline in performance is not provided. | Approaching Competence The explanation of the cause of the decline in performance is not supported by scenario data or is not clearly connected to organizational performance. | Competent The explanation of the cause of the decline in performance is supported by scenario data and clearly connected to organizational performance. |
A2:PREDICTION OF TRENDS
Not Evident A prediction of operational trends is not provided. | Approaching Competence The prediction includes fewer than 2 operational trends or includes trends that are not likely if the current workflows remain unchanged based on the data. | Competent The prediction includes 2 operational trends that are likely if the current workflows remain unchanged based on the data. |
A3:COURSE OF ACTION
Not Evident A course of action to improve workflow performance is not provided. | Approaching Competence The course of action is not technology enabled or is not appropriate for improving workflow performance. | Competent The course of action is technology enabled and appropriate for improving workflow performance. |
B1:INTRODUCTION OF OPERATIONAL SITUATION
Not Evident An introduction to the operational situation is not provided. | Approaching Competence The introduction does not clearly relate the operational situation to workflow performance or is unclear to stakeholders. | Competent The introduction clearly relates the operational situation to workflow performance and is understandable for stakeholders. |
B2:CAUSE OF WORKFLOW PERFORMANCE DECLINE
Not Evident A description of the cause of the workflow performance decline is not provided. | Approaching Competence The description of the cause of the workflow performance decline is unclear or does not communicate the need for action to stakeholders. | Competent The description of the cause clearly communicates the need for action to stakeholders. |
B2A:DATA VISUALIZATION
Not Evident A data visualization is not provided. | Approaching Competence The data visualization does not represent workflow-performance metrics from the scenario or does not enhance stakeholder understanding. | Competent The data visualization represents workflow-performance metrics from the scenario and enhances stakeholder understanding. |
B3:PROPOSED SOLUTION
Not Evident A proposed solution is not provided. | Approaching Competence The proposed solution is not technology enabled, is not supported by scenario data, or does not address the identified cause. | Competent The proposed solution is technology enabled, is supported by scenario data, and addresses the identified cause. |
B3A:KPI DESCRIPTION
Not Evident A description of operational KPIs is not provided. | Approaching Competence The description includes fewer than 2 operational KPIs or includes KPIs that are not appropriate for measuring the proposed solution's success. | Competent The description includes 2 operational KPIs that are appropriate for measuring the proposed solution's success. |
B3B:CONCLUSION
Not Evident A conclusion describing steps to implement the solution is not provided. | Approaching Competence The conclusion includes fewer than 5 steps or includes steps that do not support technology adoption or process change. | Competent The conclusion includes 5 steps that support technology adoption and process change. |
C1:EXECUTIVE SUMMARY: PROBLEM
Not Evident An explanation of the operational problem is not provided. | Approaching Competence The explanation does not clearly identify the operational problem or is not aligned with the presentation. | Competent The explanation clearly identifies the operational problem and is aligned with the presentation. The submission logically explains the operational situation facing the organization in the executive summary. |
C2:EXECUTIVE SUMMARY: CAUSE
Not Evident An explanation of the current workflow issues is not provided. | Approaching Competence The explanation does not clearly link workflow issues to performance problems or does not justify the need for change. | Competent The explanation clearly links workflow issues to performance problems and justifies the need for change. |
C3:EXECUTIVE SUMMARY: SOLUTION
Not Evident An explanation of the proposed technology-enabled solution is not provided. | Approaching Competence The explanation of the proposed technology-enabled solution is unclear or not aligned with the presentation. | Competent The explanation of the proposed technology-enabled solution is clear and aligned with the presentation. |
C4:EXECUTIVE SUMMARY: IMPACT OF SOLUTION
Not Evident An explanation of the impact of the proposed solution is not provided. | Approaching Competence The explanation does not clearly describe the impact or does not align with the proposed solution. | Competent The explanation clearly describes the impact of the proposed solution and aligns with the scenario. |
D:SOURCES
Not Evident The submission does not include both in-text citations and a reference list for sources that are quoted, paraphrased, or summarized. | Approaching Competence The submission includes in-text citations for sources that are quoted, paraphrased, or summarized and a reference list; however, the citations or reference list is incomplete or inaccurate. | Competent The submission includes in-text citations for sources that are properly quoted, paraphrased, or summarized and a reference list that accurately identifies the author, date, title, and source location as available. |
E:PROFESSIONAL COMMUNICATION
Not Evident This submission includes pervasive errors in professional communication related to grammar, sentence fluency, contextual spelling, or punctuation, negatively impacting the professional quality and clarity of the writing. Specific errors have been identified by Grammarly for Education under the Correctness category. | Approaching Competence This submission includes substantial errors in professional communication related to grammar, sentence fluency, contextual spelling, and/or punctuation. Specific errors have been identified by Grammarly for Education under the Correctness category. | Competent This submission includes satisfactory use of grammar, sentence fluency, contextual spelling, and punctuation, which promote accurate interpretation and understanding. |