GPM Consulting
FIX THE FLOW.
Functional departments don’t move. The information you need to decide never reaches you. Whatever falls through the cracks ends up on the project’s plate.
Until the structure changes, the same problems keep coming back.
We redesign how your projects are run and develop the people who run them, so manufacturing and heavy-industry teams get ahead of problems instead of chasing them.
Nothing comes up from the departments except problems. When a job gets out of hand, the whole thing lands on your desk, and you have no choice but to absorb it. Your responsibilities grow without limit, and the first casualty is the time you had for actually managing.
Information sits in departmental silos and is never assembled into a picture of the whole project. When a decision is forced on you, the evidence isn’t there. Cost overruns and schedule slips become facts of life you are expected to accept.
A term as basic as “critical path” doesn’t land. Everyone works their own way and improvises as they go. Vocabulary, methods, the picture of what good looks like: none of it is shared.
In the start-up phase that was fine. You filled the gaps with overtime, pushed through on sheer effort, and delivered. But that success is exactly what kept standardization at bay. Experience lives only in people’s heads, so even a win can’t be repeated.
In the status meeting, everything sounds on track. Walk the floor and you see a different picture: defects and delays piling up. By the time a problem reaches the project, the options are gone. All that’s left is overtime and more people.
You stand in front of senior management explaining a delay. The late work is your own design. You say “we’ll recover” while thinking “there’s no way.” And you carry that contradiction alone, because there is no one you can tell.
No department is accountable for the project’s deliverables. Every department has a clear remit, but only for its own work. Deliverables that cut across departments belong to no one, and the dropped work collects in the project. Even if you try to push it back where it belongs, the project has no authority over people or work. All it has is the responsibility. The organization isn’t broken. It was never designed for projects.
“Just push yourself harder” fails for a simple reason. If it worked, you would already be on schedule. You’re behind precisely because it doesn’t. This isn’t about grit. It’s what happens when one person is both the worker and the manager.
No one has designed how information comes together or what the common language is. Things still run because a few people with leadership are covering for the missing system through sheer effort. But that cover reaches only as far as they do. Beyond it, decisions lose their inputs and problems are found later and later. Telling the team to “take ownership” won’t close the gap. Ownership isn’t something you demand. It’s something a system produces.
Leave these three alone and a vicious cycle sets in. Firefighting consumes the slack, the lack of slack keeps risks unspoken, and unspoken risks bring the next fire. Eventually, bad news gets buried.
It’s not your fault. It’s the structure. So we fix the structure.
You already know what the problems are. What you lack is someone whose job it is to drive the change.
That is the role GPM takes on. You get momentum, not an analysis report.
And we plan our exit from day one, so you are left with a structure that runs without us.
Diagnose first. Redesign to change the flow. Then make it stick with a common language.
We don’t ask whether the documents exist. We measure, on a six-level scale, whether each system has actually taken root and does its job. Wherever something exists on paper but isn’t working, you get it back with a prescription.
Where responsibility sits, how meetings are run, how information and decisions travel: we redesign these. The test is one question. Can you see the risks? Give information one place to converge, and governance starts to work.
Training isn’t the goal. It’s the means to a specific end: aligning ways of working that differ from person to person. Theory gives the team a common language; practice gives it criteria for decisions. We don’t teach right answers. We help people grow their own judgment.
These cases are not about solving problems. They are about changing the structure that produces them. Four cases from the field, told first-hand.
Dispositioning nonconforming parts ran through more than ten departments inside and outside the company, and the backlog wasn’t moving. I built a database of how many items were stuck at each step and put it in front of the weekly meeting. From then on, no approval stage could hide the fact that it was the holdup. I cleared the blockages one at a time: more staff on the inside, top-level agreement on the outside. The backlog started to fall.
Read the case →I switched the weekly meeting from reports by department to reports by deliverable. Materials had to be updated every time, minutes went out after every session, and I kept the discussion moving. I insisted on having people in the room who could decide. Once the meeting was seen as worth attending, attendance rose from 70% to 90%.
Read the case →Bad news comes up immediately. Impact assessed within a week. Plenty of countermeasures on the table from the start. I made the same demands every time a major problem hit, two or three times a year. The team learned the playbook, and because everyone knew what was expected, each round got faster. The program got steadier as a direct result.
Read the case →I handed the program to my successor. Then a crisis hit: parts supply was running dry. The new team worked the playbook they had inherited and recovered without stopping engine assembly. In calm times you can’t tell whether a system is real. The only proof is a crisis after the person who built it has gone.
Read the case →
Kintaro Hashi spent sixteen years on large-scale projects at Kawasaki Heavy Industries: eight in chemical plant EPC, including design for a JPY 150 billion overseas plant, and eight in program management on an international aero-engine collaboration (PW1100G-JM). He is a U.S. Professional Engineer (PE) and a Project Management Professional (PMP).
Areas of practice: project and program management, project governance design, and PM talent development in manufacturing and heavy industry.
You tell us where things stand. Before the call ends, you get one working hypothesis about where the project is stuck. There is nothing to prepare.
The PM Maturity Diagnostic tests that hypothesis across your whole project organization. We agree the scope and approach with you and put a quote on the table. Up to this point there is no charge.
The first contract is a small, clearly bounded diagnostic. It begins with the documents you already have and two 60-minute interviews.
One person, start to finish. Diagnostic, redesign, training: I do all of it myself, from the first conversation to the last. You will not meet a salesperson and then be handed to someone else.
Nothing gets lost in hand-offs. With no one in between, nothing has to be explained twice and no detail goes missing. The person you talk to in the first 30 minutes is the person who does the work.
Contracts by phase. Diagnostic, redesign, and embedding are contracted separately. You decide whether to go on after seeing the results of the phase before.
Confidentiality. Where needed, we sign an NDA before any documents change hands.
I don’t “support” you from the sidelines. I lead from the front until the results show. That is my promise.
If all you can say is “we don’t know where to start,” that is enough to begin.