PROJECT COACHING: DESIGNING LEADERSHIP SUPPORT FOR TRANSFORMATION PROJECTS

As transformation programmes take up a larger share of the corporate agenda, human resources and talent management functions face a new design question: how do you structure development support for leaders assigned not to a permanent role, but to a defined and time-bound project role? Digitalisation programmes, operating model changes, merger integrations and institutionalisation initiatives move a manager off the authority base of their day-to-day role and place them in an assignment with high uncertainty and a compressed timeline. The conventional development architecture annual training plans, long-horizon coaching engagements, periodic review cycles often cannot keep pace with that assignment. Project coaching is the format built to close this gap: a time-bound development practice that focuses coaching methodology on the duration, agenda and milestones of a defined project. This article addresses the definition of the format and its boundaries with adjacent roles, the leadership equation that creates the need, the technical components of programme design, and the application limits and measurement indicators connecting each to the design practice of HR teams.

What Is Project Coaching? Definition and Boundaries with Adjacent Roles

Project coaching is a goal-oriented, time-bound coaching practice that accompanies the leader managing a critical project or transformation initiative and, where required, the core project team throughout the life of that initiative. Methodologically it belongs to the same family as executive coaching: structured feedback, a session architecture built on powerful questions, a confidentiality framework and measurement discipline all apply here as well. The distinction lies in the source of the development agenda and the definition of the calendar. In classic executive coaching the agenda derives from the individual's general leadership development plan; in project coaching it derives from the concrete leadership challenges of the project, and the session calendar is matched to the project's phase structure.

For HR teams, the first boundary to clarify is the difference from project management consulting. A project management consultant or project office deals with plan, methodology, scope and deliverable quality it monitors the status of the work and produces corrective recommendations. The project coach deals with the leader's behavioural set: how decisions are made under uncertainty, how resistant stakeholders are managed, what practices sustain team energy, and which behaviour patterns emerge under pressure. One strengthens the mechanics of the project, the other its leadership line. The two roles are not alternatives to one another; however, when their scopes are not separated at the contracting stage, the coaching engagement effectively turns into an advisory relationship and the distinctive value of the format is lost.

The second boundary is with change management consulting. Change management works with programme-level instruments such as communication planning, stakeholder analysis, training design and adoption measurement. Project coaching focuses on behavioural change at the individual and team level. Using both components in the same programme is common; what matters is that the organisation defines in advance which output it expects from each. The format's place within the coaching family should also be clear: onboarding coaching focuses on a new role and team coaching on team dynamics, while project coaching focuses on the leadership equation of a defined initiative. Our article examining the definition, process and variants of executive coaching in detail sets out the methodological ground of the format as a whole.

The Source of the Need: The Leadership Equation of Project Roles

Three structural dynamics drive demand for project coaching. The first is the normalisation of transformation. Major change programmes, once experienced at long intervals, are now simultaneous and continuous in many organisations. As transformation intensity rises, leadership demand shifts from permanent roles to time-bound project roles and these roles usually fall outside the coverage of the standard development architecture. The need of a programme leader expected to deliver results within six months does not even align in calendar terms with an annual planning cycle.

The second dynamic is the distinctive role structure of project leadership. A manager running a transformation project is typically inside the equation of influence without authority: they must obtain output from functions that do not report to them, manage resistance without using hierarchical power, and continually renegotiate resource allocation. This equation is usually added on top of the day-to-day role and is resolved on the organisation's most visible stage. Our field observation is that the combination of high uncertainty, low authority and high visibility produces unusual behavioural deviations even in experienced managers: a tendency towards micromanagement that narrows the decision space, a conflict-avoidance reflex that postpones tense topics, or signs of burnout in workload management. Project coaching establishes a structured space in which these deviations are noticed early and put on the agenda.

The third dynamic is the change in career architecture. Executive careers are increasingly shaped less by vertical progression within a single function and more through critical projects and transformation roles. Managing an integration programme, taking ownership of a digital transformation or leading the establishment of a new business line are now standard stops on the journey to senior management. In this architecture a project is not only a delivery stage but also a development assignment. For HR teams running succession planning the practical implication is this: critical project assignments are the richest environments for generating development data on the talent pool, and when supported they yield two outputs from a single investment the leadership risk of the project falls, and the development of the succession pool under real conditions accelerates.

