Starting change is easy. Actually carrying it through is harder.

An organizational development partnership is a longer-term collaboration with a leader or leadership team. Management responsibility stays inside the organization, but the development partner helps hold the overall picture, sharpen focus, and support the implementation of agreed changes. It's most useful when the need for change is clear but implementation stalls, development efforts are fragmented, or the leadership team needs an independent partner who understands the organization's context and helps maintain continuity.

The collaboration can focus on strengthening leadership, implementing strategy, leadership team collaboration, clarity of roles and responsibilities, or change management. It can also focus on cross-team collaboration, leadership culture, decision-making quality, or the organization's readiness for its next stage of growth. We don't try to address every topic at once. Together we choose the development areas whose change creates the most value for the organization.

A consultant analyzes the situation and usually gives concrete recommendations or an expert assessment. A development partner works with the leader and the organization over a longer period, helps hold the overall picture, and supports the ongoing implementation of decisions and changes. An interim manager takes on direct leadership responsibility and decision-making authority for an agreed period. In a development partnership, formal leadership responsibility stays with the leader or leadership team, but my role is to be an active thinking partner, facilitator, and, where needed, a practical support for implementation.

We start with a conversation with the leader or leadership team to understand the organization's goals, current situation, and main obstacles. Where needed, we also bring in other key people to get a fuller picture. We then define a shared development focus, priorities, and the signs by which we'll recognize real progress. Only after that do we shape a suitable way of working. The collaboration doesn't start from a ready-made program, it starts from understanding the organization's actual need.

The length of the collaboration depends on the goal and the scope of the desired change. In some cases, a suitable period may be three to six months; for deeper changes, longer. Meetings can happen weekly, a few times a month, or as more intensive periods tied to specific development stages. Before starting, we agree on an initial timeframe, meeting rhythm, milestones, and points where we assess whether the collaboration should continue.

Who takes part depends on the goal. The collaboration often starts with the CEO, owner, or leadership team, since their decisions and example influence the whole organization. At different stages, mid-level managers, teams, or other key people may also be involved. Not everyone needs to be involved in everything. We bring people in where their perspective, decision, or contribution is genuinely needed to implement the change.

Leadership responsibility stays with the organization's leader or leadership team. My role isn't to decide for them, but to help see the overall picture, define priorities, prepare important decisions, and keep attention on implementing what's been agreed. Where needed, I facilitate workshops, support leaders through coaching, help shape a leadership rhythm, or contribute practically to preparing a specific change. The role and boundaries of responsibility are always agreed clearly before the collaboration begins.

At the start of the collaboration, we agree on goals and visible signs by which to assess progress. These may relate to decision implementation, leadership practices, taking ownership, quality of collaboration, or concrete business results. We regularly review what has genuinely changed, what hasn't moved, and why, and adjust activities where needed. The goal isn't to run more development activities, but to build ways of working and capability that remain with the organization after the collaboration ends.

I bring in a partner when their expertise helps the organization reach a better result. The need might relate to, for example, people management, recruitment, communication, technology, team training, or a specific field. The client doesn't need to search for different experts and coordinate their work. I stay the main point of contact, hold the overall picture, and am responsible for making sure the activities involved support the shared goal.

The price depends on the goal of the collaboration, its duration, the regularity of meetings, the amount of preparation, and the activities involved. Some partnerships focus on regular work with a leader or leadership team, others combine coaching, workshops, team development, and practical support for implementing change. The collaboration can be priced as a monthly fee or on a stage basis. After an initial mapping of the need, I put together a clear proposal covering focus, way of working, timeline, and total investment.