My contribution to a board
I could help directors understand which business meaning a technical result supports and which meaning it does not. My equipment-import approval shows how an apparently cleaner system can lose the distinction between physical subjects. The later disconnected-work and supplier-exit exercises show why a successful upload or export does not settle every operating question. I would first learn the receiving enterprise’s commitments, delegations and assurance arrangements. Directors need to understand the tested scope, the remaining dependencies and the owner of any unresolved decision. My contribution should make those matters easier to discuss without turning the board into an implementation team. I would not present a corrected register as equipment clearance or a rehearsal as universal resilience. The useful oversight question is what the enterprise can responsibly rely on after the technical milestone, and what still needs evidence or another accountable decision.
Judgement in practice
01A simpler register could conceal a more complicated physical reality
The selected import represented 24 physical devices through 18 records because six local numbers each referred to two different items. I would ask directors how management knows that an integration has preserved the operating subjects it is meant to describe. A smaller dataset is not automatically a better account. The correction established distinct identities for the selected devices but did not establish technical suitability or a universal error rate. My approval of the original assumption belongs in the discussion because the failure was not merely a programming defect. Oversight should examine the evidence behind the meaning attached to a system result and how an operating owner can challenge it. Directors should not choose the database key themselves. They should understand whether management has tested the claim at the boundary where another person relies on it.
02An export could succeed while business functions remained dependent
Ten of twelve agreed functions ran at the first supplier-exit rehearsal; two still required supplier components. I would ask directors what management means when it describes a transition as complete. The possession of files did not demonstrate the full business scope. The later twelve-function result was useful because it came from a defined receiving environment after the dependencies had been addressed. It still did not prove every future scenario. The board should understand the scope tested, the work remaining and the basis for accepting a transition. My contribution could help translate a technical success into a decision that directors can scrutinise alongside commercial and operating advice. It would not make me the supplier negotiator or implementation owner. Those responsibilities should remain clear when a positive programme account reaches the board.
My first year on a board
I would follow one significant technology claim from the board paper into the operating capability it describes. Through the chair’s agreed process, I would meet information, operations, finance and relevant assurance owners to understand the meaning of completion and the evidence supporting it. I would examine an unresolved dependency alongside a successful test, because the remaining gap often shows whether the scope is being reported honestly. Twenty-three proposed annual days must accommodate learning, preparation, meetings and exceptional demands alongside my executive work. I would ask the chair whether my questions improve collective scrutiny or draw directors into design choices. At the first-year review, I would want a material technology discussion to state its tested conditions and remaining owner more clearly. I would also ask whether management can explain what a receiving team can actually do after the change, rather than only which files or technical tasks have been delivered.
Conflicts and their management
My CIO work provides access to equipment histories, operating arrangements, software dependencies, supplier terms and private change plans. I would disclose employer, investor, client, technology-provider, equipment-provider and adviser relationships before receiving confidential material from a prospective company. That company must assess eligibility and independence against its own circumstances, and my employer must consent to a realistic outside commitment. I would not bring another organisation’s private system weakness or supplier negotiation into my current role. Recusal may address a particular overlap, but recurring exclusion from central technology questions could make the appointment unsuitable. Capacity must allow for a material systems issue in the continuing CIO position. I would decline a seat expecting access to proprietary components, an informal technology certification or personal intervention in operating clearance. The role should improve collective assurance through accountable management and appropriate professional expertise.
My independence statement
The proposed company must examine employer, investor, client, software-provider, equipment-provider and adviser connections. I would disclose those relationships without assuming that an absence of personal equity settles independence.
Committee contribution
Chair and member readiness| Capacity | Committees |
|---|
| Ready to join | Technology-dependency and operating-risk discussions · Enterprise systems oversight where constituted |
|---|
Capacity and preferences
- Time available
- 23 days per year
- Current directorships
- 0
- Sectors
- Operators combining physical equipment with shared enterprise systems · Service enterprises preparing technology or supplier transitions
- Company type
- A private enterprise whose directors want technical completion translated into a bounded account of business capability
- Company stage
- Integrating operating records, testing disruption arrangements or rehearsing a supplier transition
The seat I am pursuing
I would explore a first non-executive contribution with a chair who wants technology claims tested through the enterprise’s actual work. My present exposure is executive reporting and presentation, not statutory directorship. Further preparation and appointment-specific assessment would come before acceptance. I could contribute to systems, dependency and operating-risk discussions alongside established governance, financial and legal experience, without claiming readiness to chair a statutory committee. The chair should explain which recurring technical conclusion directors find difficult to assess and what evidence management supplies. I could be useful where a successful milestone can be questioned without implying that the programme team has failed. The purpose would be a clearer account of what is supported, what remains uncertain and who decides next. Management would still own implementation, and qualified operating owners would retain the decisions a functioning application cannot make on their behalf.
Governance learning and readiness
IICA Independent Directors’ Databank: Not yet registered
Preparation for a first outside appointment is unfinished, including any registration applicable to the intended role. This profile makes no assessment-pass or exemption assertion.
- Preparing to examine technology assurance as a collective board responsibility
- Learning to distinguish a tested technical result from the wider operating claim made about it
Board and committee exposure
Presented to the Board or a committee
Derlashi Urban Cargo
Board systems-change and operating-continuity discussions
April 2021–present
Presents technology dependencies and tested business scope through the chief executive without statutory director status.
Reported to a committee
Derlashi Urban Cargo
Equipment-identity review through the executive responsible for enterprise services
April 2016–March 2021
Reported the import assumption and the correction of selected equipment identities.