← All services
CoachingLeadershipData

Data Leader Coaching

The technical part may no longer be the hardest part of your role.

Coaching for people moving from solving technical problems to leading people, priorities and decisions in data and technology environments.

Start with what is actually happening.

  • You are still the person everybody brings the hardest technical problem to.
  • Delegating feels slower than solving it yourself.
  • Stakeholder pressure competes with the needs of the team.
  • Your old strengths as an expert no longer solve every part of the role.
  • You want to lead without performing a version of leadership that does not feel like you.

Good work starts with better questions.

01

What are you still holding because being the expert feels safer?

02

What does your team need from you now?

03

Where are your boundaries unclear?

04

What decision are you avoiding?

05

What kind of leader do you want to become?

The scope follows the problem.

I do not force every engagement through the same checklist. These are the areas that may matter; the agreed scope determines how deep we go.

Moving from expert to leader

Delegation and trust

Priorities and boundaries

Stakeholder pressure

Conflict and difficult conversations

Identity and confidence in a new role

Decision-making

Leadership values and behaviour

Something you can use after the conversation ends.

The output should help you make a decision, change a practice or move the work forward. It should not exist simply to prove that work happened.

01

Clear Coaching Goal

We define what you want to work on and what change would matter.

02

Individual Coaching Sessions

Focused space to think, notice patterns and make deliberate choices.

03

Challenge Without Prescription

I will challenge your thinking, but the answer remains yours.

04

Actions Defined by You

Experiments and next steps come from the work, not from a leadership checklist.

05

Technical Context Without Role Confusion

I understand the environment, while keeping coaching distinct from consulting or mentoring.

Enough structure to make the work clear. Not so much process that the process becomes the work.

01

Goal

We start with what you want to change, understand or handle differently — and what would make the coaching useful.

02

Sessions

We work with real situations, choices, patterns and assumptions. The technical context can be present without turning the work into consulting.

03

Between sessions

You may choose actions or experiments to test in your actual leadership environment.

04

Review

We return to the goal and notice what has shifted, what still matters and what you want to carry forward.

The engagement is built around focused sessions. We agree cadence and practical expectations before we start.

This is likely to help if...

  • You work in data, BI, AI or technology and are moving into more leadership responsibility.
  • You want coaching rather than technical advice.
  • You are willing to examine your own patterns, choices and assumptions.
  • You want me to tell you how to manage your team.
  • You primarily need technical mentoring or architecture advice.

If the problem is real but the format is wrong, that is useful to know early. I would rather redirect the conversation than force the challenge into the wrong service.

This does not automatically lead to another engagement.

Sometimes the focused piece of work is enough. If it reveals a useful next step, these are some of the directions that may make sense.

The technical part may no longer be the hardest part of your role.

Bring me the problem, not a polished brief. A few sentences about what is happening and what you would like to change are enough to start.

Explore coaching fit

Send me a message.

You do not need a polished brief. Whether the topic is Power BI, Fabric, AI, team training, mentoring, coaching or simply a challenge that needs untangling, leave a few details and we can start from there.

SIGNALMESSAGECONVERSATION

AI & TRANSPARENCY

AI supports selected parts of my work — it does not replace my judgement, responsibility or relationship with the client.

I use AI tools for tasks such as research, organising information, structuring content and preparing materials. I treat AI as support for my work — not as an autonomous author or decision-maker. Anything I publish or use professionally remains my responsibility.

In coaching, I do not use AI to automatically assess, diagnose or make decisions about a client. AI does not replace attention, confidentiality or human responsibility for the coaching relationship.

AI may support the process. Human responsibility remains.