Project stories

I believe every project has a story to tell.

It has beginnings, middles, and ends. It carries challenges, solutions, celebrations, and frustrations.

​

Most of all, it carries people (clients, architects, contractors,...) and the emotions that come with bringing a project to life.

That’s why I believe a simple description doesn’t do a project justice.

A project is so much more than a finished building.

Each one holds multiple stories, and those stories can be turned into content that connects. Not just a single piece describing the end result, but many smaller stories that show the process, the decisions, the problems solved, and the transformation along the way.

And this matters.

Because a potential client isn’t always interested in a specific project or a location. They’re interested in their own project, in seeing how their problems could be solved and their life improved. They need to see themselves reflected in a project story. And they need to be able to understand it, which is why clear, simple language is so important as well. 

A common mistake architects make is writing project descriptions for other architects. That means lots of jargon. But clients don’t talk like that. They most likely didn’t study design, and they don’t want to spend time trying to figure out complicated words.

The opportunity now is to take that same writing and shape it into stories that also speak directly to clients, showing not just what the project is, but how it changes lives.