Each case follows the same shape: the challenge, my part in it, and what came out. Client details are sanitised, and no confidential documents, systems or data are shown.
Organisation building
Establishing AI Enterprise Solutions
1 of 7 founding members · 40+ hires supported
Problem & context
Scicom set up a new AI Enterprise Solutions department with a founding team of seven. It needed an operating foundation (hiring, administration, governance and a formal set-up) at the same time as its first projects began.
My role
One of the seven founding members. I took significant responsibility for governance, administration, hiring and departmental set-up.
Approach
Supported the hiring of 40+ people into the department
Handled administration and formal departmental set-up
Coordinated operational activity so delivery teams could focus on delivery
Helped establish the department's social media presence
Collaboration
The other founding members, department leadership, and the recruitment and support functions involved in building a new team.
Outcome
An operating foundation of people, structure and governance for the department's delivery work to build on.
User journeysThe steps a real person takes through the service, agreed before each step is built.
Functional requirements (FRS)What the system must do, written as numbered requirements that builders, testers and the client all sign off against.
System design visualsHow the parts of the solution fit together, drawn so technical and business reviewers can check the same picture.
Data governance requirementsRules for how data is owned, protected, kept and accessed, so the AI only uses what it is allowed to.
Illustrations only. No real client documents, systems or data are shown.
Problem & context
A major enterprise AI initiative with parallel workstreams, where business, technical and governance stakeholders each needed different information in different forms.
My role
Supporting several workstreams within the programme rather than a single narrow track.
Approach
Coordinated and documented user journeys and processes
Contributed to the functional requirements specification (FRS)
Prepared System Design Authority visuals by gathering technical inputs and turning them into material stakeholders could review
Gathered data-governance requirements and coordinated responses
Collaboration
Technical specialists, project teams, governance stakeholders and management, with information passing between groups that don't share the same vocabulary.
Outcome
Documentation and visuals that let different stakeholder groups review the same work, and a track record of operating across several parts of an AI programme at once.
Governance documentation for a major telecoms client
Key coordination and preparation role
The documents behind this work
Data governance requirementsRules for how data is owned, protected, kept and accessed, so the AI only uses what it is allowed to.
Compliance documentationAnswers from several teams gathered into one document that shows how the client's requirements are met.
Illustrations only. No real client documents, systems or data are shown.
Problem & context
A major Malaysian telecommunications client, one of the company's largest, required a governance and data-compliance document. The information it needed was spread across several teams.
My role
A key coordination and preparation role on the document.
Approach
Gathered the required information from the teams that held it
Coordinated responses to governance requirements across teams
Prepared documentation supporting the client's compliance requirements
Collaboration
Technical, project and governance contributors across the department, working to the client's requirements.
Outcome
A governance and compliance document assembled from many contributors for one of the company's largest clients.