On top of these three dynamics comes a shift in investment logic. Organisations have begun to notice the imbalance between the share of transformation budgets allocated to technical components systems, processes, consulting and the share allocated to the human component. The recurring finding in retrospective reviews of failed transformation programmes is not a lack of methodology so much as insufficient leadership resilience: the plan, the sponsor and the budget were in place; the leadership capacity to carry the change in the field was not adequately supported. Project coaching is a targeted and measurable investment line aimed at that gap.

Programme Design: Contract, Rhythm, Layers and Coach Profile

An effective project coaching design adapts the discipline of the classic coaching process to the operational reality of the project. In our field practice the main components of the design are as follows:

•     Project-contextual contract: The project's assignment definition is included in the tripartite contract leader, coach, sponsor; coaching objectives derive from concrete leadership challenges such as stakeholder resistance, team set-up and the speed-quality balance.

•     Intensified start: In the first weeks, more frequent sessions are used to work on role clarity, the stakeholder map and first-hundred-day priorities.

•     Milestone-aligned calendar: Instead of fixed intervals, a flexible session rhythm is set, aligned to pre-steering-committee moments, phase transitions and critical decision points.

•     Short-cycle focus: Each session connects to the leadership question current at that stage of the project; the development agenda is worked through real cases.

•     Team layer: Individual coaching is supported where needed by team sessions with the core project team; alignment and conflict management are addressed at team level.

•     Closure and transfer: As the project completes, gains are distilled; how the developed behaviours will be carried into the permanent role is the main agenda of the closing work.

Two technical subtleties of the design are decisive. The first is the confidentiality architecture. In a project environment the sponsor is often the executive accountable for the programme's outcome, and the tendency to expect information about project status from the coaching process is stronger than in classic designs. The boundary must be drawn in writing at the contracting stage: the coach gives feedback not on the status of the project, but on the leader's progress against development objectives. The second subtlety is format flexibility. Half-day session blocks are not viable at project tempo; short and frequent online sessions, preparation calls before critical meetings and post-meeting reflection calls are the format's natural working mode.

Duration and intensity parameters should also be made explicit in the contract. In our field practice project coaching engagements are typically planned for four to nine months according to the project's phase structure; session frequency rises to once every two weeks in the start-up phase, drops to a monthly rhythm in stabilised phases, and is intensified again at critical transitions. Session lengths are shorter than in classic coaching; sixty-minute blocks are supplemented by thirty-minute preparation calls before critical meetings. Writing these parameters down in advance makes both budget planning and the leader's calendar commitment workable; left undefined, the process becomes the first item postponed during intense periods of the project.

Ownership of the process within the organisation must also be defined. In practice the process owner is the HR or talent management function, and its area of responsibility consists of four steps: building the coach pool against defined criteria, matching leader and coach through a chemistry meeting, facilitating the tripartite objective-setting meeting, and running a short review of objectives at the mid-point of the process. These steps take coaching out of the category of a service purchase left to the manager's individual preference and connect it to the organisation's development architecture. The same ownership also makes it possible to carry the development output produced at the end of the process into succession planning and career conversations.

The sponsor role must likewise be redefined in the project context. In classic coaching the sponsor participates in periodic reviews; in project coaching the sponsor is usually on the steering committee and in weekly contact with the leader. Designed correctly, this proximity becomes an advantage: the sponsor observing behavioural changes aligned with coaching objectives in real time, and deliberately opening space for the leader to try new behaviours for example leaving full ownership of a critical committee presentation to the leader is among the strongest levers for accelerating development. The same proximity produces the highest risk when the confidentiality boundary is not maintained; for this reason the definition of the sponsor role is written in greater detail in project coaching contracts.

The coach profile carries its own criteria set. Accredited training, regular supervision, a defined ethical framework and business experience sufficient to read the senior management context are the basic criteria; the project context adds a layer of familiarity with how transformation programmes operate. A coach who knows the steering committee dynamic, the pressure of phase transitions and the influence-without-authority equation from the inside reads the situation the leader describes directly. Balance must be maintained: a profile with strong project experience but weak coaching discipline quickly shifts into giving recommendations and effectively moves into the position of a second project manager. The combination sought is the intersection of transformation experience and the coaching profession; writing coach selection criteria so that these two dimensions are examined separately directly raises matching quality.

