Module 4b · Illustrated Walkthrough
Project Startup
The illustrated walkthrough — how a sold pursuit becomes a project you understand well enough to lead, and how the second story finds what the client will actually call success.
Module 4b throughline — You earn the right to lead a project by understanding the project you've stepped into — well enough to explain why every decision was made, take a view on whether it still holds, and say what winning will require.Synthesizing the pursuit
In Modules 2 and 3 you learned the project’s economics — the fee, the multiplier, backlog turning into cash. Before you can protect a dollar of it, one moment has to go right. Which moment — and what has to transfer in it?
The moment
A project becomes yours when you understand it
Picture a PM handed a project the week Programming and Schematic Design begin — the project’s first phase. They step into a fee they didn’t price, a scope they didn’t write, and promises they never heard made. Weeks later, while pricing Schematic Design, a roughly $40,000 gap surfaces — work everyone assumed was in scope, that nobody had actually logged. So here is the question the whole module turns on: when does a project actually become yours?
Stepping in isn’t a single calendar event — it’s a range. The earlier you engage, the more of the project you can still shape; your leverage is highest in pursuit and narrows toward delivery. So push to get in early — and wherever you step in, own what has already been decided.
Stepping in transfers two things at once: knowledge and accountability. The contract is the written half — scope, fee, terms. The pursuit team carries the rest: the verbal promises, the fee assumptions, the priorities the client only said out loud. Both halves must be actively pulled. One lives on the server; the other walks out the door when the pursuit team moves on.
?You’re assigned a project. The signed contract is on the server, and the pursuit team is still down the hall. Is reading the contract enough to take ownership?
Before it was yours
Every project clears a gate before it reaches you
That decision has a name at Grace — the Go / No-Go. It’s the gate every opportunity must pass through during Pursuit, well upstream of Contracting and your step-in. Clear the gate and the firm commits real time and money to winning the work. Don’t, and we walk away — on purpose — to spend that energy where we’re stronger. A “No-Go” isn’t a loss; it’s a discipline.
Project Managers benefit tremendously from the earliest reasonable involvement in the Pursuit stage. Where possible, advocate for earlier involvement to provide input into the project you will ultimately own.
The Go/No-Go is a gate inside the Pursuit stage. Only opportunities that clear it advance to Contracting, your step-in, and Delivery.
Here’s what matters for you as PM: you don’t make this call — but its result becomes yours to own. The Go/No-Go is led by the Principal in Charge, working in concert with Business Development — the Pursuit Manager and BD leadership. You may be invited to the table to weigh the delivery reality: can we staff it, schedule it, win it? When you are, give an honest read. But the call sits with the PIC and BD. Your job is to be aware and contributing, not to cast the deciding vote.
The gate scores an opportunity on three honest questions.
Relationship strength
Are we known to the owner / decision-maker — or walking in cold as a stranger?
Preparedness
Did we see this coming? Was it on our Top 10 list with a capture plan — or news to us when the RFQ dropped?
Qualifications & timing
Are we technically competitive for this work, and is there real time to prepare a tailored submission?
Here’s the actual tool, filled in as a worked example of how the chart scores a pursuit. Notice how the three factors above map to its rows.
| Relevant Factors | Factoring Scoring Scale | Score | |||
|---|---|---|---|---|---|
| NEGATIVE (0–1 POINTS) |
NEUTRAL (2 POINTS) |
POSITIVE (3 POINTS) |
|||
| Factor 1 Relationship strength |
Are we known by the Owner / Decision-Maker? | Unknown to this Owner / Decision-Maker (0) | Known, but not fully cultivated | Well-developed working relationship | 2 |
| Factor 2 Preparedness |
Is this the first we’ve heard of it? Was it on our “Top 10” List? | Didn’t know until the RFQ/RFP came out; unprepared (0) | Known or on Top 10 List, but no pre-sale meeting | On Top 10 List; capture plan completed | 3 |
| Factor 3 Qualifications & timing |
Do we meet the RFQ qualifications for portfolio and team? | Capable (1) | Can meet or exceed every requirement | Technically superior — our sweet spot | 3 |
| Does marketing have adequate time for a tailored submission? | One week or less to due date (0) | Two weeks or less to due date | Over 2 weeks to due date | 3 | |
| Total score | 11 | ||||
?You’re asked to sit in on the Go/No-Go for a project your team might deliver. Does that make the decision yours?
The Pursuit-stage process steps and the “who leads / your role” breakdown live in the Quick Reference, Card 1.
That’s the upstream view. Now zoom back to your desk — the project has cleared the gate, won the work, and landed with you. The question turns practical: what, exactly, do you now own?
The output
You're stepping into decisions, not a folder
You prove you've truly stepped in by producing one thing — an eight-field Project Ownership Review, recovered from the Marketing Folder and your PIC. Fill it and you can lead the project. Leave fields blank and you’re still guessing.
Why we chased it
What made this opportunity worth pursuing in the first place.
Why we won it
What differentiated Grace and earned the client’s decision.
What was promised
The scope and deliverables you’re now on the hook for.
What was assumed
The fee basis, staffing, and scope assumptions the price depends on.
What was priced
The fee — and where the margin actually sits.
What the client values most
The priorities carried out of pursuit, in the client’s own words.
What’s unclear, stale, or at risk
The gaps and outdated assumptions you can already see from where you stand.
What must be resolved before planning
The short list that has to close before planning advances.
Your step-in is complete when you can explain why it was chased, why it was won, what was sold, what assumptions the fee depends on, what the client expects, where the risk sits, and what must be clarified before planning advances.
Notice fields 7 and 8. Readiness isn’t knowing every answer — it’s naming the unknowns and owning their closure. The strongest PMs would rather pause a day stepping in than spend a month unwinding a misunderstanding in design.
The principle
Understand the decision, then take a view on it
As owner you carry two kinds of work, and confusing them is expensive. You LEAD the substance — the calls only judgment can make. You VERIFY the process — formatting, signatures, logs, standard Grace language — prepared and finalized with Admin. Hand the judgment to process and you’ve delegated the part that was yours. Drown in the process and you’ve stopped leading.
| Situation | You LEAD (judgment) | Verify / Admin (process) |
|---|---|---|
| Contract step-in | Confirm what was promised, what is unclear, what needs follow-up. | Confirm file location, executed agreement, naming, version control. |
| Scope assumptions | Determine what must be clarified before planning advances. | Maintain the checklist / step-in record. |
| Additional-service risk | Identify where sold scope may not match the expected effort. | Confirm template, log entry, approval path. |
| Client communication | Decide what the client needs to see, and when. | Format the update or meeting record consistently. |
| Fee / staffing | Interpret what the fee allows and where the risk sits. | Confirm the budget is loaded in BST. |
The full construction-phase version of this table — pay applications, change orders, closeout — is drilled in Module 11, where it lives in the Quick Reference. Here, the principle is the point.
?A scope item looks like it may exceed the effort that was sold. Admin offers to log it and move on. Is logging it enough?
Beyond the contract
The contract is the floor, not the finish line
Imagine a PM who delivered every line of the signed scope — on time, on budget, technically clean — and the client was lukewarm. The thing they cared about most never appeared in the contract, so it never got managed. That’s the trap: meet the floor and miss the point.
The signed scope — the minimum you must deliver. Manage only to this and you’ve achieved compliance.
The client’s real definition of success — usually higher than the contract, and never fully written in it. Reaching it is value creation.
The space between floor and finish line gets filled one of two ways. You presume — quietly steering value toward your own assumptions, often wrong. Or you get curious and ask.
?Your client is a hospital, so obviously infection control is their top priority. Do you still need to ask?
The tool
Six questions that find the finish line
Every gap has an owner. Before you bring a question to the client, check whether the answer is already somewhere you can go get it — from the Marketing Folder or a debrief with your PIC. If it is, confirm it. If it only exists with the client, discover it. The six questions below are how you discover the finish line — a deliberate set, each built to surface a different driver of value, grounded in how Grace clients actually define success.
“A year after these doors open, what has to be true for the people who use this space — and how will you know?”
“Who lives, works, heals, learns, or gathers here every day — and what do they need that they’d never put in a brief?”
“Where would ‘good enough’ be a failure — the few things we must protect at all costs?”
“When scope, schedule, and budget collide, which do you most want us to protect?”
“Beyond you, who has to believe this succeeded — and what will they judge it on?”
“How, and how often, do you want to hear from us — and what does a great update look like?”
Curiosity over presumption. Ask, then go quiet. The answer you didn’t expect is usually the one that matters most.
The payoff
Same scope, different value
Two PMs can step into the same signed scope and deliver very different value. One asks, early, what matters most to the client — a real priority that never made it into the contract — and plans around it. The other meets that priority as a late-stage crisis. Same paperwork. Very different value. The whole difference was a question.
Discovery is where you stop managing the document and start managing the outcome.
And the answers don’t stay in a notebook. Your planning work begins with three inputs — what was promised, what was assumed, and what the client values most. That is the raw material for Planning, and it is where Planning takes over. The contribution loop continues: value → outcomes → money → capacity → the firm’s future.
Remember the PM we opened with — blindsided weeks into Schematic Design by a $40,000 gap nobody had logged? That’s the price of never truly owning what you stepped into. So we can finally answer the question the module turned on: when does a project become yours? Not when it’s assigned, and not when the contract is signed — it becomes yours the moment you understand it: what was promised, what was assumed, and what the client truly values, surfaced when you step in instead of discovered in a crisis.
Understanding isn’t complete when your questions run out. It’s complete when your assumptions run out. That’s why you defend it — not to yourself, to your Principal — in a readiness ceremony: seven questions, four recovered from the record, two discovered from the client, one final check. Your Principal concedes when the evidence earns it.
Module 4b · Project Startup
“The Project Plan is not where ownership begins. It’s the evidence that ownership already happened.”
Carry the three inputs forward into the plan.