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, 7