Overview

This lesson establishes the starting point for the course: a measured baseline of the learner's close performance. The video walks through the DIAGNOSE sheet in the Close Operating Model workbook, demonstrating how to enter a company profile, compare close cycle time against benchmarks, score five diagnostic dimensions, and read the resulting radar chart. This text provides the evidence base behind those benchmarks, the conceptual distinction between task management and process management, the Lean principle of data-driven diagnosis, and a formal introduction to the six Lean Six Sigma methodologies applied across the course.

Learning Objectives

After completing this lesson (video and text), the learner should be able to:

  • Interpret close cycle time benchmarks in context, understanding the survey methodologies and sample sizes behind the published numbers.

  • Explain the distinction between task management (checklist) and process management (operating model) using formal criteria.

  • Describe the Lean principle of data-driven diagnostic and why measurement precedes improvement.

  • Identify the five diagnostic dimensions used in the DIAGNOSE sheet and the operational concept each one assesses.

  • Name the six Lean Six Sigma methodologies applied across the course and state what each one addresses.

  • Complete the DIAGNOSE sheet self-assessment with their own organizational data.

Close Performance: The Evidence Base

The course opens with two data points: a median close cycle time of 6.4 days and a personal-life disruption rate of 81%. Each comes from a specific study with a defined methodology, and understanding the source strengthens the learner's ability to interpret and apply the benchmarks.

APQC's Open Standards Benchmarking survey is the largest cross-industry dataset on close performance. The General Accounting survey, which has collected responses from over 2,300 organizations, defines close cycle time as the number of calendar days between running the trial balance and completing the consolidated financial statements. This definition includes both active working time and elapsed waiting time. At the median, organizations take 6.4 calendar days. Top quartile performers (the fastest 25%) complete the close in 4.8 days or fewer. Bottom quartile organizations require 10 or more calendar days (Wiggins, 2018). The APQC data is cross-industry and cross-size, which means any individual organization's benchmark should be adjusted for complexity factors such as entity count, regulatory environment, and accounting complexity. The DIAGNOSE sheet in the workbook performs this adjustment automatically.

Ledge's 2025 month-end close benchmarks report surveyed 100 finance professionals across SaaS, healthcare, and manufacturing. The findings reinforced the APQC picture: 50% of finance teams take six or more business days to close, and only 18% achieve a three-day close or faster. The study also identified the most commonly cited barriers to faster closes: cross-team dependencies (56%), Excel-driven processes (50%), legacy systems (40%), and staffing or capacity gaps (37%). The same study found that 94% of respondents reported using Excel for close activities, and half cited it as a key reason their close runs slow (Ledge, 2025).

The FloQast/University of Georgia burnout study (2022) applied the Maslach Burnout Inventory (MBI) in an accounting setting for the first time. The MBI is the most widely used burnout measurement instrument in occupational psychology, validated by over 35 years of research. It measures burnout across three dimensions: emotional exhaustion (feeling drained by work demands), depersonalization (detachment or cynicism toward the job), and reduced personal accomplishment (feeling ineffective despite effort). Among the 204 accounting and finance professionals surveyed, 99% registered some level of burnout, with an average score of 47 on a 100-point scale. More directly relevant to close operations: 81% reported that the monthly close had disrupted their personal lives at least once in the past year, and 43% experienced that disruption in three or more months out of twelve. The study also found that burnout correlated with close quality: 85% of respondents had reopened the books in at least one month during the past year to fix errors (FloQast/UGA, 2022). The implication is direct — the close is not only a process efficiency problem but a workforce sustainability problem.

Task Management vs. Process Management

The video presents a four-row comparison between a "Close Checklist" and a "Close Operating Model." The distinction maps to a well-established concept in operations management: the difference between task management and process management.

Task management focuses on completion. It answers the question: what needs to get done? A task list, checklist, or project tracker enumerates activities, assigns owners, and tracks whether each activity has been completed. Task management is necessary — without it, work is forgotten or duplicated. But task management has structural limitations. It does not capture dependencies between tasks (which tasks must complete before others can begin). It does not distinguish between tasks that add value and tasks that consume time without producing a useful output. It does not identify root causes when tasks fail or run late. And it does not track whether the process improves over time.

Process management focuses on flow, dependencies, waste, and improvement. It answers a different set of questions: why does the work take as long as it does? Where is time lost? What causes recurring failures? Is the process getting better? Process management requires the same task visibility that a checklist provides, but adds layers of analysis: dependency mapping (which tasks are sequential and which can run in parallel), value classification (which tasks produce outputs that reviewers or regulators consume), waste identification (where time is spent on activities that do not contribute to the final deliverable), root cause analysis (why recurring problems persist despite awareness), and improvement tracking (whether changes produce measurable results).

