A career that kept following the programme further

Mandate

Lead the engineering chain from production through distribution while making the receiving experience part of the investment decision.

Outcomes

• Approved revised encoding recipes for thirty selected titles while retaining ten exceptions.
• Chose the more buffered initial live release after comparing twelve thousand eligible playbacks.
• Funded a studio timing investigation before handover and preserved its test boundaries.
• Kept unresolved caption and device-review cases explicit in release recommendations.

Decisions in context

The CTO appointment gave me responsibility for the engineering capability that prepares and carries programmes to viewers. I report to Nadia Venswick and lead 186 employees through six direct reports, with thirty-four contractors separately. My seventy-four million Canadian dollars of authority in 2026 covers engineering operations and development, not programme commissioning or enterprise applications. The recent case record shows different kinds of judgement: retaining processing exceptions, accepting more live delay, investigating clock behaviour and distinguishing caption presence from usefulness. I work with Colin Merrowby's content team while respecting its creative and editorial authority. My board exposure consists of executive presentations about these choices; I have no director appointment. The role has strengthened my ability to explain why a technical output can be valid while the programme experience still needs investigation. It also requires me to ensure that a bounded success does not become a claim about every title, receiving device or viewing condition when the recommendation reaches a wider audience.

Reason for the move

Current appointment; exploring a compatible first external board contribution subject to consent.

Mandate

Connect production and distribution development while retaining the specialist decisions required at each stage.

Outcomes

• Established a shared review of programme preparation and receiving-path assumptions.
• Developed four managers across production and distribution responsibilities.
• Required investment recommendations to distinguish successful transfer from approved presentation.

Decisions in context

I brought production, playout and distribution into one development account without assuming that the disciplines had become interchangeable. By the end of the appointment, I led 112 employees through four direct reports and held thirty-six million Canadian dollars of annual authority. The streaming operation added new receiving conditions to the existing linear-service work. I wanted managers to explain how their stage affected the next one and what a successful local test still left open. The ownership change in 2015 also brought a different investment audience, making precise recommendations more valuable. I learned to distinguish the cost of investigating a proposal from the cost of operating it after adoption. The period prepared me for the CTO role by combining technical depth with the ability to make disagreements understandable to sponsors. It also reinforced the need for the content team to retain its authority over the programme while engineering took responsibility for the capability and evidence supporting its delivery.

Reason for the move

Appointed CTO in January 2020 after developing the wider programme-engineering remit.

Mandate

Develop distribution capability and examine programme behaviour beyond the controlled production environment.

Outcomes

• Brought receiving-equipment conditions into distribution acceptance discussions.
• Separated laboratory findings from wider service conclusions in engineering reports.
• Built three management responsibilities around distribution delivery and investigation.

Decisions in context

Distribution made the limits of the production environment visible to me. A programme that behaved as intended on familiar equipment could encounter a different receiving path, and the technical account needed to follow it. I led forty-eight employees through three direct reports by December 2012, with twelve million Canadian dollars of annual authority. The company's five linear services created different operating contexts, so I resisted treating one successful examination as sufficient for every route. I worked with the CTO to make the intended scope of a trial clear before interpreting its result. This was also a period of developing managers who could explain receiving-path problems to programme colleagues without using technical vocabulary to close the discussion. I moved into programme engineering because I wanted the preparation and distribution decisions considered together, while retaining the specialist knowledge each required. The broader role built on the habit of asking what happened after the output left the team's immediate field of view.

Reason for the move

Promoted to the combined programme-engineering remit in January 2013.

Mandate

Improve video preparation while making the effect of processing choices understandable to programme teams.

Outcomes

• Used comparative viewing to examine material with different motion and texture demands.
• Connected processing recommendations with the intended programme appearance.
• Developed two team leads responsible for preparation work and technical investigation.

Decisions in context

Joining Vensalith brought my first management responsibility within a broadcaster's programme chain. By December 2005, I led sixteen employees through two direct reports and held 2.8 million Canadian dollars of annual authority. The head of engineering expected a dependable preparation capability, while programme colleagues needed to understand what a proposed treatment would do to their material. I learned that consistency of purpose could require different technical choices. Motion, texture and detail were not interchangeable problems, and an identical setting could produce an uneven account of the intended picture. I encouraged comparative viewing alongside measurement so that engineers and content colleagues had a shared basis for discussion. The appointment also taught me to explain when a result was limited to the examined material. I moved into distribution engineering to understand the next part of the chain and the receiving conditions that could change the experience after preparation had apparently been completed successfully.

Reason for the move

Promoted to lead distribution engineering from January 2006.

Mandate

Investigate signal behaviour and support technical assignments under senior engineering review.

Outcomes

• Traced observed faults through their signal path instead of assigning cause from the visible symptom alone.
• Documented test conditions and the receiving arrangement used for an investigation.
• Worked with programme operators to understand the consequence of an engineering change.

Decisions in context

My first role began after completing an electronics-engineering degree in June 1990. I worked within a four-person group under a senior broadcast engineer, with no direct reports or delegated budget. The experience taught me to follow a signal problem through the chain and to distinguish an observation from its cause. Programme operators helped me understand why a change that looked tidy in a technical account could create extra work or a different risk at the next stage. I recorded the conditions under which a result had been obtained, including the receiving arrangement, rather than present it as a statement about every possible use. The company's scale by 1997 describes the employer, not a business I managed. I left in December of that year because Vensalith offered the opportunity to lead video-processing work and connect technical choices more closely with the broadcaster's programme decisions. That move began the management progression described in the later appointments.

Reason for the move

Joined Vensalith to take responsibility for video processing within a broadcaster.