Experience

Engineering depth. Delivery breadth. Systems perspective.

Experience across engineering, product development, manufacturing systems, project delivery, operational excellence, maintenance governance and cross-functional coordination.

Engineering and manufacturing foundation

My early career developed practical capability in toolmaking, mechanical design, manufacturing and production engineering. Working close to physical processes created a strong bias toward practicality: understand the constraint, verify the interface, make the work repeatable and document what matters.

Product development and design

Product and design work expanded that foundation into lifecycle thinking. Design decisions affect tooling, production, quality, serviceability, cost and handover. Effective delivery therefore requires coordination beyond the drawing or model itself.

My experience includes engineering design, product lifecycle activities, prototyping, manufacturing handover, technical documentation and production support.

Project delivery

Over time, project responsibilities increasingly involved translating objectives into plans, coordinating internal and external contributors, managing dependencies, tracking actions and bringing work through to operational use.

The work has included production-line delivery and relocation, manufacturing improvements, equipment and tooling initiatives, contractor coordination, scheduling, risk and opportunity management, technical submissions and stakeholder engagement.

Operational excellence

Operational excellence work focuses on how the whole system performs rather than whether an isolated task is complete. Typical lenses include flow, waiting, standard work, visual controls, maintenance, traceability, ERP sequence, material movement and the information people need to make decisions.

Lean thinking and Value Stream Mapping are useful tools, but implementation matters more than terminology. Improvement needs to survive contact with daily operations.

Governance, risk and accountability

I see governance as the mechanism that keeps outcomes under control. It should make scope, ownership, assumptions, decisions, risks and progress visible enough for the right people to act.

In smaller organisations the same person may be both accountable and responsible for substantial parts of a project. That makes disciplined self-governance even more important: define the baseline, maintain evidence, escalate decisions that exceed authority and keep stakeholders informed.

Stakeholder and contractor coordination

Projects rarely fail because a schedule exists. They become difficult where people, interfaces and expectations do not align. My approach is to clarify who needs to contribute, what each party needs from the others, when decisions are required and what happens if an assumption changes.

This includes working with management, engineering, operations, maintenance, suppliers, contractors and other business stakeholders.

Executive development

My current development focus is the transition from managing individual delivery problems to thinking at a program and organisational level: prioritisation, governance, capability, commercial awareness, decision quality, long-term consequences and how multiple initiatives interact.

Operating lens

01

Context

Understand why the work matters and what constraints are real.

02

Control

Create visible scope, decisions, risks, ownership and cadence.

03

Coordination

Align technical, operational and commercial contributors.

04

Capability

Leave the organisation with a repeatable system, not a dependency.

Next conversation

Interested in discussing projects, transformation, leadership or collaboration?

Connect with Kevin