Onsite #1 · Live Kickoff · 6 hours

Design that Defines. Impact that Endures.

The live kickoff where the firm sets one standard for project delivery — and names the leader who owns it.

Onsite overview · the three core behaviors · the five outcomes · how to prepare
1

The mandate

Before the first module, we decide one thing together: what “good” looks like.

Until now, the quality of a GRACE project has depended on the internal processes established within our offices and teams over many years. These have served us well — they have propelled the performance that brought us to our current state. Although somewhat different, they share one common theme: the desire to produce high-quality work for valued clients, and to do it in a way that drives our business forward. That mandate remains our mandate today.

To solidify our identity and codify our brand experience across the firm, we aim to replace legacy approaches with a standard. And a standard only means something if the firm builds it together and someone owns it on every project.

Standards are tricky. To many, they signal constrained processes, checklists, endless procedures — busy work that takes us away from what makes us great. We aim to break that mold here by standardizing one core idea: what does Project Delivery Excellence look like, and what are the core behaviors and outcomes that reliably produce it?

Onsite #1 is where that starts. In one room, in one day, we define firm-wide intent — what great delivery looks like at GRACE — and we name who is accountable for protecting it: the Project Manager. Not a coordinator who moves paper between people, but the Accountable Owner of the outcome, delivered through a set of leadership behaviors that drive results.

“Design that Defines. Impact that Endures.” is the promise. A repeatable standard, owned on every project, is how we keep it.

2

What the day is built on

Strip away the tools and the standard is three behaviors.

Project Delivery Excellence isn’t a binder. It reduces to three behaviors the Project Manager owns on every project. The day is built on them — one per working block — and so is the program that follows.

Core Behavior I

Establishing Clarity

Define the finish line before the team takes the first step: scope, fee, the strategic plan, the contract, and a single client liaison — settled before work advances.

Is your project’s finish line defined, or assumed?
Core Behavior II

Controlling Advancement

Own the daily momentum of the work: client budgets, schedules, program, and team assignments held on track — not discovered off it.

Do you steer your burn each week, or hear about it at review?
Core Behavior III

Protecting Integrity

Guard technical and professional quality to the end: code compliance, consultant and model coordination, constructability, and documentation that keep the project insurable.

Where would a quality miss surface on your project first?

These aren’t abstractions. Clarity defines scope and aligns commitments; Advancement keeps delivery controlled and predictable; Integrity protects the design and technical work. Practiced together, and through people, they compound into a financially healthy firm and stronger teams — the outcomes we go to next.

3

What good produces

Five outcomes the firm is investing in.

The behaviors exist to produce results. These are the five the program is built to deliver — each one tied directly to how the firm performs.

4

Run-of-show

From a shared standard, to the real gaps, to your own commitment.

The day moves in three arcs — build the standard together, surface the gaps honestly, then make it personal. Here’s the shape of the day.

9:00–9:25Open

Welcome & the mandate

Why we’re here, how the day runs, and one shared standard for what good looks like. Meet your table and take a quick baseline self-rating.

9:25–10:00Warm-up

Best & worst projects

Surface what you’ve lived — the projects that soared and the ones that sank — and what made the difference.

10:00–10:10Break

Break

Stretch and reset.

10:10–11:25Block 1

Sort the role, discover the behaviors

Build the PM role from the work itself, then uncover the three behaviors that separate great delivery from the rest.

11:25–12:00Block 2

Gap & tool inventory

Map honestly where today’s process and tools fall short — and leave with each priority gap named and owned.

12:00–1:00Lunch

Lunch

Transition and networking.

1:00–1:20Re-energize

Recall game

A fast, low-stakes reset that locks in the morning.

1:20–1:55Business

The business stream

Why the PM owns the financial result — and the few levers you actually steer.

1:55–2:05Break

Break

Stretch and reset.

2:05–2:35Practice

Your throughline project

Frame the real project you’ll carry through all twelve modules — its numbers, its open decision, its weak spot.

2:35–3:25Stakes

Goals & peer pods

Set two or three specific goals tied to the behaviors and your project, and form the pod that holds you to them.

3:25–4:00Close

Close & commitment

How the next sixteen weeks run, and your commitment — said out loud to the people who’ll hold you to it.

Schedule shown is the working plan; final times confirmed before the session.

5

Before you arrive

Bring one real project. We’ll use it all program long.

Choose a through-line project — one active project you’ll carry through all twelve modules and test every standard against. The behaviors only mean something applied to real work.

Do before the day

  • Choose your through-line project — active, real, and yours to steer.
  • Know its numbers — fee, current burn, schedule status, and team.
  • Name the open decision — the one call on it you can’t currently make.
  • Locate where it’s least clear — scope, integrity, or advancement.

Bring to the room

  • Your project’s numbers and current schedule.
  • A laptop or notebook for capture.
  • Your hardest current project problem.
  • Readiness to be challenged on what you already “know.”
6

What you’ll leave with

A standard, two maps, and your name on the outcome.

The day produces two tools the firm builds together: a Project Process Map (how a GRACE project actually flows) and a Project Responsibility Map (who owns what, at each step). You build them — so you’ll defend them. The PM Excellence Scorecard is how the standard is reinforced after today.

Your reference for both is the live Lifecycle Map. On it the three core behaviors run across the lifecycle — Clarity up front, Advancement & Integrity through execution — while the three streams (Client, Team & Business) run down every phase. Three views: Leadership Outcomes (what good looks like), PM Responsibilities (who owns what), and the Project Manager Playbook, with every Grace tool and template linked.

The throughline of the role is simple: lead the workflow, don’t do everyone’s work. Leverage your SMEs and the Administrative Project Coordinator. Own the outcome, not the paperwork.

Design that Defines, and Impact that Endures, starts with how you run the next project. That’s yours to own.