Direct technical leadership, with responsibilities agreed for each engagement.
The delivery model, access needs, review stages, and support arrangements depend on the work. These principles describe the baseline.
- 01
Delivery responsibility
I lead the technical direction of my engagements and remain involved in requirements, architecture, and delivery reviews. Depending on the scope, implementation may be handled directly by me or with the TABSAP team. The people involved, their responsibilities, and the support arrangements are agreed for the project.
- 02
Access and confidentiality
Access requirements and data handling are agreed for each engagement. Access should be limited to the systems and permissions needed for the work. Client information is handled according to the agreed confidentiality requirements, and handover includes a review of access and retained project materials.
- 03
Review and handover
Projects are divided into reviewable stages. Testing, release arrangements, documentation, and ongoing support are defined around the system and its risks. Where changes affect production, the implementation plan should include recovery arrangements appropriate to the environment.
- 04
AI-assisted development
AI-assisted tools may support development and analysis where suitable. Their use must respect the client's data-handling requirements, and outputs need review and validation before being relied on in delivery.
Specific promises about data deletion, access revocation, certifications, insurance, subcontractors, or publication checks are documented only when the operating process for that engagement supports them.
Let's discuss what you're building.
Share the problem, the current setup, and what a useful outcome would look like. For research inquiries, include the topic or opportunity you would like to discuss.