Start
You see it everywhere. Your team is asking what the company is doing about it. You have a licence or two, maybe a few people experimenting on their own. What you don't have is a place to start that you would be comfortable defending.
Ninety seconds: what a starting point you could defend actually looks like, and which of the three formats fits who is asking. Everything below is the same argument in detail, for whoever wants it.
Two of those deserve a straight answer before anything else. Feeling behind and being behind are different things: almost every company has licences and very few have changed how a single department works, so the distance is usually much smaller than it looks from the inside. And the learning is not the hard part. The format asks for about four hours of your time across a month, on work already on your desk, and nobody sits through a curriculum. Starting is the part people find difficult, and starting is the part we take off you.
Leaders who have used the tools on their own work and can judge for themselves. One team working differently, with documented use cases. A short list of departments to address, in order, with a first view of the value in each.
Two costs are avoided. The first wrong move: a platform standard that locks you in for two or three years, a rollout that lands on people who were never shown how to use the tools, a sequence that costs margin instead of earning it. And the cost of waiting: every quarter spent on “we should do something” is a quarter a department somewhere keeps turning work away.
The first step comes in three formats, set out below. They fail in different ways, so each is designed against a different thing.
Executive fluency fails on the calendar. Executive time is the scarcest resource in the building, so it asks for about four hours per leader across a month, on work already on the desk. Adoption also follows the corner office, which is why leaders go first rather than last.
Team onboarding barely touches the leader at all. It fails when a team reads it as training stacked on top of the job. So it runs inside their own week on their own files, and the team lead signs off on the updated procedures rather than a trainer.
Strategy and roadmap is the opposite of fluency. It genuinely needs leadership time, and a roadmap written without it is a document nobody owns. We say what that costs in leadership hours before it starts rather than discovering it halfway through.
Two things hold across all three. The tools move faster than any curriculum, so what gets taught is the habit of learning with the tool. And nobody's technical team gets pulled into rollout work.
Three formats, depending on who is asking.
One leader at a time, at your workstation, on the work already on your desk. Three sessions over four weeks: install the tools and produce one real deliverable together; review what you tried alone and raise the ambition; consolidate and write your personal playbook. Philippe is reachable directly between sessions. No queue.
One team, six to seven weeks. Two cycles of daily use on real work, individual interviews, findings shared back so people learn from each other, updated procedures with the team lead, and a learning rhythm the team keeps going on its own.
For the leadership team that needs to answer which departments, in what order. A register of needs the leadership validates, a list of initiatives sized for value and effort, and a six, twelve and eighteen-month roadmap you can present.
For larger organizations: three leaders coached, plus a short written business case addressed to the people who decide, so the pilot ends in a decision whichever way it goes.
A tender business, where winning the mandate and executing it both decide the year. It had begun on its own. We joined partway and added fluency for the executives deciding, guardrails, a diagnostic on the estimation and RFP response departments, and an aspiration worth aiming at.
Read the caseThirty minutes to confirm the situation, pick the format, and decide whether we are the right people for it.