Kitchen's Ink

Every association has one – That list of things that are clearly important, clearly understood to be important, and consistently not done.

The brand guide that’s been needed for three years. The crisis communications protocol that doesn’t exist yet. The onboarding documentation that would make every staff transition faster and less destabilizing. The competitive intelligence process that would inform every strategic planning conversation but never gets built because there’s always something more urgent on this week’s list.

The organization that doesn’t have time to build the onboarding documentation is the same organization that will spend six months recovering from the next staff departure, because the institutional knowledge walked out the door.

These items don’t make it off the someday list because they share a common characteristic: they’re important but not urgent, which means in any given week they lose to things that are both. And because they lose consistently, the cost of not having them never shows up as a line item — it shows up as organizational low-level friction, poor decisions, slow recovery from disruption, and a kind of institutional fragility that’s hard to name until it breaks something.

What the Someday List Is Really Made Of

The someday list isn’t made of low-priority items. It’s made of high-priority items that lost the battle for capacity.

Most small associations are operating close to their practical capacity most of the time. Staff are fully occupied with the recurring operational work that keeps the organization running: the newsletter, the conference, the membership renewals, the board meeting preparation, the certification applications, the accreditation reviews. That work is genuinely necessary and genuinely consuming. There is rarely leftover capacity for the infrastructure work that would make all of it easier.

This creates a structural trap. The organization that doesn’t have time to build the onboarding documentation is the same organization that will spend six months recovering from the next staff departure, because the institutional knowledge walked out the door. The organization that doesn’t have time to build the brand guide is the same one that will spend three years managing vendor inconsistency and internal drift. The organization that doesn’t have time to build the crisis communications protocol is the same one that will navigate its next reputational challenge improvising in real time.

The someday list is where organizations go to stagnate — not dramatically, not visibly, but steadily and compoundingly.

What It Takes to Get Items Off It

Getting items off the someday list requires either additional capacity or a reorganization of what consumes existing capacity. Usually both.

The additional capacity question is relatively straightforward: it’s a resource argument to leadership. Here are the infrastructure items that we haven’t been able to build. Here is what they cost us in their absence. Here is what it would take to build them and how long the investment would pay for itself. That argument, made with specificity and organizational data, is a legitimate budget conversation.

The reorganization question is harder, because it requires honest accounting of how current capacity is being spent and what it would mean to redirect some of it. The marketing team that spends 60 percent of its time on production tasks can’t also build infrastructure — unless some of the production is automated, delegated, or eliminated. The executive director who spends half her time in reactive operational work can’t also do the strategic infrastructure development the organization needs — unless the operational load is restructured.

Neither of those conversations is comfortable. Both are necessary.

The Leadership Signal in How an Organization Treats Its Someday List

How an organization treats its someday list is a leadership signal.

Without fault, organizations where the someday list never shrinks are organizations where the urgency of the present consistently overwhelms the importance of the future — and where leadership hasn’t made the structural changes that would tip that balance. It happens a lot.

Organizations where the someday list gets worked are organizations where someone is responsible for it. Not responsible in the sense of “it’s on your list” but responsible in the sense of: someone’s job is to think about what the organization needs to build, to make the case for the resources to build it, and to actually build it rather than waiting for a distant week when there’s nothing more urgent.

We all know that week never comes. The infrastructure gets built when someone decides to build it despite the urgency of everything else. That decision is an executive decision, and it’s one of the more consequential ones an organizational leader makes.