The Close Operating Model built in this course is a process management tool. It contains a task list — the 127-task library in the TRACK sheet — but extends it with SIPOC mapping, Critical Path and Resource-Constrained Scheduling, waste decomposition, Fishbone and 5-Whys root cause analysis, and a PDCA improvement cycle. The distinction matters because organizations that manage tasks without managing the process tend to achieve consistent execution (the close finishes) without achieving improvement (the close does not get faster, more accurate, or less dependent on individual heroics). In practice, the transition from task management to process management is difficult because it requires the close lead to invest time in analysis during a period that already feels time-constrained. The diagnostic completed in this lesson is designed to minimize that investment: a five-minute self-assessment that identifies where to focus before any process redesign begins.

The Data-Driven Diagnostic

In Lean Six Sigma, the first step in any improvement effort is measurement. The principle is straightforward: before attempting to fix a process, quantify its current state. Without a baseline, there is no way to determine whether a change produced an improvement, a regression, or no effect at all.

The DIAGNOSE sheet implements this principle as a structured self-assessment. It captures two types of data:

Quantitative benchmarking. The learner enters five organizational characteristics (revenue range, entity count, team size, regulatory environment, accounting complexity) and their actual close cycle time in business days. The sheet compares the cycle time against a benchmark range adjusted for those characteristics. This adjusts for the fact that a single-entity private company and a 15-entity SEC registrant face very different close workloads. A raw comparison against the APQC global median (6.4 days) would be misleading for organizations at either extreme.

Qualitative diagnostic. The learner scores five dimensions on a 1-to-5 scale:

  • Timeline Control assesses whether the close schedule accounts for task dependencies and slack. A score of 1 indicates no documented schedule; a score of 5 indicates a dependency-mapped schedule with critical path visibility.

  • Prevention assesses whether problems are identified and addressed before close begins or only discovered during execution. Low scores indicate reactive firefighting; high scores indicate pre-close data validation and exception handling.

  • Quality Gates assesses whether the close includes defined checkpoints with pass/fail criteria. Without quality gates, the close proceeds on subjective judgment ("it looks right") rather than measurable thresholds.

  • Communication assesses whether close status is visible to stakeholders without requiring the close lead to be asked. High scores indicate systematic status reporting; low scores indicate that close status lives in one person's head.

  • Improvement assesses whether the close process changes based on data. A score of 1 indicates no improvement tracking; a score of 5 indicates a monthly PDCA cycle with tracked actions and measured outcomes.

The radar chart produced from these scores provides a shape, not just a total. Two organizations can score 13 out of 25 and have entirely different profiles: one may be strong on Communication and Timeline Control but weak on Improvement, while another may be strong on Prevention but weak on Quality Gates. The shape identifies the specific dimension where improvement effort will have the greatest impact. In Lean terminology, this is the constraint — the dimension that most limits overall close performance.

The Lean Six Sigma Toolkit: From Diagnosis to Improvement

The course applies six Lean Six Sigma methodologies, each addressing a different aspect of close operations. The video introduces them briefly through the AP accrual example and the methodology list. This section provides formal definitions and academic origins.

Benchmarking is the practice of comparing an organization's performance metrics against external reference points. In the context of this course, benchmarking compares close cycle time against APQC's cross-industry dataset and the learner's complexity-adjusted range. Benchmarking does not prescribe a target; it establishes where the organization stands relative to peers and identifies the gap between current and achievable performance (Camp, 1989).

SIPOC (Supplier, Input, Process, Output, Customer) is a process mapping tool used in the Define phase of the DMAIC improvement cycle. It documents the supply chain of each process step: who provides the input, what the input is, what the process does to it, what output it produces, and who consumes that output. In close operations, SIPOC makes visible the upstream dependencies that are otherwise implicit. A task that requires data from Procurement has a specific supplier, a specific input, and a specific customer. When that supply chain is documented, breakdowns become diagnosable rather than anecdotal. Lesson 3 applies SIPOC to the full task library.

Critical Path Method (CPM) is a scheduling algorithm that identifies the longest sequence of dependent tasks in a project. Tasks on the critical path have zero float: any delay in a critical-path task delays the entire project by an equal amount. Tasks not on the critical path have float — they can slip by a defined number of days without affecting the project deadline. CPM was developed independently by DuPont and the U.S. Navy in the late 1950s and has been a standard project management tool since. Applied to the close, CPM identifies which of the 127 tasks actually control the close deadline and which have slack. Lessons 4 and 5 implement CPM and Resource-Constrained Scheduling in the TRACK sheet.

