My contribution to a board
I could help directors identify the business decision hidden inside an apparently routine system action. My experience includes approving a calendar rule that presented gross scheduled hours as available capacity, then correcting it after an operating challenge. Later reviews concerned workspace inheritance and archive eligibility, where technical consistency could again appear to supply authority the business had not fully established. I would first learn the receiving company’s operating model, delegations and professional assurance. The board should understand which commitments automation can create without becoming a technical approval forum. I would ask who owns a recurring rule, how its conditions remain visible and what happens when an unresolved case cannot be answered safely by the default. A useful contribution could make a material workflow easier to challenge before repetition makes an unexamined assumption look like established policy.
My first year on a board
I would start by tracing one material automated workflow from the decision recorded in the board or management account to the action a colleague can perform. Through the chair’s agreed process, I would meet operating, technology, security and contractual owners to understand which conditions survive implementation and who can challenge the default. I would examine a held case beside a completed one, because the unresolved case often reveals where authority has been assumed. Twenty-three proposed annual days must include preparation and exceptional demands alongside my executive role. I would ask the chair whether my questions help directors understand the commitment or pull them into designing the system. A useful first-year contribution could leave one recurring action with clearer ownership, visible conditions and a practical route back to an accountable decision when the default no longer fits. After the first significant rule change, I would ask whether the board received a clearer account of the authority carried into the system and the exceptions still awaiting a business decision.
Conflicts and their management
My CIO role provides access to private client workspaces, technology arrangements, staffing information and contractual records. I would disclose employer, investor, client, software-provider and adviser relationships before receiving protected material for another appointment. The receiving company would need its own eligibility and independence review, and my employer would need to consent. I would not use another enterprise’s permission model or confidential planning data to resolve a problem in my current role. A particular conflict may allow recusal, but repeated exclusion from the main technology or client-governance agenda could make the seat unsuitable. Capacity must include a significant system correction requiring executive attention. I would decline an appointment expecting privileged supplier access, an informal security certification or a parallel technology-management function supplied by a director. Collective oversight should work through accountable management and appropriate professional assurance rather than bypass them.
My independence statement
Employer, fund, client, technology-provider and adviser connections require an assessment for the proposed appointment. No personal equity is held; independence is not asserted in advance.
Judgement in practice
01The calendar’s arithmetic omitted an operating decision
Forty colleagues with thirty scheduled hours gave 1,200 gross hours, but approved leave and training accounted for 240. The remaining 960 were only potential hours before assignment and skill fit, against 1,120 proposed allocation. I would ask directors whether a system-generated capacity figure preserves the conditions that make it usable. The correction did not establish a universal planning formula or prove actual overtime and cancellation. My approval matters because the apparent permission was embedded in a rule I supported. Oversight should make the accountable operating challenge available before management relies on the cleaner number, while people and delivery owners retain the decisions needed to turn potential capacity into a supported commitment.
02A completed project did not settle the archive decision
The sixty-project review found forty-five eligible under owner review and fifteen with unresolved contractual questions. I would ask a board how the enterprise distinguishes an operational milestone from authority for a later action involving its records. The held projects were not proof that material must be retained forever, and the example supplies no legal retention period. Qualified owners needed to decide the actual obligation. Technology’s role was to preserve that question instead of clearing it to complete a workflow. Directors could examine whether recurring automation carries a named decision owner and an effective route for exceptions, without taking responsibility for each archive item or substituting their own interpretation for professional advice.
Committee contribution
Chair and member readiness| Capacity | Committees |
|---|
| Ready to join | Enterprise technology and operating-risk discussions · Information-governance oversight where constituted |
|---|
Capacity and preferences
- Time available
- 23 days per year
- Current directorships
- 0
- Sectors
- Campaign and commissioned professional services · Enterprises whose workflows carry material client or operating permissions
- Company type
- A private services enterprise whose board wants the authority behind recurring system actions made explicit
- Company stage
- Consolidating business applications or introducing automation across distinct operating responsibilities
The seat I am pursuing
I would explore a first non-executive contribution under a chair who wants to understand what the company’s systems permit people to promise or do. Further governance preparation and assessment must precede acceptance; executive presentations do not establish statutory director experience. Initial work could involve enterprise technology, operating risk or information-governance discussions alongside established legal, financial and governance skills. I am not proposing to chair a statutory committee. The chair should identify the recurring decision whose authority is difficult for directors to see and the assurance currently available about it. I could contribute where management is willing to hold an unanswered case, correct a convenient default and explain the cost of preserving the business boundary. The purpose would be better collective scrutiny of commitments, with technical design and professional decisions still owned by the people appointed to make them.
Board and committee exposure
Presented to the Board or a committee
Veqzorn Campaign Services
Board technology and operating-commitment reviews
April 2021–present
Presents system-rule and change accounts through the CEO without statutory directorship.
Reported to a committee
Veqzorn Campaign Services
Enterprise systems review through the services director
April 2015–March 2021
Reported the calendar correction and the operating assumptions omitted from the original rule.
Governance learning and readiness
IICA Independent Directors’ Databank: Not yet registered
Further governance learning and any registration relevant to the prospective seat remain necessary. This profile does not claim a completed assessment or exemption.
- Preparing to scrutinise technology-enabled commitments from a non-executive role
- Learning how directors examine system authority without approving technical designs