How to Gather Great AEC Case Studies (Even When Your Project Teams Are Busy)
Every AEC firm has them: great projects that never become great case studies. The project was complex. The team solved a difficult problem. The client was thrilled. Maybe there was even an innovative approach or a result worth really publicizing.
But when marketing asks for the project information, what comes back?
“Here’s the project description from the proposal.”
Or worse: a few bullet points, a project name, and a promise to “send more later.”
The challenge usually isn't a lack of good stories. It's that the people who know those stories best are busy designing, building, managing, and delivering their NEXT project. So how do you get the good stuff out of their heads and turn it into content that is useful for marketing, business development, and your audience?
It starts with asking better questions.
Stop Asking for a Case Study
One of the easiest ways to make a technical team member avoid marketing is to send them a blank document and ask them to “write a case study.” They don't know how long it should be. They don't know what information you need. And they probably don't think of themselves as a writer.
Instead, make it a conversation. A 20-minute interview can uncover far more useful information than a request for a 500-word project description. And don't start with, “Tell me about the project.”
Start with questions that make people remember the story:
What was the client struggling with when you got involved?
What made this project harder than it initially appeared?
Was there a moment when the team had to rethink its approach?
What was something you solved that the client may not have even realized was a problem?
What are you most proud of?
What would have happened if the team hadn't addressed this issue?
What did you learn that you would apply to the next project?
Those questions get you past the facts and into the story.
Look for the Stories Hiding in Plain Sight
Some of the best case studies aren't the projects with the biggest budgets or the flashiest photos. They are the projects with a problem worth solving.
Maybe a team had to work within an unusually tight site. Maybe a project stayed operational throughout construction. Maybe an owner had a very aggressive schedule. Maybe a design decision saved money, improved functionality, or prevented a much bigger problem later.
Those details can easily get overlooked because they're second nature to the people who worked on the project. That's where marketing can add real value.
A technical expert might say, “We just redesigned the system to accommodate the existing conditions.”
A marketer hears:
“The existing conditions created a problem that could have delayed the project, so the team developed a solution that kept the project moving.”
Same project. Better story. The goal isn't to exaggerate the work. It's to uncover the significance that may be obvious to the project team but isn't obvious to everyone else.
Try These Less-Obvious Ways to Gather Information
Interviews aren't the only way to collect great case study content.
1. Ask for the project “postmortem.”
After a project wraps up, ask the team: What surprised you?
This often produces better content than asking what went well. Unexpected challenges, changes in scope, unusual site conditions, or creative solutions can become the most compelling parts of a story.
2. Look through the old pursuit.
The original proposal can tell you what the client cared about before the project began. Compare that with what actually happened.
Did the team's priorities change? Did the project solve a different problem than originally anticipated? Did the firm bring a capability to the project that became particularly important?
3. Ask the project manager what they tell their coworkers.
This is one of my favorite questions: “If another project manager asked you about this project, what would you tell them?”
You'll often get a much more candid answer than you would from a formal questionnaire.
4. Talk to someone who wasn't the project lead.
A project architect, engineer, coordinator, superintendent, or junior team member may notice something completely different. Sometimes the most interesting story isn't the one the project leader thinks is most important.
5. Mine your award submissions.
Awards submissions are a gold mine of case study content. they often already contain the challenge, solution, innovation, collaboration, and results—just written for a different audience.
Don't let that content live and die in an awards folder.
How to Write for the Technical Expert - and Everyone Else
AEC case studies have a tricky job. They need enough technical substance to demonstrate credibility to someone who understands the work, but they also need to be accessible to someone who doesn't. The answer isn't to remove the technical details. It's to give those details context.
Instead of:
“The team implemented a centralized building automation system integrating HVAC controls across 14 zones.”
Try:
“Because the facility needed to operate efficiently across 14 distinct zones, the team developed a centralized controls strategy that gave the owner greater visibility and control over building performance.”
The technical detail is still there. But now the reader understands why it matters.
A strong case study should answer three questions:
What was the challenge?
What problem, constraint, or opportunity did the client face?
What did your team do about it?
What was your approach—and what made it different?
Why does it matter?
What changed as a result? What did the client gain? What makes this experience relevant to future clients?
Don't Let the Case Study End on Your Website
Once you've done the hard work of gathering and writing the story, don't use it once and forget about it. A good case study is an evergreen content asset.
One project can become:
A full website case study
A proposal project description
A LinkedIn post
A project spotlight
A blog article
An award submission
A conference presentation
A newsletter feature
A client success story
A recruiting post
A sales presentation slide
A capabilities brochure
A short video or interview
A series of social posts focused on different aspects of the project
You can even pull individual lessons from a project and turn them into thought leadership.
For example, a healthcare project that required the facility to remain operational during construction could become a LinkedIn post about phasing strategies, a blog about minimizing disruption, and a proposal example demonstrating your firm's experience working in occupied facilities. One project. Multiple stories. Multiple audiences.
Build a Case Study Habit, Not a Case Study Scramble
The best time to gather project stories isn't six months after the project closes when everyone has moved on to something else. Build information gathering into your process.
At project milestones, capture:
The original challenge
Major decisions
Unexpected obstacles
Innovative solutions
Client feedback
Project outcomes
Photos and visuals
Lessons learned
You don't need a polished case study every time. You just need enough information that when marketing is ready to tell the story, the story hasn't been forgotten.
Your Technical Teams Have the Stories. Marketing's Job Is to Find Them.
The best AEC case studies aren't necessarily the ones with the most impressive statistics. They're the ones that make someone think: “That's exactly the kind of problem we're dealing with.”
Your project teams already have the expertise. They know the challenges, the decisions, the near-misses, the creative solutions, and the moments when everything came together. The job of marketing isn't to turn them into writers. It's to ask the questions that uncover the story, and then translate that expertise into something your clients, prospects, partners, recruits, and industry peers can understand and remember.