It’s 10:45 on a Tuesday. You just wrapped a requirements session for your new AMS, and your head is swimming with membership types and renewal rules. In fifteen minutes, you have a call with your annual meeting venue. Three emails arrive: a board member’s “quick question,” a vendor asking for sign-off on a data mapping, and a member who can’t log in.
Sound familiar?
When I worked in association management, I supported several associations at the same time. Different industries, boards, politics, and deadlines. The hardest part wasn’t any single task. It was the constant context switching between them. Now I help associations through technology projects, and I see context switching’s impact on association staff as they navigate their day jobs and their tech project tasks.
What the Research Says About Context Switching
While most people have heard it takes people more than 20 minutes on average to return to their work when interrupted; they don’t fully grasp the costs. That time to get back on task when interrupted doesn’t mean 20 minutes of staring at a screen. People typically detour through two other tasks before returning to their original task. Meaning the path back to deep work runs through other work.
That finding stems from one of Professor Gloria Mark’s best-known field studies where her team shadowed 36 managers, analysts, developers, engineers and project leaders, timing their activities to the second. They grouped people’s tasks into “working spheres:” sets of activities tied together by a common goal, people, resources, and timeframe. Consequently, they found people switched between working spheres roughly every 10 and a half minutes. Her later research added another wrinkle: interrupted people often compensate by working faster, but they report more stress, frustration, and time pressure. Thus, the work gets done; however, the cost shows up in us.
Why Context Switching Hits Tech Projects Hard
Your tech project is a new working sphere. It has its own goals, people (vendors, consultants, an internal project team), tools, and deadlines. Moreover, it’s the cherry on top of everything else. Despite new demands on time, attention, and bandwidth; the organization’s mission-critical aspects (e.g., renewals, the annual meeting, member questions) must continue uninterrupted.
For a year or more, your membership director is also a requirements expert, a test-script writer, and a change champion. Your finance lead reconciles legacy data between month-end closes. Your executive director makes platform decisions between board calls.
That’s where implementations quietly go sideways. Not in a dramatic failure, but in small leaks: a test session where half the team is still thinking about a sponsor email, a decision deferred because nobody had the headspace, a vendor request that sat for a week. Each one is small. Together, they add up to missed defects, slipping timelines, and exhausted staff who associate the new system with burnout.
Five Practices to Maintain Focus and Momentum
These “simple” practices address challenges associated with context switching so you can decrease frustration, lessen the load, and manage both your day job and the tech project:
1. Build a 15-minute buffer. Don’t go straight from a vendor demo into a board call. Use the buffer to write down exactly where you stopped, take a few breaths, review what matters most in the next block, close the old tabs, and open the new ones. While it may appear like lost time, it’s insurance against the 20-minute detour.
2. Have an interruption plan ready. Something will blow up mid-project. However, before you drop everything, run a quick check. Is it truly urgent or does it just feel urgent? If it’s an actual emergency: deal with it. If it’s a routine issue dressed in urgency: write down where you stopped, set a time limit, try to delegate (see below), and inform affected parties about the delay. Then use your buffer to get back on track.
3. Tackle what matters, not what’s loudest. Each week, organize both project and non-project tasks into four boxes: immediate, schedule, delegate, eliminate. Tag each one by working sphere so you can see when the project is crowding out everything else, or the reverse. When in doubt, ask whether it will matter in six months.
4. Delegate tasks, not responsibility. Implementations depend on staff beyond the core team. For each handoff, set clear expectations, provide the resources and authority to act, agree on a timeline with success measures, and schedule a check-in. You stay accountable for the outcome. Your colleagues get to grow.
5. Close the week with a 15-minute review. On Friday, look back at what worked, what didn’t (no judgment, just data) and what to adjust. Check your project for red flags: anything more than a week behind, a decision stuck without an owner, or a vendor request aging out. Two or more red flags means you schedule time to address them next week, not someday.
Partner Up to Manage Context Switching
Personal systems help. But some context switching costs are built into the project itself, and those are a project management problem, not a willpower problem.
That’s a big part of what we do at Achurch, absorb switching costs so your team doesn’t have to:
- A predictable rhythm. Standing meetings on consistent days to protect staff’s focus time.
- Capacity planning. We plan testing and data validation around your association calendar and workloads.
- A filter on “urgent.” We triage vendor requests and questions, so you can focus on the decisions that truly need your attention.
- Project-level red flags. We track the slipping tasks, aging decisions, and open vendor items, so your Friday review can focus on your own work.
- Realistic project plans. A project plan only matters if staff can sustain it alongside their real jobs. Adoption starts with a pace your team can keep.
Switch on purpose
While you can’t avoid context switching during a tech project, you can mitigate the frustration, stress, and productivity drains that accompany it. You can switch on purpose: with a buffer, a plan for interruptions, a clear view of what matters, and a partner to help with the load.
If you’re heading into an AMS selection or implementation and wondering how your team will juggle it all, let’s talk.
