We read your program before we prescribe a solution.
The Dokusha Diagnostic — a fixed-scope, fixed-fee engagement for programs that have stalled.
You know when a group of people are all trying to get the same thing done, and somehow it just… doesn’t happen?
Most stalled programs are not stalled because anyone is underperforming.
They are stalled because something structural is invisible from the inside. Meetings meander and actions go nowhere — but those are symptoms. The real cause is ownership that was never formally assigned, a dependency nobody is tracking, or a decision that quietly never got made. The people closest to the work are usually too close to see it, and the status report describes a program that no longer exists.
I find the cause. Then we get things moving.
An outside reader has no history with the program, no side to take, and no reason to be diplomatic about what the evidence actually shows.
I’m that outsider. And I don’t diagnose and disappear.
I dig in.
Who this is for
Growth-stage companies where 10 to 50 people, across several teams, are working toward the same date — big enough that delivery needs real structure, young enough that nobody has built it yet.
Sound familiar?
- “Product, tech, marketing, legal, finance — everyone’s busy, and none of it lines up.”
- “We raised on this roadmap, and the launch has already moved twice.”
- “We’ve been trying to hire a PM for months. The work can’t wait that long.”
- “We’re strong on product and sales. Nobody actually owns delivery.”
- “I’ve just stepped in as COO, and I can’t see into half of this.”
- “Our PM just resigned. Right in the middle of it.”
I specialise in steering programs and projects where multiple workstreams have to work together, especially when the teams involved have never had to collaborate this closely before.
If you’ve voiced one of those concerns above lately…
Let’s talkThe Dokusha Reading Framework
Shaped by life inside Amazon, Disney+ and Singtel.
Three reads before any prescription.
-
Read the Program
Documentation audit and current-state mapping. What was the plan, and what is actually happening?
-
Read the People
Structured stakeholder interviews, broad then targeted. What do the people doing the work already know that hasn’t reached the top?
-
Read the Data
Metrics, timelines, decision logs, tested against the status-report narrative. Where do the numbers and the story diverge?
-
Write the Solution
A sequenced plan: what happens, who owns it, by when, and how you’ll know it worked. Not a list of observations.
That’s the Reading.
Then the work has to be run — by your team, or with me alongside them for a four-week Sprint or a twelve-week Arc.
Three ways to work together
-
4 weeks
Express Reading
One clearly named problem. For when you already know what is broken and need to know why, and what to do about it. Your team runs it from there — or add a Sprint on that same problem and I stay.
-
8 weeks
Reading + Sprint
A program-wide Reading, then four weeks working the plan with your team — cadence set, owners in place, things moving. For when you can tell something is wrong, can’t see it from the inside, and need momentum within two months.
-
16 weeks
Reading + Arc
The Reading, then twelve weeks alongside your team, shepherding the plan as it beds in. For when the program needs a steady hand for a full quarter: while you recruit, or while bigger changes take shape.
A previous engagement
A Singapore media company had to launch a new consumer app against a date that couldn’t move. When I joined, it was six weeks behind.
The working theory was people: someone not doing their job. Two weeks in, the reading said structure. Nobody clearly owned the key product track, and nobody was holding the vendor to its commitments. Over the following weeks, the same pattern showed program-wide — owners never assigned, decisions never made or raised, dependencies nobody tracked.
I advised the product lead on a reset with the vendor, facilitated the teams in agreeing who owned what, and gave the program meeting a weekly rhythm, agendas and follow-through.
- 6 weeks recovered in about three months — and the app met its hard deadline
- 463 actions, 71 decisions and 26 risks closed across 37 stakeholders and four product tracks, up to launch
- 3 hours → 1 from ad-hoc program meetings to a one-hour weekly
Organisation not named; details generalised. This work predates Dokusha World and shaped the framework it now uses.
Sound like what you’re dealing with?
Tell me what’s going on.
A first conversation is free, carries no obligation, and stays between us. If a Reading isn’t the right answer, I’ll say so.
I’ll reply within three working days to set up a time to talk.
All fields are required.
Questions
How do you price your work?
Every engagement is fixed-scope and fixed-fee, quoted after our first meeting. If you need me for longer, we add a Sprint.
Why not just hire a full-time PM?
You probably should. But hiring takes months, and you likely need to give the new PM time to find their feet. So the real question is: what does the wait cost you?
If it’s too much, I can get things moving now and keep them going until your hire starts. My settling-in is the Reading, and it ends with a plan.
What happens when we first meet?
We talk. About 45 minutes, in person.
I’ll run what librarians call a reference interview: working out what you actually need, which isn’t always what you first ask for. Then I’ll recommend the way forward, with a quote. If what you need isn’t what I can provide, I’ll tell you that too.
What do you need from us?
Three things: access to your documents, data and systems; time with the people closest to the work; and a team committed to changing course. The Reading is only as good as what I can observe and analyse — and what follows is only as good as your team’s commitment.
Who will I be working with?
Me. The person you talk to is the person who does the work.
Do you use AI?
Yes — for research, analysis, synthesis and drafting. The findings and recommendations are my own judgement, and confidentiality is built into my standard terms.
Who is this for — and who isn’t it for?
If you need your tech team, product, marketing, sales, customer service and everyone else moving together — yes, I’m your guy.
On tech projects, if you need someone to lead the technical work itself — system architecture, code, technical decisions — no, I’m not your guy.
If you’re in construction, building or property development and looking for a construction project management consultant, you’ll want a specialist firm. Not me.
What’s your project methodology?
The textbook answer: a hybrid of Waterfall and Agile.
The honest answer: whatever works.
The Reading doesn’t change — it’s how I find what’s actually wrong. How we run the work after that depends on your team, your deadline and what the Reading finds. Methodology matters, but it’s rarely what’s stalling a program. Together, we focus on what matters most.
What industries do you specialise in?
My methods travel, so it’s more about the problem you are facing and how we work on it together, not the industry you’re in.
That said, I’ve spent my career working in pop culture, the arts, media and entertainment, gaming, e-commerce and digital platforms, so that’s where I’m most at home.
About
I’m Peck Keong Goh, and I’ve been a reader for most of my life.
I studied English Literature, then worked as a film librarian, where I learned how to do a reference interview: the art of drawing out the question behind the question. After that came books and merch buying for Books Kinokuniya, then delivering Singapore Comic Con, then esports at Singtel, streaming at Disney+ and e-commerce at Amazon.
Along the way, I kept landing in work that had stalled or had never been done before — priorities unclear, people pulling in different directions, a date that couldn’t move. A GST change at Disney+ that needed five internal teams and an external partner ready on the same day, without a single subscriber noticing. A Black Friday Sale at Amazon Singapore that ran eight days for the first time, instead of the usual four. A sticky cross-team issue there that had sat unresolved for six months, cleared in two weeks once I mapped out who actually owned what. And the app launch in the case study above.
Different worlds, different functions, same role: read it properly, make it clear, sequence the work, get the right people pulling together, and keep it moving.
Dokusha is Japanese for “reader”. Reading is how I start. Making things happen is why I’m there.
PMP® · English · Mandarin (business) · Japanese (JLPT Level 2)
Outside work: Anime, manga, and a serious case of tsundoku with my collection of books, games and movies. Also, if I had a licence, I’d be a Gourmet Hunter.