Please enable JavaScript.

Coggle requires JavaScript to display documents.

Chapter 24 - Coggle Diagram

- - - - Knowledge Gaps: The audience may not understand the mathematical foundation of the data, requiring the presenter to explain necessary concepts like standard deviation without turning the meeting into a full-scale statistics lesson
        
        Technical Derailment: Presentations can be sidetracked by statistical questions from knowledgeable sponsors or by confusing non-experts with too many complex examples
        
        Credibility Balance: Despite these challenges, statistics must be included because they provide the credibility needed to support conclusions and process changes
- - - - Process Owners/Staff: Provide more granular details about specific workflow changes and how they impact daily tasks
        
        Specialized Departments: Be prepared to answer department-specific questions:
        
        Compliance: Focus on adherence to regulations and risk mitigation
        
        Finance: Provide results in dollar formats and discuss savings vs. costs
        
        Marketing/Sales: Highlight customer-centric data and the "Voice of the Customer"
- - - - Question Title: Use a concise question as the slide title (e.g., "Did software changes increase production?")
        
        Visual Answer: Include a graph (like a box plot or Pareto chart) that visually answers the question
        
        Basic Stats: Briefly list the test used and the p-value for reference
        
        Text Conclusion: Provide a clear, one-sentence answer to the title question
        
        Concise Formatting: Use active language, avoid long blocks of text, and ensure font sizes and colors are legible for a projected audience
        
        Effective Labeling: Edit graph titles and data labels so the image can tell a story on its own, even if removed from the context of the presentation
- - - - Integrity in Analysis: Never force an analysis to fit a desired conclusion, and never hide small sample sizes or conflicting test results
        
        Project Integrity: Decisions about data gathering, process mapping, or brainstorming should be driven by the needs of the project, not by what will "look good" in a final presentation
        
        Peer Review: Utilize a Master Black Belt to review analysis before finalized presentations to catch inadvertent errors or biases