DOWNTIME is an acronym for the eight categories of waste in Lean methodology: Defects, Overproduction, Waiting, Non-utilized talent, Transportation, Inventory, Motion, and Extra processing (Womack & Jones, 2003; the original Toyota Production System identified seven, with "Non-utilized talent" added later). In a close context, these categories are reinterpreted: "Transportation" becomes cross-functional handoffs, "Inventory" becomes data queued between process steps, "Waiting" becomes contention for shared resources, and "Defects" becomes journal entries requiring correction. The DOWNTIME framework provides specificity — instead of "we are wasting time," it identifies which type of waste is occurring, which determines the appropriate fix. Lesson 6 applies DOWNTIME to the learner's close.

Fishbone (Ishikawa) diagram and 5-Whys are root cause analysis tools. The Fishbone diagram, developed by Kaoru Ishikawa in the 1960s, organizes potential causes of a problem into categories (in this course: People & Ownership, Process & Sequence, Data & Systems, Upstream Dependencies, Standards & Documentation). The 5-Whys method, originating from Toyota's production system, asks "why" iteratively until the analysis reaches a systemic cause rather than a surface symptom. Applied to the close, these tools convert "the AP accrual was late again" into a structured investigation that identifies whether the root cause is an accountability gap, a process design flaw, a data or system configuration issue, an upstream dependency, or a missing standard. Lesson 7 implements both tools in the TRACK sheet.

PDCA (Plan-Do-Check-Act) is a continuous improvement cycle formalized by W. Edwards Deming (though Deming himself attributed the concept to Walter Shewhart). It structures improvement as a repeating loop: plan a change, implement it, measure the result, and decide whether to standardize it or try something different. In this course, PDCA operates on a monthly cadence tied to the close cycle. Each month, the learner identifies one improvement action, implements it, measures its impact on the KPI dashboard, and decides whether to keep it. Lesson 9 implements PDCA in the TRACK sheet's improvement plan.

These six methodologies are not independent tools applied in isolation. They form a connected diagnostic-to-improvement sequence: benchmarking establishes the gap, SIPOC maps the process, CPM identifies the critical path, DOWNTIME quantifies waste, Fishbone and 5-Whys diagnose root causes, and PDCA drives iterative improvement. The workbook is the container that holds this sequence. The methodology is the thinking that makes it work.

The Workbook and the Exercise

The Close Operating Model workbook contains five tabs (START, DIAGNOSE, BENCHMARK, TRACK, NEXT). The video provides a complete walkthrough of the DIAGNOSE sheet, including the company profile inputs, benchmark comparison, diagnostic dimensions, radar chart, and case studies. Detailed exercise instructions are available in the video and in the workbook's START tab.

The exercise for this lesson is to complete the DIAGNOSE sheet with the learner's own organizational data: company profile, close cycle time, and five diagnostic dimension scores. The output is a benchmarked self-assessment with a radar chart showing the learner's close health profile and their weakest dimension identified.

Summary

The monthly close is both a process efficiency problem and a workforce sustainability problem, as evidenced by cross-industry benchmarking data (APQC, Ledge) and burnout research (FloQast/UGA). The distinction between task management and process management clarifies why checklists, while necessary, cannot drive improvement: they lack the structural layers required to analyze dependencies, classify work by value, identify waste, diagnose root causes, and track change. The data-driven diagnostic completed in this lesson establishes a measured baseline — the Lean prerequisite for any improvement effort. The six Lean Six Sigma methodologies introduced here (Benchmarking, SIPOC, CPM, DOWNTIME, Fishbone/5-Whys, PDCA) form the connected sequence that the remaining nine lessons implement.

References

  • APQC. (2018). Cycle time to perform the monthly close. APQC Open Standards Benchmarking, General Accounting Survey (n = 2,300 organizations). Referenced in Wiggins, P. D. (2018, March). Metric of the month: Cycle time for monthly close. CFO.com.

  • Camp, R. C. (1989). Benchmarking: The search for industry best practices that lead to superior performance. ASQC Quality Press.

  • FloQast & University of Georgia. (2022). Controller's guidebook: Burnout in accounting — Understanding the problem, leveraging solutions. Study conducted March 2022; n = 204 accounting and finance professionals. Used the Maslach Burnout Inventory (MBI), validated by 35+ years of research.

  • Ishikawa, K. (1985). What is total quality control? The Japanese way. Prentice Hall.

  • Ledge. (2025, April). The state of month-end close in 2025: Finance team benchmarks and insights. Ledge Research (n = 100 finance professionals). https://www.ledge.co/content/month-end-close-benchmarks-for-2025

  • Madhani, P. M. (2021). Lean Six Sigma in finance and accounting services for enhancing business performance. International Journal of Service Science, Management, Engineering, and Technology, 12(6), 141–165.

  • Weygandt, J. J., Kimmel, P. D., & Kieso, D. E. (2018). Financial accounting (10th ed.). Wiley.

  • Womack, J. P., & Jones, D. T. (2003). Lean thinking: Banish waste and create wealth in your corporation (2nd ed.). Simon & Schuster.