When you experience a project firsthand, your perspective changes.
There’s something interesting that happens with some projects: while you’re working on them, you look at them from the perspective of a specific need. There’s a goal to achieve, a deadline to meet, a series of decisions to make, and a result to deliver.
But sometimes, a project continues after it’s finished.
New conversations emerge. You get to know the people behind it. You discover the ecosystem it operates in. You gain a better understanding of why what you helped build exists in the first place.
And sometimes, you’re even invited to become part of it.
That’s what happened to us with Volcano Innovation Summit.
After developing their website, the Volcano team invited us to attend the 7th edition of the event, held from September 5–7 in Antigua Guatemala.
Accepting the invitation allowed us to see the project from a different perspective. We were no longer simply the people who had worked on its digital presence: we were part of the experience.
And that difference between building a project and experiencing it gave us an insight that we believe can apply to many other projects.
A Project Is Always Bigger Than the Deliverable
When we take on a project, it’s natural to focus on what we need to solve. In our case, the challenge was to develop the website for an international event that brings together entrepreneurs, investors, corporations, startups, and industry leaders from different countries.
The website had to communicate the event’s proposition, showcase speakers, organize the program, facilitate participation, and work properly across different devices.
But while we were developing the project, our focus was necessarily on the solution.
Being there allowed us to see everything that doesn’t appear in a brief.
People arriving from different countries. The conversations that take place. The spontaneous encounters. The opportunities that emerge between one activity and the next. The way a digital experience becomes part of an in-person experience.
The project was much bigger than the website we had developed.
And that is probably true of many projects.
The Challenge: Building a Digital Experience for a Complex Ecosystem
Volcano Summit needed a website capable of organizing a large amount of information while also conveying the event’s identity and scale.
It wasn’t simply a matter of aesthetics.
There were different audiences, different needs, and different possible journeys.
Someone might be looking for information about the speakers. Another person might need to check the program. A startup might be interested in Startup Avenue. An investor might be looking for networking opportunities. An international attendee might need practical information to plan their participation.
The challenge was to make all of those needs coexist within a single experience.
The Solution: Organizing Information to Make the Experience Simpler
We organized the content so that each visitor could quickly find what they needed and created a carefully crafted mobile experience. The website had a very specific purpose: to reduce the complexity of the event for those who weren’t there yet.
Before arriving, people could understand what they would find, who would be participating, and how to take part.
The website served as a first point of contact. And that made us think about something we try not to lose sight of: when we design a digital experience, we’re not only designing what happens on a screen. We’re designing what that experience enables to happen afterward.
The website fulfilled its role as an information and access point for the event.
But for us, another outcome emerged that wasn’t part of the project’s initial scope: the invitation to be part of the in-person experience.
And that may be one of the most interesting aspects of this type of project.
Not every outcome can be anticipated.
When a project is done well, it can lead to something that wasn’t included in the timeline or the initial brief.
It can build trust.
It can lead to a recommendation.
It can spark a new conversation.
It can connect us with people we didn’t have contact with before.
It can open the door to an industry or market we want to grow in.
It can even change the way we understand our own work.
When a Project Lets You See What You Couldn’t See Before
Taking part in Volcano allowed us to observe from the inside what we had previously known mainly through the information we needed to develop the website.
We saw the dynamics of the three-day event, the diversity of profiles, the activity around the talks, and, above all, the value of the conversations that emerge when people with different interests share the same space.
That changed our perception of the project.
But there’s something even more interesting: this isn’t unique to Volcano.
It can happen with any project.
A visual identity can end up supporting a brand in a market that wasn’t originally part of the plan.
A website can connect a company with a new type of client. A campaign can start a conversation with someone who eventually becomes a strategic partner.
A presentation can lead to a meeting.
A meeting can lead to a project.
And a project can take us somewhere we never imagined when we started.
What Happens When We Look at Our Projects This Way?
Perhaps one of the best questions we can ask ourselves when a project is finished isn’t simply: Did it work?
We can also ask ourselves:
What else could it generate?
Who did it allow us to meet?
What did we learn that we didn’t know before?
What conversation did it bring us into?
What doors could it open?
What other projects could it connect with?
What ecosystem does it bring us closer to?
This doesn’t mean expecting every project to turn into a major opportunity.
It means recognizing that projects can have a life beyond the final delivery. And that many times, the most interesting outcomes emerge precisely there.
A Project Can Be the Beginning of Something We Don’t Know Yet
The invitation to participate in Volcano Summit was, for us, an opportunity to experience the project firsthand. And perhaps the most valuable takeaway is remembering that every project we develop can have a reach that we don’t yet know when we begin.
We can deliver a website, a visual identity, a campaign, a strategy, or a piece of communication with a specific goal in mind. And that’s perfectly fine.
We need objectives, metrics, and results.
But we can also leave room for something less predictable: the relationships, learnings, and opportunities that may emerge around that work.
Because a project doesn’t always end when we deliver what we were asked to create.
Sometimes, that’s precisely when something new begins to happen.
And that’s how we like to look at projects: not only asking ourselves what we’re going to deliver, but also what could happen next.
