Exploratory testing is a supplementary software testing approach that complements other testing methods, including functional, regression, and performance, by exploring an application's functionality without predefined test scripts, allowing testers to leverage their creativity and intuition to uncover issues. This paper reports the results and insights derived from scenario-based exploratory testing performed on the KSECI, an online knowledge-sharing application. From the twelve features of the KSECI application, 88 scenarios were derived, simulating diverse user interactions and scenarios. The test results revealed that 48 test scenarios were passed, whilst 40 failed. Among the 40 issues identified, 26 were functionality issues (mostly rated as low severity), and 14 issues were associated with usability and interface design flaws. Given our limited resources, time constraints, and lack of profound product knowledge, we found scenario-based exploratory testing is effective, as it eliminates the necessity for detailed test scripts, enabling testers to focus on testing rather than documentation. This strategy is recommended in resource-limited environments, balancing structured testing with adaptive exploration to identify critical, user-impacting problems. The findings highlight the significance of exploratory testing in projects that requiring flexibility, offering a practical framework where traditional scripted methods may be impractical or time intensive.