From the drawing to the product commitment

Mandate

Direct product technology and engineering investment around the duty, measurement and service obligations the company can support.

Outcomes

• Selected a pump route using an explicit twelve-hour operating comparison rather than peak efficiency alone.
• Improved pilot measurement capability while preserving the authorised acceptance rule.
• Committed a bounded component bridge alongside a separately staged redesign programme.

Decisions in context

The CTO appointment extended my responsibility from the engineering portfolio to the technology choices behind our product commitments. I lead the present 214-person employee team and hold the 2026 authority described here; neither figure is intended to describe every year since 2021. My work connects design, test capability and industrialisation, while quality and product-safety owners retain their decisions. Recent cases show how an operating schedule, measurement uncertainty or an installed interface can change the recommendation. The supplier-component transition remains a programme in progress, with its prototype stage distinguished from release. My continuing foundation directorship is a separate appointment with its own time allocation. I want the technology discussion to give commercial and operating colleagues enough understanding to make consistent promises, especially when a simple headline would conceal a condition that matters to the product's selection or support.

Reason for the move

Current company technology appointment following broader product-engineering leadership.

Concurrent appointment

Separate non-executive director of Belverne Skills Foundation throughout this role; twelve annual days, not another full-time job.

Mandate

Balance new product development with testing capability and the engineering needed to sustain established families.

Outcomes

• Made mature-product support work visible beside new programme requests.
• Linked shared development capacity to an explicit product-family investment plan.
• Introduced cross-functional examination of the promises created by proposed design changes.

Decisions in context

As vice-president I had to compare work that looked very different in a development budget. A new family, a test facility and a mature-product redesign could each be necessary, yet their benefits and timing were not interchangeable. I worked with product and service colleagues to make the continuing obligation visible before allocating capacity. By December 2020 I led 142 employees through five reports with C$51 million annual authority. Those figures marked the final remit after several years of growth. I also began my separate skills-foundation directorship in July 2019, with an agreed calendar and relationship arrangements. That experience encouraged me to listen beyond the engineering case and consider the whole organisation's responsibilities. The CTO role built on this portfolio work, asking me to connect technical direction with the conditions under which the company could responsibly continue designing, manufacturing and supporting its products.

Reason for the move

Promoted to CTO to connect the broader technology direction with company strategy and continuing product obligations.

Concurrent appointment

Began a separately governed non-executive appointment at Belverne Skills Foundation in July 2019; it continued alongside employment.

Mandate

Coordinate related product platforms while examining the manufacturing and service consequences of common design choices.

Outcomes

• Established an interface review before shared components entered several product families.
• Brought field-service knowledge into product-platform discussions.
• Connected test capability proposals to the performance decisions they needed to support.

Decisions in context

The engineering-director role began as Caldriven entered its listed period. My responsibility grew across several related product groups, reaching 74 employees and C$23 million annual authority by 2014. Shared engineering offered useful economies of attention, but I learnt that visual similarity between components could conceal different service requirements. I introduced an earlier review of interfaces and the evidence needed before treating a part as common. Field-service colleagues helped identify conditions that the development office did not encounter directly. I also connected investment in test capability with the decisions product teams expected its results to support. This period strengthened my interest in the relationship between a design's technical merits and the obligations it created elsewhere. The next promotion expanded that judgement from coordinating related platforms to choosing the balance of work across a much larger product and support portfolio.

Reason for the move

Moved into vice-presidential responsibility for the wider development and sustaining-engineering portfolio.

Mandate

Connect pump requirements, design examination and manufacturing preparation for a defined product group.

Outcomes

• Used application requirements to frame product performance comparisons.
• Clarified the rationale behind demanding dimensions before manufacturing commitment.
• Prepared handovers that linked design choices to test and service expectations.

Decisions in context

I joined Caldriven to work on products whose performance depended strongly on their application. The role developed from a small product responsibility into a 26-person team with C$6.2 million authority by the final year. Design, test and manufacturing colleagues needed the same understanding of the intended duty before their individual work could form a useful product. I learnt to question a comparison that favoured an impressive isolated result while leaving the customer's operating circumstances unclear. I also worked on the reasons behind tolerances and the practical interpretation of service instructions. The employer's 1,500 people and C$420 million revenue describe 2008, not my personal scope throughout the appointment. Moving into engineering directorship gave me responsibility for the shared choices among product groups, where a local improvement could create a wider interface or support consequence that another team would inherit.

Reason for the move

Promoted to engineering director as the company coordinated several related product platforms.

Mandate

Produce usable designs and prototype records that connect dimensions and interfaces with their intended function.

Outcomes

• Prepared drawings with clearer explanations of functionally important dimensions.
• Supported prototype investigations with records another engineer could examine.
• Worked with manufacturing colleagues to understand the practical cost of design choices.

Decisions in context

My first appointment followed graduation in May 1994. I began with drawing and prototype work in a seven-person group, learning how much manufacturing effort could follow from an apparently small design decision. I did not have independent expenditure authority or employees reporting to me. The company's 340 people and C$68 million revenue refer to 2001 and describe the environment at the end of the role. Senior colleagues encouraged me to ask why a requirement existed before treating precision as an end in itself. I learnt to retain the observations behind a prototype change so another engineer could understand what had been tried. After more than seven years, I wanted responsibility for connecting those design choices with a complete product and its application. Caldriven offered that progression, along with the management and resource responsibilities that became increasingly important in my subsequent career.

Reason for the move

Joined Caldriven to lead a product group and work more directly with application and manufacturing requirements.