Issue #115•
•10m read

Intentional Environments

I’ve lived in Florida for nearly 24 years. And my wife has been here even longer. I went to school in Orlando and stayed here for my career and family. But, with my step-daughter graduating high school and heading off to school next year, it’s the perfect moment for us to make a move. My boys are at the right age for it. We’ve always dreamed of living in New York City, so we’re selling our house and car and moving to Brooklyn. It’s a major change, but we’re so excited for a new adventure—for a chance to simplify our way of living and start fresh again.

I’ve been thinking a lot about physical spaces and how we experience them. Think about your living room. I bet there’s a sofa or some kind of seating, a coffee table, and a TV or entertainment center. I suspect, like me, you decorate your house the way we’ve all grown accustomed to because of societal norms. I like to do things against the grain, but I still fall into the same decorating pattern. We let the aggregation of components dictate our experiences instead of letting them emerge from the interactions and relationships we have with the environment. When you move, you move with your things. They are the components carried over without the understanding of the relationships you’ll have with them in the new environment.

Familiarity limits possibility

Every living room I’ve had contains seating and a TV. I find it exceptionally difficult to envision a living room arranged in another way. Sure, you could shuffle the seating arrangement and type of furniture, but the core components would still remain.

We do it because it’s familiar.

It’s the mental model we have.

Think about software. When I design an interface, I’m pulling from existing mental models I have—the software I’ve used and can recall performing similar functions. Design begins with gathering inspiration. It’s the prior art to build from. It’s familiar, like the living room with the arrangement you’re used to.

It’s hard to see what’s possible when you limit yourself to what’s familiar.

Another example: the team meeting we have on Fridays. This is a meeting I inherited when I joined the company. It includes product, design, engineering, and QA. More team members have joined over time. It’s a meeting to update the team on what you worked on during the week. The format is “popcorn updates,” where you share what you worked on and then pick the next person to share after you. It’s simple. And it works. It’s familiar. Everyone shows up and knows what to do. It’s comfortable and safe like we humans enjoy.

But I changed it.

I despise status meetings because the system is responsible for holding the status, not forced, synchronous updates where only the person delivering the status pays attention.

The intention behind the meeting isn’t just to share what you worked on. It’s to share work, context, and capture feedback. It’s to celebrate the work as a team, to build collective ownership over the mission of progress. And when you know the intention, you can look at the conditions to determine whether they are supporting the goal, or holding it back.

Intentions shape conditions

When we discussed moving, we started assessing everything we own to determine what we want to bring with us: the sofas, beds, TVs, desks, and other furniture and items. The outcome became trying to find a place for what we have, instead of trying to make space for the new life we want.

But it’s going to be different. It’s a new way of living—one aligned with our theme of simplification. We want less stuff so we can make space for more experiences. The intention is to live a simpler life with fewer things to carry with us so we can focus on the things that really matter.

The intention shapes the conditions. It doesn’t prescribe outcomes. Start with the experience you want to cultivate, and then create the conditions that make it possible.

Now let’s return to the Friday meeting. If the intention is to celebrate the work and share in collective ownership of the mission, what conditions can make that possible?

As with anything, there are hundreds of ways to solve a problem. And let’s be clear: this isn’t even a problem per se. The meeting works, but it has room for improvement. For example, there is an awkward pause before the first person volunteers to go, like in school when the teacher asks for a volunteer to go first. And when someone is done with their updates, they often forget who went already, generating more awkward handoffs. The meeting should feel relaxed and fun, but it didn’t.

That’s where it starts. You latch onto the tension points in a system. That’s where you start to experiment. Find ways to intervene so you can learn more about the emergent properties of the system. You can’t control them, but you can see them and begin to surround them with conditions where they are more likely to emerge.

So I redesigned the meeting in place.

I created a new app called “Popcorn” that randomly selects someone, and then gives them prompts on what to share. It even pulls in data from Linear, GitHub, and Figma so it’s easy for each team member to recall their work for the week. And when they’re done, they say “pop it” and I click the button to randomly pick the next person. No awkward pauses in a meeting whose intention is celebration and positivity. It includes fun features like shout-outs and a random speed-round question, like “Are you a morning person or a night owl?” When everyone has gone, I wrap up the meeting with what I worked on, and I include context I think the whole team should know about. Sometimes it’s signals in the metrics, customer feedback, process updates, strategy changes, or casting vision. I let the mood of the day and week decide.

