Last year, our team came back from a retreat in Istanbul. The energy was great — we'd spent real time together, planned ahead, reconnected as people. For a fully remote team spread across multiple countries and time zones, those few days in the same city felt rare and important.
But retreats have a way of making everything feel fine. You're in the same room, you're laughing over Turkish breakfast, you're aligned. It's easy to fly home and assume that good energy means everything is working.
We didn't want to assume. So we ran an Org360 employee engagement survey on ourselves.
At a glance
- Team: Nonprofit Builder, a fully remote team spread across several countries and time zones
- Survey: an Org360 employee engagement survey, run after our team retreat in Istanbul
- Top finding: too many meetings. We met every day, and it was eating into deep-work time.
- Change made: 5 meetings a week became 3 (Monday check-in, Wednesday strategy, optional Friday wrap-up), all under an hour
- A year later: the 3-meeting structure is still in place
Practicing what we build
I should be honest about what this felt like. When our leadership asked me to help facilitate an Org360 survey for our own team after the Istanbul retreat, I said yes. But helping surface honest feedback from people you work with every day — that's a different kind of exercise.
What the data told us
The results came back and most things looked healthy. People felt connected to the mission, supported by each other, clear on their roles. That was reassuring.
But one theme came through loud and clear, across multiple questions and in the open-ended responses: people were unhappy with meetings. Specifically, the volume. We had been meeting every single day. It had started with good intentions — we're remote, we're geographically dispersed, we wanted to stay connected. But what was meant to create connection had become a drain. People felt like they couldn't get deep work done. The meetings were eating into their actual working hours. Some days the meeting was the work, and the real work got pushed to evenings. Some meetings were still useful. Others felt repetitive, and strategic discussions kept getting lost in operational updates.
This wasn't one person's opinion. It was the team telling us, clearly: this rhythm isn't working.
When the meeting feedback started showing up in the data, it wasn't a surprise to me. I felt it too. But seeing it reflected back from the whole team made it real — and made it something leadership couldn't set aside.
What we did about it
This is the part that matters. Not the survey. Not the data. What you do next.
Leadership sat with the feedback and asked a simple question: what do meetings actually need to accomplish for a remote, dispersed team? We came up with three things — connection, coordination, and strategic alignment. Then we designed a weekly structure around those three purposes and nothing more.
Monday — 40 minutes. Our start-of-week check-in. How was the weekend? How are you doing? What are you working on this week? It's warm and human first, then practical. For a remote team, Monday morning is the moment where you remember you're not working alone.
Wednesday — 1 hour. Our strategic meeting. Fundraising, communications, program design, partnerships — whatever needs collective thinking. This is the meeting where we actually make decisions, not just share updates. Because it only happens once a week, people come prepared and the conversations are sharper.
Friday — 25 minutes. Short and light. What did you get done? Anything you're proud of? Part-time team members join if they want but it's optional. This one exists purely for morale — ending the week feeling like a team, not just a group of people who happen to share a Slack workspace.
Three meetings, all under an hour. Down from five.
What changed
The difference was almost immediate. People had actual blocks of uninterrupted time on Tuesdays and Thursdays. The quality of work improved because people could think. The quality of meetings improved because each one had a clear purpose and people showed up differently.
But the thing that surprised me most: team morale didn't drop from fewer meetings. It went up. People felt heard. Not because we ran a survey — because we ran a survey and then visibly changed something within weeks.
That was a year ago. The three-meeting structure is still in place. It stuck because it works, and it works because it came from the team, not from leadership guessing what the team needed.
What else the survey surfaced
Meetings were the loudest theme, but the survey opened other conversations too. Questions about how we use our platforms and how our leave policy works came up on their own.
Some of that feedback confirmed that what we had was already working. Some of it showed us where people had understood a policy differently, so we cleared it up and agreed on shared expectations.
The pattern was the same each time: ask, listen, act, and then check back in to see if the change worked.
Why I'm sharing this now
Because a year later, the impact is clearer than it was at the time. The meeting restructure was a small change. Nobody was miserable before. Nobody was about to quit. We just had too many meetings and people were too polite to keep bringing it up in the meetings themselves — which, if you think about it, is perfectly ironic.
A well-designed survey caught what daily conversation didn't. And acting on it quickly, visibly, and without defensiveness turned a small frustration into a trust-building moment that's lasted well beyond that post-Istanbul glow.
That's the whole model. Ask. Listen. Act. Say what you did. We build Org360 for exactly this.
We asked. We heard "too many meetings." Now we have three good ones instead of five mediocre ones. And the team knows that when we ask next time, we mean it.
Muqaddus Kundi, Client Success Manager, Org360