Objective
To establish a structured business analysis and documentation framework at Focus Edumatics for a legacy online tutoring platform, improving system clarity, scalability, and delivery efficiency while supporting ongoing high-volume operations.
Strategy
Adopt an iterative documentation and process standardisation approach to stabilise a monolithic, poorly documented system, ensuring alignment between business needs and technology delivery without disrupting live operations.
Implementation
-
Identified critical challenges stemming from an 8-year-old legacy platform built reactively on ad hoc requirements, resulting in fragmented workflows, inconsistent feature usage, and lack of documentation.
-
Analysed system usage and operational workflows to uncover duplicate features, low adoption areas, and reliance on manual workarounds such as CSV-based data handling.
-
Introduced structured process mapping (current and future state) to visualise workflows, identify inefficiencies, and define standardised operating procedures.
-
Established formal requirements documentation practices, including business requirements, functional specifications, and acceptance criteria for all new and enhanced features.
-
Embedded documentation into the development lifecycle, ensuring that every feature release included clearly defined requirements, test scenarios, and validation criteria.
-
Standardised testing practices by defining test scenarios and test cases, improving quality assurance and reducing defects in production.
-
Developed and published knowledge base articles, FAQs, and demo videos alongside release notes to improve user understanding and reduce dependency on informal communication channels.
-
Implemented telemetry tracking to monitor feature adoption and system usage, enabling data-driven decisions on feature effectiveness and prioritisation.
-
Continuously refined documentation and processes in parallel with ongoing system usage, ensuring minimal disruption to daily operations while progressively improving system structure.
| Aspect | Before | After |
|---|---|---|
| Documentation | None / ad hoc | Process maps, BRDs, acceptance criteria |
| Feature Usage | Multiple versions, low adoption | Aligned to needs, high adoption |
| Workarounds | Manual CSVs | Automated / integrated workflows |
| Testing | Informal | Structured test scenarios & cases |
| Knowledge Sharing | Tribal knowledge | FAQs, knowledge base, demo videos |
Outcome
-
Improved overall system clarity and maintainability, enabling more efficient onboarding of new features and enhancements.
-
Reduced duplication, inconsistencies, and reliance on manual workarounds, leading to more streamlined operations.
-
Increased feature adoption and usability by aligning solutions more closely with actual user needs and behaviours.
-
Enabled data-driven product and process decisions through telemetry insights and usage tracking.
-
Established a scalable foundation for ongoing system optimisation and structured delivery, supporting high-volume operations without compromising performance.