In public-sector grants administration, speed must never compromise fairness, transparency, compliance, or stewardship of public funds. However, a controlled process does not need to be a slow process.
Value Stream Mapping (VSM) makes the complete flow visible: how applications, evidence, decisions, approvals, information, and agreements move from one stage to the next. It distinguishes customer value from necessary control activity, delay, duplication, and rework.
For this worked example, the customer outcome is not simply “an application assessed.” It is an eligible, fairly assessed applicant receiving a timely funding decision and executed agreement. That definition brings the applicant, funding body, assessors, delegates, and community outcomes into the same improvement conversation.
This approach aligns with established VSM guidance from the National Institute of Standards and Technology and public-sector improvement guidance from Lean Enterprise Institute.
1. Select the Scope: Applications Close to Executed Agreement
The scope begins at applications close and ends when the funding agreement is executed and the outcome notification is ready for release.
This boundary is deliberately specific:
- Start: the program round closes and the final application enters the processing queue.
- End: the successful applicant has an executed funding agreement and the formal outcome notification can be issued.
- Excluded: program policy design, applicant acquisition before applications close, payment processing, and post-award monitoring.
Why choose this start and end point? The service standard applies to the period from close to agreement. It also captures the largest concentration of delay: eligibility checking, merit assessment, panel moderation, approval, and agreement preparation.
The mapping team should include the grants manager, assessors, panel secretariat, compliance, legal or contracts, finance, information technology, applicant support, and the approval delegate. The team must map how work actually flows, not how the procedure manual says it should flow.
A well-defined Lean Six Sigma project scope prevents the workshop from becoming a general discussion about government administration.
2. Current-State Map: Where the 138 Days Go
The current-state flow is:
Applications close → eligibility and compliance screening → merit assessment → panel scheduling and moderation → funding decision and approval → agreement preparation and execution → outcome notification
The baseline contains 2,400 applications in one program round.
| Current-state measure | Baseline |
|---|---|
| End-to-end time to executed agreement | 138 days |
| Published service standard | 90 days |
| Eligibility and compliance elapsed time | 11.4 days |
| Hands-on screening effort | 3.1 hours per application |
| Panel scheduling and moderation | 19 days |
| Applications requiring two panel rounds | 46%, or approximately 1,104 applications |
| Applications returned for missing or inconsistent evidence | 34%, or approximately 816 applications |
| Average delay from evidence returns | 21 days |
| Total administrative effort | 6.4 hours per application, or 15,360 hours per round |
| Genuinely value-adding merit assessment | 47 minutes per application, or approximately 1,880 hours per round |
| Assessors’ time spent on eligibility/compliance | 62% |
| Duplicate evidence-reviewed findings | 18% |
| Approval sign-off publication delay | 12 days |
| Applicants contacting the team at least twice for status | 29%, or approximately 696 applicants |
| Process cycle efficiency | Approximately 1.5% |
The 138-day result is 48 days beyond the published standard. Although 6.4 hours of administrative effort are applied to each application, only 47 minutes represent direct merit evaluation. The remainder is largely consumed by screening, evidence handling, coordination, correction, movement between systems, and waiting.
The fundamental purpose of the Analyse Phase in DMAIC is to identify and validate root causes rather than assume that the slowest step is the only problem. In this case, the data indicates a system of causes: weak entry quality, repeated compliance work, batch scheduling, approval queues, and poor visibility for applicants.
3. The Eight DOWNTIME Wastes in the Current State
The eight DOWNTIME categories provide a practical diagnostic lens. Each waste must be quantified where possible and then connected to a process cause.
| Waste | Evidence in this grants stream | Quantified impact |
|---|---|---|
| Defects | Incomplete submissions, inconsistent evidence, and assessment corrections | 816 applications returned; 34% of the round; 21 days average added delay |
| Overproduction | Assessing applications before evidence is reliable and re-reviewing evidence already verified | 62% of assessor time is diverted to eligibility/compliance rather than merit |
| Waiting | Panel availability, approval sign-off, and applicant response turnarounds | 19 days for panel scheduling; 12 days publication lag; 21 days for returned evidence |
| Non-utilised talent | Subject matter experts perform repetitive compliance checks instead of applying specialist judgement | 62% of assessment time used for eligibility/compliance activity |
| Transportation | Applications and evidence move between the grants platform, email, shared drives, assessment files, and approval records | Four systems are used to find and transfer information |
| Inventory | Unassessed applications accumulate in the queue before review, moderation, or approval | 2,400 applications enter the round; 1,104 require two panel rounds |
| Motion | Assessors switch between systems and folders to locate evidence, criteria, and previous findings | Four-system searching is repeated across thousands of application reviews |
| Excess processing | Two reviewers duplicate evidence findings and staff manually answer status requests | 18% duplicate findings; at least 1,392 status contacts from 696 applicants contacting the team twice |
The waste categories overlap. For example, an evidence defect creates rework, which creates waiting, increases inventory, and generates additional status enquiries. That is why VSM looks at the whole value stream, not isolated departmental efficiency.
The Voice of the Customer is timely, transparent treatment and a clear decision. The Voice of the Business is sound stewardship, consistent governance, and funding aligned to policy objectives. The Voice of the Process is visible in the data: a 1.5% process cycle efficiency and a 48-day service-standard gap.
4. Future-State Build: Faster Flow with Stronger Control
The future state should not remove mandatory controls. It should move controls earlier, standardise their execution, and eliminate repeated handling.
Kaizen Burst 1: Validate at the Point of Entry
Create a submission validation gate with:
- Real-time required-field and evidence checks
- Plain-language prompts for inconsistent information
- An applicant-facing completion checklist
- A clear audit trail showing what was validated and when
This prevents avoidable defects from entering the assessment queue. It also reduces the need for assessors to become document detectives.
Kaizen Burst 2: Route by Complexity and Risk
Introduce a triage matrix based on application complexity, risk, funding value, and evidence requirements:
- Low-complexity applications: one trained assessor
- High-complexity or high-risk applications: two-assessor review and panel pathway
- Clearly ineligible applications: controlled disposition without unnecessary merit assessment
This applies the Theory of Constraints by reducing demand on the constrained assessment and panel capacity. It also uses risk-based governance rather than applying the same processing intensity to every application.
Kaizen Burst 3: Make Merit Assessment the Primary Work
Use a standardised merit rubric with embedded evidence references. Reviewers should record:
- The criterion being assessed
- The evidence supporting the score
- The score and rationale
- Any material risk or clarification required
This shifts the assessor’s role from repeated compliance investigation to consistent merit evaluation. It also reduces variation between reviewers and makes panel moderation more focused.
Kaizen Burst 4: Create Predictable Panel and Approval Flow
Replace ad hoc panel scheduling with fixed fortnightly panel windows. Applications ready by a defined cut-off move into the next available session.
Approval should retain the required formal checkpoint, but use a complete decision pack, standard delegation pathway, and visible due date. Approval is essential governance; uncontrolled approval queues are a bottleneck.
Outcome letters should be templated and scheduled for release on a fixed publication date. A self-service status portal should show an application’s current stage, expected next milestone, and any applicant action required.
5. Current State Versus Future State
| Measure | Current state | Future state |
|---|---|---|
| Close to executed funding agreement | 138 days | 74 days |
| Applications returned for evidence | 34% | 9% |
| Assessor time on eligibility/compliance | 62% | 24% |
| Administrative effort per application | 6.4 hours | 3.1 hours |
| Duplicate reviewer findings | 18% | 3% |
| Panel rounds per application | 2.0 | 1.4 |
| Outcome publication lag | 12 days | 3 days |
| Status enquiries per applicant | 2.0 | 0.5 |
| Process cycle efficiency | 1.5% | 5.2% |
At 3.3 fewer administrative hours per application, the future state releases approximately 7,920 hours per 2,400-application round. That capacity can support additional funding rounds, stronger applicant guidance, better risk analysis, or more meaningful evaluation of community outcomes.
The benefit is not merely a shorter internal process. It is grant funding reaching recipients sooner, while assessors spend more time applying expertise where it matters.
6. 30/60/90-Day Kaizen Sequence
| Timing | Kaizen actions | Accountable owners |
|---|---|---|
| Days 1–30 | Establish the application data baseline; create an eligibility-failure Pareto; confirm operational definitions; design the submission checklist; validate the current-state map | Grants manager, data analyst, compliance lead |
| Days 31–60 | Build the validation gate; pilot the triage matrix; configure the standard merit rubric; define evidence-reference rules; train assessors and panel secretariat | Product owner, assessment lead, compliance lead, learning lead |
| Days 61–90 | Launch fixed panel windows; automate conflict-of-interest and eligibility screening; deploy outcome templates; implement the self-service portal; introduce control charts for screening cycle time and return rate | IT owner, panel chair, contracts lead, service owner |
Control should include weekly review of:
- Screening cycle time
- Evidence return rate
- Applications waiting for panel
- Duplicate findings
- Approval queue age
- Agreement execution time
- Applicant status enquiries
If screening cycle time or return rate moves outside agreed limits, the team should investigate special-cause variation before adding more controls or staff.
7. Build the Capability to Improve the Stream
A grants value stream is a strong Lean Six Sigma project because it combines customer requirements, process data, governance, risk, and cross-functional flow. A Yellow Belt can support data collection and kaizen activity. A Green Belt can analyse variation, validate causes, and lead improvement work. A Black Belt can lead the end-to-end project, mentor Green Belts, and align the future state with enterprise priorities.
For structured, practical development, explore Lean Six Sigma online training, the Green Belt course, or the Black Belt course. The courses are designed around practical application, case studies, data, charts, and worked examples, with accreditation by the Council for Six Sigma Certification.
Start your CSSC-accredited lean six sigma training today and build the capability to map, analyse, and improve the value streams that determine public-sector outcomes.
Kaizen. Kai-Care. Kai-Done. Lean Six Sigma.
