Portfolio Project 2 · Process Improvement · Business Analyst Demo

Business Process Improvement Tracker

Closed-loop BA workflow for CoAct operational process improvements: capture scattered pain points, prioritise by business value, manage stage gates, compare As-Is and To-Be workflows, and validate benefits after implementation.

Role

Business Analyst / Process Improvement Designer

Scope

15+ core operational processes

Methods

Stakeholders, BRD, process maps, UAT, PIR

Core processes

15+

BA stages

6

Validated saving

286

hrs / month from IMP-204

Toolkit

6

templates embedded

Case Study Readout

From scattered improvement ideas to governed delivery

The portfolio narrative is structured around one BA question: how do operations teams turn informal pain points into prioritised, documented, measured improvements?

6-8 week simulated delivery

Problem

Improvement requests were split across email, meetings and Slack, with limited visibility of ownership, priority or realised value.

Approach

Define a stage-gate BA workflow, standardise deliverables and connect process maps, approvals, UAT and benefits tracking.

Outcome

A closed-loop tracker that shows what is in progress, what changed, what value was delivered and what can be reused.

My BA Contribution

What this portfolio piece demonstrates

Stakeholder analysis

Needs mapped to system capabilities.

Requirements definition

BRD, rules and acceptance criteria.

Process analysis

As-Is, To-Be and change impact.

Benefits realisation

Before/after metrics and PIR loop.

Current Operating View

Viewing: Year to Date / All departments / All owners

Stage-gate portfolio health, benefit validation and delivery risk.

Stage Distribution

Current BA stage-gate load across the filtered portfolio.

FR-01

Benefits Target vs Actual

Compares expected and validated monthly hours saved.

FR-06

Pipeline Aging

Average days in stage, with a 30-day review threshold.

Gate risk

Priority / Effort Matrix

Intake scoring view for BA prioritisation decisions.

FR-10

Alert-to-Action Register

Executive Decision Log

Trigger	Decision	Owner	Status

Stakeholder Needs → System Capabilities

Shows the BA traceability from stakeholder concern to system design.

Stakeholder	Role	Concern	System Need	Engagement

BA Process Evidence

From scattered pain points to controlled operational change

This section explains the analysis path behind the demo: stakeholder needs, problem framing, stage-gate governance, process mapping, UAT readiness and benefit validation.

1 · Identify

Problem intake

Capture ideas from email, meetings and Slack into a single triage queue with a one-page problem statement.

2 · Analyse

Current state analysis

Interview stakeholders, confirm root cause, map As-Is handoffs and quantify operational delay.

3 · Design

To-Be solution design

Define business rules, exception handling, controls and acceptance criteria before implementation.

4 · Implement

UAT and rollout

Prepare test scenarios, confirm sign-off and document training or change-management needs.

5 · Review

Benefits realisation

Measure actual hours saved, capture lessons learned and identify reusable improvement patterns.

Traceability Thread

Stakeholder concern

Regional managers manually assign new client cases and miss CRM updates.

Requirement

System must support rules-based assignment using workload, expertise and location.

Design control

Assignment reason is logged and exception cases route to manual review.

Measured outcome

Average allocation time reduced from 4.2 hours to approximately 5 minutes.

BA Artefacts Produced

Methodology

BA governance model used in the demo

The demo combines stage-gate governance, impact-effort scoring, process analysis, controlled delivery and PIR-based benefit validation.

Framework Components

Stage-gate workflow

Each initiative must pass an explicit decision point before moving to the next delivery stage.

Impact / effort scoring

Requests are prioritised by business impact, frequency, compliance risk, staff pain, effort and data readiness.

Benefits realisation

Target savings and actual savings are tracked separately to avoid overstating projected value.

Portfolio Architecture

Data layer

Initiatives, requests, gates, benefits, documents

Workflow layer

Intake, stage movement, approval checks, timeline

Reporting layer

KPI summary, charts, risk register, benefit table

Evidence layer

BRD, process map, UAT, PIR, lessons learned

Improvement Intake Queue

Before initiatives enter delivery, BA team assesses value, effort, risk and sponsorship.

3 pending assessment

Assessment Model

Impact + urgency + risk - effort.

Improvement Delivery Board

Stage-gate delivery lifecycle: Identified → Analysing → Designing → Implementing → Completed → Reviewing.

Featured Initiative IMP-204

Client Case Allocation Automation

As-Is / To-Be mapping with removed manual steps, automation logic, business rules and exception handling.

Before

4.2h

avg allocation

After

5m

target cycle

Reduction

98%

time saved

Current State · As-Is

Manual / fragmented

Change Impact

Improvement Notes

Manual decision points are replaced with rule-based allocation. CRM becomes the single source of truth, while exception cases are escalated instead of silently failing.

Future State · To-Be

Automated / governed

Business Rules

Exception Handling

Before vs After by Initiative

Average process time reduction after improvement implementation.

Monthly Cumulative Hours Saved

Benefits realisation across completed and reviewed initiatives.

Benefits Validation Table

Initiative	Target Saving	Actual Saving	Benefit Status	Owner

ROI Calculator

Simulated cost-benefit calculation for BA initiatives.

Implementation hours Hourly cost ($) Monthly hours saved

BA Deliverables Library

Templates mapped to stage gates and case evidence

Each deliverable shows ownership, completion status, required inputs and example content generated from IMP-204.

6

Templates

5

Gate assets

MD

Export

Deliverable Catalogue

Select a document to preview its role in the BA workflow.

Business Requirements Document

Standard BRD format for process improvement initiatives.

Generated from IMP-204 Analyse / Design Ready

IMP-204 Benefits Validated

Post-Implementation Review Control Panel

The final loop: validate target vs actual, capture user feedback, assign follow-up actions and log reusable patterns.

Target vs Actual Validation

4-week data collected

Metric	Baseline	Target	Actual	Variance

Sign-off Evidence

User Feedback Themes

Follow-up Action Register

Lessons Learned

Reusable Improvement Pattern

The allocation-rule pattern can be reused wherever teams manually match people, cases, training seats or employers based on capacity, location and specialist capability.

3 candidate workflows

Portfolio takeaway

This project demonstrates stakeholder analysis, requirements definition, stage-gate governance, As-Is / To-Be process analysis, business rules design, UAT planning, benefit measurement and post-implementation review — not just a generic dashboard UI.