The signs tend to show up before anyone can name what's causing them.
Symptom · 01
The date was tight on day one. It's tighter now.
Each status report moves a milestone by a week or two. Work that wasn't in the plan keeps landing, so there's no room left for the next surprise. The date matters for a reason, which is why longer days have been covering the gap.
Symptom · 02
Your best people are named to the project. Their regular jobs never stopped.
The project was added to jobs that were already full. Whatever can't wait until tomorrow gets their hours first. The plan still counts on time that keeps not arriving.
Symptom · 03
Everyone agreed to it. The work still isn't done.
The same items show the same status from one update to the next. Ask about one and you get a good reason and a new date. Since nobody has said no, a commitment that's stuck looks just like one that's running late.
Symptom · 04
The person leading it answers for decisions they don't get to make.
Nearly every decision the project depends on, from spending to who can be pulled onto the work, needs someone else's sign-off. Each one waits a while, though to whoever signs off, each one looks small. Added up, those waits are where the schedule went. If you're the one leading it, answering for decisions other people make is exhausting.
↳ What's underneath
These are signs, not causes. Any one of them can come from several places. Most struggling projects have more than one cause at work. A fix aimed at the wrong one still costs the time and the money. Knowing which ones are running on yours, and which to take on first, is the hard part.
§ Section III
How we read a conversation.
Five layers, every interview. The diagnosis lives in how they line up.
Surveys ask what people think. We read what each person says, what they hedge, what they skip and what they bring up without being asked. Then we read all the conversations together, because the same problem often shows up in different words from different seats.
L01
Verbal Tells
The words themselves.
Hedging about things in the speaker's own area.
Absolutes. "This will never work." "Everyone knows."
Sarcasm and dark humor as sideways truth.
Ownership language, like "leadership wants this" against "we need this."
Whether the sponsor comes up as "we," as "they" or not at all.
L02
Movement Tells
Where an answer goes.
An answer that circles before it lands.
Specifics that turn general as the question gets closer to home.
Qualifiers that stack up on one subject and nowhere else.
The real point arriving after the answer seemed finished.
L03
Structural Tells
What they don't say.
Topic avoidance. What people steer away from.
Silence on a subject everyone else raised.
Short answers in places that warrant long ones.
A subject that never comes up from the people closest to it.
L04
Behavioral Tells
The paper-vs-reality gap.
A meeting or process that exists, described as if it doesn't matter.
Staffing that doesn't match the stated priority.
Who's missing from the conversations about a project they own.
Commitments that are solid on paper and thin in practice.
L05
Across Interviews
Where the diagnosis lives.
Frequency and intensity across ten interviews.
Where accounts from different levels don't match.
Which patterns show up together, and which one sets off the next.
Different words from different people, describing the same thing.
This is what we listen for. The full analytical engine is proprietary, built on twenty-five years of project rescues.
When to run a Pulse Check. Each moment carries a different cost of waiting.
IN TROUBLE
Rescue.
Find what's actually broken. Get the specific roadmap to fix it, in the order that matters most. Past the cheap fixes, but never past fixing.
WHILE IT'S RUNNING
Health check.
An independent read on a project already underway, whether or not anything looks wrong yet. You'll see what's holding and what's quietly drifting, with a clear roadmap to adjust while the corrections are still small.
BEFORE KICKOFF
Prevention.
The patterns that derail projects often take hold before launch. Name them now, while it's cheapest, and you start with a roadmap built to keep them from setting in.
Whichever moment you're in, the Comprehensive Pulse Check works the same way. You get a clear diagnosis and a detailed roadmap your own team runs. The earlier you start, the more leverage it has.
§ Section V
The free Pulse Check.
Start with the free Pulse Check. See it for yourself.
After one confidential call of up to thirty minutes, you'll know more about your project than you do now.
STEP 01
A single confidential call
Just you, one-on-one, answering questions about what kind of project it is, what stage it's at, what's not working and what's worrying you.
STEP 02
Our read on your situation
Shortly after the call. The email names the likely patterns at work in your situation and tells you plainly whether a Comprehensive Pulse Check would help, and what you'd learn from it. If it's not the right fit, we point you toward the kind of help that is.
STEP 03
Decide what’s next
You'll know what a Comprehensive Pulse Check would tell you and whether it's worth doing. Then you decide. No pitch, no pressure.
What you’ll walk away with
What you get depends on where you stand. Nobody leaves empty-handed.
If the call is yours to act on
A meaningful read on the patterns likely at play in your project, and a clear picture of exactly what a Comprehensive Pulse Check would tell you.
If you’re raising the flag
The same read on what's likely going on, plus language to take it to the people who hold the budget and the decision.
If we’re not your answer
A different way to look at your situation and a pointer toward the kind of help that actually fits. No pretending we're the right fit when we're not.
What this isn’t
This isn’t a diagnosis. One conversation can’t deliver one. It’s a first read, sharp enough to tell you what to do next.
A major system or integration project is one of the larger investments a company makes. This buys you a clear read on what's in the way and the specific roadmap to correct it with your own team.
§ Section VII
Why I built this.
Founder note · Davina Eccard
Twenty-five years of walking into failing projects.
I should have put a couch in my office.
By the time a company called me, I was as much therapist as consultant. The project lead was usually doing two jobs while operations still had to run every day.
Every one of those projects had clues hiding in plain sight. Expectations nobody said out loud. Updates that stayed upbeat after the concerns stopped coming. Agreement that never turned into done. Decisions waiting on a sponsor with too much else on their plate. I learned to spot them. Then I learned what to do about them.
A Fortune 500 with a big project going sideways.
Stressful for the team. The company barely notices. Clients still get served. The stock stays oblivious.
A $30M company with a major project struggling.
Nobody's free to pick up the slack. Every dollar hits harder. Every week of delay compounds. Growth stalls. Reputation slips. The good people start polishing résumés.
I launched, grew and sold a mid-sized business of my own. I know what it's like making decisions with real money and no margin for error.
So I built a platform grounded in twenty-five years of those patterns. It runs confidential interviews across every level of the project and reads them the way I learned to. Then you get a clear read on what's in the way and a roadmap your own team can run. What I found, over and over, was that the trouble sat in how decisions got made and how the work got staffed, not in the software.
Earlier is cheaper, but a project already in trouble is still fixable. The fastest way back starts with knowing exactly what to fix.
Davina Eccard
Founder, Project Pulse Check
Practice
Outta the Weeds, LLC
Twenty-five years inside struggling projects.
Focus
Companies where the project and the business run on the same people. ERP, CRM, automation, AI, M&A integration.
§ Section VIII
What buyers ask first.
Frequently asked questions.
How confidential are the interviews, really?
Completely. Each interview is one-on-one. No one else listens. For frontline interviews, the managers of each affected area nominate a pool, and the system draws from it, so no one picks who's interviewed.
The report describes the underlying issues and what to do about them. It doesn't quote anyone or attribute anything to a person, by name or by role, so you never learn who said what.
Will people really talk openly with an AI?
Most people choose their words a little when the person asking can affect their job. That's true at every level, and it's ordinary. Our interviews come from outside your company, from an AI with no part in anyone's review, pay or schedule. Every interview is a phone call, on a mobile or a landline, so nobody needs a computer or an app.
How is our data protected?
Interviews are transcribed, not recorded. The report goes to you. Nothing said in an interview goes to your vendors, your consultants or anyone at your company. Your data is yours.
Can we actually fix this ourselves, or will we need consultants?
The roadmap is built so you can run it with your own team. Every action names who should own it and when to take it on.
You'll have what you need to move without bringing anyone else in.
How long does it take?
Free Pulse Check: a call of up to thirty minutes, with our read on your situation by email shortly after.
Comprehensive Pulse Check: timing depends on how quickly your ten participants book their interviews. The roadmap lands within 24 hours of the final interview.
What if it doesn't work? What if we can't turn this around?
Every project can be turned around. What changes is how much it takes.
The roadmap draws on twenty-five years of real project rescues, not a framework from a textbook. Some of it asks for uncomfortable things, like clear accountability, different decision rights or naming a dynamic out loud. The earlier those changes start, the less they cost.
§ Begin
Find out which patterns are actually at play on your project.
Once you know what's in the way, you know where to start. A free call of up to thirty minutes gets you a first read on what's slowing your project.