The scope decision is also part of the design. The primary candidate is the programme or project leader; however, the design that increases impact defines coaching for several roles at the critical nodes of the transformation at once: the leader running the programme, the manager of the function where resistance is highest, and the key middle management implementing change in the field. The agenda of the team layer is equally concrete. Transformation teams are often assembled quickly from people drawn from different functions who have taken on project load in addition to their main roles; the agenda of the first sessions is therefore role and expectation clarity. In later phases the agenda shifts to how decision rights operate, to open discussion of the tensions between functional priorities and the programme objective, and to workload balance during intense periods. The scenarios in which the format produces the highest return fall under these headings: merger and acquisition integrations, institutionalisation and restructuring initiatives, large-scale system and operating model transitions, and critical assignments of high potentials taking on programme leadership for the first time.

Application Limits, Measurement and Institutionalisation

A balanced assessment also requires defining the limits of the format. Project coaching is not a remedy for weakness in project management: the problem of a programme without a plan, with unmanaged scope and weak sponsorship is not solved by coaching; the coach can support the leader in noticing these structural gaps and raising them, but cannot close the gap itself. The second limit is that it should not be confused with crisis intervention: coaching defined at the final stage of a seriously delayed programme operates under an unrealistic expectation; the correct timing for the format is the project's start-up phase, or at the latest the first signs of strain. The third limit is scope discipline: project coaching is by definition time-bound and agenda-bound; a quiet expansion of the process into general executive coaching weakens the measurability of both formats if the need is there, it should be established with a new contract.

Measurement is the component that establishes the format's organisational legitimacy, and the project context makes this easier. Because coaching objectives derive from the leadership challenges of the project, progress can be tied to observable points: change in steering committee interactions, the course of relationships with resistant stakeholders, team pulse survey results, the time taken to make critical decisions, and movement in the targeted behavioural dimensions of 360-degree feedback. Attributing the entirety of project outcomes to coaching is not methodologically sound; what is measured is the change in leadership behaviour and the observable reflection of that change in the project environment.

For measurement to be workable, a reference point must be established at the outset. A short baseline assessment on the targeted behavioural dimensions as the process begins structured feedback from the sponsor and a few key stakeholders is sufficient makes subsequent comparison possible. Reporting frequency is then tied to the project's phase structure: one mid-process review and one closing assessment is an adequate rhythm for most programmes. The content of the report must be consistent with the confidentiality framework; what is shared is not session content, but progress on the targeted behavioural dimensions and a recommendation regarding continuation of the process.

From the leader's side, the day-to-day value of the format falls under three headings. The first is reflection space: transformation tempo consumes the opportunity to pause and assess first; the session, as the protected reflection time of the week, produces output in its own right. The second is rehearsal: working in advance on a conversation with a resistant stakeholder, a difficult committee presentation or a piece of hard feedback measurably affects performance in the real setting. The third is workload and resilience management: the fatigue of long-running programmes is cumulative and leaders usually notice their own burnout signals late; an outside perspective brings the sustainability conversation onto the agenda before the signals grow.

At organisational scale, making the format permanent is a process design question. Applied on a case basis at first, it evolves over time into a standard in organisations with high transformation intensity: adding a leadership support component to the start-up template of every programme above a defined budget or strategic importance threshold, keeping the coach pool and contract framework ready in advance, and connecting measurement indicators to programme reporting. For organisations evaluating the decision to begin, the low-risk entry route is a pilot: coaching support is established for the leader of a single critical initiative in the portfolio, with objectives defined at the start of the project. The pilot's evaluation questions are simple how did the leader experience the process, did the sponsor observe behavioural change, was a difference created in steering committee interaction. You can find our holistic approach to corporate transformation programmes on our transformation solutions for companies service page.

The ultimate measure of the format is not the project's delivery date but the capacity with which the leader emerges from the project. Deliverables are completed, systems go live, the programme closes; what remains is the behavioural repertoire gained by the leader who went through that assignment. Demanding programmes run without support can wear down capable leaders and weaken the succession pool; the same programmes run with support prepare the leaders who will manage the organisation's next transformation. Project coaching is therefore not a project expense but an investment in leadership capacity made under real conditions.

At Kaan Böke Management Consulting, with 35+ years of corporate experience and 25+ years of C-level leadership perspective, we deliver strategic and applicable solutions for project coaching programmes from contract design to measurement indicators. Contact us to strengthen the leadership line of your critical projects.