KSB 4.2 — Demonstrate effective technology leadership and change management skills for managing technology driven change and continuous improvement

Situation

At 100AND10% the development workflow had historically been shaped by the company’s focus on WordPress-based projects. Development practices were relatively informal, and as the organisation began exploring more complex digital systems such as the Client_2’s application, it became clear that stronger technical practices would be required to support larger software projects.

Task

My responsibility was to contribute to discussions about how the organisation could improve its development practices and adopt technologies that would support more scalable and maintainable systems. This required identifying areas where changes in tools, workflows, and system architecture could improve the organisation’s technical capability.

Action

One example of this was my proposal to adopt GitHub Pro as the organisation’s primary version control platform. I analysed the risks associated with informal code management and presented a structured workflow based on branching strategies, pull requests, and CI/CD integration. This change would allow the team to collaborate more effectively and safely manage code changes.

In parallel, during discussions around the Client_2’s application, I recommended building the system as a standalone Laravel application rather than a WordPress plugin. This architectural decision supported a shift toward more structured software development practices and enabled the organisation to pursue more advanced digital systems.

Result

These initiatives demonstrated how technology leadership can support organisational change by introducing more effective development practices and scalable technical architecture. By advocating for improvements to both development workflows and system design, I contributed to the organisation’s transition toward more professional software engineering practices and continuous technical improvement.