Module 4b · Illustrated Walkthrough
Project Startup
The illustrated walkthrough: how a sold pursuit becomes a project a manager understands well enough to lead, and how the second story finds what the client will actually call success.
Module 4b throughline: A project manager earns the right to lead a project by understanding the project that has already been handed over, 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 the manager’s when the manager understands it
Consider a PM handed a project the week Programming and Schematic Design begin, the project’s first phase, stepping into a fee they did not price, a scope they did not 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. This is the question the whole module turns on: when does a project actually become the manager’s to lead?
Stepping in covers a range of moments rather than a single calendar event. The earlier a project manager engages, the more of the project can still be shaped, since leverage is highest in pursuit and narrows steadily toward delivery. A project manager shall push to engage early, and shall own what has already been decided at whatever point the step-in occurs.
Stepping in transfers two things at once: knowledge and accountability. The contract is the written half, covering scope, fee, and terms, and the pursuit team carries the rest, the verbal promises, the fee assumptions, and the priorities the client only said out loud. Both halves must be actively pulled, since one half lives on the server and the other leaves with the pursuit team when its members move on to the next opportunity.
?You are 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 the assignment
What happens before a project reaches a project manager?
That decision has a name at Grace, the Go / No-Go, the review every opportunity must pass through during Pursuit, well upstream of Contracting and the step-in. Clear the review and the firm commits real time and money to winning the work. Fail to clear it and the firm walks away on purpose, to spend that energy where Grace is stronger. A “No-Go” is a discipline rather than a loss.
Project Managers benefit tremendously from the earliest reasonable involvement in the Pursuit stage. Where possible, a project manager shall advocate for earlier involvement and provide input into the project they will ultimately own.
The Go/No-Go is a review inside the Pursuit stage. Only opportunities that clear it advance to Contracting, the step-in, and Delivery.
What matters for the project manager is this: the project manager does not make this call, and its result still becomes theirs 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. A project manager may be invited to the table to weigh the delivery reality: whether the firm can staff it, schedule it, and win it. When invited, a project manager gives an honest read, although the call still sits with the PIC and BD. The project manager’s job is to be aware and contributing, not to cast the deciding vote.
The review 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?
Consider the actual tool, filled in as a worked example of how the chart scores a pursuit, with the three factors above mapping directly to its rows.
| Relevant Factors | Factoring Scoring Scale | Score | |||
|---|---|---|---|---|---|
| NEGATIVE (0 to 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 have heard of it? Was it on our “Top 10” List? | Did not 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 are 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. Common questions on the review, covering the hotline, cross-studio coordination, and who has final say, are answered in the Pursuit & Go/No-Go FAQ.
That is the upstream view. The assigned project has now cleared the review, the firm has won the work, and the project has landed with a project manager. The question turns practical: what, exactly, does the project manager now own?
The output
What is a project manager actually stepping into?
A project manager proves a completed step-in by producing one thing, an eight-field Project Ownership Review, recovered from the Marketing Folder and the PIC. A completed review allows a project manager to lead the project, and blank fields leave the project manager 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 now owed to the client.
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 is unclear, stale, or at risk
The gaps and outdated assumptions already visible at step-in.
What must be resolved before planning
The short list that has to close before planning advances.
The step-in is complete when a project manager 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, where readiness rests on 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
What does a project manager lead, and what does a project manager verify?
The owner of a project carries two kinds of work, and confusing them is expensive. One is to LEAD the substance, the calls only judgment can make, and the other is to VERIFY the process, including formatting, signatures, logs, and standard Grace language, prepared and finalized with Admin. A project manager who hands the judgment to process has delegated the part that belonged to the role. A project manager consumed by process has stopped leading.
| Situation | 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, covering pay applications, change orders, and closeout, is drilled in Module 11, where it lives in the Quick Reference, and 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
Why is the signed contract only the floor?
Consider a PM who delivered every line of the signed scope, on time, on budget, technically clean, and the client was lukewarm. The thing the client cared about most never appeared in the contract, so it never got managed. That is the trap: meet the floor and miss the finish line.
The signed scope, the minimum that must be delivered. Managing only to this achieves 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. A project manager can presume, quietly steering value toward assumptions that are often wrong, or a project manager can 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
Which six questions find the finish line?
Every gap has an owner. Before a question goes to the client, a project manager checks whether the answer already sits somewhere retrievable, in the Marketing Folder or in a debrief with the PIC. If it does, confirm it, and if it only exists with the client, discover it. The six questions below are how a project manager discovers 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 would 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, because the unexpected answer is usually the one that matters most.
The payoff
Why does the same scope produce 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, while the other meets that same priority as a late-stage crisis. Same paperwork, very different value. The whole difference was a question.
Discovery is where a project manager stops managing the document and starts managing the outcome.
The answers do not stay in a notebook, since 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.
Recall the PM this walkthrough opened with, blindsided weeks into Schematic Design by a $40,000 gap that nobody had logged. That is the price of never truly owning the project handed over. The question the module turned on can finally be answered: when does a project become the manager’s to lead? Assignment does not make it so, and neither does contract signature. A project becomes the manager’s at the moment the manager comes to understand it: what was promised, what was assumed, and what the client truly values, surfaced at step-in rather than discovered in a crisis.
Understanding is complete when the assumptions run out, and not merely when the questions run out. A project manager defends that understanding to the Principal in a readiness ceremony: seven questions, four recovered from the record, two discovered from the client, one final check. The Principal concedes when the evidence earns it.
Module 4b · Project Startup
“The Project Plan is the evidence that ownership already happened, rather than the place where ownership begins.”
Carry the three inputs forward into the plan.