A free, burnout resilience newsletter for Architects. One actionable tactic each week to help you overcome chronic burnout, engineer self-awareness, and build a thriving career in architecture.
Stop drawing for a perfect world ✏️ 📐
Published 2 months ago • 6 min read
Did someone forward this to you? Join our valued community of ambitious Architect subscribers. Learn more→
June 22, 2026
Hey, Architect.
Your construction documents are wrong the moment the contractor opens them.
Not because you made a mistake. Because you can’t account for everything.
No set of drawings, no matter how detailed, can anticipate every condition a project will encounter in the real world.
A wall doesn’t line up the way you assumed.
A material gets discontinued mid-construction.
The contractor finds something in the field that no amount of pre-design investigation could have caught.
You’ve been here. Staring at an RFI that tells you the drawing said one thing, but the world is saying another.
Most of us respond to that gap by drawing harder.
More detail, more notes, more coordination meetings. And when we’re not in the room to make the call ourselves, our team gets stuck. Not because they’re incapable, but because nobody ever told them what success actually means here, beyond “follow the drawings exactly.”
I’ve been reading “Made to Stick,” a phenomenal book by Chip and Dan Heath about the power of communicating ideas clearly.
One concept from the book stopped me cold—the commander’s intent.
In the 1980s, the U.S. military realized its operational plans had become so complex that, once soldiers hit the field, the plans fell apart and nobody knew how to adapt.
How did they solve the issue?
They built a framework that travels with every plan: a clear statement of purpose, a short list of key tasks, and a description of the end state.
Together, those three things tell a soldier what to accomplish and why, without locking them into a rigid sequence of steps. If the plan failed in five different ways but that purpose and end state still held, the mission was a success. Soldiers in the field could make their own calls under pressure, because they knew the target they were aiming at, not just the steps they were supposed to follow.
Today I want to walk through:
Purpose: the why behind your project, and why your drawings can’t carry it alone
Key tasks: the small set of broad actions your team owns, not a step-by-step procedure
End state: what “done right” actually looks like when the project is finished
Let’s get into it.
1. Purpose: the why behind the project
Before scope, schedule, and budget, your team needs to understand why this project matters, not just what it includes.
Purpose explains how this effort fits into the bigger picture, so a decision made under pressure can be checked against the reason the project exists in the first place.
Years ago, my team kicked off an office renovation with a design meeting. We reviewed the schedule, walked through deliverables, and everyone went their own way to start designing. We each assumed the other designers were checking in with us as conflicts came up.
They weren’t.
Early in construction, an RFI (Request for Information) surfaced a conflict in the main lobby, one of the most visible spaces in the building.
The interior designers had laid out ceiling baffles. The fire protection engineer had laid out sprinkler heads. Neither one asked the other about spacing, and a broken link between their Revit models meant the clash never showed up in coordination.
The Building Code required a specific distance between baffles and sprinklers to ensure adequate coverage in the event of a fire. We found out we’d missed it in a contractor’s RFI, weeks after contracts were signed and scope costs were locked in.
The solution—revisit the Code, recalculate distances, get on a coordination call, change several drawings (ceiling plans, sprinkler layouts, lighting plans, etc.), issue a bunch of sketches, request costs from the contractor for the changes.
Hours of extra effort, tracking, and explanations to the Owner because we didn’t communicate better with our team.
Nobody on that team did anything outrageously wrong as individuals. They were working in their own lanes, just trying to get their work done.
What was missing was a stated purpose at the beginning.
Something like “the lobby is the client’s signature space, and every system in it gets reviewed against every other system before it leaves this office.” That single line would have told two designers why their layouts needed to talk to each other, not just that they did.
If you're an Ambitious Architect: The next time you kick off a project, write your purpose statement first, before your first sketch. One or two sentences. Pin it to the top of your design narrative and your OACM meeting notes.
2. Key Tasks: the what, not the how
Purpose tells your team why the project matters. Key tasks tell them what has to get done to make it real.
This is also the part of the framework people get wrong most often.
Why?
Because key tasks are three to five broad actions rather than a sequence of steps.
A key task isn’t “submit the lobby ceiling RCP by Friday.” It’s “coordinate every overhead system in the lobby before issuing for construction.” The first is an instruction. The second is an outcome, and your team gets to decide how they reach it.
This distinction is what gives your team room to adapt.
A plan with no flexibility built in is a hope, not a plan.
If you hand someone a checklist of steps, they’re stuck the moment reality doesn’t match the checklist.
If you hand them a short list of outcomes they own, they can rearrange their own day, solve a problem you never anticipated, and still land exactly where the project needed them to.
If you're an Ambitious Architect: Write 3-5 key tasks for your next phase as outcomes, not instructions. If a task reads like a single to-do item, rewrite it until it reads like something a teammate could achieve five different ways.
3. End State: what right looks like
It may not always be clear in the moment what success looks like.
A submittal gets value-engineered. A finish gets substituted. A schedule gets compressed.
None of that has to mean the project failed, as long as everyone can describe the same end state and ask: Does this decision still get us there?
End state is the plain description of what’s true when the project is actually done well, separate from your construction documents:
Example: The lobby reads as the client’s signature space, every system in it was coordinated before issuing for construction, nothing got value-engineered out of the parts that mattered.
That description is what gives you and your team a fast, shared way to evaluate change in the moment, instead of every decision landing back on your desk as a fire drill.
Final Thoughts
Your drawings are a best effort at a moment in time, not a guarantee.
The gap between the plan and the field is where most project stress actually lives, and it’s rarely because your team is careless.
On that office renovation, every individual designer did their job well. What was missing was a shared purpose, a clear key task, and an end state everyone could picture. The kind of thing that would have made one designer pick up the phone and call another.
Here’s what you learned today:
Purpose tells your team why the project matters, not just what’s in scope
Key tasks are 3-5 broad outcomes your team owns, never a step-by-step procedure
End state gives everyone a shared picture to check decisions against when something changes
Your Resilient Next Step (One Small Way to Build Resilience in Your Archi-Life Right Now 🧱)
Before your next project kickoff, write three things:
One sentence of purpose
3-5 key tasks framed as outcomes
One short description of your end state.
Share all three with your team before the drawings go out, not after something goes wrong.
To make this easier for you, I've developed a 1-page worksheet (with instructions).
→ For daily(ish) insights on burnout resilience, follow me on LinkedIn → Forwarded this email? Sign up here.
And whenever you’re ready, there are 3 other ways I can help you:
Speaking at Your Firm or Event: Bring these conversations to your workplace with workshops tailored to your team's specific challenges
1-on-1 Coaching: Work directly with me to develop personalized strategies for sustainable practice and career longevity.
Monthly Q&A: Have a question about burnout or your Archi-life? Submit it, and I'll try to answer it in an upcoming issue of The Resilient Architect Newsletter!
A free, burnout resilience newsletter for Architects. One actionable tactic each week to help you overcome chronic burnout, engineer self-awareness, and build a thriving career in architecture.