Everyone loves the new format. Each person shares more, the vibe feels better, and the meeting represents the intention it’s designed to serve, not an outcome it’s beholden to.

That’s why intentions matter. They become a North Star to follow. But what really matters is how you adapt to what you learn when you meet reality. You have to see, sense, and shape the experience in real-time. That’s the key.

Experience drives understanding

Reality defines what really works. You can plan and assume and simulate all you want, but you never really know how something truly works until you’ve experienced it. Our brains are powerful enough to simulate and predict, but they can also deceive us into believing we know the outcome before we experience it.

We don’t know what living in a Brooklyn apartment will be like until we do it. That means we can’t imagine the environment with enough certainty to furnish it before we’ve lived in it. Lived experience is the performance metric that really counts. Our plan is to live in the space and use the data to inform our decisions about what we need.

Intention shapes the conditions, and the experience fortifies our understanding of what really works and what doesn’t. The intention is the compass. The experience is the guide.

Every variable in a system can change the larger system. If lived experience reveals that the original intention needs to change, then you change it. If the intention is the direction, then you better make sure it’s right, like you would navigating uncertain terrain.

The first meeting with the new format wasn’t the final state. By no means. I kept iterating for the next 3-4 meetings, learning from observation and feedback. As facilitator, I watched as the team shared their updates and engaged with one another. Then I made small tweaks to fine-tune. It’s a continuous process that requires constant cultivation.

To make it easier for each person to see the key areas they worked on, I built a “spotlight” feature. When it’s their turn, I click a button and Claude compiles and groups all their work into 3-5 nodes that circle their avatar. Then they can talk through the key areas of work without forgetting what happened this week, an affliction we all face unless we diligently write things down. It reduced friction in a meaningful way, because you don’t want someone to miss sharing important context.

It’s easy to roll out a new process or system and forget that the most important part of the process is to observe and iterate. No matter how good you are, it won’t be right on the first try. And even if it is, it’s going to change. This meeting won’t be the same in six months. The apartment won’t stay constant while we live there. The software you build should be in a constant state of flux. That’s the work. You set a clear intention, and then you learn and adapt through lived experience. See, sense, shape.

The Practice

Much of what I talk about is how to feel, sense, and strategically intervene to make something better, to solve a problem. I say that because it’s the most effective way to influence complex systems. If you operate under the illusion of control, you fool yourself into believing you can just point at a process document or create a checklist to change behaviors. Complex systems (software, teams, companies, nature, governments, financial systems, the human body) require a different way of working. I’ve always seen myself as designing systems to orchestrate intelligence, so a world with AI is just another way to leverage intelligence to make an impact.

When I talk to engineers who are concerned about AI, I tell them to learn about complex systems. It teaches you more about how the world works than almost anything else.

Transferable knowledge.

Building intentional environments takes a simple practice you can use in any system.

See the intention. Begin with the experience you want to cultivate, and question the current arrangement to make sure it’s meeting the needs of the intention. The intention of our move is to create a space with fewer items so we have more room to live. The intention of the team meeting is to share and celebrate the work we’re doing as a collective team.

Sense the experience. Don’t live in the simulation. Create movement and pay special attention. Let the lived experience reveal tensions, behaviors, relationships. We won’t know until we’re living in a new space what that will look like. I didn’t know how the changes would affect the meeting until I ran it a few times and observed. You won’t know how people will use your software until they do. Sense what matters through experience. If you want to improve your judgement, you need more repetitions. You’ll find the line where you’ve seen enough to make a change.

Shape through intervention. Look at what conditions you can change. The question I always ask myself is what’s the smallest change that would teach me the most? It seems simple, but it shows you how the system works, and which parts require intervention. Whether the intervention works or not doesn’t matter, because it teaches you either way. Living in the space and experimenting with furniture arrangements and building software to create a shared mental model with your team are simple examples of this in action. An intervention can produce learning or improve the environment—or both. Distinguishing the difference is built through experience.

Your Turn

Now it’s your turn. Look at your environment to see the components, relationships, and principles governing behavior. Then you can understand the shape of the environment, built around a clear intention.

See the intention.

Sense the experience.

Shape through intervention.

Build intentional environments.

Enjoying this issue? Sign up to get weekly insights in your inbox:

Full search